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.
> 

So we think it may be enospc, so try btrfs-next

git://git.kernel.org/pub/scm/linux/kernel/git/josef/btrfs-next.git

which has an enospc fix related to creating a crapptone of files.  Let me know
if that helps.  Thanks,

Josef
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to