Bug 497257 - The tmpfs filesystem goes on readonly mode.
The tmpfs filesystem goes on readonly mode.
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel (Show other bugs)
i686 Linux
urgent Severity high
: rc
: 5.3
Assigned To: Larry Woodman
Red Hat Kernel QE team
: OtherQA
Depends On:
Blocks: 533192 525215 526775
  Show dependency treegraph
Reported: 2009-04-22 23:09 EDT by Lachlan McIlroy
Modified: 2015-04-12 19:14 EDT (History)
9 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-03-30 02:55:34 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Patch to fix this problem (361 bytes, patch)
2009-09-29 11:54 EDT, Larry Woodman
no flags Details | Diff

  None (edit)
Description Lachlan McIlroy 2009-04-22 23:09:20 EDT
Description of problem:
Root filesystem went read-only after do_get_write_access() encountered a memory failure.

do_get_write_access: OOM for frozen_buffer
ext3_reserve_inode_write: aborting transaction: Out of memory in __ext3_journal_get_write_access
EXT3-fs error (device dm-0) in ext3_reserve_inode_write: Out of memory
Aborting journal on device dm-0.
EXT3-fs error (device dm-0) in ext3_dirty_inode: Out of memory
ext3_abort called.
EXT3-fs error (device dm-0): ext3_journal_start_sb: Detected aborted journal
Remounting filesystem read-only 

There was a lot of oomkiller activity around the time this happened.

Version-Release number of selected component (if applicable):

How reproducible:
Customer has seen this a few times.

Steps to Reproduce:
Actual results:

Expected results:

Additional info:

I did some digging through the code and found this suspect bit in __alloc_pages() added by patch linux-2.6-mm-oom-prevent-from-killing-several-processes.patch from BZ 392351.

--- a/mm/page_alloc.c
+++ b/mm/page_alloc.c
@@ -994,6 +994,8 @@ nofail_alloc:
 		goto nopage;
+	if (test_thread_flag(TIF_MEMDIE))
+		goto nopage;
 	/* We now go into synchronous reclaim */

I'm pretty sure that if a thread tagged with TIF_MEMDIE (which means it has been targetted by the oomkiller) enters this code with __GFP_NOFAIL it can fail to honour that flag and return with NULL.

Maybe the original problem from BZ 392351 could instead be fixed with:
which wont have this new bug.
Comment 2 Lachlan McIlroy 2009-05-11 21:12:25 EDT
Updating priority to reflect issue status.
Comment 5 Larry Woodman 2009-09-29 11:54:16 EDT
Created attachment 363038 [details]
Patch to fix this problem

The attached patch fixes this problem by not bailing out of __alloc_pages if __GFP_NOFAIL was passed in.
Comment 7 RHEL Product and Program Management 2009-10-01 12:16:13 EDT
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
Comment 13 Don Zickus 2009-11-17 16:55:44 EST
in kernel-2.6.18-174.el5
You can download this test kernel from http://people.redhat.com/dzickus/el5

Please do NOT transition this bugzilla state to VERIFIED until our QE team
has sent specific instructions indicating when to do so.  However feel free
to provide a comment indicating that this fix has been verified.
Comment 16 Chris Ward 2010-02-11 05:32:39 EST
~~ Attention Customers and Partners - RHEL 5.5 Beta is now available on RHN ~~

RHEL 5.5 Beta has been released! There should be a fix present in this 
release that addresses your request. Please test and report back results 
here, by March 3rd 2010 (2010-03-03) or sooner.

Upon successful verification of this request, post your results and update 
the Verified field in Bugzilla with the appropriate value.

If you encounter any issues while testing, please describe them and set 
this bug into NEED_INFO. If you encounter new defects or have additional 
patch(es) to request for inclusion, please clone this bug per each request
and escalate through your support representative.
Comment 20 errata-xmlrpc 2010-03-30 02:55:34 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.