public inbox for linux-bcache@vger.kernel.org
 help / color / mirror / Atom feed
From: Piergiorgio Sartor <piergiorgio.sartor-i47jiTeKxPI@public.gmane.org>
To: linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: (b)cache trashing
Date: Thu, 13 Jun 2013 22:33:49 +0200	[thread overview]
Message-ID: <20130613203348.GA3019@lazy.lzy> (raw)

Hi all,

one (or two), naive, question.

I assume that bcache will cache on reads too.

What will happen if something like this is run:

find /home -type -f -exec md5sum {} \;

That is, the md5 of *all* files is computed.

I assume that the cache will be completely
trashed and no old data will be present.

Is this the case?

Now, assuming we have a RAID something, with
LVM on top, with different volumes.
For example one for /home, one for /usr, etc.
Would it make sense, in respect of the above
trashing, to have different SSD (or paritions)
to cache the different volumes?
Instead of caching the complete RAID, of course.

Thanks a lot in advance,

bye,

-- 

piergiorgio

                 reply	other threads:[~2013-06-13 20:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20130613203348.GA3019@lazy.lzy \
    --to=piergiorgio.sartor-i47jitekxpi@public.gmane.org \
    --cc=linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.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