From: Eric Sandeen <sandeen@redhat.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: ext4 development <linux-ext4@vger.kernel.org>,
Leonardo Menezes Vaz <lvaz@redhat.com>
Subject: Re: [PATCH] resize2fs: move bitmaps if shrinking would orphan them
Date: Fri, 21 Jun 2013 09:13:17 -0500 [thread overview]
Message-ID: <51C45F7D.1030208@redhat.com> (raw)
In-Reply-To: <20130621024707.GC10730@thunk.org>
On 6/20/13 9:47 PM, Theodore Ts'o wrote:
> On Tue, Jun 18, 2013 at 08:37:05PM -0500, Eric Sandeen wrote:
>> It is possible to have a flex_bg filesystem with block groups
>> which have inode & block bitmaps at some point well past the
>> start of the group.
>>
>> If an offline shrink puts the new size somewhere between
>> the start of the block group and the (old) location of
>> the bitmaps, they can be left beyond the end of the filesystem,
>> i.e. result in fs corruption.
>>
>> Check each remaining block group for whether its bitmaps
>> are beyond the end of the new filesystem, and reallocate
>> them in a new location if needed.
>>
>> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
>
> Looks good, thanks for the patch. I made a few minor changes to fix
> up some extra whitespace and a minor optimization.
Great, thanks for the review.
> - Ted
>
> diff --git a/resize/resize2fs.c b/resize/resize2fs.c
> index 28131c2..204b10a 100644
> --- a/resize/resize2fs.c
> +++ b/resize/resize2fs.c
> @@ -889,7 +889,7 @@ static errcode_t blocks_to_move(ext2_resize_t rfs)
> * bitmaps which are beyond the end of the new filesystem.
> */
> new_size = ext2fs_blocks_count(fs->super);
> - if (ext2fs_blocks_count(fs->super) < ext2fs_blocks_count(old_fs->super)) {
> + if (new_size < ext2fs_blocks_count(old_fs->super)) {
thanks, I think I *meant* to do that
> for (g = 0; g < fs->group_desc_count; g++) {
> /*
> * ext2fs_allocate_group_table re-allocates bitmaps
> @@ -900,13 +900,13 @@ static errcode_t blocks_to_move(ext2_resize_t rfs)
> retval = ext2fs_allocate_group_table(fs, g, 0);
> if (retval)
> return retval;
> - }
^ whoops sorry
> + }
> if (ext2fs_inode_bitmap_loc(fs, g) >= new_size) {
> ext2fs_inode_bitmap_loc_set(fs, g, 0);
> retval = ext2fs_allocate_group_table(fs, g, 0);
> if (retval)
> return retval;
> - }
^ whoops sorry^2!
> + }
> }
> }
>
>
prev parent reply other threads:[~2013-06-21 14:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 0:24 offline shrink bug w/ testcase & image Eric Sandeen
2013-06-19 1:37 ` [PATCH] resize2fs: move bitmaps if shrinking would orphan them Eric Sandeen
2013-06-21 2:47 ` Theodore Ts'o
2013-06-21 14:13 ` 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=51C45F7D.1030208@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=lvaz@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).