linux-ext4 - Re: >16TB issues

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <150c16850908112235o10970aefqa16f2e08490d74e7@mail.gmail.com>
Date:	Tue, 11 Aug 2009 22:35:56 -0700
From:	Justin Maggard <jmaggard10@...il.com>
To:	Eric Sandeen <sandeen@...hat.com>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: >16TB issues

On Tue, Aug 11, 2009 at 9:21 PM, Eric Sandeen<sandeen@...hat.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
>
> This is roughly halfway through the filesystem; the journal is roughly
> in the middle of the filesystem; this is just over 2^31 blocks.  I bet
> there are still ints or longs in the userspace journal code.  I'll take
> a look.

Thanks for looking into this.  That log message is from when I was
running a 32-bit kernel, and I was apparently running into page cache
index limitations.  That error went away when I switched to a x86_64
kernel, but there are still other errors, as posted in one of my more
recent messages.

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