file system (UFS2) consistancy after -current crash?

From: Aaron Wohl <freebsd_at_soith.com>
Date: Fri, 03 Oct 2003 05:03:34 -0600
After crashes recently ive been geting softupdate inconsistancies. 
Directories in which a file has recently been renamed have neither the
old file nor the new file.  fsck -y recovers the inode and drops it in
lost in found.

I was under the impression that atomic rename() synced all the way to the
disk before returning?

Does softupdate enabled/disable have any bearing on this?

The disks themselfs are a raid5 on an adaptec 5400s.  We have had some
problems recently with aac (the 5400s driver) related crashes we have
been working with Scott Long on.  I was wondering if maybe rename is only
syncing as far as the raid controller memory?
Received on Fri Oct 03 2003 - 02:03:37 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:24 UTC