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 20:21:39 -0400 [thread overview]
Message-ID: <42532B93.5010300@steeleye.com> (raw)
In-Reply-To: <4253206F.7020600@mvista.com>
Dave Jiang wrote:
> Paul Clements wrote:
>> Dave Jiang wrote:
> From my understanding of SCSI reservations ownership of the entire disk
> claimed. If we have multiple host blades, it is possible that multiple
SCSI 3 reservations can be used to lock an extent (e.g., a partition) of
a disk (you can even do read only reservations, which lock out only
writes). But yes, given your requirements, that may not be the easiest
solution.
> Perhaps the UUID within the superblock could be built via a function
> that could be abstracted or overloaded. The data within only needs to be
> unique within its environment so it could contain geographical
> addressing, target information or whatever fits. Perhaps this sounds a
> bit less intrusive and requires little or perhaps no kernel changes?
Yes, the md driver doesn't care what the UUID is, so you can make it
anything you want and then assemble the array. When you change
initiators, you rewrite the UUID (you just have to make sure that the
UUID is unique and that all UUIDs for disks in a given array are the
same). The UUID is 128 bits long, so it should suffice for your purposes.
--
Paul
prev parent reply other threads:[~2005-04-06 0:21 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
2005-04-05 23:34 ` Dave Jiang
2005-04-06 0:21 ` Paul Clements [this message]
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=42532B93.5010300@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).