From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-iy0-f174.google.com ([209.85.210.174]:58154 "EHLO mail-iy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751507Ab2IAILY (ORCPT ); Sat, 1 Sep 2012 04:11:24 -0400 Received: by iahk25 with SMTP id k25so2327917iah.19 for ; Sat, 01 Sep 2012 01:11:23 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: From: Shentino Date: Sat, 1 Sep 2012 01:10:42 -0700 Message-ID: Subject: Re: rfc: fuzz testing by direct writes to device To: linux-btrfs@vger.kernel.org Content-Type: text/plain; charset=UTF-8 Sender: linux-btrfs-owner@vger.kernel.org List-ID: 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 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.