From: Paul Clements <paul.clements@steeleye.com>
To: Dave Jiang <djiang@mvista.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: multi-hosting support for carrier grade Linux
Date: Tue, 05 Apr 2005 17:50:23 -0400 [thread overview]
Message-ID: <4253081F.6000901@steeleye.com> (raw)
In-Reply-To: <20050405204155.GA32724@blade.az.mvista.com>
Dave Jiang wrote:
> I'm attempting to implement multihost support of the MD for environments
> such as carrier grade Linux. Multihost support allows the RAID array to
> be claimed by a particular host via a unique ID (unique SCSI host ID,
> FibreChannel WWN, or geographical address of a chassis blade. That way
> another host that can access the disks do not claim the same disks that
> are used by the RAID array.
Why not just use SCSI reservations?
> I would like to store a 64bit unique ID on the
> superblock of the device. The least intrusive way IMHO to do this is
> implementing the feature via the management app such as mdadm in
> userland. However, it seems that after I instruct the kernel to create the MD array via mdadm, the kernel starts out with a blank superblock and clobbers the
If you write a valid superblock to the disk and then assemble the array,
the superblock doesn't get clobbered.
> data I have stored on the superblock via mdadm. Would it be acceptable
> to modify the kernel such that the unique ID info is preserved during
> the creation of the superblock by the kernel? Example patch follows:
As for adding additional fields to the various superblock formats, you'd
have to ask Neil if he's open to that.
--
Paul
next prev parent reply other threads:[~2005-04-05 21:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-05 20:41 multi-hosting support for carrier grade Linux Dave Jiang
2005-04-05 21:50 ` Paul Clements [this message]
2005-04-05 23:34 ` Dave Jiang
2005-04-06 0:21 ` Paul Clements
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=4253081F.6000901@steeleye.com \
--to=paul.clements@steeleye.com \
--cc=djiang@mvista.com \
--cc=linux-raid@vger.kernel.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).