Re: /home: mount pending error: blocks 14 files 3
On Thu, 02 Aug 2001 10:42:29 +0100, Brian Somers wrote: If the error keeps turning up, I would guess that you have a 0 or empty fsck field in /etc/fstab and fsck -s therefore not fixing the problem. Nope. I have passno set for the filesystem on which I also see this. I used to have background fsck enabled, but I disabled it because of horrid unkillable fsck behaviour. Perhaps background fsck did something nasty to my filesystem that normal fsck isn't seeing? The soft-updates code stores two block counts and two file counts in the superblock so that df(1) can give sane answers for filesystems where soft-updates is enabled. fsck(8) fixes them up (and frees off the bitmaps etc) on my machines ok. Ciao, Sheldon. -- Brian [EMAIL PROTECTED][EMAIL PROTECTED] http://www.freebsd-services.com/brian@[uk.]FreeBSD.org Don't _EVER_ lose your sense of humour ! brian@[uk.]OpenBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: /home: mount pending error: blocks 14 files 3
Am I desynched? I went to single-user, tried to do a fsck -s, and found there is no such option. Also, the /etc/fstab didn't need changed at all. It is already proper. Needless to say, going to single-user, running just `fsck -y /dev/ad0s1g` fixed the problem, although it noted no errors. Could there be a bug in softupdates again? Below is a copy of the top of the manpage for the version of fsck on my -current, and a copy of my [unmodified since ???] /etc/fstab. --- FSCK(8) FreeBSD System Manager's ManualFSCK(8) NAME fsck - file system consistency check and interactive repair SYNOPSIS fsck [-dvplfyn] [-B | -F] [-l maxparallel] [-t fstype] [-T fstype:fsoptions] [special | node ...] # DeviceMountpoint FStype Options Dump Pass# /dev/ad0s1b noneswapsw 0 0 /dev/ad0s1a / ufs rw 1 1 /dev/ad0s1e /usrufs rw 2 2 /dev/ad0s1f /varufs rw 2 2 /dev/ad0s1g /home ufs rw 2 2 /dev/ad0s1h /tmpufs rw 2 2 /dev/ad1s1e /misc ufs rw 2 2 /dev/da0s1 /ms-dog msdosfs rw 0 0 /dev/cd0c /cdrom cd9660 ro,noauto 0 0 proc/proc procfs rw 0 0 proc/usr/compat/linux/proc linprocfs rw 0 0 #argus:/misc/argus.misc nfs rw 0 0 --- In case you feel like asking, my cheetah died, and all I could afford was a big IDE at the time, the 'cuda winblowz is on is still alive tho... One of these days... Brian Somers wrote: The error means that your machine crashed with soft-updates enabled, leaving 14 blocks and 3 files still allocated on disk (using up blocks inodes). If the error keeps turning up, I would guess that you have a 0 or empty fsck field in /etc/fstab and fsck -s therefore not fixing the problem. To fix it, correct fstab and run fsck -B. I've never had this before, and I have traced the message to ufs/ffs/ffs_vnops.c on line 634. I have recently noticed [since my last svsup] that this is happening on boot and shutdown [in which case, the messasge is also in the same file, but for umount conditions]. I am not a filesystem expert.. How concerned should I be? This is -current a week or two old [before all the lockup threads began]... jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: /home: mount pending error: blocks 14 files 3
On 02-Aug-01 Sheldon Hearn wrote: On Thu, 02 Aug 2001 09:33:41 MST, John Baldwin wrote: I get these messages when I reboot or crash before the background fsck finishes sometimes. Sometimes I get them when the filesystems are clean, too. They always happen when the previous boot did a background fsck, however. Then you're not seeing the whole problem. :-) As I said, I'm not using background fsck any more and have had several fsck runs report the filesystem as clean since I turned it off. Hmm, any more. I didn't see them at all until I started using background fsck. *shrug* I get them all the time though myself. I thought they were a feature of background fsck. Perhaps they aren't. :( Maybe fsck is failing to clean your filesystem or something ? A boot -s followed by a successful fsck should get rid of them. I was seeing them at Usenix and mentioned it to Kirk. He explained their nature -- ie, you've just got some blocks and inodes marked in use that shouldn't be. Or maybe these numbers are the only thing corrupt about your fs so they're not being re-written after fsck finishes ??? Ciao, Sheldon. -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc Power Users Use the Power to Serve! - http://www.FreeBSD.org/ -- Brian [EMAIL PROTECTED][EMAIL PROTECTED] http://www.freebsd-services.com/brian@[uk.]FreeBSD.org Don't _EVER_ lose your sense of humour ! brian@[uk.]OpenBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: /home: mount pending error: blocks 14 files 3
On Thu, 02 Aug 2001 11:21:21 EST, Jim Bryant wrote: Could there be a bug in softupdates again? In fsck, more likely. This is why background fsck is enabled by default, I guess -- to get the bugs shaken out. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
/home: mount pending error: blocks 14 files 3
I've never had this before, and I have traced the message to ufs/ffs/ffs_vnops.c on line 634. I have recently noticed [since my last svsup] that this is happening on boot and shutdown [in which case, the messasge is also in the same file, but for umount conditions]. I am not a filesystem expert.. How concerned should I be? This is -current a week or two old [before all the lockup threads began]... jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: /home: mount pending error: blocks 14 files 3 [correction]
Jim Bryant wrote: I've never had this before, and I have traced the message to ufs/ffs/ffs_vnops.c on line 634. I have recently noticed [since my last svsup] that this is happening on boot and shutdown [in which case, the messasge is also in the same file, but for umount conditions]. I am not a filesystem expert.. How concerned should I be? This is -current a week or two old [before all the lockup threads began]... correction: s/ffs_vnops.c/ffs_vfsops.c hun -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
