linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Keltz <jas@cse.yorku.ca>
To: linux-raid@vger.kernel.org
Subject: MD component device renaming with udev and MD on full disk
Date: Fri, 21 Nov 2014 16:42:15 -0500	[thread overview]
Message-ID: <546FB1B7.3050304@cse.yorku.ca> (raw)

Hi.

I have two questions about MD..

1) I've written a udev rule to remap /dev/sdX devices on my system to 
/dev/cXeYsZpA (controller, enclosure, slot, partition) mapping. When I 
reboot the system, I see that all the devices in /dev are appropriately 
renamed.  If I look at /proc/mdstat, it still has the kernel names of 
the devices (/dev/sdX) even though those devices no longer exist.  If I 
do an mdadm --detail /dev/mdX the system reports the proper device name 
makeup.  I manually failed a device, and I got the correct device name 
in the email.  I'm just wondering what command I would execute to make 
/proc/mdstat update the devices in its output?

2) Unrelated to 1) -- the argument re: using MD on full devices versus 
partitions has been around for a long time.  I've been experimenting 
with using it on full devices.  One of the arguments that I've read for 
not using full devices is that apparently, if you have two devices that 
are identical, but one of them is slightly smaller than the other due to 
say, bad sectors, then these disks can't be used together in one MD 
because they are different sizes. I'm wondering how valid that argument 
is?  Surely it would make sense if MD was using full devices for it to 
actually stop short of the end of the disk for situations like these...

Thanks for any help you can provide.

Jason.

             reply	other threads:[~2014-11-21 21:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-21 21:42 Jason Keltz [this message]
2014-11-25  2:55 ` MD component device renaming with udev and MD on full disk NeilBrown

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=546FB1B7.3050304@cse.yorku.ca \
    --to=jas@cse.yorku.ca \
    --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).