public inbox for linux-bcache@vger.kernel.org
 help / color / mirror / Atom feed
From: ching <lsching17@gmail.com>
To: Eric Wheeler <bcache@lists.ewheeler.net>
Cc: linux-bcache@vger.kernel.org
Subject: Re: scrub backing device
Date: Thu, 12 May 2016 07:34:26 +0800	[thread overview]
Message-ID: <E3BCB47C-9466-4B3F-8AE2-DC7183B3B08D@gmail.com> (raw)
In-Reply-To: <alpine.LRH.2.11.1605111212540.22680@mx.ewheeler.net>

for example https://btrfs.wiki.kernel.org/index.php/Manpage/btrfs-scrub

On May 12, 2016 3:13:22 AM GMT+08:00, Eric Wheeler <bcache@lists.ewheeler.net> wrote:
>On Wed, 11 May 2016, ching lu wrote:
>
>> The read cache prevent the program to scrub the backing device
>directly.
>> 
>> if a few bits flipped in the backing device, the cache may still
>> return healthy data for a while.
>> 
>> Must i remove cache device before scrubbing?
>
>What do you mean by scrub?
>
>--
>Eric Wheeler
>
>> 
>> 
>> On Wed, May 11, 2016 at 9:15 AM, Eric Wheeler
><bcache@lists.ewheeler.net> wrote:
>> > On Fri, 29 Apr 2016, ching lu wrote:
>> >
>> >> Hello,
>> >>
>> >> i want to develop a script to perform data scrubbing periodically.
>> >
>> > I think you want to set dirty_percent to 0 and
>cache_mode=writethrough.
>> > Then wait a long time for dirty_percent to actually reach 0.
>> >
>> > --
>> > Eric Wheeler
>> >
>> >
>> >>
>> >> For my use case, i think it is meaningless to scrub cached data.
>> >>
>> >> If i change the cache mode to "none", will it turn off the read
>cache too?
>> >>
>> >> Furthermore, will this invalidate cached data? (i do not want to
>"warm
>> >> up" the cache again after the scrubbing)
>> >>
>> >> Thanks in advance,
>> >> c
>> >> --
>> >> 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
>> >>
>> --
>> 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
>> 

  reply	other threads:[~2016-05-11 23:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-29  2:13 scrub backing device ching lu
2016-05-11  1:15 ` Eric Wheeler
2016-05-11  1:36   ` ching lu
2016-05-11 19:13     ` Eric Wheeler
2016-05-11 23:34       ` ching [this message]
2016-05-11 23:57         ` Marc MERLIN
2016-05-12 10:25           ` ching
2016-05-13 22:10             ` Marc MERLIN
2016-05-13 22:21           ` Kent Overstreet
2016-05-15 23:56             ` ching

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=E3BCB47C-9466-4B3F-8AE2-DC7183B3B08D@gmail.com \
    --to=lsching17@gmail.com \
    --cc=bcache@lists.ewheeler.net \
    --cc=linux-bcache@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