You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If mdadm is stopped with mounted filesystems then corruption could occur. In fact, it wont allow it unless it's --force'ed and that's not done with /etc/init.d/mdadm as-is (nor should it be). i.e.
mdadm: Cannot get exclusive access to /dev/md0:Perhaps a running process, mounted filesystem or active volume group?
The proper order would be to umount first, then stop the meta device(s).
I've been trying to work around the installed packaged code, to avoid breaking the upgrade paths. However, this is one that I think should be fixed upstream. Changing /etc/init.d/mdadm to STOP=99 would not suffice because m is before u in the sort order. Many other permutations, e.g. K100mdadm or K999mdadm sort incorrectly too.
What would work is to reverse the order, e.g. mdadm is STOP=98 and umount is STOP=97. Leave 99 open for future use.
josephtingiris:
Supply the following if possible:
specifically tested & confirmed on x86-64 and ipq806x
18.06.1 and snapshot
opkg install mdadm
The text was updated successfully, but these errors were encountered: