Bug 876535
| Summary: | Document risks of using udevlog on kernel cmdline | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Marian Csontos <mcsontos> |
| Component: | udev | Assignee: | Harald Hoyer <harald> |
| Status: | CLOSED ERRATA | QA Contact: | Leos Pol <lpol> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.4 | CC: | lpol, mnavrati, psklenar, udev-maint-list, wmealing |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
If "udevlog" is specified on the kernel command line to debug udev, all udev logs are stored in the /dev/.udev/udev.log file. Running a system with the udev debug log turned on and using "udevlog" on the kernel command line for an extended period of time could cause /dev/.udev/udev.log to become very large and the devtmpfs mounted on /dev to become full. Consequently, if /dev became full, no new symbolic links and device nodes could be included. With this update, start_udev contains a verbose warning message describing the possibility.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-07-22 07:19:28 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: | |||
|
Description
Marian Csontos
2012-11-14 11:20:19 UTC
How do you know about "udevlog" in the first place? (In reply to comment #2) > How do you know about "udevlog" in the first place? Source code is the best decumentation. Is this one of the "undocumented" features one's not supposed to use? (In reply to comment #3) > (In reply to comment #2) > > How do you know about "udevlog" in the first place? > > Source code is the best decumentation. > > Is this one of the "undocumented" features one's not supposed to use? Yes, it's an "undocumented" debugging feature for customer debugging support. :-) If you use it, you should be aware of the problems it causes. Of course, I can document it in the source code of the shell script. This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux. Another alternative is to repeat the warning in the form of a kcs article. # grep -A2 udevlog start_udev
if strstr "$cmdline" udevlog; then
echo 'WARNING: udevlog is active!' >&2
echo "$udev_root/.udev/udev.log can grow big very quick and resides in RAM" >&2
echo 'Turn off udev logging as soon as you booted!' >&2
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. https://rhn.redhat.com/errata/RHBA-2015-1382.html |