From: "michael@kmaclub.com" <michael@kmaclub.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: David Greaves <david@dgreaves.com>,
Michal Soltys <soltys@ziu.info>,
linux-raid@vger.kernel.org
Subject: Re: Confused about UUID mounting and mirrors
Date: Tue, 17 Jun 2008 07:19:40 -0700 [thread overview]
Message-ID: <4857C7FC.9000000@kmaclub.com> (raw)
In-Reply-To: <48576394.8090609@msgid.tls.msk.ru>
Michael Tokarev wrote:
> michael@kmaclub.com wrote:
> []
>> mdadm --detail /dev/md0 | grep UUID
>> UUID : 3531a48d:1180bdf3:bfcd9e76:5b7e5957
>
> This is a RAID (md) -- i.e., device, UUID. Think of it
> as of disk drive serial number for example -- look at
> /dev/disk/by-id/.
>
>> mount -U 3531a48d:1180bdf3:bfcd9e76:5b7e5957 /mnt
>> mount: no such partition found
>
> And mount expects *filesystem* UUID, not a device UUID.
> I.e., the UUID which was written by mkfs. For a ext[234]fs,
> tune2fs -l /dev/md0 will show it; for other filesystems
> use appropriate tools.
I understand. I was trying this based on a suggestion further back in
this thread.
Using the filesystem ID doesn't work either because /dev/sda, /dev/sdb,
and /dev/md0 all have the same UUID since it is a mirror. How do you
tell the system to mount /dev/md0 and not the individual drives which is
what it is trying to do now.
Michael
next prev parent reply other threads:[~2008-06-17 14:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-16 17:54 Confused about UUID mounting and mirrors michael
2008-06-16 20:41 ` Michal Soltys
2008-06-16 21:29 ` michael
2008-06-16 21:38 ` David Greaves
2008-06-17 2:29 ` michael
2008-06-17 7:11 ` Michael Tokarev
2008-06-17 14:19 ` michael [this message]
2008-06-17 16:10 ` Clive Messer
2008-06-18 14:00 ` Michael Tokarev
2008-06-18 14:42 ` michael
2008-06-20 2:17 ` michael
2008-06-17 19:17 ` Peter Grandi
2008-06-17 21:37 ` Michal Soltys
2008-06-19 3:56 ` Neil Brown
2008-06-22 20:05 ` 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=4857C7FC.9000000@kmaclub.com \
--to=michael@kmaclub.com \
--cc=david@dgreaves.com \
--cc=linux-raid@vger.kernel.org \
--cc=mjt@tls.msk.ru \
--cc=soltys@ziu.info \
/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).