From: Mike Fedyk <mfedyk@matchmail.com>
To: linux-kernel@vger.kernel.org
Subject: Fwd: Re: [2.6] nfs_rename: target $file busy, d_count=2
Date: Thu, 15 Jan 2004 21:06:13 -0800 [thread overview]
Message-ID: <20040116050613.GE1748@srv-lnx2600.matchmail.com> (raw)
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.
Mike
----- End forwarded message -----
next reply other threads:[~2004-01-16 5:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-16 5:06 Mike Fedyk [this message]
2004-01-16 5:28 ` Trying to make a module Kuroi
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
2004-01-16 5:14 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=20040116050613.GE1748@srv-lnx2600.matchmail.com \
--to=mfedyk@matchmail.com \
--cc=linux-kernel@vger.kernel.org \
/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®