From: "J. Bruce Fields" <bfields@fieldses.org>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: nfs@lists.sourceforge.net
Subject: Re: Move (mv) hangs with NFSv4
Date: Wed, 16 Mar 2005 12:47:04 -0500 [thread overview]
Message-ID: <20050316174704.GD21258@fieldses.org> (raw)
In-Reply-To: <42382772.9030303@drzeus.cx>
On Wed, Mar 16, 2005 at 01:32:50PM +0100, Pierre Ossman wrote:
> No change in behaviour from the last attempt. idmapd keeps running just
> fine.
> Dump from new run included.
OK, thanks for the data. It still looks like a server-side idmapping
problem. Next time it gets into this state, it would be interesting to
know whether sending rpc.idmapd a SIGHUP (or just restarting it) makes
any difference. I'll try to find the time to investigate further
later this week....--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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2005-03-16 17:46 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
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 [this message]
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=20050316174704.GD21258@fieldses.org \
--to=bfields@fieldses.org \
--cc=drzeus-list@drzeus.cx \
--cc=nfs@lists.sourceforge.net \
/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