From: Neil Brown <neilb@suse.de>
To: Doug Ledford <dledford@redhat.com>
Cc: Jon Nelson <jnelson-linux-raid@jamponi.net>,
LinuxRaid <linux-raid@vger.kernel.org>
Subject: Re: [Patch] mdadm ignoring homehost?
Date: Tue, 21 Apr 2009 16:54:01 +1000 [thread overview]
Message-ID: <18925.28041.731116.459343@notabene.brown> (raw)
In-Reply-To: message from Doug Ledford on Monday April 20
On Monday April 20, dledford@redhat.com wrote:
> On Apr 20, 2009, at 3:23 AM, Neil Brown wrote:
> > The kernel supports this. We just need to make sure it works with
> > udev and get mdadm to use it.
> >
> > echo md_foo > /sys/modules/md_mod/parameters/new_array
> > ls -l /dev/md_foo
> >
> > no numbers at all.
>
> Even in the output of /proc/mdstat?
>
Yep.
# ls -l /dev/md_foo
brw-rw---- 1 root disk 9, 513 2009-04-21 16:50 /dev/md_foo
# cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [multipath] [faulty]
md_foo : active raid1 sdf[0]
156249920 blocks [1/1] [U]
# ls -ld /sys/block/md*
drwxr-xr-x 6 root root 0 2009-04-21 16:49 /sys/block/md127
drwxr-xr-x 6 root root 0 2009-04-21 16:50 /sys/block/md_foo
NeilBrown
next prev parent reply other threads:[~2009-04-21 6:54 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 16:57 mdadm ignoring homehost? Jon Nelson
2009-04-01 15:15 ` Jon Nelson
2009-04-01 22:46 ` Neil Brown
2009-04-06 14:47 ` [Patch] " Doug Ledford
2009-04-06 19:33 ` Luca Berra
2009-04-17 3:49 ` Neil Brown
2009-04-17 7:08 ` Gabor Gombas
2009-04-20 5:23 ` Neil Brown
2009-04-21 6:34 ` Gabor Gombas
2009-04-21 7:06 ` Luca Berra
2009-04-17 18:17 ` Doug Ledford
2009-04-17 18:40 ` Piergiorgio Sartor
2009-04-18 7:54 ` Luca Berra
2009-04-18 8:36 ` Piergiorgio Sartor
2009-04-18 10:19 ` Luca Berra
2009-04-18 13:06 ` Piergiorgio Sartor
2009-04-20 5:58 ` Neil Brown
2009-04-20 12:29 ` Doug Ledford
2009-04-20 18:17 ` Piergiorgio Sartor
2009-04-20 19:49 ` Leslie Rhorer
2009-04-20 20:04 ` Piergiorgio Sartor
2009-04-20 21:18 ` Luca Berra
2009-04-20 21:13 ` Luca Berra
2009-04-20 21:24 ` Piergiorgio Sartor
2009-04-20 23:47 ` Doug Ledford
2009-04-21 0:00 ` Doug Ledford
2009-04-21 8:57 ` Michal Soltys
2009-04-21 6:29 ` Luca Berra
2009-04-21 18:15 ` Piergiorgio Sartor
2009-04-22 16:06 ` Andrew Burgess
2009-04-23 1:20 ` Doug Ledford
2009-04-23 5:51 ` Luca Berra
2009-04-23 6:09 ` Luca Berra
2009-04-23 11:05 ` Doug Ledford
2009-04-23 21:31 ` Luca Berra
2009-04-24 16:46 ` Doug Ledford
2009-04-24 19:15 ` Piergiorgio Sartor
2009-04-26 11:52 ` Doug Ledford
2009-04-26 12:14 ` Piergiorgio Sartor
2009-04-26 12:58 ` Piergiorgio Sartor
2009-04-26 18:06 ` Doug Ledford
2009-04-26 19:08 ` Piergiorgio Sartor
2009-04-26 21:37 ` Michal Soltys
2009-04-18 14:34 ` Andrew Burgess
2009-04-18 8:12 ` Luca Berra
2009-04-18 8:44 ` Piergiorgio Sartor
2009-04-18 13:35 ` Doug Ledford
2009-04-18 13:52 ` Piergiorgio Sartor
2009-04-18 14:50 ` Doug Ledford
2009-04-18 14:48 ` Jon Nelson
2009-04-20 6:08 ` Neil Brown
2009-04-20 12:26 ` Luca Berra
2009-04-20 12:36 ` Doug Ledford
2009-04-18 13:58 ` Bill Davidsen
2009-04-20 7:23 ` Neil Brown
2009-04-20 13:15 ` Doug Ledford
2009-04-21 6:54 ` Neil Brown [this message]
2009-05-11 6:47 ` Neil Brown
2009-04-01 22:47 ` Michal Soltys
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=18925.28041.731116.459343@notabene.brown \
--to=neilb@suse.de \
--cc=dledford@redhat.com \
--cc=jnelson-linux-raid@jamponi.net \
--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).