David Schultz wrote: > 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.
Something similar happened to me in 4-STABLE several months ago. After a panic/crash (caused by an unstable USB audio driver) the automatic fsck failed. This happened twice; the second time my filesystem was totally messed up, and after fsck did its thing, several files were missing, including files in /usr/bin and /usr/sbin that had not been touched for many weeks (ie since the last installworld). The damage wasn't as extensive as Greg reports, and my home directory was spared, but I had to reinstall the base system to get things working smoothly again. I then turned off write caching on the IDE drive. Afterwards I had several such crashes (caused by the same driver) but never again had filesystem damage -- automatic fsck always worked. Nevertheless, as you say, it's strange files which had not been touched went missing. - Rahul To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
