Re: fio reports data corruption with btrfs

2012-07-03 Thread Alex Lyakas
Hi Josef, tested with your master branch, commit 157331741ba010ffcb2212b88342fb21ae140636. fio compiled from tag fio-2.0.8 (commit cf9a74c8bd63d9db5256f1362885c740e11a1fe5). Result: some kernel warnings about hung tasks, fio segfault and mismatch errors. Below are some outputs... I will try some

Re: fio reports data corruption with btrfs

2012-07-02 Thread Alex Lyakas
Hi Josef, which branch from your (or another?) repo should I try this on: remotes/origin/HEAD - origin/master remotes/origin/enospc3c78455 Btrfs: fall back to non-inline if we don't have enough space remotes/origin/for-chris 7e9ce65 Btrfs: hold a ref on the inode during writepages

Re: fio reports data corruption with btrfs

2012-07-02 Thread Josef Bacik
On Mon, Jul 02, 2012 at 05:48:43AM -0600, Alex Lyakas wrote: Hi Josef, which branch from your (or another?) repo should I try this on: Master, and make sure you've checked out a more recent fio from git to make sure it's not a bug in fio. Thanks, Josef -- To unsubscribe from this list: send

Re: fio reports data corruption with btrfs

2012-06-27 Thread Alex Lyakas
Hi Josef, I have rerun the test with btrfs-next master branch. fio reported mismatched blocks again. Mount options were the same (-o noatime,nodatacow). In both cases the drive is a 135Gb drive, while the total size of allocated block groups is around 60Gb: Data: total=62.01GB, used=49.04GB

Re: fio reports data corruption with btrfs

2012-06-27 Thread Josef Bacik
On Wed, Jun 27, 2012 at 02:15:59AM -0600, Alex Lyakas wrote: Hi Josef, I have rerun the test with btrfs-next master branch. fio reported mismatched blocks again. Mount options were the same (-o noatime,nodatacow). Ok I'll try running it again here locally, I didn't realize it was nodatacow.

Re: fio reports data corruption with btrfs

2012-06-26 Thread Alex Lyakas
Hi Josef, Mount options were noatime, nodatacow. So you say that fio might have received ENOSPC, but didn't abort the test? I will compile your branch and let you know. I did not see any error messages from the kernel, except from: Jun 25 10:04:28 vc kernel: [ 436.730890] btrfs: setting

fio reports data corruption with btrfs

2012-06-25 Thread Alex Lyakas
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

Re: fio reports data corruption with btrfs

2012-06-25 Thread Josef Bacik
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

Re: fio reports data corruption with btrfs

2012-06-25 Thread Josef Bacik
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