[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201012211310.oBLDAT2n021131@demeter1.kernel.org>
Date: Tue, 21 Dec 2010 13:10:29 GMT
From: bugzilla-daemon@...zilla.kernel.org
To: linux-ext4@...r.kernel.org
Subject: [Bug 25352] resizing ext4 will corrupt filesystem
https://bugzilla.kernel.org/show_bug.cgi?id=25352
--- Comment #6 from Lukas Czerner <lczerner@...hat.com> 2010-12-21 13:10:28 ---
On Mon, 20 Dec 2010, Ted Ts'o wrote:
> On Mon, Dec 20, 2010 at 08:56:46PM +0000, bugzilla-daemon@...zilla.kernel.org wrote:
> >
> > Using resize2fs on an ext4 will result in a corrupted filesystem. This is a
> > regression (obviously).
>
> Yes, this is a regression new to 2.6.37-rc1, which was introduced by
> commit a31437b85: ext4: use sb_issue_zeroout in setup_new_group_blocks.
>
> When we replaced the loop zero'ing the inode table blocks with
> sb_issue_zeroout, we accidentally also removed this little tidbit:
>
> - ext4_set_bit(bit, bh->b_data);
>
> ... which was responsible for setting the block allocation bitmap to
> reserve the block descriptor blocks and inode table blocks. Oops...
>
> I believe this patch should fix things.
>
> - Ted
>
>
>
Oops indeed. Ted, thanks for the patch, it seems to fix the problem
completely.
-Lukas
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists