From: "Bikram Assal" <bikram.assal@wku.edu>
To: Burton Windle <bwindle@fint.org>, linux-kernel@vger.kernel.org
Subject: ENOMEM in do_get_write_access, retrying
Date: Thu, 10 Jun 2004 17:07:04 -0500 [thread overview]
Message-ID: <web-68590618@mailadmin.wku.edu> (raw)
In-Reply-To: <Pine.LNX.4.58.0406101737090.959@morpheus>
The kernel version installed on the server is 2.4.18-5
Would that be a problem ? Do I need to upgrade my kernel ?
Since the memory doesn't seem to be a problem apparently, what should be my next step to check the flaw.
Although this happened only once, this could lead to a possible problem.
Thanks a lot for your help.
- Bikram.
On Thu, 10 Jun 2004 17:39:33 -0400 (EDT)
Burton Windle <bwindle@fint.org> wrote:
> On Thu, 10 Jun 2004, Bikram Assal wrote:
>
> > Hi,
> >
> > I got this error in /var/log/messages only one time.
> > the error is : ENOMEM in do_get_write_access, retrying.
> >
> > Please help me find out the cause of it.
> >
> >
> > - Bikram
> > OCA ( Oracle Certified Associate )
> > Database Specialist, WKU
> > http://www.wku.edu/~bikram.assal/
> > -
>
> That message comes from line 1598 in linux/fs/jbd/journal.c
>
> It happens if the kernel tries to allocate memory for a journal (ext3)
> operation, but fails because there isn't any memory free currently.
>
> With as much memory cached as you reported, this shouldn't happen.
>
> --
> Burton Windle bwindle@fint.org
>
- Bikram
OCA ( Oracle Certified Associate )
Database Specialist, WKU
http://www.wku.edu/~bikram.assal/
next parent reply other threads:[~2004-06-10 22:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.58.0406101737090.959@morpheus>
2004-06-10 22:07 ` Bikram Assal [this message]
2004-06-10 22:28 ` ENOMEM in do_get_write_access, retrying Andrew Morton
2004-06-11 7:05 ` Arjan van de Ven
2004-06-10 21:33 Bikram Assal
-- strict thread matches above, loose matches on Subject: below --
2002-08-22 1:33 Andy Smith
2002-08-22 1:57 ` Andrew Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=web-68590618@mailadmin.wku.edu \
--to=bikram.assal@wku.edu \
--cc=bwindle@fint.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox