From: Eric Sandeen <sandeen@redhat.com>
To: "Theodore Ts'o" <tytso@mit.edu>, Chris Hunter <chris.hunter@yale.edu>
Cc: linux-ext4@vger.kernel.org
Subject: Re: errors following ext3 to ext4 conversion
Date: Wed, 26 Aug 2015 22:43:45 -0500 [thread overview]
Message-ID: <55DE8771.9050109@redhat.com> (raw)
In-Reply-To: <20150827033949.GA12151@thunk.org>
On 8/26/15 10:39 PM, Theodore Ts'o wrote:
> Merely turning on the extents feature doesn't actually convert any
> files to use extents. So if e2fsck is showing errors like this:
>
>> e2fsck shows a variety of errors:
>> Pass 1: Checking inodes, blocks, and sizes
>> Inode 118843400, end of extent exceeds allowed value
>> (logical block 1409, physical block 3803034390, len 976)
>> Inode 118843400, end of extent exceeds allowed value
>> (logical block 2385, physical block 3803056554, len 4294966945)
>
> This suggests that the file system was likely corrupted before you
> tried converting the file system, since there should not have been any
> extent-mapped files in an ext3 file system.
Hm, do we not require a freshly-fsck'd fs (tm) prior to a conversion attempt,
like we do (I think) for resize?
That might be a good idea ...
-Eric
next prev parent reply other threads:[~2015-08-27 3:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 0:53 errors following ext3 to ext4 conversion Chris Hunter
2015-08-27 3:39 ` Theodore Ts'o
2015-08-27 3:43 ` Eric Sandeen [this message]
2015-08-27 4:15 ` Darrick J. Wong
2015-08-27 18:58 ` Theodore Ts'o
2015-08-27 19:28 ` Chris Hunter
2015-08-27 22:46 ` Theodore Ts'o
2015-08-28 16:23 ` Chris Hunter
2015-08-28 18:32 ` Theodore Ts'o
2015-08-27 21:34 ` Eric Sandeen
2015-08-28 16:09 ` Andreas Dilger
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=55DE8771.9050109@redhat.com \
--to=sandeen@redhat.com \
--cc=chris.hunter@yale.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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