Bug 1141451
| Summary: | Failures in tests: /dev/sda1: No such file or directory | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Community] Virtualization Tools | Reporter: | Richard W.M. Jones <rjones> | ||||
| Component: | libguestfs | Assignee: | Richard W.M. Jones <rjones> | ||||
| Status: | CLOSED UPSTREAM | QA Contact: | |||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | unspecified | CC: | agk, mbooth, prajnoha, ptoscano, rbalakri | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2015-04-14 10:34:52 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: | 910269 | ||||||
| Attachments: |
|
||||||
Ugh. Turns out to be a stupid udev rule. Whenever you close a device, the kernel sends a "change" event to udev which fires off a whole set of rules. It runs at least: scsi_id, path_id, blkid. And these operations overlap the subsequent mkfs or other operation. More udev workarounds needed. Thanks agk for pointing me in the right direction. |
Created attachment 937243 [details] build.log Description of problem: This is a placeholder for the extremely mysterious heisenbug where the /dev/sda1 device node does not get created, or magically disappears. Version-Release number of selected component (if applicable): It started happening in Fedora 21 and above. How reproducible: Rare, but annoying. Happens a lot more often under Koji than anywhere else, but can be reproduced in a VM occasionally. Only appears to happen after we write to the first sector of /dev/sda. In the attached build log, it happens twice. Search for the error message "/dev/sda1: No such file or directory"