These are 4 unrelated patches that I've gathered
over the last few weeks.
The last one is probably the most interesting and one
that you should probably think carefully before apply
(but I hope you'll decide in favour).
When you --assemble -or --create an array, udev immediately has a look
at the new device and might act on that content. e.g. tell udisks it
can mount a filesystem, or tell mdadm that there is part of a RAID
array in here.
When you --assemble an array you want that to happen.
When you --create it, you don't.
udev cannot distinguish 'assemble' from 'create'.
This can be annoying.
The way I have found to tell udev about the distinction to create a
/run/udev/rules.d/01-mdadm.rules file which marks any newly appearing
md array as SYSTEMD_READY==0. This is created before the array, and
removed once the array exisits (and hopefully has been handled by
udev).
Most udev rules which might process a newly appearing device will
avoid doing so i SYSTEMD_READY is set to 0.
Thanks,
NeilBrown
---
NeilBrown (4):
Grow_continue_command: ensure 'content' is properly initialised.
systemd/mdadm-last-resort: use ConditionPathExists instead of Conflicts
Detail: ensure --export names are acceptable as shell variables.
Create: tell udev device is not ready when first created.
Create.c | 9 +++++++++
Detail.c | 12 +++++++++---
Grow.c | 1 +
lib.c | 22 ++++++++++++++++++++++
mdadm.h | 2 ++
systemd/mdadm-last-resort@.service | 2 +-
6 files changed, 44 insertions(+), 4 deletions(-)
--
Signature
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
