file system (UFS2) consistancy after -current crash?
Aaron Wohl
freebsd at soith.com
Fri Oct 3 04:03:37 PDT 2003
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?
More information about the freebsd-current
mailing list