From: Eric Sandeen <sandeen@redhat.com>
To: Justin Maggard <jmaggard10@gmail.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: >2TB file issue with e2fsck
Date: Thu, 18 Mar 2010 16:57:23 -0500 [thread overview]
Message-ID: <4BA2A1C3.3080809@redhat.com> (raw)
In-Reply-To: <4BA29D56.4040607@redhat.com>
On 03/18/2010 04:38 PM, Eric Sandeen wrote:
> commmit 8a8f36540bbf5d4397cf476e216e9a720b5c1d8e added handling of
> the high i_blocks number, but did not enlarge the container it
> went into:
>
> - if ((pb.num_blocks != inode->i_blocks) ||
> + if ((pb.num_blocks != ext2fs_inode_i_blocks(fs, inode)) ||
>
> -Eric
>
Actually, no, that was too quick a skim through, sorry. :)
does your filesystem end up with the EXT4_FEATURE_RO_COMPAT_HUGE_FILE
feature set after your posix_fallocate test?
-Eric
prev parent reply other threads:[~2010-03-18 21:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-18 21:25 >2TB file issue with e2fsck Justin Maggard
2010-03-18 21:38 ` Eric Sandeen
2010-03-18 21:57 ` Eric Sandeen [this message]
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=4BA2A1C3.3080809@redhat.com \
--to=sandeen@redhat.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).