> Are other people seeing 2.1.106 corrupting disks and memory on x86 ?
I have had a filesystem corrupted by 2.1.106. After trying out 2.1.106 I
rebooted to 2.0.34 (no fsck was done since all disk unmounted cleanly). I
tried to delete a large number of files which produced various ext2
errors. I don't think the filesystem is fixed even after several passes of
fsck.
This is an SMP kernel on UP Intel P133, IDE system.
-- Alistair Riddell - BOFH IT Support Department, George Watson's College, Edinburgh Tel: +44 131 447 7931 Ext 176 Fax: +44 131 452 8594 Microsoft - because god hates us
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu