From: Andrew Morton <akpm@zip.com.au>
To: Andy Smith <asmith@umdgrb.umd.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ENOMEM in do_get_write_access, retrying.
Date: Wed, 21 Aug 2002 18:57:38 -0700 [thread overview]
Message-ID: <3D644512.585BF69D@zip.com.au> (raw)
In-Reply-To: Pine.LNX.4.33.0208212133070.7748-100000@umdgrb.umd.edu
Andy Smith wrote:
>
> ENOMEM in do_get_write_access, retrying.
> ENOMEM in do_get_write_access, retrying.
> ENOMEM in do_get_write_access, retrying.
> ENOMEM in journal_alloc_journal_head, retrying.
> ENOMEM in do_get_write_access, retrying.
> ENOMEM in do_get_write_access, retrying.
>
> Hi All,
>
> I am getting a bunch of these in my messages file while cp'ing
> files from one computer 2 another. Both machines have 3c996 gigabit
> and large disk arrays. The computer with the errors is receiving the
> files.
>
Your gigE NIC gobbled up all the free memory. ext3 is stuck
in a corner where it just _has_ to allocate some memory, so it
retries the allocation.
bdflush or nfsd or kswapd write some memory back to disk, it
becomes reclaimable and ext3 is happy.
We should kill that printk.
next prev parent reply other threads:[~2002-08-22 1:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-22 1:33 ENOMEM in do_get_write_access, retrying Andy Smith
2002-08-22 1:57 ` Andrew Morton [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-10 21:33 Bikram Assal
[not found] <Pine.LNX.4.58.0406101737090.959@morpheus>
2004-06-10 22:07 ` Bikram Assal
2004-06-10 22:28 ` Andrew Morton
2004-06-11 7:05 ` Arjan van de Ven
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=3D644512.585BF69D@zip.com.au \
--to=akpm@zip.com.au \
--cc=asmith@umdgrb.umd.edu \
--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