From: "J. Bruce Fields" <bfields@fieldses.org>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>, nfs@lists.sourceforge.net
Subject: Re: Move (mv) hangs with NFSv4
Date: Tue, 7 Dec 2004 16:17:15 -0500 [thread overview]
Message-ID: <20041207211715.GQ31250@fieldses.org> (raw)
In-Reply-To: <41B61C89.2060000@drzeus.cx>
On Tue, Dec 07, 2004 at 10:11:37PM +0100, Pierre Ossman wrote:
> Here's a tcpdump of the transfer (I figure that's what you mean with a
> pcap file). The last couple of packets keep repeating themselves so the
> line never goes quiet (until I ^C).
> The transfer is a mv of a empty file named 'foo'.
Thanks. It's a problem with the idmapping on the server, argh. Is
rpc.idmapd still running after this, or does it die?--b.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2004-12-07 21:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-03 17:51 Move (mv) hangs with NFSv4 Pierre Ossman
2004-12-03 18:18 ` Trond Myklebust
2004-12-07 15:52 ` J. Bruce Fields
2004-12-07 21:11 ` Pierre Ossman
2004-12-07 21:17 ` J. Bruce Fields [this message]
2004-12-08 11:44 ` Pierre Ossman
2005-01-02 18:48 ` Pierre Ossman
2005-03-12 18:51 ` J. Bruce Fields
2005-03-13 16:36 ` Pierre Ossman
2005-03-13 16:48 ` J. Bruce Fields
2005-03-14 16:03 ` Pierre Ossman
2005-03-15 22:31 ` J. Bruce Fields
2005-03-16 12:32 ` Pierre Ossman
2005-03-16 17:47 ` J. Bruce Fields
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=20041207211715.GQ31250@fieldses.org \
--to=bfields@fieldses.org \
--cc=drzeus-list@drzeus.cx \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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.