From: Eric Sandeen <sandeen@redhat.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: more resize breakage
Date: Thu, 29 May 2014 00:29:35 -0500 [thread overview]
Message-ID: <5386C5BF.7080202@redhat.com> (raw)
In-Reply-To: <20140529052733.GD17413@birch.djwong.org>
On 5/29/14, 12:27 AM, Darrick J. Wong wrote:
> On Thu, May 29, 2014 at 12:22:37AM -0500, Eric Sandeen wrote:
>> After considering how many resize2fs corruptions we've had, I decided to try to write a resize fuzzer which picks random parameters and sizes, and sees what happens with online & offline grow & offline shrink. When I get it cleaner, I'll send it out to play with.
>>
>> But it is indeed finding resize issues; for example, with e2fsprogs git master & v3.15-rc3,
<snip>
>> Sad face. :(
>
> D'oh!
>
> /me wonders, is offline grow any better?
Yes, offline passed.
> Also I "extended" fsfuzz to corrupt only metadata blocks and made the
> kernel+e2fsck chew through all that crap. The kernel survived, but e2fsck
> seemed to die either failing to allocate blocks to resurrect the journal (bad
> bbitmap) or because of that thing where calling block_iterate on an inline data
> file makes e2fsck abort.
>
> So, uh, ... long live the patchbomb? :(
yeah. Maybe I (you?) should try my testcase w/ your latest patchbomb. ;)
-Eric
next prev parent reply other threads:[~2014-05-29 5:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-29 5:22 more resize breakage Eric Sandeen
2014-05-29 5:27 ` Darrick J. Wong
2014-05-29 5:29 ` Eric Sandeen [this message]
2014-05-29 6:00 ` Darrick J. Wong
2014-05-29 6:09 ` 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=5386C5BF.7080202@redhat.com \
--to=sandeen@redhat.com \
--cc=darrick.wong@oracle.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.