From: Neil Brown <neilb@suse.de>
To: Andrew Dunn <andrew.g.dunn.dod@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Question about preferred minor.
Date: Thu, 3 Jun 2010 11:13:16 +1000 [thread overview]
Message-ID: <20100603111316.74d96d1f@notabene.brown> (raw)
In-Reply-To: <AANLkTimbMat99Su8F4FauQIa8mpeZJk6syJ0oXjHyygG@mail.gmail.com>
On Wed, 2 Jun 2010 20:53:28 -0400
Andrew Dunn <andrew.g.dunn.dod@gmail.com> wrote:
> I have never noticed this, my apologies for not being able to resolve
> this independently.
>
> I have this array that I am using for the primary bulk of my data and
> today was the first day that I noticed this designator in the detailed
> output:
>
> storrgie@MINERVA:~$ sudo mdadm -D /dev/md2
> /dev/md2:
> Version : 00.90
> Creation Time : Fri Apr 30 21:13:28 2010
> Raid Level : raid6
> Array Size : 11721071616 (11178.09 GiB 12002.38 GB)
> Used Dev Size : 1953511936 (1863.01 GiB 2000.40 GB)
> Raid Devices : 8
> Total Devices : 8
> Preferred Minor : 2
> Persistence : Superblock is persistent
snip
>
> What is the meaning of Preferred Minor : 2 ?
It means that if the array is auto-assembled, whether by the kernel with
auto-detect or by mdadm with --incremental or '-As', it will be assembled
as /dev/md2 - i.e. the device file will have a major number of 9 (meaning
an md raid array) and the minor number will be 2.
NeilBrown
>
> Thank you all.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-06-03 1:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-03 0:53 Question about preferred minor Andrew Dunn
2010-06-03 1:13 ` Neil Brown [this message]
2010-06-03 8:42 ` Christian Gatzemeier
2010-06-03 11:15 ` Andrew Dunn
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=20100603111316.74d96d1f@notabene.brown \
--to=neilb@suse.de \
--cc=andrew.g.dunn.dod@gmail.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