From: Clemens Schwaighofer <cs@tequila.co.jp>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: linux-raid@vger.kernel.org
Subject: Re: from raidtools2 to mdadm
Date: Tue, 21 Jun 2005 15:32:42 +0900 [thread overview]
Message-ID: <42B7B48A.4000402@tequila.co.jp> (raw)
In-Reply-To: <17079.45804.485652.77989@cse.unsw.edu.au>
[-- Attachment #1: Type: text/plain, Size: 1033 bytes --]
On 06/21/2005 03:25 PM, Neil Brown wrote:
> No..
> The 'devices=' bits by themselves aren't enough, and are rarely
> wanted.
> If a device isn't listed in the DEVICES lines, then it won't be
> considered for use in an array.
okay
> The 'devices=' words are quite different. They say "this is how you
> recognise a device that is in this array. All the devices in it are
> on this list".
> This is reported by "mdadm --detail --scan" largely for interest. It
> should rarely be included in mdadm.conf. The very latest version ofn
> mdadm does not report them unless --verbose is given.
okay, then I have an old one, because mine gives it to me, thats why I
had it in my conf file.
thanks for all the help
--
[ Clemens Schwaighofer -----=====:::::~ ]
[ TEQUILA\ Japan IT Group ]
[ 6-17-2 Ginza Chuo-ku, Tokyo 104-8167, JAPAN ]
[ Tel: +81-(0)3-3545-7703 Fax: +81-(0)3-3545-7343 ]
[ http://www.tequila.co.jp ]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
next prev parent reply other threads:[~2005-06-21 6:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-21 5:40 from raidtools2 to mdadm Clemens Schwaighofer
2005-06-21 5:54 ` Neil Brown
2005-06-21 5:59 ` Clemens Schwaighofer
2005-06-21 6:25 ` Neil Brown
2005-06-21 6:32 ` Clemens Schwaighofer [this message]
2005-06-22 18:48 ` Bill Davidsen
2005-06-24 2:01 ` Neil Brown
2005-06-21 16:15 ` Luca Berra
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=42B7B48A.4000402@tequila.co.jp \
--to=cs@tequila.co.jp \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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).