Re: How do inodes work?
On Sun, May 16, 2004 at 02:25:37AM -0300, Marc G. Fournier wrote: so I take there are 'gaps' in the inode list? it doesn't re-use freed ones but keeps climbing until maybe it rolls around or something? A particular numbered inode always lives in the same place on the disk. When choosing what inode to use for a new file, the filesystem tries to pick a inode to put the file close to the directory it is being created in. This is the dirpref optimisation introduced a few years ago - previously inodes were chosen from a part of a disk that had the most nearby free space. David. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Odd firewire pcmcia card behavior...
Hello! Everyone! I have wrote about my PCMCIA firewire card problems some time ago, now I have cvsup'ed -CURRENT and it behaves completely different (but still is not working) Card is Domex Technology DMX-5140 Under 5.2.1-release it looked like: -- cut here -- cardbus0: Expecting link target, got 0x0 cardbus0: Resource not specified in CIS: id=10, size=800 cardbus0: Resource not specified in CIS: id=14, size=4000 cardbus0: Resource not specified in CIS: id=18, size=800 fwohci0: Texas Instruments TSB12LV23 mem 0x88008000- 0x880087ff,0x88004000-0x88007fff,0x88008800-0x88008fff irq 11 at device 0.0 on cardbus0 fwohci0: OHCI version ff.ff (ROM=1) fwohci0: invalid OHCI version fwohci0: FireWire init failed device_probe_and_attach: fwohci0 attach returned 5 cbb0: CardBus card activation failed -- cut here -- Now with 5.2-current (as of yesterday) it looks like: -- cut here -- cardbus0: Resource not specified in CIS: id=10, size=100 cardbus0: Resource not specified in CIS: id=14, size=100 cardbus0: Resource not specified in CIS: id=18, size=1000 cardbus0: display, VGA at device 0.0 (no driver attached) cbb0: CardBus card activation failed -- cut here -- if I'm in X session when card is inserted - X completely freezes. Any tips are much appreciated. Alex. p.s. please CC me, as I'm subscribed only to -questions. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
fsck: % done possible?
right now, my fsck is reporting: ZERO LENGTH DIR I=9222075 OWNER=root MODE=40755 SIZE=0 MTIME=May 10 17:33 2004 CLEAR? yes any way of findign out what the max I= will be, so that one can know how close to the end things are? Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fsck: % done possible?
In the last episode (May 16), Marc G. Fournier said: right now, my fsck is reporting: ZERO LENGTH DIR I=9222075 OWNER=root MODE=40755 SIZE=0 MTIME=May 10 17:33 2004 CLEAR? yes any way of findign out what the max I= will be, so that one can know how close to the end things are? Run dumpfs /mountpoint | head, and multiply ncg by ipg. That'll give you your total inode count. 9 million inodes seems awfully high, so it's got to be near the end. -- Dan Nelson [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fsck: % done possible?
On Sun, 16 May 2004, Dan Nelson wrote: In the last episode (May 16), Marc G. Fournier said: right now, my fsck is reporting: ZERO LENGTH DIR I=9222075 OWNER=root MODE=40755 SIZE=0 MTIME=May 10 17:33 2004 CLEAR? yes any way of findign out what the max I= will be, so that one can know how close to the end things are? Run dumpfs /mountpoint | head, and multiply ncg by ipg. That'll give you your total inode count. 9 million inodes seems awfully high, so it's got to be near the end. Actually, it hit 14million by the time the fsck finished ... Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fsck: % done possible?
how about just hitting ^T? On Sun, 16 May 2004, Marc G. Fournier wrote: right now, my fsck is reporting: ZERO LENGTH DIR I=9222075 OWNER=root MODE=40755 SIZE=0 MTIME=May 10 17:33 2004 CLEAR? yes any way of findign out what the max I= will be, so that one can know how close to the end things are? Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How do inodes work?
On 16 May, David Malone wrote: On Sun, May 16, 2004 at 02:25:37AM -0300, Marc G. Fournier wrote: so I take there are 'gaps' in the inode list? it doesn't re-use freed ones but keeps climbing until maybe it rolls around or something? A particular numbered inode always lives in the same place on the disk. When choosing what inode to use for a new file, the filesystem tries to pick a inode to put the file close to the directory it is being created in. This is the dirpref optimisation introduced a few years ago - previously inodes were chosen from a part of a disk that had the most nearby free space. The preferred location of inodes for regular files has always been in the same cylinder group as their parent directory. The dirpref optimization changed the policy for selecting the cylinder group when new directories are created. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fsck: % done possible?
Cause I never knew about that? :) I take it that that is the SIGINFO refer'd in: If fsck receives a SIGINFO (see the ``status'' argument for stty(1)) sig- nal, a line will be written to the standard output indicating the name of the device currently being checked, the current phase number and phase- specific progress information. Wish I had known that yesterday ... :( On Sun, 16 May 2004, Julian Elischer wrote: how about just hitting ^T? On Sun, 16 May 2004, Marc G. Fournier wrote: right now, my fsck is reporting: ZERO LENGTH DIR I=9222075 OWNER=root MODE=40755 SIZE=0 MTIME=May 10 17:33 2004 CLEAR? yes any way of findign out what the max I= will be, so that one can know how close to the end things are? Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED] Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Odd firewire pcmcia card behavior...
In message: [EMAIL PROTECTED] Schizik [EMAIL PROTECTED] writes: : cardbus0: Resource not specified in CIS: id=10, size=100 : cardbus0: Resource not specified in CIS: id=14, size=100 : cardbus0: Resource not specified in CIS: id=18, size=1000 : cardbus0: display, VGA at device 0.0 (no driver attached) : cbb0: CardBus card activation failed This is almost certainly the bus numbering problem I recently introduced. Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
