Linux NFS development
 help / color / mirror / Atom feed
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: Wed, 16 Mar 2005 13:32:50 +0100	[thread overview]
Message-ID: <42382772.9030303@drzeus.cx> (raw)
In-Reply-To: <20050315223125.GE11916@fieldses.org>

[-- Attachment #1: Type: text/plain, Size: 1143 bytes --]

J. Bruce Fields wrote:

>On Mon, Mar 14, 2005 at 05:03:16PM +0100, Pierre Ossman wrote:
>  
>
>>I've tried the patch and the problem remains.
>>
>>[root@apollo home]# ~/mv ~/freedesktop.org.xml .
>>Updating timestamps...done
>>Updating ownership...
>>
>>(this is my hacked mv which lists each operation as it is performed)
>>    
>>
>
>Hm.  Maybe my "mv" doesn't work quite the same as yours, but I'm not
>seeing this.  Could I see a raw packet trace?  (tcpdump s0 -wtmp, send
>me tmp.pcap).  Are you having any problems with rpc.idmapd dying on the
>server?
>  
>

No change in behaviour from the last attempt. idmapd keeps running just
fine.
Dump from new run included.

Previous test:
http://marc.theaimsgroup.com/?l=linux-nfs&m=110245477428548&w=4
http://marc.theaimsgroup.com/?l=linux-nfs&m=110250639332016&w=4

As I was playing around with idmapd (after running the test) it started
to work just fine. I am unable to reproduce the error now, even though
idmapd is started the same way as originally. A reboot might get the
error back but I can't test that on this machine. I'll see if I can find
another machine to torture.

Rgds
Pierre

[-- Attachment #2: tmp.pcap --]
[-- Type: application/octet-stream, Size: 8166 bytes --]

  reply	other threads:[~2005-03-16 12:33 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 [this message]
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=42382772.9030303@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