From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 25352] New: resizing ext4 will corrupt filesystem
Date: Mon, 20 Dec 2010 20:56:46 GMT [thread overview]
Message-ID: <bug-25352-13602@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=25352
Summary: resizing ext4 will corrupt filesystem
Product: File System
Version: 2.5
Kernel Version: 2.6.37-rc6
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: ext4
AssignedTo: fs_ext4@kernel-bugs.osdl.org
ReportedBy: kees@outflux.net
Regression: Yes
Using resize2fs on an ext4 will result in a corrupted filesystem. This is a
regression (obviously).
I would expect "fsck" to be clean on a recently resized filesystem, but it is
not:
Pass 5: Checking group summary information
Block bitmap differences: +(2621440--2621951) +(2654210--2655360)
+(2686976--2687487) +(2719744--2720255) +(2752512--2753023) +(2785280--2785791)
+(2818048--2818559) +(2850816--2851327) +(2883584--2884095) +(2916352--2916863)
+(2949120--2949631) +(2981888--2982399) +(3014656--3015167) +(3047424--3047935)
+(3080192--3080703) +(3112960--3113471) +(3145728--3146239) +(3178496--3179007)
+(3211264--3211775) +(3244032--3244543) +(3276800--3277311) +(3309568--3310079)
+(3342336--3342847) +(3375104--3375615) +(3407872--3408383) +(3440640--3441151)
+(3473408--3473919) +(3506176--3506687) +(3538944--3539455) +(3571712--3572223)
+(3604480--3604991) +(3637248--3637759) +(3670016--3670527) +(3702784--3703295)
+(3735552--3736063) +(3768320--3768831) +(3801088--3801599) +(3833856--3834367)
+(3866624--3867135) +(3899392--3899903)
etc
Reproducer script attached...
--
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 reply other threads:[~2010-12-20 20:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-20 20:56 bugzilla-daemon [this message]
2010-12-20 20:57 ` [Bug 25352] resizing ext4 will corrupt filesystem 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
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=bug-25352-13602@https.bugzilla.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).