On Tue, Jul 18, 2006 at 12:01:31PM +0100, Jo Shields wrote:
Mickael Marchand wrote:
check your memory (yes it's going to be long, but that's almost always
the reason of reiserfs failures)
I am stressing hard reiserfs on various amd64/em64t boxes, no pbl so
far.
every box I found corrupting filesystems were having :
1 - bad hard drives that a low scan confirmed
or 2 - bad memory that a real long memtest could detect
Cheers,
Mik
I'll add to this - I've seen corruption with all filesystems on my
office desktop (which has screwed memory, but they refuse to fix it).
EXT3 gave up on journalling & just started writing junk, costing me my
/home.
Ext2/ext3 complains about errors, but you normally don't see that
because it's hidden in the system log files. It's a good thing to mount
partitions with the "errors=remount-ro" option. If anything goes wrong,
the kernel will mount the partition read-only. Reboot+fsck will save
your data.
Reiser is lasting up better, but reiserfsck segfaults when it
sees /home
That means that the filesystem has errors. Reiserfsck is able to detect
them, but because nobody has seen those errors before it will segfault
on them. That also means that the reiserfs filesystem driver in the
kernel will happily screw the filesystem further up without notice.
Back up your data *NOW* before it's too late.