All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anand Jain <Anand.Jain@oracle.com>
To: lsf-pc@lists.linux-foundation.org, dm-devel@redhat.com,
	Mike Snitzer <snitzer@redhat.com>
Cc: Chris Mason <clm@fb.com>, Jan Kara <jack@suse.cz>,
	"JAIN, ANAND" <anand.jain@oracle.com>
Subject: Re: [LSF/MM ATTEND]: Hot spare module ? And Btrfs volume management without mount
Date: Thu, 29 Jan 2015 16:31:35 +0800	[thread overview]
Message-ID: <54C9EFE7.7040207@oracle.com> (raw)
In-Reply-To: <20150128163324.GA11823@redhat.com>


Hi Mike,

  Thanks for looking into this and commenting.

> This seems like such a niche issue I think it isn't ever going to get
> traction.

  I anticipate some implementation challenges so community participation
  will help.

  btrfs needs hot spare solution, which I am working on, and its better
  to have it soon especially for data center uses.

  btrfs is another VM in the system. Now there is more pressure to look
  at system-wide hot spare efficiency for systems with heterogeneous VMs.

  Its a kind of important that we provide a holistic hot spare solution
  to the end user.

  In the days when system used to have one type of VM in the system,
  its global hot spare was really a system-wide global hot spare as well.
  Now with more types of VMs in the system these global hot spare aren't
  truly global any more, from the customers point of view who would
  also be concerned about total cost-per-byte.


> Having a common pool of hot spares doesn't buy you much if
> all the different volume managers were to experience a failure -- in
> that case the sharing actively works against you (if you've only
> accomodated for say 1 of the 3 different volume managers failing at any
> one time; but if you have provisioned for worst case of all solutions
> failing then what was the point of the exercise?).

  Good point. But what you have mentioned is a solution problem.
  Currently we do have global hot spare with in a VM containing different
  Raid volumes, and your point will apply their as well. And we expect
  customer to configure it properly as per their business needs.

  With system wide hot spare module, it will help to have global hot
  spare really a global hot spare no matter of whats underlaying VM is.
  And the same global hot spare rule/algorithm will apply but across VMs
  and Raids with in the system. As usual customers will still have
  choice to assign dedicated hot spare for more critical VM-raids if
  needed.

Thanks, Anand

  reply	other threads:[~2015-01-29  8:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <54B8C174.4020802@oracle.com>
2015-01-27 10:18 ` [Lsf-pc] [LSF/MM ATTEND]: Hot spare module ? And Btrfs volume management without mount Jan Kara
2015-01-28 10:45   ` Anand Jain
2015-01-28 16:33     ` Mike Snitzer
2015-01-29  8:31       ` Anand Jain [this message]
2015-01-29 13:59         ` Mike Snitzer
2015-01-30  2:40           ` Anand Jain

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=54C9EFE7.7040207@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=clm@fb.com \
    --cc=dm-devel@redhat.com \
    --cc=jack@suse.cz \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=snitzer@redhat.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.