Re: XFS crashed twice, once in 2.6.16.20, next in 2.6.17, reproducable

> fatal error -- can't read block 16777216 for directory inode 1507133580

This looks to be the same problem as http://oss.sgi.com/bugzilla/show_bug.cgi?id=631
Note that the block numbers are identical in both reports: 16777216 = 0x1000000.
A very suspicious block number, wouldn't you say?

Best wishes,

Duncan.
-
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:
  • XFS crashed twice, once in 2.6.16.20, next in 2.6.17, reproducable
    • From: "Avuton Olrich" <[email protected]>
  • Re: XFS crashed twice, once in 2.6.16.20, next in 2.6.17, reproducable
    • From: Nathan Scott <[email protected]>
  • Re: XFS crashed twice, once in 2.6.16.20, next in 2.6.17, reproducable
    • From: "Avuton Olrich" <[email protected]>

• Prev by Date: Re: [patch] increase spinlock-debug looping timeouts (write_lock and NMI)
• Next by Date: Re: [patch] do_no_pfn
• Previous by thread: Re: XFS crashed twice, once in 2.6.16.20, next in 2.6.17, reproducable
• Next by thread: Re: XFS crashed twice, once in 2.6.16.20, next in 2.6.17, reproducable
• 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]