From: Janos Farkas <chexum+dev@gmail.com>
To: Neil Brown <neilb@suse.de>
Cc: nfs@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: nfs problems with 2.6.18-rc1
Date: Mon, 17 Jul 2006 12:08:56 +0200 [thread overview]
Message-ID: <priv$efbe06145615$0a94d550eb@200607.gmail.com> (raw)
In-Reply-To: <17594.51834.20365.820166@cse.unsw.edu.au>
On 2006-07-17 at 09:23:38, Neil Brown wrote:
> On Thursday July 13, chexum+dev@gmail.com wrote:
> > I recently updated two (old) hosts to 2.6.18-rc1, and started noticing
> > weird things with the nfs mounted /home s.
> So this is both the client and the server that you upgraded? That
> makes is harder to point the finger of blame :-)
Yeah, smart thing :) Thank you for the response! When I have
downgraded the server to 2.6.17, none of those errors happened again.
(And I left the setup that way, because some programs have been
corrupting their config files because of the spurious read errors --
most notably zsh and firefox.)
> I wonder if that is pointing the finger at
>
> http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=8c7b389e532e964f07057dac8a56c43465544759
>
> as that is a recent change that returns 'EACCES'... but I cannot see
> that being relevant in this case as it only affects directories.
As far as I can see, that patch is from May 21st, and went in 17-rc5,
thus obviously 2.6.17 is newer than that... But a bunch of nfs changes
happened in 18-rc1.
> The standard answer for tracing nfs problems if 'tcpdump'.
> e.g.
> tcpdump -s 0 -w /tmp/trace host $CLIENT and host $SERVER and port 2049
>
> that should show whether the error is coming from the server, or if
> the client is generating it all by itself.
Well, I tried that, but I couldn't see errors flying on the wire. That
would point to flaws in the 18-rc1 client (but only surfacing with an
rc1 server?), or in my eyes :)
> Also turn on tracing. Something like:
> on server
> echo 32767 > /proc/sys/sunrpc/nfsd_debug
> on client
> echo 32767 > /proc/sys/sunrpc/nfs_debug
>
> You can be a bit more selective by only enabling individual flags.
> For the server, these are in include/linux/nfsd/debug.h
> You probably want FH, EXPORT AUTH PROC FILEOP
>
> For the client, they are near the end of include/linux/nfs_fs.h
> Not sure which to choose... maybe just all of them.
Thanks, that's probably what I've been looking for. I'll try to debug
this with a 2.6.18-rc2(client):2.6.17(server) and 2.6.18-rc2(both) setup
later this day, but those machines are currently in the process of
reorganizing their RAID config :)
--
Janos
romfs is at http://romfs.sourceforge.net/
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
WARNING: multiple messages have this Message-ID (diff)
From: Janos Farkas <chexum+dev@gmail.com>
To: Neil Brown <neilb@suse.de>
Cc: linux-kernel@vger.kernel.org, nfs@lists.sourceforge.net
Subject: Re: nfs problems with 2.6.18-rc1
Date: Mon, 17 Jul 2006 12:08:56 +0200 [thread overview]
Message-ID: <priv$efbe06145615$0a94d550eb@200607.gmail.com> (raw)
In-Reply-To: <17594.51834.20365.820166@cse.unsw.edu.au>
On 2006-07-17 at 09:23:38, Neil Brown wrote:
> On Thursday July 13, chexum+dev@gmail.com wrote:
> > I recently updated two (old) hosts to 2.6.18-rc1, and started noticing
> > weird things with the nfs mounted /home s.
> So this is both the client and the server that you upgraded? That
> makes is harder to point the finger of blame :-)
Yeah, smart thing :) Thank you for the response! When I have
downgraded the server to 2.6.17, none of those errors happened again.
(And I left the setup that way, because some programs have been
corrupting their config files because of the spurious read errors --
most notably zsh and firefox.)
> I wonder if that is pointing the finger at
>
> http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=8c7b389e532e964f07057dac8a56c43465544759
>
> as that is a recent change that returns 'EACCES'... but I cannot see
> that being relevant in this case as it only affects directories.
As far as I can see, that patch is from May 21st, and went in 17-rc5,
thus obviously 2.6.17 is newer than that... But a bunch of nfs changes
happened in 18-rc1.
> The standard answer for tracing nfs problems if 'tcpdump'.
> e.g.
> tcpdump -s 0 -w /tmp/trace host $CLIENT and host $SERVER and port 2049
>
> that should show whether the error is coming from the server, or if
> the client is generating it all by itself.
Well, I tried that, but I couldn't see errors flying on the wire. That
would point to flaws in the 18-rc1 client (but only surfacing with an
rc1 server?), or in my eyes :)
> Also turn on tracing. Something like:
> on server
> echo 32767 > /proc/sys/sunrpc/nfsd_debug
> on client
> echo 32767 > /proc/sys/sunrpc/nfs_debug
>
> You can be a bit more selective by only enabling individual flags.
> For the server, these are in include/linux/nfsd/debug.h
> You probably want FH, EXPORT AUTH PROC FILEOP
>
> For the client, they are near the end of include/linux/nfs_fs.h
> Not sure which to choose... maybe just all of them.
Thanks, that's probably what I've been looking for. I'll try to debug
this with a 2.6.18-rc2(client):2.6.17(server) and 2.6.18-rc2(both) setup
later this day, but those machines are currently in the process of
reorganizing their RAID config :)
--
Janos
romfs is at http://romfs.sourceforge.net/
next prev parent reply other threads:[~2006-07-17 10:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-13 18:22 nfs problems with 2.6.18-rc1 Janos Farkas
2006-07-13 18:22 ` Janos Farkas
2006-07-16 23:23 ` Neil Brown
2006-07-16 23:23 ` Neil Brown
2006-07-17 10:08 ` Janos Farkas [this message]
2006-07-17 10:08 ` Janos Farkas
2006-07-18 12:20 ` Janos Farkas
2006-07-18 12:20 ` Janos Farkas
2006-07-18 23:29 ` Neil Brown
2006-07-18 23:29 ` Neil Brown
2006-07-20 8:11 ` Frank van Maarseveen
2006-07-20 8:11 ` [NFS] " Frank van Maarseveen
2006-07-17 9:03 ` Tony Reix
2006-07-17 9:03 ` [NFS] " Tony Reix
2006-07-17 11:25 ` Janos Farkas
2006-07-17 11:25 ` Janos Farkas
-- strict thread matches above, loose matches on Subject: below --
2006-07-13 20:15 Ottman, Tom
2006-07-13 20:38 Gilman, Mark
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='priv$efbe06145615$0a94d550eb@200607.gmail.com' \
--to=chexum+dev@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--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.