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 <[email protected]> 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 [email protected]
>
- Bikram
OCA ( Oracle Certified Associate )
Database Specialist, WKU
http://www.wku.edu/~bikram.assal/
"Bikram Assal" <[email protected]> wrote:
>
> 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.
It's just a warning. The filesystem retries the allocation and it succeeded. There's
nothing you need to do.
On Fri, 2004-06-11 at 00:07, Bikram Assal wrote:
> The kernel version installed on the server is 2.4.18-5
>
> Would that be a problem ?
No
> Do I need to upgrade my kernel ?
Yes (well if it's a RHL kernel that is, but even if it's from another
vendor; 2.4.18 had quite a long list of security holes that got since
fixed so you'll want an upgrade)