From: Neil Brown <neilb@suse.de>
To: "Don Allingham" <Don.Allingham@dothill.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: NFS randomly denying permission to files
Date: Fri, 2 Feb 2007 12:23:25 +1100 [thread overview]
Message-ID: <17858.37517.24831.277303@notabene.brown> (raw)
In-Reply-To: message from Don Allingham on Thursday February 1
On Thursday February 1, Don.Allingham@dothill.com wrote:
>
> Kernel version for the server and clients are (uname -a):
>
> Linux vlsi-fs0 2.6.17-10-generic #2 SMP Tue Dec 5 21:16:35 UTC 2006 x86_64 GNU/Linux
>
> The no_subtree_check option seems to have made a big difference.
Hmmm... The bug I was thinking of (affected ext3 with dir_index if you
didn't use no_subtree_check) was fixed will before 2.6.17 came out.
What filesystem are you using? If ext3, what does
tune2fs -l /dev/XXXX
say (for the device holding the filesystem).
>
> I'm not familar with tcpdump. However, the new system is on a 1G
> ethernet link, and the old was on a 10/100 link. However, I will
> investigate this if I start seeing the problem again.
I wouldn't both. If no_subtree_check fixes it, then tcpdump won't
show us anything interesting.
NeilBrown
-------------------------------------------------------------------------
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
next prev parent reply other threads:[~2007-02-02 1:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-01 22:42 NFS randomly denying permission to files Don Allingham
2007-02-01 22:50 ` Neil Brown
2007-02-02 0:25 ` Don Allingham
2007-02-02 1:23 ` Neil Brown [this message]
2007-02-02 4:55 ` Don Allingham
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=17858.37517.24831.277303@notabene.brown \
--to=neilb@suse.de \
--cc=Don.Allingham@dothill.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox