From: Josef Bacik <jbacik@fusionio.com>
To: Alex Lyakas <alex.bolshoy.btrfs@gmail.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: fio reports data corruption with btrfs
Date: Mon, 25 Jun 2012 15:10:40 -0400 [thread overview]
Message-ID: <20120625191039.GE7404@localhost.localdomain> (raw)
In-Reply-To: <CAHf9xvafQugP2c_3_rxNAn55TgF_GiCM7udNS6yLEqVfPD1_wg@mail.gmail.com>
On Mon, Jun 25, 2012 at 12:30:34PM -0600, Alex Lyakas wrote:
> Greetings everybody,
>
> I am running a fio test on btrfs compiled from
> git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git,
> up to commit:
> cb77fcd88569cd2b7b25ecd4086ea932a53be9b3 Btrfs: delay iput with async extents
> including this commit.
>
> Below is a fio configuration file, and later fio textual output.
> Here:
> https://docs.google.com/folder/d/0B1AuaIB8xZtbNTRuSW1zVGozWFE/edit
> are "expected" vs "received" mismatch reports. Strangely, when I read
> the mismatched block from the file reported as corrupted by fio, I
> receive data different both from "expected" and "received" blocks that
> fio reports. I added one such file (job0.1.0.88576.now) to the
> pastebin as well.
>
> If you think that my fio configuration file is faulty, please let me
> know. fio version is 1.59. The idea is to run 10 io processes in
> parallel.
>
Mount options? I'm running the test now, I'll let you know if I can reproduce.
Thanks,
Josef
next prev parent reply other threads:[~2012-06-25 19:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-25 18:30 fio reports data corruption with btrfs Alex Lyakas
2012-06-25 19:10 ` Josef Bacik [this message]
2012-06-25 19:26 ` Josef Bacik
2012-06-26 7:39 ` Alex Lyakas
2012-06-27 8:15 ` Alex Lyakas
2012-06-27 13:46 ` Josef Bacik
2012-07-02 11:48 ` Alex Lyakas
2012-07-02 12:49 ` Josef Bacik
2012-07-03 10:35 ` Alex Lyakas
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=20120625191039.GE7404@localhost.localdomain \
--to=jbacik@fusionio.com \
--cc=alex.bolshoy.btrfs@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).