Re: Bug: get EXT3-fs error Allocating block in system zone

Linus Torvalds schrieb:

But the disk errors are something else, doesn't ring a bell. Sounds like IO corruption on the group descriptor block or something like that. Might be worth testing to see if the problem goes away with less than 4GB of RAM..

Today, I tested with different amounts of RAM:

2 GB: everything works fine
4 GB: same issue as described before with allocating block in system zone

So what to do, in order to use more than 2 Gigs of RAM?

Marco

--
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: Bug: get EXT3-fs error Allocating block in system zone
    • From: Linus Torvalds <[email protected]>

• References:
  • Bug: get EXT3-fs error Allocating block in system zone
    • From: Marco Gatti <[email protected]>
  • Re: Bug: get EXT3-fs error Allocating block in system zone
    • From: Andrew Morton <[email protected]>
  • Re: Bug: get EXT3-fs error Allocating block in system zone
    • From: Linus Torvalds <[email protected]>

• Prev by Date: Re: scsi_wait_scan Kconfig option
• Next by Date: Re: [PATCH 1/6] indirect: use asmlinkage in i386 syscall table prototype
• Previous by thread: Re: Bug: get EXT3-fs error Allocating block in system zone
• Next by thread: Re: Bug: get EXT3-fs error Allocating block in system zone
• 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]