| |||||||||||||
Only with a UPSOnly with a UPSPosted Sep 10, 2009 12:02 UTC (Thu) by xilun (subscriber, #50638)In reply to: Only with a UPS by ncm Parent article: POSIX v. reality: A position on O_PONIES
On the other hand, I've already written file system _highly_ intrusive software (in the form of specialized data reordering for HFS+ to be able to non destructively resize this fs) and tested it like 20 times on a non trivial fs content by unplugging the power cord of the computer in the middle of a resize operation, without experiencing a single data corruption (and the fs was also always at least recoverable quickly, but this wasn't even needed for read only operations to properly work).
I know that my statistic sample is to small (and worse, this was 6 years ago and I don't know if HD today are of the same quality), but anyway my first guess is that if the software is careful enough and the hardware of decent quality, the risk of massive data corruption due to a power failure is not too high (at least in absence of bad system design, like using RAID 5/6 in a power unsafe context)
(Log in to post comments)
Only with a UPS Posted Sep 10, 2009 14:13 UTC (Thu) by Cato (subscriber, #7643) [Link]
Since we are trading anecdotes, here's mine: http://lwn.net/Articles/350072/ - loss of thousands of files and LVM metadata corruption on a PC using ext3 on top of LVM.
This PC was frequently reset accidentally by the user pressing the power button, which caused at least one data loss event within one year. Since disabling write caching (and a couple of other changes) I've not had any data loss on this PC, but it's probably too early to be sure these changes have fixed the problem.
FWIW, I believe that at least on this setup, disabling write caching helps avoid ext3 and LVM corruption.
|
|||||||||||||