From: John L Fjellstad <john-hotplug@fjellstad.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev and mkraid
Date: Wed, 23 Jun 2004 20:46:56 +0000 [thread overview]
Message-ID: <20040623204656.GA3312@fjellstad.org> (raw)
In-Reply-To: <pan.2004.06.22.12.37.36.47922@leogic.com>
[-- Attachment #1: Type: text/plain, Size: 1249 bytes --]
On Wed, Jun 23, 2004 at 05:59:08AM -0700, Kevin P. Fleming wrote:
> that's not happening on your system, it would be interesting to find out
> why. It certainly happens on mine, and I rely on that behavior to boot
> my machines.
I just upgraded to 2.6.7, but this was true for 2.6.5 too. I'm using
Linus' original kernel...
On my server, which has RAID1, I have the raid code compiled into the
kernel. AFAIK, it gets created by udev. Using udevinfo, I can see that
md0 is a /block/md0, with these SYSFS information:
SYSFS{dev}="9:0"
SYSFS{range}="1"
SYSFS{size}="690560"
SYSFS{stat}=" 1636 0 34472 0
600583 0 4804664 0 0 0
0"
For md1, I see these information:
looking at class device '/sys/block/md1':
SYSFS{dev}="9:1"
SYSFS{range}="1"
SYSFS{size}="267257088"
SYSFS{stat}=" 20071 0 261188 0
458504 0 3676670 0 0 0
0"
So the information does look like it is exported to sysfs.
On the workstation, I don't have raid code compiled in, and get no mdX
nodes created.
--
John L. Fjellstad
web: http://www.fjellstad.org/ Quis custodiet ipsos custodes
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2004-06-23 20:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-22 12:37 udev and mkraid Andreas Jellinghaus
2004-06-22 12:57 ` Kevin P. Fleming
2004-06-22 22:15 ` John L Fjellstad
2004-06-23 12:59 ` Kevin P. Fleming
2004-06-23 20:46 ` John L Fjellstad [this message]
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=20040623204656.GA3312@fjellstad.org \
--to=john-hotplug@fjellstad.org \
--cc=linux-hotplug@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).