All of lore.kernel.org
 help / color / mirror / Atom feed
From: David McBride <dwm37@cam.ac.uk>
To: Gandalf Corvotempesta <gandalf.corvotempesta@gmail.com>
Cc: Sebastien Han <sebastien.han@enovance.com>,
	"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>,
	Weil Sage <sage@inktank.com>,
	Patrick McGarry <patrick@inktank.com>
Subject: Re: Ceph Ansible Repo
Date: Thu, 06 Mar 2014 13:28:30 +0000	[thread overview]
Message-ID: <531877FE.6040106@cam.ac.uk> (raw)
In-Reply-To: <CAJH6TXhSTRvn3NRqh=WXY5VdPhbW+HxPZAbUGCEqtX6rB6YFWg@mail.gmail.com>

On 06/03/14 13:19, Gandalf Corvotempesta wrote:
> 2014-03-06 13:07 GMT+01:00 David McBride <dwm37@cam.ac.uk>:
>> This causes the IO load to be nicely balanced across the two SSDs,
>> removing any hot spots, at the cost of enlarging the failure domain of
>> the loss of an SSD from half a node to a full node.
> 
> This is not a solution for me.
> Why not using LVM with a VG striped across both SSD ?
> I've never used LVM without raid, what happens in case of failure
> of a phisical disks?  The whole VG is lost ?

Yes.  A stripe-set depends on all of the members of an array, whether
managed through MD or LVM.

Thus, in a machine with two SSDs, which are striped together, the loss
of *either* SSD will cause all of the OSDs hosted by that machine to be
lost.

(Note: if you want to use LVM rather than GPTs on MD, you will probably
need to remove the '|dm-*' clause from the Ceph udev rules that govern
OSD assembly before they will work as expected.)

Kind regards,
David
-- 
David McBride <dwm37@cam.ac.uk>
Unix Specialist, University Computing Service

  reply	other threads:[~2014-03-06 13:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-02 23:26 Ceph Ansible Repo Sebastien Han
2014-03-03  2:59 ` Ian Colle
2014-03-03  8:49   ` Sebastien Han
2014-03-03 15:30     ` Travis Rhoden
2014-03-03 17:13       ` Ian Colle
2014-03-03 18:13         ` Sebastien Han
2014-03-06  9:36 ` Gandalf Corvotempesta
2014-03-06 10:14   ` Sebastien Han
2014-03-06 10:28     ` Gandalf Corvotempesta
2014-03-06 10:42       ` Sebastien Han
2014-03-06 10:43         ` Gandalf Corvotempesta
2014-03-06 12:07   ` David McBride
2014-03-06 13:19     ` Gandalf Corvotempesta
2014-03-06 13:28       ` David McBride [this message]
2014-03-06 16:31         ` Sebastien Han
2014-03-06 16:45           ` Gandalf Corvotempesta
2014-03-06 18:05             ` Sebastien Han
2014-03-07 13:09               ` Sebastien Han

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=531877FE.6040106@cam.ac.uk \
    --to=dwm37@cam.ac.uk \
    --cc=ceph-devel@vger.kernel.org \
    --cc=gandalf.corvotempesta@gmail.com \
    --cc=patrick@inktank.com \
    --cc=sage@inktank.com \
    --cc=sebastien.han@enovance.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.