From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 25352] resizing ext4 will corrupt filesystem
Date: Tue, 21 Dec 2010 13:10:29 GMT [thread overview]
Message-ID: <201012211310.oBLDAT2n021131@demeter1.kernel.org> (raw)
In-Reply-To: <bug-25352-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=25352
--- Comment #6 from Lukas Czerner <lczerner@redhat.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@bugzilla.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.
next prev parent reply other threads:[~2010-12-21 13:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-20 20:56 [Bug 25352] New: resizing ext4 will corrupt filesystem bugzilla-daemon
2010-12-20 20:57 ` [Bug 25352] " bugzilla-daemon
2010-12-21 3:32 ` [Bug 25352] New: " Ted Ts'o
2010-12-21 12:28 ` Lukas Czerner
2010-12-21 3:33 ` [Bug 25352] " bugzilla-daemon
2010-12-21 4:05 ` bugzilla-daemon
2010-12-21 4:26 ` bugzilla-daemon
2010-12-21 12:31 ` bugzilla-daemon
2010-12-21 13:10 ` bugzilla-daemon [this message]
2010-12-21 14:19 ` bugzilla-daemon
2010-12-21 18:03 ` bugzilla-daemon
2010-12-21 19:19 ` bugzilla-daemon
2010-12-21 22:32 ` bugzilla-daemon
2010-12-24 13:38 ` bugzilla-daemon
2010-12-24 13:40 ` bugzilla-daemon
2010-12-30 13:47 ` bugzilla-daemon
2010-12-30 14:12 ` bugzilla-daemon
2011-03-30 21:59 ` bugzilla-daemon
2011-03-31 16:26 ` bugzilla-daemon
2011-03-31 16:43 ` bugzilla-daemon
2011-03-31 19:24 ` bugzilla-daemon
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=201012211310.oBLDAT2n021131@demeter1.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--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).