Re: [Resolved: bad RAM] Filesystem silent crash with EXT3

Stef Epardaud wrote:

I feel like a fool now. You're absolutely right, my RAM is corrupted.
Sorry for the trouble folks, I'm very happy to come to the conclusion I
can rely on EXT3. Now I have to start worrying about how to detect RAM
corruption before it screws up my data next time.

That is what memory with parity is for. Don't know if
that exists for laptops though.

Helge Hafting
-
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/

---

• References:
  • Filesystem silent crash with EXT3
    • From: Stef Epardaud <[email protected]>
  • Re: Filesystem silent crash with EXT3
    • From: Krzysztof Halasa <[email protected]>
  • [Resolved: bad RAM] Filesystem silent crash with EXT3
    • From: Stef Epardaud <[email protected]>

• Prev by Date: 2.6.22.6: kernel BUG at fs/locks.c:171
• Next by Date: Re: [PATCH] State limits to safety of _safe iterators
• Previous by thread: [Resolved: bad RAM] Filesystem silent crash with EXT3
• Next by thread: [-mm PATCH] Memory controller make charging gfp mask aware
• 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]