From: Ben DJ <bendj095124367913213465@gmail.com>
To: Michael Evans <mjevans1983@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Clarify /etc/mdadm.conf format and content?
Date: Wed, 4 Nov 2009 23:21:54 -0800 [thread overview]
Message-ID: <babafd2f0911042321k4dfda707he80f40596fba2a3b@mail.gmail.com> (raw)
In-Reply-To: <4877c76c0911042217r76d7e46cg4ceeb391e9098a6@mail.gmail.com>
Hi,
On Wed, Nov 4, 2009 at 10:17 PM, Michael Evans <mjevans1983@gmail.com> wrote:
> -U, --update=homehost
> --auto-update-homehost
The man pages suggest what to do when assembling/creating the array.
Since I've _got_ arrays already created, that are auto-assembled using
the info IN mdadm.conf, I'm unclear as to how to change/correct the
name= field. Can you clarify?
To my other question, http://man-wiki.net/index.php/8:mdadm#DEVICE_NAMES says,
The standard names for non-partitioned arrays (the only sort of md
array available in 2.4 and earlier) either of
/dev/mdNN
/dev/md/NN
where NN is a number. The standard names for partitionable arrays (as
available from 2.6 onwards) is one of
/dev/md/dNN
/dev/md_dNN
Since my arrays are each a single partition (the RAID-10 has LVMs on
the single partition), I guess that the "either of"
/dev/mdNN
/dev/md/NN
applies? And, even if so, why do mdadm --examine & mdadm --detail use
_different_ output formats?
BenDJ
--
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:[~2009-11-05 7:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-05 5:53 Clarify /etc/mdadm.conf format and content? Ben DJ
2009-11-05 6:17 ` Michael Evans
2009-11-05 7:21 ` Ben DJ [this message]
2009-11-05 7:31 ` Michael Evans
2009-11-05 16:24 ` Ben DJ
2009-11-05 17:03 ` Ben DJ
2009-11-09 4:57 ` Neil Brown
2009-11-10 0:11 ` Michael Evans
2009-11-12 1:05 ` Ben DJ
2009-11-07 17:06 ` Doug Ledford
2009-11-12 0:48 ` Ben DJ
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=babafd2f0911042321k4dfda707he80f40596fba2a3b@mail.gmail.com \
--to=bendj095124367913213465@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=mjevans1983@gmail.com \
/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).