linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* rfc: fuzz testing by direct writes to device
@ 2012-09-01  6:44 Shentino
  2012-09-01  8:10 ` Shentino
  0 siblings, 1 reply; 15+ messages in thread
From: Shentino @ 2012-09-01  6:44 UTC (permalink / raw)
  To: linux-btrfs

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.

^ permalink raw reply	[flat|nested] 15+ messages in thread

end of thread, other threads:[~2012-09-05 21:23 UTC | newest]

Thread overview: 15+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-09-01  6:44 rfc: fuzz testing by direct writes to device Shentino
2012-09-01  8:10 ` Shentino
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

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).