Description of problem: During shutdown the system displays an error message something along the lines of "error waiting for /dev/md126 to be clean". Upon reboot, the "mdadm" starts a full resync of the mirrored drive. Version-Release number of selected component (if applicable): 4.6.7-300.fc24.x86_64 How reproducible: happens every shutdown Steps to Reproduce: 1. initiate system shutdown 2. wait for error message right before power-off 3. Actual results: mirrored drive keeps resyncing Expected results: clean drive Additional info:
See bug https://bugzilla.redhat.com/show_bug.cgi?id=1359352
See also https://bugzilla.redhat.com/show_bug.cgi?id=1359352
ping
SYS V Semaphores are enabled in the kernel via the CONFIG_SYSVIPC config option. That has been enabled in the kernel forever and continues to be.
Thanks, Josh. Even if its not a kernel issue it is still broken and was broken recently. I am not in a position to figure out who broke it, so what the process for getting this to the right people?
I have the same issue: https://bugzilla.redhat.com/show_bug.cgi?id=1375002
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 24 kernel bugs. Fedora 24 has now been rebased to 4.7.4-200.fc24. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 25, and are still experiencing this issue, please change the version to Fedora 25. If you experience different issues, please open a new bug report for those.
(In reply to Laura Abbott from comment #8) > *********** MASS BUG UPDATE ************** > > Fedora 24 has now been rebased to 4.7.4-200.fc24. Please test this kernel > update (or newer) and let us know if you issue has been resolved or if it is > still present with the newer kernel. > Both issues "Kernel not configured for semaphores (System V IPC). Not using udev synchronisation code" and "Software RAID broken!" still present with 4.7.4-200.fc24
"Kernel not configured for semaphores (System V IPC). Not using udev (In reply to robert.shteynfeld from comment #6) > Thanks, Josh. Even if its not a kernel issue it is still broken and was > broken recently. I am not in a position to figure out who broke it, so what > the process for getting this to the right people? "Kernel not configured for semaphores (System V IPC). Not using udev synchronisation code" is not a reason of "Software RAID broken!" The true reason of "Software RAID broken!" is a wrong selinux policy for mdadm. I'd like to change title of this issue, rest only the semaphores and adress it back to kernel. Broking of software raid is a subject of another bug: https://bugzilla.redhat.com/show_bug.cgi?id=1375002
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 24 kernel bugs. Fedora 25 has now been rebased to 4.10.9-100.fc24. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.