[Bug 528981] Re: Repetitive massive filesystem corruption

[Scott Testerman]

Thanks for your update, Stuart.  In trying to save log files when the
filesystem goes read-only, I've found it helpful to use either a USB key
or SD Card, which can be mounted even when the boot filesystem has gone
read-only.  In most cases when testing for this problem, I even mount an
SD Card as soon as my system boots so I can immediately capture the data
when the (inevitable) corruption happens.  You can then do something
like "dmesg > /dev/sdc1/dmesg.txt" to capture data about the event,
unmount the USB key, reboot and submit an update to this bug report.

You mentioned the RC; I'm guessing you're using kernel 2.6.32-21.  We've
been asked to also try using the "latest" upstream kernel.  I've already
tried the 2.6.33 series, which seems to solve the problem, but 2.6.34 is
also available.  Can you please help by getting an upstream kernel
(either 2.6.33.3-lucid or 2.6.34-rc5-lucid) from here:
http://kernel.ubuntu.com/~kernel-ppa/mainline .  Full instructions and
complete information about the process are at
https://wiki.ubuntu.com/KernelMainlineBuilds .

You have my personal thanks for continuing to help on this problem,
since this corruption problem is extremely frustrating!

-- 
Repetitive massive filesystem corruption
https://bugs.launchpad.net/bugs/528981
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to linux in ubuntu.