From: Larkin Lowrey <llowrey@nuclearwinter.com>
To: dptrash@arcor.de, linux-bcache@vger.kernel.org,
linux-btrfs@vger.kernel.org
Subject: Re: btrfs on bcache
Date: Wed, 30 Jul 2014 18:01:06 -0500 [thread overview]
Message-ID: <53D97932.8010505@nuclearwinter.com> (raw)
In-Reply-To: <1368165877.1162129.1406757898943.JavaMail.ngmail@webmail06.arcor-online.net>
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 level
raid. My bcache backing devices are LVM volumes that span multiple md
raid6 arrays. So, either the bug has been fixed or my configuration is
not susceptible.
I'm running kernel 3.15.5-200.fc20.x86_64.
--Larkin
On 7/30/2014 5:04 PM, dptrash@arcor.de wrote:
> 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 still have no "incomplete page write" messages in "dmesg | grep btrfs" and the checksums of some manually reviewed files are okay.
>
> Who has more experiences about this?
>
> Thanks,
>
> - dp
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bcache" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-07-30 23:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 22:04 btrfs on bcache dptrash
2014-07-30 23:01 ` Larkin Lowrey [this message]
2014-08-04 12:57 ` Fábio Pfeifer
[not found] <CAFvEZVF8J0jbYnTtV7X6uJWL1pBkwG6iFbH-KoNSPGq0Mc7bTw@mail.gmail.com>
[not found] ` <1387483201.23881.2.camel@ret.masoncoding.com>
2013-12-20 12:36 ` eb
2013-12-20 12:42 ` Fábio Pfeifer
2013-12-20 15:46 ` Chris Mason
2013-12-24 16:44 ` Fábio Pfeifer
2014-01-06 23:37 ` Kent Overstreet
2014-01-08 19:35 ` Chris Mason
2014-01-08 21:13 ` Kent Overstreet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53D97932.8010505@nuclearwinter.com \
--to=llowrey@nuclearwinter.com \
--cc=dptrash@arcor.de \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).