Date: Thu, 02 Aug 2001 11:21:21 -0500 From: Jim Bryant <kc5vdj@yahoo.com> To: Brian Somers <brian@Awfulhak.org> Cc: freebsd-current@FreeBSD.ORG, brian@freebsd-services.com Subject: Re: /home: mount pending error: blocks 14 files 3 Message-ID: <3B697E01.A2E1C397@yahoo.com> References: <200108020942.f729gT859796@hak.lan.Awfulhak.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 Manual FSCK(8)
NAME
fsck - file system consistency check and interactive repair
SYNOPSIS
fsck [-dvplfyn] [-B | -F] [-l maxparallel] [-t fstype]
[-T fstype:fsoptions] [special | node ...]
# Device Mountpoint FStype Options Dump Pass#
/dev/ad0s1b none swap sw 0 0
/dev/ad0s1a / ufs rw 1 1
/dev/ad0s1e /usr ufs rw 2 2
/dev/ad0s1f /var ufs rw 2 2
/dev/ad0s1g /home ufs rw 2 2
/dev/ad0s1h /tmp ufs 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 majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3B697E01.A2E1C397>