Messages in this thread | | | Date | Mon, 08 Jan 2007 15:00:26 -0800 | From | Ben Greear <> | Subject | Re: ext3 file system went read-only in 2.6.18.2 (plus hacks) |
| |
Theodore Tso wrote: > Well, the filesystem obviously got corrupted. The only question is > *why* it got corrupted. It could be memory corruption, or a bug in > your propietary kernel patches, or some kind of hardware issue with > the CF device. There's really no way to say for sure.
Ok. I certainly can't guarantee my code is not somehow causing the problem.
> Were there any error messages in the system log from the device > driver?
I looked and did not see anything obvious. The file system was not overly full (49MB free, not counting the reserved space for the root user.)
I appreciate you looking at the report. If we see it again or manage to find some way to reliably reproduce this on other hardware, I will of course let you know.
Thanks, Ben
-- Ben Greear <greearb@candelatech.com> Candela Technologies Inc http://www.candelatech.com
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |