On Thu, Oct 30, 2014 at 3:50 AM, Koen Kooi wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Dan Merillat schreef op 30-10-14 04:17:
>> It's specifically BTRFS related, I was able to reproduce it on a bare
>> drive (no lvm, no md, no bcache). It's not bad RAM, I was able to
>> reproduc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dan Merillat schreef op 30-10-14 04:17:
> It's specifically BTRFS related, I was able to reproduce it on a bare
> drive (no lvm, no md, no bcache). It's not bad RAM, I was able to
> reproduce it on multiple machines running either 3.17 or late RCs.
It's specifically BTRFS related, I was able to reproduce it on a bare
drive (no lvm, no md, no bcache). It's not bad RAM, I was able to
reproduce it on multiple machines running either 3.17 or late RCs.
I've tested 3.18-rc2 for about 2 hours now, can't get any failures, so
that's good. If anyone
The following code reliably throws a SIGBUS in the memset, and cat
testfile > /dev/null returns an IO error.
I've sometimes gotten as high as iteration 900 before a SIGBUS, so
don't assume a single clear is OK.
linux 3.17.0, SATA -> MD(raid5) -> bcache (ssd) -> btrfs
Working on eliminating more
I'm in the middle of debugging the exact same thing. 3.17.0 -
rtorrent dies with SIGBUS.
I've done some debugging, the sequence is something like this:
open a new file
fallocate() to the final size
mmap() all (or a portion) of the file
write to the region
run SHA1 on that mmap'd region to validat
Hi, it seems that when using rtorrent to download into a btrfs system,
it leads to the creation of files that fail to read properly.
For instance, I get rtorrent to crash, but if I try to rsync the file he
was writting into someplace else, rsync also fails with the message
"can't map file "$file":
