From: Anu Matthew <anu.matthew@bms.com>
To: linux-raid@vger.kernel.org
Subject: Re: Problems with SCSI devices renaming...
Date: Tue, 19 Oct 2004 15:38:01 -0400 [thread overview]
Message-ID: <41756D19.7040409@bms.com> (raw)
In-Reply-To: <LGEHJKEJFBMMDCIAJCDCEEAOCCAA.mc@openskynet.de>
mdadm - with multipath devices: I remember it bringing up the md device
after the names changed, but had to manually add the alternate path.
And, thereafter it behaved well, and have not added any more luns yet.
Not sure if it is so in v1.7.0.
You may want to check out devlabel as Matt said..
Martin Clauss wrote:
>>forget autodetect,
>>forget raidtools,
>>switch to mdadm.
>>
>>
>Yep, seems a bit smarter, and I discovered that there were multiple superblocks
>on some of the disks (from former usage i guess), which confused mdrun....
>Now I hope that it can handle changed device names, I'll try tomorrow...
>
>Thanks,
>Martin
>
>
>
next prev parent reply other threads:[~2004-10-19 19:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-19 14:47 Problems with SCSI devices renaming Martin Clauss
2004-10-19 15:02 ` Luca Berra
2004-10-19 17:35 ` Martin Clauss
2004-10-19 19:38 ` Anu Matthew [this message]
2004-10-19 15:08 ` Matt Domsch
2004-10-19 15:15 ` Guy
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=41756D19.7040409@bms.com \
--to=anu.matthew@bms.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;
as well as URLs for NNTP newsgroup(s).