Filesystem goes read-only without the underlying storage reporting errors
This document (3735930) is provided subject to the disclaimer at the end of this document.
SUSE Linux Enterprise Desktop 10
No errors are reported from the storage layer underlying the affected filesystem.
Normally, this behavior occurs when the underlying storage layer (like SCSI) reported an error when the filesystem code was trying to write out vital data. Errors or warnings reported by the underlying storage layer will precede the messages from the filesystem layer and the issue can only be addressed by fixing the hardware and/or configuration problem with the storage layer.
With a system under heavy load, a bug in the read-ahead optimization part of the ext3, reiserfs and udf code could be triggered in which it mistook a temporary error condition from the storage layer ("please retry again later") for an unrecoverable error.In this case, only the filesystem layer reports errors; these errors are not preceded by errors or warnings reported by the underlying storage layer.
In the case of ext3, messages similar to the following arelogged:
ERROR: EXT3-fs error (device sda1): ext3_readdir: directory #133120 containsa hole at offset 4096
ERROR: Aborting journal on device sda1.
ERROR: ext3_abort called.
ERROR: EXT3-fs abort (device sda1):
ERROR: ext3_journal_start: Detected aborted journal
ERROR: Remounting filesystem read-only
- Document ID:3735930
- Creation Date: 20-Sep-2007
- Modified Date:23-Feb-2021
- SUSE Linux Enterprise Desktop
- SUSE Linux Enterprise Server
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com