linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michal Soltys <nozo@ziu.info>
To: linux-raid@vger.kernel.org
Subject: Re: md device naming question
Date: Tue, 25 Sep 2007 06:49:25 +0200	[thread overview]
Message-ID: <46F89355.9040201@ziu.info> (raw)
In-Reply-To: <87lkawzge0.fsf@hades.wkstn.nix>

Nix wrote:
> On 19 Sep 2007, maximilian attems said:
> 
>>
>> i presume it may also be /sys/block/mdNN ?
> 
> That's it, e.g. /sys/block/md0. Notable subdirectories include holders/
> (block devices within the array, more than one if e.g. LVM is in use),
> 

Also, if you mount the raid as a partitionable one, /sys/block/md_dNN ;

mdadm has pretty decent handling of all the names (check out auto options, 
both usable in mdadm.conf and from command line). Also from my experience, 
if you try to use udev on partitionable arrays, partition related uevents 
will be delayed until next mdadm invocation, or some partition related 
command (like fdisk).



      reply	other threads:[~2007-09-25  4:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-19  8:10 md device naming question maximilian attems
2007-09-24  7:12 ` Nix
2007-09-25  4:49   ` Michal Soltys [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=46F89355.9040201@ziu.info \
    --to=nozo@ziu.info \
    --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).