On 04/19/2017 10:40 PM, NeilBrown wrote:
When an array is created the content is not initializes,
so it could have remnants of an old filesystem or md array
etc on it.
udev will see this and might try to activate it, which is almost
certainly not what is wanted.
So create a temporary udev rules files to set ENV{SYSTEMD_READY}="0"
while the creation event is processed. This is fairly uniformly
used to suppress actions based on the contents of the device.
Signed-off-by: NeilBrown <neilb@xxxxxxxx>
---
Create.c | 9 +++++++++
lib.c | 22 ++++++++++++++++++++++
mdadm.h | 2 ++
3 files changed, 33 insertions(+)
Neil,
I have heard of this problem before, but I have some concerns about the
solution. First of all, /run/udev/rules.d/ isn't a universal directory.
At least Fedora doesn't have it, so we need to take that into account. I
wasn't aware it was possible to create temporary udev rules like this.
Second, isn't this going to be racey if you have multiple arrays
running? I am wondering if we cannot find a solution that relies on a
permanently installed udev rule that we enable/disable with systemctl
and use the device name as an argument?
Thoughts?
Jes
--
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
