Bug 947815
| Summary: | udev doesn't update ID_FS_TYPE of MD RAID members | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jan Safranek <jsafrane> | ||||||
| Component: | mdadm | Assignee: | Jes Sorensen <Jes.Sorensen> | ||||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 20 | CC: | agk, dledford, harald, Jes.Sorensen, johannbg, lnykryn, metherid, msekleta, plautrba, rvokal, systemd-maint, vpavlin, zbyszek | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | |||||||||
| : | 1016131 (view as bug list) | Environment: | |||||||
| Last Closed: | 2015-06-29 11:51:26 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 1016131 | ||||||||
| Attachments: |
|
||||||||
Created attachment 732815 [details]
Proposed patch
With the patched mdadm, I am not able to hit the bug. Did you post this patch upstream? (In reply to comment #3) > Did you post this patch upstream? no... please review and do so. Created attachment 734166 [details]
Proposed revised patch
Slightly modified patch posted upstream - lets see what the maintainer says to it. This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle. Changing version to '20'. More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora20 Any news here? What did upstream say? (In reply to Jan Safranek from comment #8) > Any news here? What did upstream say? Looking at the thread and git there does not seem to have been any movement or discussion of that patch at all.. This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |
(discussed with Kay and Harald on IRC, Harald can reproduce it) After mdadm -C ..., udev sometimes doesn't show 'ID_FS_TYPE = linux_raid_member' for a member device of the new RAID. Version-Release number of selected component (if applicable): systemd-199-1.fc20.x86_64 kernel-3.9.0-0.rc4.git0.1.fc20.x86_64 How reproducible: ~ 10% Steps to Reproduce: 1. run this loop: for i in $(seq 100); do echo ---------------; mdadm -S /dev/md0; wipefs -a /dev/sdb1; wipefs -a /dev/sdb2; udevadm settle; udevadm info /dev/sdb1 | grep ID_FS_TYPE; mdadm -C --force -l 0 -n 2 /dev/md0 /dev/sdb1 /dev/sdb2; udevadm settle; udevadm info /dev/sdb1 | grep ID_FS_TYPE; done | tee log 2. grep ID_FS_TYPE log | wc -l Actual results: less than 100 'ID_FS_TYPE' strings found in the log Expected results: exactly 100 'ID_FS_TYPE' strings found in the log Additional info: It is reproducible only with two devices on one disk, i.e. sdb1 and sdb2. With two different disks, e.g. sda1 and sdb1, it works well. Also, when 'udevadm info /dev/sdb1' doesn't show ID_FS_TYPE, it is still *not* updated after ~1 minute or 'udevadm settle'. Only 'udevadm trigger' helps. (This indicates that something did not generate some event, but I really don't know udev or kernel internals).