From: Goldwyn Rodrigues <rgoldwyn@suse.com>
To: David Teigland <teigland@redhat.com>
Cc: linux-kernel@vger.kernel.org, NeilBrown <neilb@suse.de>
Subject: Re: clustered MD
Date: Tue, 09 Jun 2015 15:08:11 -0500 [thread overview]
Message-ID: <557747AB.7080706@suse.com> (raw)
In-Reply-To: <20150609194505.GA17536@redhat.com>
Hi David,
On 06/09/2015 02:45 PM, David Teigland wrote:
> On Tue, Jun 09, 2015 at 02:26:25PM -0500, Goldwyn Rodrigues wrote:
>> On 06/09/2015 01:22 PM, David Teigland wrote:
>>> I've just noticed the existence of clustered MD for the first time.
>>> It is a major new user of the dlm, and I have some doubts about it.
>>> When did this appear on the mailing list for review?
>>
>> It first appeared in December, 2014 on the RAID mailing list.
>> http://marc.info/?l=linux-raid&m=141891941330336&w=2
>
> I don't read that mailing list. Searching my archives of linux-kernel, it
> has never been mentioned. I can't even find an email for the md pull
> request that included it.
Is this what you are looking for?
http://marc.info/?l=linux-kernel&m=142976971510061&w=2
>
> The merge commit states:
>
> - "experimental" code for managing md/raid1 across a cluster using
> DLM. Code is not ready for general use and triggers a WARNING if
> used. However it is looking good and mostly done and having in
> mainline will help co-ordinate development.
>
> That falls far short of the bar for adding it to the kernel. It not only
> needs to work, it needs to be reviewed and justified, usually by showing
Why do you say it does not work? It did go through it's round of reviews
on the RAID mailing list. I understand that you missed it because you
are not subscribed to the raid mailing list.
> some real world utility to warrant the potential maintenance effort.
We do have a valid real world utility. It is to provide
high-availability of RAID1 storage over the cluster. The distributed
locking is required only during cases of error and superblock updates
and is not required during normal operations, which makes it fast enough
for usual case scenarios.
What are the doubts you have about it?
--
Goldwyn
next prev parent reply other threads:[~2015-06-09 20:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-09 18:22 clustered MD David Teigland
2015-06-09 19:26 ` Goldwyn Rodrigues
2015-06-09 19:45 ` David Teigland
2015-06-09 20:08 ` Goldwyn Rodrigues [this message]
2015-06-09 20:30 ` David Teigland
2015-06-09 20:33 ` David Lang
2015-06-10 3:33 ` Goldwyn Rodrigues
2015-06-10 8:00 ` Richard Weinberger
2015-06-10 13:59 ` Goldwyn Rodrigues
2015-06-10 15:01 ` David Teigland
2015-06-10 15:27 ` Goldwyn Rodrigues
2015-06-10 15:48 ` David Teigland
2015-06-10 16:23 ` Goldwyn Rodrigues
2015-06-10 17:05 ` David Teigland
2015-06-10 19:22 ` David Teigland
2015-06-10 20:31 ` Neil Brown
2015-06-10 21:07 ` David Teigland
2015-06-10 22:11 ` David Teigland
2015-06-10 22:50 ` Neil Brown
2015-06-12 18:46 ` David Teigland
2015-06-14 22:19 ` Goldwyn Rodrigues
2015-06-23 1:34 ` NeilBrown
2015-06-09 20:14 ` Goldwyn Rodrigues
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=557747AB.7080706@suse.com \
--to=rgoldwyn@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=teigland@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox