From: Andreas Dilger <adilger@sun.com>
To: Justin Maggard <jmaggard10@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: >16TB issues
Date: Tue, 21 Jul 2009 13:21:23 -0600 [thread overview]
Message-ID: <20090721192123.GK4231@webber.adilger.int> (raw)
In-Reply-To: <150c16850907211152y3136aadx6ce42a8535a6ed61@mail.gmail.com>
On Jul 21, 2009 11:52 -0700, Justin Maggard wrote:
> No, no error messages from the kernel. But your llverdev utility
> ended up showing problems on the device. After asking around on the
> MD mailing list, that was apparently because of the page cache index
> limit (at the time I was using a 32-bit kernel).
>
> Switching to a 64-bit kernel allowed me to pass the llverdev test and
> get much further with a very large filesystem, but I'm running into
> other issues now. I wrote up a very simple script to write 2TB files
> onto the filesystem until the device fills up. It was able to write
> ~16TB, but after that it ran into some problems. My kernel log now
> has lots of messages like these:
There is a matching "llverfs" tool that does essentially this, with
data verification also.
> EXT4-fs error (device md2): ext4_mb_generate_buddy: EXT4-fs: group
> 163548: 32744 blocks in bitmap, 32768 in gd
> - and -
> EXT4-fs error (device md2): ext4_mb_mark_diskspace_used: Allocating
> block 4294967391 in system zone of 131072 group
>
> I shouldn't need e2fsprogs to be compiled 64-bit as well, right?
> Currently I've got a 64-bit kernel with 32-bit userspace.
Yes, that is a potential problem.
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
next prev parent reply other threads:[~2009-07-21 19:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-02 22:23 >16TB issues Justin Maggard
2009-07-03 14:38 ` Andreas Dilger
2009-07-16 18:04 ` Justin Maggard
2009-07-16 18:59 ` Valerie Aurora
2009-07-21 16:10 ` Andreas Dilger
2009-07-21 18:52 ` Justin Maggard
2009-07-21 18:57 ` Eric Sandeen
2009-07-21 19:21 ` Andreas Dilger [this message]
2009-07-22 22:27 ` Justin Maggard
2009-07-27 22:03 ` Valerie Aurora
2009-07-30 22:23 ` Valerie Aurora
2009-08-01 1:24 ` Justin Maggard
2009-08-03 17:20 ` Valerie Aurora
2009-08-11 21:39 ` Valerie Aurora
2009-08-11 22:05 ` Theodore Tso
2009-08-12 1:25 ` Valerie Aurora
2009-08-12 2:04 ` Theodore Tso
2009-08-12 17:59 ` Valerie Aurora
2009-08-28 2:30 ` Justin Maggard
2009-08-28 12:40 ` Theodore Tso
2009-08-28 20:27 ` Justin Maggard
2009-08-12 4:21 ` Eric Sandeen
2009-08-12 5:35 ` Justin Maggard
2009-08-12 14:12 ` Eric Sandeen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090721192123.GK4231@webber.adilger.int \
--to=adilger@sun.com \
--cc=jmaggard10@gmail.com \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).