Hello all,
I got a report recently that a Raid1 resource failed to stop. It
turned out that some web management daemon called amDaemon kept
the MD devices open. After commit
2f8ec082408fb5c825a5fe30ec436c7e5208aa0a (attached), there is a
code now which stops such processes.
Do you have objections to this or do you think it should be done
in a different way? Note that it won't change stuff like
filesystems mounted or VG running on top of an MD device.
And did you ever see such a process opening the MD device? I'm
worried a bit about killing processes which are not supposed to
be removed.
Cheers,
Dejan
I got a report recently that a Raid1 resource failed to stop. It
turned out that some web management daemon called amDaemon kept
the MD devices open. After commit
2f8ec082408fb5c825a5fe30ec436c7e5208aa0a (attached), there is a
code now which stops such processes.
Do you have objections to this or do you think it should be done
in a different way? Note that it won't change stuff like
filesystems mounted or VG running on top of an MD device.
And did you ever see such a process opening the MD device? I'm
worried a bit about killing processes which are not supposed to
be removed.
Cheers,
Dejan