On Sat, Jan 19, 2002 at 08:16:11AM -0700, Jim Bernard wrote:
> > Also, when I reboot this machine, I'll find that /usr and /var were
> > not shutdown cleanly.  They'll require an fsck to bring the back into
> > a usable state.  And, it's not just that the clean bit was not set;
> > fsck will find and fix lots of problems.
> 
>   It's mentioned in the following commit message.  Evidently when softdeps
> are in use it's possible for files not to be fully deleted, such that when
> fsck is run after a reboot, it reconnects them.  The problem was present
> before Frank's change, but it might have gone undetected for some time,
> since the file systems would have been marked clean on shutdown, and fsck
> would not have been run automatically on reboot.
> 
> 
> > 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!

cu Jo