A reiserfs catastrophe

Chris Carlen

No guarantee. At least it depends upon the NIC you have - some (not the 8139 or similar brand) respond to pings "by hardware". You should have compiled the krenel with the sysrq option to get a clue if it's still alive. However, I guess the filesystem went r-o due to some error, and not even a log entry made it to disk from that time.

.... Could always be some bad karma. Or a slightly loose drive cable, *the* single-bit failure that happens once a hundred years. Btw., you are certain your ide cabling is ok when using 66-100-133Mhz and DMA (80pl, master(s) at cable end, slave at the 2-3 distance from mobo connector)?

Control everything you can, as suggested. I don't really trust the hd manufacturors test tools, they tend to say everything ok even when the drive is clicking, screeching like crazy and needs 10 retries to read or write a sector.

I use reiserfs and reiser4, at home with development kernels and I try too much, freezes are not uncommon here - but I never had such a big shuffling to lost+found, except once with a dying harddrive.

..... That's because SuSe uses reiser as default filesystem :)

Better use the journalling ext3, you'll get another level of protection. -- Longhorn error#4711: TCPA NGSCP VIOLATION: Microsoft optical mouse detected penguin patterns on mousepad. Parbreastion scan in progress ÊtoÊremoveÊoffendingÊincompatibleÊproducts.ÊÊReactivateÊMSÊsoftware. Linux woodwoody wood pecker.homnet.at 2.6.10-mm1LinuxCounter#295241,ICQ#4918962