Bug 947149
| Summary: | logrotate.status: Read-only file system error: could not read state file, will not attempt to write into it. | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Douglas Schilling Landgraf <dougsland> |
| Component: | ovirt-node | Assignee: | Ryan Barry <rbarry> |
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.4 | CC: | acathrow, bsarathy, cboyle, cshao, gouyang, hadong, huiwa, jboggs, leiwang, linux, mburns, mjenner, ovirt-maint, rbarry, tlavigne, yaniwang, ycui |
| Target Milestone: | rc | Keywords: | TestOnly |
| Target Release: | 6.5 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | ovirt-node-3.0.1-2.el6 | Doc Type: | Bug Fix |
| Doc Text: |
When trying to rotate files manually, an error was generated on logrotate.status:
# logrotate /etc/logrotate.d/vdsm
error: error creating state file /var/lib/logrotate.status: Read-only file system
error: could not read state file, will not attempt to write into it.
A bug in the do_filp_open() function caused it to exit early if any write access was requested on a read-only file system. This prevented the opening of device nodes on a read-only file system. With this update, the do_filp_open() has been fixed to no longer exit if a write request is made on a read-only file system.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-01-21 19:30:40 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
Douglas Schilling Landgraf
2013-04-01 18:35:47 UTC
rhev-h is a read-only file system, so when executing "logrotate /etc/logrotate.d/vdsm" , it will print above error info. workaround here: mount -o remount, rw / I'm not sure this is as bad as it appears. logrotate still seems to work even if this file doesn't work. The fix should be either making the file rw (editing rwtab) or moving the file to another location that is read-write. there is a -s or --state option to specify a different state file location. This bug is currently attached to errata RHBA-2013:15277. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag. Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information: * Cause: What actions or circumstances cause this bug to present. * Consequence: What happens when the bug presents. * Fix: What was done to fix the bug. * Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore') Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug. For further details on the Cause, Consequence, Fix, Result format please refer to: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thanks in advance. Test version: rhev-hypervisor6-6.5-20131106.0.el6ev.noarch.rpm ovirt-node-3.0.1-7.el6.noarch vdsm-4.13.0-0.6.beta1.el6ev.x86_64 Test steps: 1. [root@dhcp-8-136 admin]# cat /etc/rwtab |grep logrotate.status files /var/lib/logrotate.status 2. [root@dhcp-8-136 admin]# logrotate /etc/logrotate.d/vdsm no error info was shown in console, so this bug has been fixed, change it into "VERIFIED". 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-2014-0033.html |