From: Pierre Ossman <drzeus-list@drzeus.cx>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: nfs@lists.sourceforge.net
Subject: Re: Move (mv) hangs with NFSv4
Date: Sun, 13 Mar 2005 17:36:37 +0100 [thread overview]
Message-ID: <42346C15.4080402@drzeus.cx> (raw)
In-Reply-To: <20050312185119.GA1064@fieldses.org>
J. Bruce Fields wrote:
>On Sun, Jan 02, 2005 at 07:48:54PM +0100, Pierre Ossman wrote:
>
>
>>>J. Bruce Fields wrote:
>>>
>>>
>>>>Thanks. It's a problem with the idmapping on the server, argh. Is
>>>>rpc.idmapd still running after this, or does it die?--b.
>>>>
>>>>
>>>>
>>>>
>>>It's still running. The effect is only local to the mv process. Other
>>>traffic to the same mount continue to work perfectly. There has been a
>>>few incidents where the entire mount hangs. But in these cases I have to
>>>restart the client, not the server.
>>>
>>>Can I get some debug output from idmapd that will pinpoint where the
>>>problem is?
>>>
>>>
>>>
>>Any updates to this issue?
>>
>>
>
>Sorry for the overly long delay on the response. Cleaning out my inbox
>prompted me to look back at this issue. I did find one bug in the ACL
>code which could cause a "mv" with the target on an NFSv4 partition to
>fail. Other than that I can't reproduce any problems with move.
>
>It's possible we've fixed something since the beginning of the year, or
>it's possible something else is going on. If you get the chance to
>retest with our latest patches, let me know.
>
>--b.
>
>
Ehm... where would these patches be located? I didn't see anything
obvious on the web page for any recent kernel. Or perhaps you meant the
lats nfs-utils? or both? =)
Rgds
Pierre
-------------------------------------------------------
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
next prev parent reply other threads:[~2005-03-13 16:36 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 [this message]
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=42346C15.4080402@drzeus.cx \
--to=drzeus-list@drzeus.cx \
--cc=bfields@fieldses.org \
--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