I'm one of those that used to have problems with btrfs on top of bcache.
After some corruptions, I gave up this setup.
Recently (from February, I think) I gave it another shot, and I have
had no problems since.
I use bcache in writeback mode, with very good performance. I'm
feeling btrfs very stab
Any update on this?
I have here exactly the same issue. Kernel 3.12.5-1-ARCH, backing
device 500 GB IDE, cache 24 GB SSD => /dev/bcache0
On /dev/bcache I also have 2 subvolumes, / and /home. I get lots of
messages in dmesg:
(...)
[ 22.282469] BTRFS info (device bcache0): csum failed ino 56193 o
Forgot to mention: bcache is in writeback mode
2013/12/19 Fábio Pfeifer :
> Any update on this?
>
> I have here exactly the same issue. Kernel 3.12.5-1-ARCH, backing
> device 500 GB IDE, cache 24 GB SSD => /dev/bcache0
> On /dev/bcache I also have 2 subvolumes, / and /h
Hello,
I put the "WARN_ON(1);" after the printk lines (incomplete page read
and incomplete page write) in extent_io.c.
here some call traces:
[ 19.509497] incomplete page read in btrfs with offset 2560 and length 1536
[ 19.509500] [ cut here ]
[ 19.509528] WARNING:
ymore, but I can
make some tests in a spare HD and SSD i have here. I'll report back
after Christmas.
thanks,
Fabio
2013/12/20 Chris Mason :
> On Fri, 2013-12-20 at 10:42 -0200, Fábio Pfeifer wrote:
>> Hello,
>>
>> I put the "WARN_ON(1);" after the printk lines
st regards,
Fábio Pfeifer
2014-07-30 20:01 GMT-03:00 Larkin Lowrey :
> I've been running two backup servers, with 25T and 20T of data, using
> btrfs on bcache (writeback) for about 7 months. I periodically run btrfs
> scrubs and backup verifies (SHA1 hashes) and have never had a corrup
