On 14/01/13 16:20, Roman Mamedov wrote:
On Mon, 14 Jan 2013 15:22:36 +0000
Tomasz Kusmierz <tom.kusmierz@xxxxxxxxx> 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.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html