From: Shentino <shentino@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: rfc: fuzz testing by direct writes to device
Date: Sat, 1 Sep 2012 01:10:42 -0700 [thread overview]
Message-ID: <CAGDaZ_p2dXLr6rOZewXUEWYKV4b=dW9OZj4yXG4qPoUax2a8CA@mail.gmail.com> (raw)
In-Reply-To: <CAGDaZ_oFzakgBC+NzK4X3J9yL0Q5YfZVKk671QKN0xHAMgPN7g@mail.gmail.com>
Also, since the problem prevented me from syncing my other filesystmes
I couldn't capture the debug info.
It vanished during the cold boot still sitting in dirty page cache.
On Fri, Aug 31, 2012 at 11:44 PM, Shentino <shentino@gmail.com> wrote:
> How effective would it be to directly write to the underlying device
> and then running tests to see if the corruption is properly detected?
>
> I just ran a fuzz test by syncing, and then manually corrupting a file
> with the help of a surgical sed (yes, the before and after patterns
> had fixed equal lengths). First I got an I/O error (expected), then I
> ran scrub and got more problems (not ok), the system froze (not good),
> a reboot failed to mount the system again (worse), and then the fsck
> program dumped core.
next prev parent reply other threads:[~2012-09-01 8:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-01 6:44 rfc: fuzz testing by direct writes to device Shentino
2012-09-01 8:10 ` Shentino [this message]
2012-09-01 15:41 ` Michael
2012-09-01 17:23 ` Shentino
2012-09-01 20:59 ` cwillu
2012-09-01 22:31 ` Shentino
2012-09-01 23:49 ` Michael
2012-09-02 1:03 ` Shentino
2012-09-02 5:44 ` David Sterba
2012-09-02 11:43 ` Shentino
2012-09-05 15:04 ` David Sterba
2012-09-05 21:23 ` Shentino
2012-09-04 18:15 ` Goffredo Baroncelli
2012-09-05 1:59 ` Shentino
2012-09-05 5:46 ` Goffredo Baroncelli
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='CAGDaZ_p2dXLr6rOZewXUEWYKV4b=dW9OZj4yXG4qPoUax2a8CA@mail.gmail.com' \
--to=shentino@gmail.com \
--cc=linux-btrfs@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).