From: Andre Noll <maan@systemlinux.org>
To: Neil Brown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: mdadm-2.3.1 fails to hotadd device
Date: Sun, 26 Feb 2006 23:20:50 +0100 [thread overview]
Message-ID: <20060226222050.GO7030@skl-net.de> (raw)
In-Reply-To: <17410.8082.794478.606126@cse.unsw.edu.au>
On 08:37, Neil Brown wrote:
> Your '/dev' is a symlink, and mdadm doesn't seem to like that.
>
> Can you change the 'nftw' call in 'map_dev' in 'util.c' to
>
> nftw("/dev/.", add_dev, 10, FTW_PHYS);
>
> and see if that helps?
Jup, that does the trick:
# ./mdadm /dev/md1 -a /dev/hdd1
mdadm: re-added /dev/hdd1
> It isn't really the right fix, but it is a quick-and-dirty that might
> work.
Is it considered an invalid configuration to have /dev being a symlink
(to /udev as in my case)?
Thanks
Andre
--
The only person who always got his work done by Friday was Robinson Crusoe
next prev parent reply other threads:[~2006-02-26 22:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-26 11:08 mdadm-2.3.1 fails to hotadd device Andre Noll
2006-02-26 11:41 ` Neil Brown
2006-02-26 12:13 ` Andre Noll
2006-02-26 21:37 ` Neil Brown
2006-02-26 22:20 ` Andre Noll [this message]
2006-02-26 22:57 ` Neil Brown
2006-02-26 14:37 ` Andre Noll
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=20060226222050.GO7030@skl-net.de \
--to=maan@systemlinux.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).