public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Ted Ts'o <tytso@mit.edu>
To: Kazuya Mio <k-mio@sx.jp.nec.com>
Cc: ext4 <linux-ext4@vger.kernel.org>, Andreas Dilger <adilger@dilger.ca>
Subject: Re: [PATCH] e2fsck: Fix the wrong error detection for non-extent file
Date: Fri, 25 Nov 2011 21:31:24 -0500	[thread overview]
Message-ID: <20111126023124.GG5167@thunk.org> (raw)
In-Reply-To: <4ECF433C.4030604@sx.jp.nec.com>

On Fri, Nov 25, 2011 at 04:26:52PM +0900, Kazuya Mio wrote:
> When I create a non-extent file with the maximum size in ext4,
> e2fsck detects the following error:
> 
> Pass 1: Checking inodes, blocks, and sizes
> Inode 12, i_size is 4402345721856, should be 4402345721856. Fix?
> 
> As we know, e2fsck checks the size field of the inode in pass 1.
> However, in case of the ext4 with the feature of ^extent and huge_file,
> the maximum file size calculated in e2fsck is less than the real one.
> The patch fixes this problem.
> 
> Signed-off-by: Kazuya Mio <k-mio@sx.jp.nec.com>

Thanks, applied.

					- Ted

      reply	other threads:[~2011-11-26  2:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-25  7:26 [PATCH] e2fsck: Fix the wrong error detection for non-extent file Kazuya Mio
2011-11-26  2:31 ` Ted Ts'o [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=20111126023124.GG5167@thunk.org \
    --to=tytso@mit.edu \
    --cc=adilger@dilger.ca \
    --cc=k-mio@sx.jp.nec.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