I ran into this as well. I unwisely worked around it by placing the
backup file on /tmp. I don't recommend that choice! I didn't see
your AVC on your EMail, but I recommend you reach out to the SELinux
folks for labeling help. I've reach out to them in the past and have
found them very helpful (as are the folks here). Getting the labeling
corrected will not only help you but everyone else in the long term.
I agree that it would be good for mdadm to handle this kind of failure
in a more productive fashion as well. But I'm only a lurker here. I
don't have enough knowledge to suggest what would be better. One
thing that really helped me debug this was commenting out the lines
#StandardOutput=null
#StandardError=null
in the systemd file /lib/systemd/system/mdadm-grow-continue@.service
-- note you have to run systemctl daemon-reload after changing the
file for the change to be noticed.
Once I did that, the system logs had much more useful information.
I'm not sure where that file is sourced, whether it's from the
linux-raid people or from the distributions or somewhere in between.
Does anyone here know if there's a reason why standard out and
standard error are sent to /dev/null for this service?
Eddie
--
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
