From: Mike Snitzer <snitzer@redhat.com>
To: Anand Jain <anand.jain@oracle.com>
Cc: Chris Mason <clm@fb.com>,
dm-devel@redhat.com, lsf-pc@lists.linux-foundation.org,
Jan Kara <jack@suse.cz>
Subject: Re: [LSF/MM ATTEND]: Hot spare module ? And Btrfs volume management without mount
Date: Wed, 28 Jan 2015 11:33:24 -0500 [thread overview]
Message-ID: <20150128163324.GA11823@redhat.com> (raw)
In-Reply-To: <54C8BDB2.1020700@oracle.com>
On Wed, Jan 28 2015 at 5:45am -0500,
Anand Jain <anand.jain@oracle.com> wrote:
>
>
> Thanks for the reply.
>
> now based on your advise, if my participation is confirmed, by march,
> I would come up with a concrete proposal or an experimental code
> to share results at the conference if needed.
Maybe I'm misunderstanding the proposal but..
This seems like such a niche issue I think it isn't ever going to get
traction. 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?).
next prev parent reply other threads:[~2015-01-28 16:33 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 [this message]
2015-01-29 8:31 ` Anand Jain
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=20150128163324.GA11823@redhat.com \
--to=snitzer@redhat.com \
--cc=anand.jain@oracle.com \
--cc=clm@fb.com \
--cc=dm-devel@redhat.com \
--cc=jack@suse.cz \
--cc=lsf-pc@lists.linux-foundation.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