On Thu, 2010-01-07 at 10:44 +0100, Andi Kleen wrote: > Tim Nufire <[email protected]> writes: > > > Andi, > > > >> That's a inconsistency in a block bmap, in particular a higher level > >> points to a block > >> that doesn't exist. > > > > Any idea why I would be hitting this consistently? Is it related to my > > volume size? Are there any parameters in JFS I can tune? > > My (uneducated) guess would be that it's some corruption (e.g. bitflip) that > fsck is unable > to fix.
I'm sorry I haven't had time to look into this, but I'm guessing it's a software bug. jfs_fsck rebuilds the block map, so any corruption would most likely be a result of a bug in the rebuild code. We didn't have volumes this big back when this code was written. I'll try to dig into this a little later. Shaggy > > -Andi -- David Kleikamp IBM Linux Technology Center ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Jfs-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jfs-discussion
