linux-bcache.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Tripathy <jonnyt-Nf8S+5hNwl710XsdtD+oqA@public.gmane.org>
To: linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Bcache in Xen Environment
Date: Wed, 01 Aug 2012 10:20:15 +0100	[thread overview]
Message-ID: <5fe181f7719e9d85f15e0906688388bd@abpni.co.uk> (raw)

Hi Everyone,

I wish to investigate using bcache in a Xen virtualisation environment. 
We wish to use bcache to add a SSD (single drive) cache to a RAID10 
device (using metal spindles), and I have a few questions.

1) On the bcache website, it says this:

"It won't return a write as completed until everything necessary to 
locate it is on stable storage, nor will writes ever be seen as 
partially completed (or worse, missing) in the event of power failure."

Is this just true for write-through? Or write-back mode as well? If it 
is true for write-back mode, how does this work? I thought the point of 
write-back mode was to return write quickly due to the fast buffer 
storage.

2) When we delete a virtual machine, it is common for us to run dd to 
"zero" the LVM LV so that data is deleted. If we introduce bcache, can 
we still be sure that all data is gone? We need to make sure that no 
data leakage can occur between LVs.

3) SSD storage has a much more limited write span that metal spindles. 
If an SSD drive were to fail, will the RAID10 spindle array still 
continue to function? Will any data be lost? How does write-through and 
write-back handle these cases?

Thanks for your time.

             reply	other threads:[~2012-08-01  9:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-01  9:20 Jonathan Tripathy [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-08-01  9:30 Bcache in Xen Environment Jonathan Tripathy
2012-08-03  7:03 ` Alex Elsayed

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=5fe181f7719e9d85f15e0906688388bd@abpni.co.uk \
    --to=jonnyt-nf8s+5hnwl710xsdtd+oqa@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;
as well as URLs for NNTP newsgroup(s).