Subject: Re: umount pending error
To: Joachim Kuebart <firstname.lastname@example.org>
From: Jim Bernard <email@example.com>
Date: 01/19/2002 10:57:35
On Sat, Jan 19, 2002 at 05:55:55PM +0100, Joachim Kuebart wrote:
> On Sat, Jan 19, 2002 at 08:16:11AM -0700, Jim Bernard wrote:
> > > Module Name: syssrc
> > > Committed By: fvdl
> > > Date: Sun Dec 30 15:46:55 UTC 2001
> > >
> > > Modified Files:
> > > syssrc/sys/ufs/ffs: ffs_vfsops.c
> > >
> > > Log Message:
> > > XXXX temporary measure: in the case of a softdep 'unmount pending error',
> > > do not mark the filesystem clean, as this will mean that one or more
> > > files were likely not completely removed (will show up as unconnected
> > > in fsck). Prevents filesystems from being marked clean while they're
> > > not until this problem has been figured out.
> Thanks a lot for the enlightening response! So, if I understand
> everything correctly, we can only "win" deleted files by this problem,
> not lose data. That feels good!
I don't really know how safe it is to live with this. All the files
I've examined in lost+found (only a fraction of the files that have been
reconnected), I could identify as files that had been deleted after builds.
It may be harmless in principle, but with thousands of files reconnected,
it becomes very difficult to distinguish reconnected deleted files from other
reconnected files that one might actually want to salvage. It's kind of like
living with a fire alarm that gives frequent false alarms but might signal a
real fire some day. So I've turned off softdeps for now.