On Thu, 2002-03-28 at 07:26, Guy Zelck wrote: ---snip---
> Interesting thread I thought to post my troubles with XFS to. > 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 esteem 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. Your results are interesting. But as in most other things it's important to have a reference point(s) for comparison. So I've got some questions: 1) What is the history of this hardware with relation to the previously installed scheme(s)? (what filesystem, Linux version, Win version) 2) Can you recall crashes under other circumstances that did not involve XFS in any way? (under this hardware config) Focus a little on hard drive history, as well as everything else. 3) What is the hardware's history with respect to diagnostics and tests? Has the memory been checked, dos diagnostics run, cpu checked.. If not, has the hardware got a respectable history of problem free operation under the previous OS? yay or nay...plus some details would be nice. > 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. Thanks and Regards, LX -- ��������������������������������������������������� Kernel 2.4.8-26mdk Mandrake Linux 8.1 Enlightenment 0.16.5 Evolution 1.02 Registered Linux User #268899 http://counter.li.org/ ��������������������������������������������������� _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
