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 "unsubscrib
>
> 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 w
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.
C
On 02-Aug-01 Sheldon Hearn wrote:
>
>
> 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 file
> 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
>
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.
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'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 exper
