mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Michael Loftis <mloftis@wgops.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.8 NFS not stateless and random failures?
Date: Mon, 16 Jan 2006 10:42:48 -0500	[thread overview]
Message-ID: <1137426168.7853.32.camel@lade.trondhjem.org> (raw)
In-Reply-To: <5B305675488C8F97FCE35455@dhcp-2-206.wgops.com>

On Mon, 2006-01-16 at 02:01 -0700, Michael Loftis wrote:
> (Sincere apologies if this gets posted twice, old habits die hard, and I 
> was posting to rutgers instead of kernel.org!)
> 
> We recently attempted to upgrade a completely working Linux 2.4 NFS 
> environment to 2.6 based server, nothing else has changed, at all, just the 
> server.
> 
> On with the show, when did the 2.6 series NFS lose it's stateless ability? 
> Now whenever I update NFS exports, or reboot the NFS server, I have to 
> remount or reboot all NFS clients now.  I thought part of the whole point 
> of NFS is it is stateless.  Indeed we didn't have this behavior before 
> 2.6...
> 
> Secondly we're getting weird intermittent failures, most easily seen by the 
> webservers with logs along the lines of below, apparently random, and 
> inconsistent.  I removed the particular path and client from the below log 
> entry.  There is NOT a permissions problem on these elements.  Subsequent 
> accesses will (usually) succeed.  Right after a reboot everything will be 
> fine for a while...then after a bit the webserver starts to get these 
> errors intermittently, with no apparent reasoning behind them.  Again, with 
> 2.4, we had nothing of the sort going on except in the (very very limited 
> and few) legitimate cases caused by customers setting incorrect perms.
> 
> [Sun Jan 15 12:14:00 2006] [error] [client a.b.c.d] (13)Permission denied: 
> access to /path... failed because search permissions are missing on a 
> component of the path
> 
> Debian 3.1 Kernel 2.6.8-2-686-smp w/ ReiserFS on LVM on a qlogic QLA2342 
> (2312) based PCI-X/133Mhz card.

AFAIK, most of these bugs have been fixed.

Please try to reproduce the problems on a more recent kernel, or get
Debian to backport the fixes.

Cheers,
  Trond


  reply	other threads:[~2006-01-16 15:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-16  9:01 Michael Loftis
2006-01-16 15:42 ` Trond Myklebust [this message]
2006-01-16 21:44   ` Michael Loftis

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=1137426168.7853.32.camel@lade.trondhjem.org \
    --to=trond.myklebust@fys.uio.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mloftis@wgops.com \
    /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

all inboxes | Powered by JetHome®