Re: kern/38717: sysinst shouldn't create LFS file systems

[Alan Barrett <apb%cequrux.com@localhost>]

The following reply was made to PR kern/38717; it has been noted by GNATS.

From: Alan Barrett <apb%cequrux.com@localhost>
To: gnats-bugs%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost
Cc: 
Subject: Re: kern/38717: sysinst shouldn't create LFS file systems
Date: Mon, 2 Jun 2008 08:53:10 +0100

 On Mon, 02 Jun 2008, David Holland wrote:
 > On Mon, Jun 02, 2008 at 12:24:27AM +0100, Alan Barrett wrote:
 >  > Twice recently I have noticed files that ended
 >  > up with random binary content (of exactly the same size as the original
 >  > file) after a crash.
 > 
 > That's expected behavior in ffs-without-softdep.
 
 Maybe.  I had the impression that, after a crash, files would usually be
 missing, or moved to lost+found, or still containing old content (or a
 mixture of old and new content).
 
 >  > ffs with -o async [...]
 > ... cannot reasonably be expected to work.
 
 If what you mean is "there are known bugs in this area", OK; but if you
 mean "crashing is not a bug" then I disagree.  I expect the file system
 to be left in a bad state if the machine crashes for some reason (due to
 hardware failure or a kernel bug), but I do not expect the mere usage
 of ffs-async to cause the machine to crash.
 
 --apb (Alan Barrett)