On Mon, Nov 30, 2009 at 11:34:06PM -0800, James Phillips typed: > > > --- On Mon, 11/30/09, Bruce Cran <br...@cran.org.uk> wrote: > > > > > This is actually the way UFS/FFS works too: when my system > > was crashing > > fairly regularly I was a bit surprised to find empty files > > after > > editing them. > > > > Also, I just verified that saving a file, rebooting, > > editing it again > > (with ee(1)) and powering off the system does still result > > in a zero > > length file being on disk. > > > > Ok, good to know. > > I saw UFS corruption once with frequent restarts, but assumed that was > because the "delayed filesystem checking" never had a chance to run. > > Since I don't have a UPS I guess backups are doubly important.
Note that finding an empty file you had just been editing before a crash is NOT UFS corruption. It's data loss, probably caused by softupdates, which guarantees filesystem consistency in the case of a crash, but it can sometimes be up to a minute behind in actually writing the data blocks to the disk. Ruben _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
