mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chuck Lever III <chuck.lever@oracle.com>
To: Igor Mammedov <imammedo@redhat.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1] NFSD: Decode NFSv4 birth time attribute
Date: Tue, 12 Jul 2022 13:46:33 +0000	[thread overview]
Message-ID: <78752B5D-7D24-4856-A368-5C4633CDF491@oracle.com> (raw)
In-Reply-To: <20220712100900.1c8b18dc@redhat.com>


> On Jul 12, 2022, at 4:09 AM, Igor Mammedov <imammedo@redhat.com> wrote:
> 
> On Mon, 11 Jul 2022 17:18:38 +0000
> Chuck Lever III <chuck.lever@oracle.com> wrote:
> 
>>> On Jul 11, 2022, at 1:14 PM, Igor Mammedov <imammedo@redhat.com> wrote:
>>> 
>>> on tangent:
>>> when copying file from Mac (used 'cp') there is a delay ~4sec/file
>>> 'cp' does first triggers create then extra open and then setattr
>>> which returns
>>> SETATTR Status: NFS4ERR_DELAY
>>> after which the client stalls for a few seconds before repeating setattr.
>>> So question is what makes server unhappy to trigger this error
>>> and if it could be fixed on server side.
>>> 
>>> it seems to affect other methods of copying. So if one extracted
>>> an archive with multiple files or copied multiple files, that
>>> would be a pain.
>>> 
>>> With vers=3 copying is 'instant'
>>> with linux client and vers=4.0 copying is 'instant' as well but it
>>> doesn't use the same call sequence.
>>> 
>>> PS:
>>> it is not regression (I think slowness was there for a long time) 
>> 
>> A network capture would help diagnose this further, but it
>> sounds like it's delegation-related.
> yep, there was delegation request/response right after SETATTR failure
> possibly prompted by NFS4ERR_DELAY
> 
> shall I provide a network capture (I guess pcap file) from test env
> I have?

Yes, you can send it directly to me.


--
Chuck Lever




      reply	other threads:[~2022-07-12 13:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-10 18:46 Chuck Lever
2022-07-11 11:36 ` Jeff Layton
2022-07-11 14:29   ` Chuck Lever III
2022-07-11 14:46     ` Jeff Layton
2022-07-11 14:56       ` Chuck Lever III
2022-07-11 17:14 ` Igor Mammedov
2022-07-11 17:18   ` Chuck Lever III
2022-07-12  8:09     ` Igor Mammedov
2022-07-12 13:46       ` Chuck Lever III [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=78752B5D-7D24-4856-A368-5C4633CDF491@oracle.com \
    --to=chuck.lever@oracle.com \
    --cc=imammedo@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®