From: Martin Wilck <mwilck@arcor.de>
To: linux-raid@vger.kernel.org
Cc: neilb@suse.de
Subject: Re: [PATCH 2/2] DDF: new algorithm for subarray UUID
Date: Sat, 07 Sep 2013 21:23:22 +0200 [thread overview]
Message-ID: <522B7D2A.4000409@arcor.de> (raw)
In-Reply-To: <1378502781-849-2-git-send-email-mwilck@arcor.de>
On 09/06/2013 11:26 PM, mwilck@arcor.de wrote:
> Some fake RAID BIOSes (in particular, LSI ones) change the
> VD GUID at every boot. These GUIDs are not suitable for
> identifying an array. Luckily the header GUID appears to
> remain constant.
>
> We construct a pseudo-UUID from the header GUID and those
> properties of the subarray that we expect to remain constant.
Thinking about it once more, it may actually be better to construct the
subarray UUID only from the container GUID and the member number (and
name), because if we implement Grow or Reshape for DDF, the other
properties might change.
I'm open for comments and suggestions.
Martin
next prev parent reply other threads:[~2013-09-07 19:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-06 21:26 [PATCH 1/2] DDF: brief_examine_subarrays_ddf: print array name mwilck
2013-09-06 21:26 ` [PATCH 2/2] DDF: new algorithm for subarray UUID mwilck
2013-09-07 19:23 ` Martin Wilck [this message]
2013-09-09 1:20 ` NeilBrown
2013-09-09 18:37 ` Martin Wilck
2013-09-09 23:51 ` NeilBrown
2013-09-09 1:15 ` [PATCH 1/2] DDF: brief_examine_subarrays_ddf: print array name NeilBrown
2013-09-09 18:31 ` Martin Wilck
2013-09-09 18:40 ` [PATCH 2/2] DDF: handle fake RAIDs with changing subarray UUIDs mwilck
2013-09-09 23:48 ` NeilBrown
2013-09-10 0:01 ` [PATCH 1/2] DDF: brief_examine_subarrays_ddf: print array name NeilBrown
2013-09-11 19:50 ` Martin Wilck
2013-09-11 19:55 ` Martin Wilck
2013-09-12 5:47 ` NeilBrown
2013-09-11 19:55 ` [PATCH 1/2] DDF: factor out array name generation mwilck
2013-09-11 19:55 ` [PATCH 2/2] DDF: brief_examine_subarrays_ddf: print array name mwilck
2013-09-12 5:44 ` NeilBrown
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=522B7D2A.4000409@arcor.de \
--to=mwilck@arcor.de \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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.