All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Golombek <daveg@permabit.com>
To: Benjamin LaHaise <bcrl@kvack.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.31 hangs, no information on console or serial port
Date: 27 Feb 2006 12:48:06 -0500	[thread overview]
Message-ID: <7yd5h8u209.fsf@questionably-configured.permabit.com> (raw)
In-Reply-To: <20060227163944.GB18291@kvack.org>

Benjamin LaHaise <bcrl@kvack.org> writes:
> 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.

Unfortunately, --bind is not an option for us.  The custom nfs-server
is actually a protocol adapter, mapping a custom filesystem spread
across a cluster of machines into NFS.  We have the loopback mount in
order to provide CIFS access via samba.  Looking at
http://www.ussg.iu.edu/hypermail/linux/kernel/0407.3/0297.html

it certainly does seem like we're susceptible to this failure and are
looking at memory usage at the time of the crash.

Thanks,
Dave


      reply	other threads:[~2006-02-27 17:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-21 15:23 2.4.31 hangs, no information on console or serial port 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
2006-02-27 17:48       ` David Golombek [this message]

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=7yd5h8u209.fsf@questionably-configured.permabit.com \
    --to=daveg@permabit.com \
    --cc=bcrl@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.