From: Benjamin LaHaise <bcrl@kvack.org>
To: David Golombek <daveg@permabit.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.31 hangs, no information on console or serial port
Date: Mon, 27 Feb 2006 11:39:45 -0500 [thread overview]
Message-ID: <20060227163944.GB18291@kvack.org> (raw)
In-Reply-To: <7yfym4lqhh.fsf@questionably-configured.permabit.com>
On Mon, Feb 27, 2006 at 11:24:10AM -0500, David Golombek wrote:
> We're beginning to suspect that a hung loopback NFS mount might be to
> blame, although we can't reproduce this trivially. Is there anyway in
> which a mount that was behaving badly could affect the kernel in this
> manner?
Loopback NFS can deadlock in trying to free memory when writing back dirty
pages. Use mount --bind instead.
-ben
--
"Ladies and gentlemen, I'm sorry to interrupt, but the police are here
and they've asked us to stop the party." Don't Email: <dont@kvack.org>.
next prev parent reply other threads:[~2006-02-27 16:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-21 15:23 David Golombek
2006-02-21 15:29 ` Benjamin LaHaise
2006-02-21 16:04 ` David Golombek
2006-02-21 21:41 ` Willy Tarreau
2006-02-27 16:24 ` David Golombek
2006-02-27 16:39 ` Benjamin LaHaise [this message]
2006-02-27 17:48 ` David Golombek
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=20060227163944.GB18291@kvack.org \
--to=bcrl@kvack.org \
--cc=daveg@permabit.com \
--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
Powered by JetHome