From: Theodore Ts'o <tytso@mit.edu>
To: Jon Severinsson <jon@severinsson.net>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Resize2fs corrupts ext4 fs with bigalloc [Was: Re: Release candidate for e2fsprogs 1.42.7]
Date: Sun, 20 Jan 2013 00:27:44 -0500 [thread overview]
Message-ID: <20130120052744.GC9874@thunk.org> (raw)
In-Reply-To: <201301182047.53924.jon@severinsson.net>
On Fri, Jan 18, 2013 at 08:47:16PM +0100, Jon Severinsson wrote:
>
> In both versions resize2fs corrupts a clean ext4 fs if bigalloc is
> enabled.
>
Thanks for the bug report. From what I can tell, resize2fs never
worked correctly on bigalloc file systems. The following patches seem
to fix it, but we need to do more careful testing before I'd trust
resize2fs to resize bigalloc file systems containing production data.
- Ted
next prev parent reply other threads:[~2013-01-20 5:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-18 19:47 Resize2fs corrupts ext4 fs with bigalloc [Was: Re: Release candidate for e2fsprogs 1.42.7] Jon Severinsson
2013-01-20 5:27 ` Theodore Ts'o [this message]
2013-01-20 5:35 ` [PATCH 1/3] libext2fs: teach the ext2fs_*_block_bitmap_range2() about clusters Theodore Ts'o
2013-01-20 5:35 ` [PATCH 2/3] resize2fs: correctly account for clusters when calculating summary stats Theodore Ts'o
2013-01-20 5:35 ` [PATCH 3/3] resize2fs: move a cluster at a time with bigalloc file systems Theodore Ts'o
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=20130120052744.GC9874@thunk.org \
--to=tytso@mit.edu \
--cc=jon@severinsson.net \
--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).