Re: ext3 file system went read-only in 2.6.18.2 (plus hacks)

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.

Were there any error messages in the system log from the device
driver?

						- Ted
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: ext3 file system went read-only in 2.6.18.2 (plus hacks)
    • From: Ben Greear <[email protected]>

• References:
  • ext3 file system went read-only in 2.6.18.2 (plus hacks)
    • From: Ben Greear <[email protected]>
  • Re: ext3 file system went read-only in 2.6.18.2 (plus hacks)
    • From: Alan <[email protected]>
  • Re: ext3 file system went read-only in 2.6.18.2 (plus hacks)
    • From: Ben Greear <[email protected]>

• Prev by Date: [PATCH] x86_64 ioapic: check_timer_pin Don't add_pin_to_irq if it is already there.
• Next by Date: Re: [PATCH] Make BH_Unwritten a first class bufferhead flag
• Previous by thread: Re: ext3 file system went read-only in 2.6.18.2 (plus hacks)
• Next by thread: Re: ext3 file system went read-only in 2.6.18.2 (plus hacks)
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]