summaryrefslogtreecommitdiffstats
path: root/udev-md-raid.rules
Commit message (Collapse)AuthorAgeFilesLines
* Update udev rules for hotplug support.NeilBrown2010-06-301-6/+6
| | | | | | | | | - split the rules for handling components of array to be clearly separate from rules for handling the arrays themselves. - add call to "-If" when removing a device - uncomment the --incremental call when adding a device. Signed-off-by: NeilBrown <neilb@suse.de>
* vol_id was removed by the udev upstream maintainer in May 2009.Marco d'Itri2009-10-291-1/+1
| | | | | | | | | | | | One should use /sbin/blkid -o udev -p ... (from util-linux >> 2.16) instead of vol_id --export ... Author: Marco d'Itri <md@linux.it> Bug-Debian: http://bugs.debian.org/541884 Reviewed-by: martin f. krafft <madduck@debian.org> Signed-off-by: NeilBrown <neilb@suse.de>
* udev-md-raid.rules: use string_escapeNeilBrown2009-05-111-2/+2
| | | | | | For safety, "MD_NAME" strings should be escaped in udev. Signed-off-by: NeilBrown <neilb@suse.de>
* udev rules fix for partitions.NeilBrown2009-04-141-0/+4
| | | | | | | | | | sysfs directories for partitions do not have md/* files, but should not for that reason be ignored. Thanks to Michal Soltys for original fix. Signed-off-by: Michal Soltys <soltys@ziu.info> Signed-off-by: NeilBrown <neilb@suse.de>
* mdadm udev rules changeDoug Ledford2009-04-081-0/+2
| | | | | | | | | | | | | | | | | | | | | | | I'm not attaching a patch for this because it's so simple. Long story short, watching both add and change events in udev rules is bad for md devices. Specifically, the kernel will generate a change event on things like array stop, and on things like fdisk close. In the case of array stop, it can result in the array being assembled again immediately. In the case of fdisk close, the situation is worse. Let's say you stop all the md devices on some block device in order to repartition. You run fdisk, change the partition table, then issue a write of the table. The write of the table triggers the change event *before* the kernel updates the partition table in memory for the block device, causing udev to rerun the incremental rules on the old partition table and restart all the arrays you just stopped with the old partition table layout, at which point the kernel is unable to reread the partition table. So, once you've enable incremental assembly, it becomes apparent that what we really want is to only start devices on add, not on add|change. -- Doug Ledford <dledford@redhat.com>
* Fix udev-rules for case where array isn't really there..NeilBrown2009-03-091-0/+1
| | | | | | See http://git.kernel.org/?p=linux/hotplug/udev.git;a=commitdiff;h=b822542608326092e177fd1707ca7fb53b2846c4 Signed-off-by: NeilBrown <neilb@suse.de>
* Add udev rules file for mdadm.NeilBrown2008-11-041-0/+31
This is based on the rules from openSUSE 11.1-rc3.
generated by cgit (git 2.34.1) at 2024-05-04 07:10:30 +0000