linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Linux Raid List <linux-raid@vger.kernel.org>
Subject: Relabeling UUID
Date: Tue, 12 Dec 2006 18:30:53 -0500	[thread overview]
Message-ID: <457F3BAD.6060206@tmr.com> (raw)

I needed to move an array to other drives, and because of the way the 
array is used, want to keep the UUID on the new array. It doesn't appear 
that uuid= works with create (why?), or that stopping the array and then 
using assemble with uuid= will renumber the array in the superblock.

What's the correct way to do this, or is it broken? And why can't I 
specify uuid= in create?

-- 
bill davidsen <davidsen@tmr.com>
  CTO TMR Associates, Inc
  Doing interesting things with small computers since 1979


             reply	other threads:[~2006-12-12 23:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-12 23:30 Bill Davidsen [this message]
2006-12-13  0:29 ` Relabeling UUID Neil Brown
2006-12-13  5:42   ` Bill Davidsen
2006-12-13 10:50     ` Neil Brown
2006-12-13 14:30       ` David Greaves
2006-12-13 21:37       ` Bill Davidsen

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=457F3BAD.6060206@tmr.com \
    --to=davidsen@tmr.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).