On Sun, Jul 15, 2007 at 11:40:01AM +0200, Erik Bertelsen wrote:
> 2007/7/15, David Laight <david@l8s.co.uk>:
> 
> >
> >However, since the fs code tries to allocate blocks in the same CG
> >as the inode, if there is a problem with big sector numbers it would tend
> >to affect big inode numbers.
> >The output of 'dumpfs -s /' might be informative (if terse).
> 
> fsize   2048    shift   11      mask    0xfffff800
> bpg     11733   fpg     93864   ipg     23168

ok, inode 500000 is in CG 500000/23168, which starts in
fragment 500000/23168*93864, or byte offset 500000/23168*93864*2048.
Which is 0xf747e91b.

So I guess there is an error reading beyond 4G, either for the inode itself,
or because the file would have blocks in the same area of the disk.

	David

-- 
David Laight: david@l8s.co.uk