Bug 838451
Summary: | udev is throwing " rename(/dev/disk/by-id/wwn-xxx.udev-tmp, /dev/disk/by-id/wwn-xxx) failed: No such file or directory" out | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | mjin <mjin> |
Component: | udev | Assignee: | Harald Hoyer <harald> |
Status: | CLOSED ERRATA | QA Contact: | qe-baseos-daemons |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 6.1 | CC: | azelinka, harald, jwest, kvolny, rnelson, tlavigne, wili |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-02-21 10:29:10 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: | 895654 |
Description
mjin
2012-07-09 07:12:54 UTC
did you turn on debug or did you strace? ah, sorry.. I see, it's a real error message... Seems to be a race. customer wants to know the progress of this bug, so i am changing view right from Red Hat Employee (internal) -> ALL, Please correct me if something wrong with such action, (In reply to comment #4) > customer wants to know the progress of this bug, so i am changing view right > from Red Hat Employee (internal) -> ALL, > > Please correct me if something wrong with such action, no problem We have a solution, which basically circumvents the error message, but not the outcome. > (In reply to comment #4)
> > customer wants to know the progress of this bug
As Harald said, the "fix" is to suppress the message of racing events
fighting about the same symlink name. It's nothing udev could work
around or solve.
There will be no change in behaviour, besides that it is not logged any more.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-0435.html |