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 14:59:54 +0900 [thread overview]
Message-ID: <42B7ACDA.1000605@tequila.co.jp> (raw)
In-Reply-To: <17079.43900.652982.735401@cse.unsw.edu.au>
[-- Attachment #1: Type: text/plain, Size: 1726 bytes --]
On 06/21/2005 02:54 PM, Neil Brown wrote:
>>#> mdadm --detail --scan>> mdadm.conf
>>
>>is enought to get the raid started the next time I have to reboot
>>the box.
>
>
> 1/ remove the 'devices=' parts. Then it should be ok, providing there
> is a suitable DEVICES line at the top.
yeah I have a devices line on the top. If I don't have, I will need the
devices lines I guess.
> 2/ If you were depending on 'raidstart' to start your arrays before,
> mdadm will definitely be more reliable (which is to say that it
> should still work if you lose the first drive of your array...)
no, it should be now called via the mdadm start
> 3/ Best way to find out is to try it!
well :) not if you have production boxes with sw raid :D
>>Until now I used only the raidtools (raidhotadd, lsraid, etc). Is there
>>somehwere a reference like what raidhotadd would be in mdadm
>>command?
>
>
> Well, there is the man-page for mdadm. An understanding is always
> better than a cheat-sheet...
yeah, I am crawling through the docs, and man pages to get a thinking of it.
> But raidhotadd /dev/mdX /dev/hdY -> mdaddm /dev/mdX --add /dev/hdy
> s/add/remove/
> raidstop -> mdadm --stop
>
> There is no real equivalent for mkraid. mdadm --create does the same
> thing in a very different way.
yeah, but I more often have to add/remove a device than I have to create
a new raid, so its fine :)
--
[ 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 5:59 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 [this message]
2005-06-21 6:25 ` Neil Brown
2005-06-21 6:32 ` Clemens Schwaighofer
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=42B7ACDA.1000605@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).