From: Roman Kagan <Roman.Kagan@itep.ru>
To: linux-kernel@vger.kernel.org
Subject: Re: Fwd: [2.6] nfs_rename: target $file busy, d_count=2
Date: Fri, 16 Jan 2004 15:32:32 +0300 [thread overview]
Message-ID: <20040116123232.GA22836@panda.itep.ru> (raw)
On Thu, Jan 16, 2004 at 05:01:12AM -0500, Mike Fedyk wrote:
> 1. nfs_rename: target $file busy, d_count=2
> 2. RPC request reserved 0 but used 40
>
> Hi, I'm getting [1] in kernel log on the nfs client, and [2] on the nfs server.
> After that I get nfs stale file handles.
I started to get "RPC request reserved 0 but used X" where X ranged from
24 to 32900, when I switched from NFS over UDP to NFS over TCP. Both
servers and clients are on vanilla 2.6.1, one of the servers exibiting
this does only readonly exports. There are no apparent effects
associated with that message, however the comment in svc_sock_release()
in net/sunrpc/svcsock.c says that it's an indication of a bug. I'll try
to run it with debugging enabled to see on which code path it happens.
I don't see your nfs_rename problem on the clients. Nor do they get
stale NFS handles: there used to be some until I added no_subtree_check
export option.
> Both client and server are running the same 2.6.1-bk2 kernel with TCP-NFS.
> SMP, Highmem, & preempt.
In my case UP, no highmem, no preempt.
Roman.
next reply other threads:[~2004-01-16 12:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-16 12:32 Roman Kagan [this message]
2004-01-16 13:43 ` Fwd: [2.6] nfs_rename: target $file busy, d_count=2 Trond Myklebust
-- strict thread matches above, loose matches on Subject: below --
2004-01-16 5:01 Mike Fedyk
2004-01-16 4:22 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=20040116123232.GA22836@panda.itep.ru \
--to=roman.kagan@itep.ru \
--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 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.