From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs on bcache
Date: Fri, 1 Aug 2014 01:55:08 +0000 (UTC) [thread overview]
Message-ID: <pan$a04fa$5cd7ad2f$4c951447$c4e27df6@cox.net> (raw)
In-Reply-To: 1028108337.2120293.1406820944449.JavaMail.ngmail@webmail09.arcor-online.net
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_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?
See the reply (not mine) to your earlier post of the question:
http://permalink.gmane.org/gmane.linux.kernel.bcache.devel/2602
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2014-08-01 1:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1731942750.1162128.1406757898913.JavaMail.ngmail@webmail06.arcor-online.net>
2014-07-31 15:35 ` btrfs on bcache dptrash
2014-08-01 1:55 ` Duncan [this message]
2014-08-20 20:17 raphead
-- strict thread matches above, loose matches on Subject: below --
2014-07-30 22:04 dptrash
2014-07-30 23:01 ` Larkin Lowrey
2014-08-04 12:57 ` Fábio Pfeifer
2014-04-30 18:16 Felix Homann
2014-05-01 11:33 ` Austin S Hemmelgarn
2013-12-18 17:17 eb
2013-12-19 19:04 ` Fábio Pfeifer
2013-12-19 19:05 ` Fábio Pfeifer
2013-12-20 22:26 ` Henry de Valence
2013-12-19 19:59 ` Chris Mason
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='pan$a04fa$5cd7ad2f$4c951447$c4e27df6@cox.net' \
--to=1i5t5.duncan@cox.net \
--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).