Guy Zelck wrote: > Hi all, > > When I installed md8.1 on my home system I went from reiserfs, which > never gave me trouble, to using xfs which I knew from work having it > on our Silicon Graphics machine. I also read a lot about it and for > speed and features it seemed the best and having a high esteme for SGI > I did not hesitate. > > Nevertheless I've experienced about 4 times so far the following (I > have an IDE system disk 'quantum fireball' of 8GB): > Every time there's a power cut I find a lot of files corrupted. > Instead of their original contents they contain nothing but ^@ (viewed > with vim) characters. The files concerned are e.g. all the KDE config > files of apps that were open at the time of the power cut, but I once > had inittab & message affected too. You can imagine that KDE wouldn't > start after that in the 1st case and the whole system was fucked in > the 2nd. This for me is totally unacceptable and I don't dare to > imagine what this would mean for a company's production machine. > > My technical knowledge in this field is not sufficiant enough to > pinpoint what exactly is the cause: the version of xfs included in > 8.1, the way f.s. are checked (or not checked) on boot-up? I don't > know. I've read before that journaling file systems didn't need to be > fsck'ed but why do you find a fsck for reiser & xfs then? Mar 25 > All I see in the messages file is this : > 22:57:40 gz kernel: Start mounting filesystem: ide0(3,6) > Mar 25 22:57:40 gz kernel: XFS: WARNING: recovery required on readonly > filesystem. > Mar 25 22:57:40 gz kernel: XFS: write access will be enabled during > mount. > Mar 25 22:57:40 gz kernel: Starting XFS recovery on filesystem: > ide0(3,6) (dev: 3/6) > Mar 25 22:57:40 gz kernel: Ending XFS recovery on filesystem: > ide0(3,6) (dev: 3/6) > > I'd be glad to learn more around this from active users of xfs since I > sure would like to remedy this 'russion roulete' situation. > > See ya, > Guy. > > > >------------------------------------------------------------------------ > >Want to buy your Pack or Services from MandrakeSoft? >Go to http://www.mandrakestore.com > My poweroff tests (random pulling of plug) have never produced anything akin to this. Perhaps we need a little more detail on your system. Theoretically this is possible on any FS at all, If you have a powerdown with the processor running wild from low voltage, you could get random data strewn all over your system, including writes to disk that make no sense.
KDE is constantly updating disk files on the positions of open windows, so it is likely to be out of sync on a powerdown, but again I have not seen this on a similar rig. (I did see it for Reiser on 8.0 and again on 8.1 where reiserfsck --rebuild-tree would not work. fsck is still necessary. Journal playback is often enough for most journaling filewsystems, but the capability of any system to produce errors in boundary conditions naturally exceeds any programmer's capability to anticipate them, according to the Laws propounded by Murphy. All journaling filesystems we offer provide an fsck of some sort. Civileme Civileme
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
