Re: >16TB issues

[Andreas Dilger <adilger@sun.com>]

On Jul 16, 2009  11:04 -0700, Justin Maggard wrote:
> On Fri, Jul 3, 2009 at 7:38 AM, Andreas Dilger<adilger@sun.com> wrote:
> >> -  Immediately running e2fsck on the volume before ever mounting it
> >> will not complete, and results in the following:
> >> # e2fsck -n /dev/md2
> >> e2fsck 1.41.7 (29-June-2009)
> >> Error reading block 2435874816 (Attempt to read block from filesystem
> >> resulted in short read).  Ignore error? no
> 
> Error reading block 576192512 (Attempt to read block from filesystem
> resulted in short read) while reading inode and block bitmaps.  Ignore
> error? no
> 
> e2fsck: Can't read an block bitmap while retrying to read bitmaps for /dev/md2
> e2fsck: aborted

What is very strange here is that the block numbers being reported as
having read errors are not even beyond the 16TB limit.  Assuming 4kB blocks:

576192512 * 4kB = 2304770048kB = 2198GB

Are there error messages in syslog/dmesg when this happens?

Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.

--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html