Hi,
has this issue been resolved?
I would like to use the bcache + btrfs combo.
Thanks
--
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
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
dptrash posted on Thu, 31 Jul 2014 17:35:44 +0200 as excerpted:
> Concerning http://thread.gmane.org/gmane.comp.file-systems.btrfs/31018,
> does this "bug" still exists?
>
> Kernel 3.14 B: 2x HDD 1 TB C: 1x SSD 256 GB
>
> # make-bcache -B /dev/sda /dev/sdb -C /dev/sdc
> --cache_replacement_polic
Concerning http://thread.gmane.org/gmane.comp.file-systems.btrfs/31018, does
this "bug" still exists?
Kernel 3.14
B: 2x HDD 1 TB
C: 1x SSD 256 GB
# make-bcache -B /dev/sda /dev/sdb -C /dev/sdc --cache_replacement_policy=lru
# mkfs.btrfs -d raid1 -m raid1 -L "BTRFS_RAID" /dev/bcache0 /dev/bcache1
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 corruption
issue.
My use of btrfs is simple, though, with no subvolumes and no btrfs
Concerning http://thread.gmane.org/gmane.comp.file-systems.btrfs/31018, does
this "bug" still exists?
Kernel 3.14
B: 2x HDD 1 TB
C: 1x SSD 256 GB
# make-bcache -B /dev/sda /dev/sdb -C /dev/sdc --cache_replacement_policy=lru
# mkfs.btrfs -d raid1 -m raid1 -L "BTRFS_RAID" /dev/bcache0 /dev/bcache1
On 2014-04-30 14:16, Felix Homann wrote:
> Hi,
> a couple of months ago there has been some discussion about issues
> when using btrfs on bcache:
>
> http://thread.gmane.org/gmane.comp.file-systems.btrfs/31018
>
> From looking at the mailing list archives I cannot tell
Hi,
a couple of months ago there has been some discussion about issues
when using btrfs on bcache:
http://thread.gmane.org/gmane.comp.file-systems.btrfs/31018
>From looking at the mailing list archives I cannot tell whether or not
this issue has been resolved in current kernels from eit
On Wed, Jan 08, 2014 at 07:35:32PM +, Chris Mason wrote:
> On Mon, 2014-01-06 at 15:37 -0800, Kent Overstreet wrote:
> > Ok, I looked again at the relevant btrfs code, I guess I can see how this
> > printk
> > isn't normally triggered. But Chris, _what on earth_ is btrfs trying to
> > check
>
On Mon, 2014-01-06 at 15:37 -0800, Kent Overstreet wrote:
> On Fri, Dec 20, 2013 at 03:46:30PM +, Chris Mason wrote:
> > On Fri, 2013-12-20 at 10:42 -0200, Fábio Pfeifer wrote:
> > > Hello,
> > >
> > > I put the "WARN_ON(1);" after the printk lines (incomplete page read
> > > and incomplete pa
On Fri, Dec 20, 2013 at 03:46:30PM +, Chris Mason wrote:
> On Fri, 2013-12-20 at 10:42 -0200, Fábio Pfeifer wrote:
> > 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:
> >
> > [
(resend int text only)
Some more information about this issue.
I installed my system last november (arch x86_64), with kernel 3.11.
That time I didn't see any csum error or
"incomplete page read" error. Some time later these errors started to
show up. I don't know exactly if it was in
3.11 -> 3.12
On Thu, Dec 19, 2013 at 2:04 PM, Fábio Pfeifer wrote:
> 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:
I also
On Fri, 2013-12-20 at 10:42 -0200, Fábio Pfeifer wrote:
> 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
> [
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:
On Thu, Dec 19, 2013 at 8:59 PM, Chris Mason wrote:
> On Wed, 2013-12-18 at 18:17 +0100, eb wrote:
> Btrfs shouldn't be setting the offset on the bios. Are you able to add
> a WARN_ON to the message that prints this so we can see the stack trace?
If you send me a patch - my experience on hacking
On Wed, 2013-12-18 at 18:17 +0100, eb wrote:
> I've recently setup a system (Kernel 3.12.5-1-ARCH) which is layered as
> follows:
>
> /dev/sdb3 - cache0 (80 GB Intel SSD)
> /dev/sdc1 - backing device (2 TB WD HDD)
>
> sdb3+sdc1 => /dev/bcache0
>
> On /dev/bcache0, there's a btrfs filesystem wit
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 /home. I get lots of
> message
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
I've recently setup a system (Kernel 3.12.5-1-ARCH) which is layered as follows:
/dev/sdb3 - cache0 (80 GB Intel SSD)
/dev/sdc1 - backing device (2 TB WD HDD)
sdb3+sdc1 => /dev/bcache0
On /dev/bcache0, there's a btrfs filesystem with 2 subvolumes, mounted
as / and /home. What's been bothering me
20 matches
Mail list logo
