On Tuesday 27 January 2009 14:05:20 Lars Marowsky-Bree wrote:
On 2009-01-26T15:54:00, Bob Williams <linux@barrowhillfarm.org.uk> wrote:
Well, I did a reboot this morning, and /dev/md0 failed the automatic fsck, forcing me to do a manual fsck. There was a whole heap of lost inodes, bad block mapping, multiple block mapping etc. So maybe the array instability was a software problem, not hardware related.
Anyway, all's well now, thanks.
I doubt that; the md code is very stable, as are the filesystems. I'd guess your hardware has some serious issues ... But best of luck.
Regards, Lars
You may well be right, given that you've a lot more knowledge about linux systems than I have. I have set up smartctl to test both drives every night, mdm to send me an e-mail if the array degrades, a full backup to another drive every night, so I'll just sit back and wait for more information from my system. I may well be back for more advice, later... Bob -- Registered Linux User #463880 FSFE Member #1300 GPG-FP: A6C1 457C 6DBA B13E 5524 F703 D12A FB79 926B 994E openSUSE 11.1, Kernel 2.6.27.7-9-default, KDE 3.5.10 Intel Core2 Quad Q9400 2.66GHz, 4GB DDR RAM, nVidia GeForce 9200GS -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org