From: "J. K. Cliburn" <jcliburn@gmail.com>
To: Grant Coady <gcoady.lk@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
neilb@suse.de, bfields@fieldses.org, linux-nfs@vger.kernel.org
Subject: Re: NFS regression? Odd delays and lockups accessing an NFS export.
Date: Mon, 18 Aug 2008 14:37:45 -0500 [thread overview]
Message-ID: <48A9CF89.9090304@bellsouth.net> (raw)
In-Reply-To: <20080818185048.GO20684@miggy.org>
Athanasius wrote:
> On Mon, Aug 18, 2008 at 12:02:20PM +1000, Grant Coady wrote:
>> I've been using NFS here for years, lately there's something odd going on
>> since about a month or so. Previously reported last month:
>> http://www.gossamer-threads.com/lists/linux/kernel/951419?page=last
>>
>> Now with 2.6.27-rc3 on one of the client boxes I get a complete stall
>> at odd times when accessing the server's exported directory, cannot
>> see a pattern to it. Eventually recovers after a Ctrl-C. Nothing in
>> the server or client log files. Not easy to reproduce either.
>
> I wonder if this is what I've been seeing. I've been otherwise too
> busy to properly report it, thinking that *someone* else must also be
> seeing it and it's being worked on, else it's a subtle configuration
> problem my end.
>
> I first started seeing this with 2.6.26 on the client end,
I see you're running the atl1 driver on your client. I'm chasing an
intermittent bug in that driver that seems to be affected by certain
offload parameters. Try disabling TSO and see if things improve.
ethtool -K eth0 tso off
Let me know if it helps.
Jay
next prev parent reply other threads:[~2008-08-18 19:41 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-18 2:02 NFS regression? Odd delays and lockups accessing an NFS export Grant Coady
2008-08-18 18:50 ` Athanasius
2008-08-18 19:19 ` Trond Myklebust
2008-08-18 19:37 ` J. K. Cliburn [this message]
2008-08-18 23:13 ` Athanasius
2009-05-12 20:27 ` Frank Filz
2009-05-13 0:05 ` Jay Cliburn
2008-08-18 19:20 ` Trond Myklebust
2008-08-20 1:10 ` Grant Coady
2008-08-20 23:17 ` Grant Coady
2008-08-22 10:23 ` Ian Campbell
2008-08-22 18:08 ` Trond Myklebust
2008-08-22 18:13 ` Ian Campbell
2008-08-22 19:33 ` John Ronciak
2008-08-22 20:00 ` Ian Campbell
2008-08-22 21:15 ` John Ronciak
2008-08-22 21:23 ` Trond Myklebust
2008-08-22 21:37 ` Ian Campbell
2008-08-22 21:56 ` Trond Myklebust
2008-08-22 22:41 ` Ian Campbell
2008-08-24 18:53 ` Ian Campbell
2008-08-24 19:17 ` Trond Myklebust
2008-08-24 19:19 ` Trond Myklebust
2008-08-24 22:09 ` Ian Campbell
2008-08-24 22:15 ` Trond Myklebust
2008-08-25 9:59 ` Ian Campbell
2008-08-25 16:04 ` Tom Tucker
2008-08-25 16:54 ` Trond Myklebust
2008-08-25 20:15 ` Tom Tucker
2008-08-26 19:27 ` J. Bruce Fields
2008-08-27 14:43 ` Tom Tucker
2008-08-30 15:47 ` Ian Campbell
2008-08-31 19:30 ` J. Bruce Fields
2008-08-31 19:44 ` Ian Campbell
2008-08-31 19:46 ` J. Bruce Fields
2008-08-31 19:49 ` Ian Campbell
2008-08-31 19:51 ` Tom Tucker
2008-08-31 19:51 ` Tom Tucker
2008-08-31 21:18 ` Ian Campbell
2008-09-01 17:20 ` Tom Tucker
2008-09-01 17:46 ` Ian Campbell
2008-09-10 8:40 ` Ian Campbell
2008-09-12 22:43 ` J. Bruce Fields
2008-09-12 23:15 ` Tom Tucker
2008-09-13 8:57 ` Ian Campbell
2008-09-16 5:48 ` Ian Campbell
2008-09-16 11:38 ` Tom Tucker
2008-09-16 15:03 ` Ian Campbell
2008-09-16 15:58 ` Tom Tucker
2008-09-16 16:24 ` Ian Campbell
2008-09-23 7:59 ` Ian Campbell
2008-09-23 11:33 ` Ian Campbell
2008-09-23 17:03 ` J. Bruce Fields
2008-09-26 15:37 ` Ian Campbell
2008-09-26 18:17 ` Ian Campbell
2008-09-27 3:54 ` J. Bruce Fields
2008-09-27 10:16 ` Ian Campbell
2008-08-25 21:39 ` Roger Heflin
2008-08-25 20:23 ` Grant Coady
2008-08-25 22:11 ` Trond Myklebust
2008-08-26 0:29 ` Grant Coady
2008-08-26 0:59 ` Muntz, Daniel
2008-08-26 1:06 ` Grant Coady
-- strict thread matches above, loose matches on Subject: below --
2008-09-10 2:51 Benoit Plessis
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=48A9CF89.9090304@bellsouth.net \
--to=jcliburn@gmail.com \
--cc=bfields@fieldses.org \
--cc=gcoady.lk@gmail.com \
--cc=jacliburn@bellsouth.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
/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