From: Tomasz Kusmierz <tom.kusmierz@gmail.com>
To: Roman Mamedov <rm@romanrm.ru>
Cc: Chris Mason <chris.mason@fusionio.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs for files > 10GB = random spontaneous CRC failure.
Date: Mon, 14 Jan 2013 16:34:14 +0000 [thread overview]
Message-ID: <50F43386.2030402@gmail.com> (raw)
In-Reply-To: <20130114222058.4dc90a81@natsu>
On 14/01/13 16:20, Roman Mamedov wrote:
> On Mon, 14 Jan 2013 15:22:36 +0000
> Tomasz Kusmierz <tom.kusmierz@gmail.com> wrote:
>
>> 1) create a single drive default btrfs volume on single partition ->
>> fill with test data -> scrub -> admire errors.
> Did you try ruling out btrfs as the cause of the problem? Maybe something else
> in your system is corrupting data, and btrfs just lets you know about that.
>
> I.e. on the same drive, create an Ext4 filesystem, copy some data to it which
> has known checksums (use md5sum or cfv to generate them in advance for data
> that is on another drive and is waiting to be copied); copy to that drive,
> flush caches, verify checksums of files at the destination.
>
Hi Roman,
Chris just provided his good old friend "stress.sh" that should do that.
So I'll dive into more testing :)
Tom.
next prev parent reply other threads:[~2013-01-14 16:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-14 11:09 btrfs for files > 10GB = random spontaneous CRC failure Tomasz Kusmierz
2013-01-14 14:59 ` Chris Mason
2013-01-14 15:22 ` Tomasz Kusmierz
2013-01-14 15:57 ` Chris Mason
2013-01-14 16:32 ` Tomasz Kusmierz
2013-01-14 16:34 ` Chris Mason
2013-01-15 16:54 ` Lars Weber
2013-01-15 23:32 ` Tom Kusmierz
2013-01-15 23:44 ` Chris Mason
2013-01-16 9:21 ` Bernd Schubert
2013-02-05 10:16 ` Tomasz Kusmierz
2013-02-05 12:49 ` Chris Mason
2013-02-05 14:10 ` Tomasz Kusmierz
2013-02-05 13:46 ` Roman Mamedov
2013-02-05 14:18 ` Tomasz Kusmierz
2013-01-14 16:20 ` Roman Mamedov
2013-01-14 16:34 ` Tomasz Kusmierz [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-01-14 11:17 Tomasz Kusmierz
2013-01-14 11:25 ` Roman Mamedov
2013-01-14 11:43 ` Tomasz Kusmierz
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=50F43386.2030402@gmail.com \
--to=tom.kusmierz@gmail.com \
--cc=chris.mason@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=rm@romanrm.ru \
/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.