From: Patrick Mau <mau@oscar.ping.de>
To: linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Cc: Mike Fedyk <mfedyk@matchmail.com>
Subject: Re: Fwd: Re: [2.6] nfs_rename: target $file busy, d_count=2
Date: Fri, 16 Jan 2004 14:03:36 +0100 [thread overview]
Message-ID: <20040116130336.GA5220@oscar.prima.de> (raw)
In-Reply-To: <20040116050642.GF1748@srv-lnx2600.matchmail.com>
On Thu, Jan 15, 2004 at 09:06:42PM -0800, Mike Fedyk wrote:
> On Thu, Jan 15, 2004 at 04:54:57PM -0800, Mike Fedyk wrote:
> > On Thu, Jan 15, 2004 at 04:03:46PM -0800, Mike Fedyk wrote:
> > > Both client and server are running the same 2.6.1-bk2 kernel with TCP-NFS.
> > > SMP, Highmem, & preempt.
> >
> > I have four clients that are all having this problem also, three 2.6, and
> > one 2.4 client.
> >
> > Using TCP-NFS they all have stale nfs handles even after a reboot (only
> > rebooted one to try with 2.4.23), but changed one to UDP-NFS, and it didn't
> > have the stale handles.
> >
> > Will do more testing with UDP-NFS.
>
> No, TCP and UDP NFS both get stale file handles. :(
>
> Can anyone reproduce?
Hi,
I was able to reproduce stale handles a long time ago.
A workable solution for me was to export using 'no_subtree_check'
on the server. Like this:
/data \
tony.local.net(rw,sync,no_root_squash,no_subtree_check) \
Could you please try and reply to my address if t works ?
Thanks,
Patrick
next prev parent reply other threads:[~2004-01-16 13:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-16 5:06 Fwd: Re: [2.6] nfs_rename: target $file busy, d_count=2 Mike Fedyk
2004-01-16 13:03 ` Patrick Mau [this message]
2004-01-16 18:40 ` Mike Fedyk
2004-01-16 18:55 ` Stale Filehandles was: " Mike Fedyk
2004-01-16 20:16 ` Mike Fedyk
[not found] ` <20040117184716.GX1748@srv-lnx2600.matchmail.com>
2004-01-20 20:12 ` [SOLVED] " Mike Fedyk
-- strict thread matches above, loose matches on Subject: below --
2004-01-16 5:14 Fwd: " Mike Fedyk
2004-01-16 5:06 Mike Fedyk
2004-01-16 1:22 Mike Fedyk
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=20040116130336.GA5220@oscar.prima.de \
--to=mau@oscar.ping.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mfedyk@matchmail.com \
--cc=netdev@oss.sgi.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 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.