Thus spake Greg Lehey <[EMAIL PROTECTED]>: > I've been thinking about what happened, and I have a possibility: the > session before shutdown included a lot of writing to that file system, > and I did a shutdown -p. It's possible that the shutdown powered off > the system before the disk had flushed its cache. For the moment I'm > avoiding shutdown -p, but when I get home I'll try to provoke it > again.
Just a heads up: Soeren tells me he will commit a fix for this in his next ATA meta-commit. I have patches if wanted. I still can't figure out why the problem would trash your entire home directory, though. Even if the disk reordered writes and failed to write some sectors, directory entries that were not being actively modified shouldn't have become corrupted, as far as I know. (Maybe your disk does track-at-once writes and just happened to be flushing the last few sectors from its cache when the power was cut.) Perhaps someone could ask Kirk, although it may take an actual hosed filesystem to diagnose what happened. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
