All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Frisk <john_a_frisk@yahoo.com>
To: nfs@lists.sourceforge.net
Subject: Re: NFS hang in 2.6.21.1
Date: Mon, 21 May 2007 11:37:10 -0700 (PDT)	[thread overview]
Message-ID: <174023.84136.qm@web54407.mail.yahoo.com> (raw)
In-Reply-To: <1179766574.6737.25.camel@heimdal.trondhjem.org>

Hi Trond,
I applied your patches to both kernels, rebooted and
still the same problem.  Once bonnie attempts to
"rewrite" it's sample file, the client machine process
cannot be killed.  The client OS however can still do
other things, such as load firefox, etc.  The
interesting thing being, it can also in another shell
access the same directory under NFS as the bonnie
program was writing in the other shell.  Sorry for not
knowing all the internals, but is the NFS client
multi-threaded too?

Output:
jfrisk@evil:~$ /usr/sbin/bonnie++ -f -s 100 -n 1 -r 0
Writing intelligently...done
Rewriting...

jfrisk@evil:~$ ps axu | grep bonnie
jfrisk    5612  0.2  0.0   2708  1012 pts/2    D+  
13:24   0:01 /usr/sbin/bonnie++ -f -s 100 -n 1 -r 0

What should I do next?  Should I capture some of the
tcpdump output or compile debugging or profiling into
the kernel for evaluation?

Thanks!

--- Trond Myklebust <trond.myklebust@fys.uio.no>
wrote:

> On Mon, 2007-05-21 at 07:18 -0700, John Frisk wrote:
> > Team,
> > I have been attempting to put together a linux HA
> NFS
> > server for my home environment.  I am currently
> > running two Debian etch 4.0 machines both running
> > vanilla 2.6.21.1 kernels that I compiled
> (exception
> > being the nvidia driver for video).  When I
> attempt to
> > do some performance benchmarks, a test of bonnie++
> > makes the NFS client stuck in a non-responsive
> > non-killable state.  The NFS server at this point
> is
> > not busy doing anything so I believe there may be
> some
> > condition leading to a deadlock in the client. 
> 
> Could you please try the patches
> 
>
http://client.linux-nfs.org/Linux-2.6.x/2.6.21/linux-2.6.21-002-no_congestion_wait_in_update_request.dif
>
http://client.linux-nfs.org/Linux-2.6.x/2.6.21/linux-2.6.21-003-cleanup_coalesce.dif
>
http://client.linux-nfs.org/Linux-2.6.x/2.6.21/linux-2.6.21-004-cleanup_coalesce2.dif
>
http://client.linux-nfs.org/Linux-2.6.x/2.6.21/linux-2.6.21-005-cleanup_readpages.dif
>
http://client.linux-nfs.org/Linux-2.6.x/2.6.21/linux-2.6.21-006-fix_dirtying_race.dif
>
http://client.linux-nfs.org/Linux-2.6.x/2.6.21/linux-2.6.21-007-fix_page_overflow.dif
> 
> and
> 
>
http://client.linux-nfs.org/Linux-2.6.x/2.6.22-rc2/linux-2.6.22-001-write_deadlock_avoidance.dif
> 
> That fixes all the write deadlock issues for me.
> 
> Trond
> 
> 



       
____________________________________________________________________________________Ready for the edge of your seat? 
Check out tonight's top picks on Yahoo! TV. 
http://tv.yahoo.com/

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

      reply	other threads:[~2007-05-21 18:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-21 14:18 NFS hang in 2.6.21.1 John Frisk
2007-05-21 16:56 ` Trond Myklebust
2007-05-21 18:37   ` John Frisk [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=174023.84136.qm@web54407.mail.yahoo.com \
    --to=john_a_frisk@yahoo.com \
    --cc=nfs@lists.sourceforge.net \
    /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.