From: Anna Schumaker <anna.schumaker@oracle.com>
To: Dan Shelton <dan.f.shelton@gmail.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: NFS4 "COPY" between exports on the same nfsd server?
Date: Fri, 22 Aug 2025 15:43:04 -0400 [thread overview]
Message-ID: <b06a4089-d29a-466b-8c3f-5d8a851276e2@oracle.com> (raw)
In-Reply-To: <CAAvCNcD3ncfvMnqeQMzQgE=qAD1JjwLYRHpN4mmGd+rS+czLJg@mail.gmail.com>
Hi Dan,
On 8/21/25 7:12 PM, Dan Shelton wrote:
> Hello!
>
> 2 questions about NFS4 "COPY":
>
> 1. Does the Linux nfsd require a special setup to allow NFS4 "COPY"
> between filesystem exports of the same nfsd, or will that "just work"
> out of the box?
This should just work out of the box.
>
> 2. If a NFS4 client does a "COPY" between exports of the same nfsd, is
> it sufficient just to have the stateid of src file and dest file?
It should be, yes. I did a quick test using the Linux client to Linux server,
and see that's exactly what the client sends the server.
I hope this helps,
Anna
>
> Dan
prev parent reply other threads:[~2025-08-22 19:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-21 23:12 NFS4 "COPY" between exports on the same nfsd server? Dan Shelton
2025-08-22 19:43 ` Anna Schumaker [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=b06a4089-d29a-466b-8c3f-5d8a851276e2@oracle.com \
--to=anna.schumaker@oracle.com \
--cc=dan.f.shelton@gmail.com \
--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