Linux NFS development
 help / color / mirror / Atom feed
From: Pierre Ossman <drzeus-list@drzeus.cx>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>, nfs@lists.sourceforge.net
Subject: Re: Move (mv) hangs with NFSv4
Date: Tue, 07 Dec 2004 22:11:37 +0100	[thread overview]
Message-ID: <41B61C89.2060000@drzeus.cx> (raw)
In-Reply-To: <20041207155227.GG31250@fieldses.org>

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

J. Bruce Fields wrote:

>
>Hm.  With our latest kernel and user utilities I actually get a segfault
>on cp -a from the getxattr to get the acl on the source file.  Probably
>a bug our modified libacl, ugh.  In any case, probably also a different
>bug from what he's seeing.  Maybe I could see a pcap file or an strace
>of the cp -a showing where it hangs?
>
>  
>
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'.

Rgds
Pierre


[-- Attachment #2: nfsbug.dump --]
[-- Type: application/octet-stream, Size: 9604 bytes --]

  reply	other threads:[~2004-12-07 21:11 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 [this message]
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

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=41B61C89.2060000@drzeus.cx \
    --to=drzeus-list@drzeus.cx \
    --cc=bfields@fieldses.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox