From: "Aurélien Aptel" <aaptel@suse.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>,
sfrench@samba.org, anna.schumaker@netapp.com,
trond.myklebust@hammerspace.com, fengxiaoli0714@gmail.com
Cc: fstests@vger.kernel.org, Murphy Zhou <xzhou@redhat.com>,
linux-cifs@vger.kernel.org, linux-nfs@vger.kernel.org,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: NFS & CIFS support dedupe now?? Was: Re: [PATCH] generic/517: notrun on NFS due to unaligned dedupe in test
Date: Fri, 31 May 2019 12:48:40 +0200 [thread overview]
Message-ID: <87woi6yk53.fsf@suse.com> (raw)
In-Reply-To: <20190530155851.GB5383@magnolia>
"Darrick J. Wong" <darrick.wong@oracle.com> writes:
> (Not sure about cifs, since I don't have a Windows Server handy)
>
> I'm not an expert in CIFS or NFS, so I'm asking: do either support
> dedupe or is this a kernel bug?
AFAIK, the SMB protocol has 2 ioctl to do server side copies:
- FSCTL_SRV_COPYCHUNK [1] generic
- FSCTL_DUPLICATE_EXTENTS_TO_FILE [2], only supported on windows "new" CoW
filesystem ReFS
Cheers,
1:https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-smb2/cd0162e4-7650-4293-8a2a-d696923203ef
2:https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-smb2/4f08d2f8-bd17-4181-9cec-54c4f6a1b439
--
Aurélien Aptel / SUSE Labs Samba Team
GPG: 1839 CB5F 9F5B FB9B AA97 8C99 03C8 A49B 521B D5D3
SUSE Linux GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Mary Higgins, Sri Rasiah HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2019-05-31 10:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 9:41 [PATCH] generic/517: notrun on NFS due to unaligned dedupe in test Murphy Zhou
2019-05-30 15:26 ` Darrick J. Wong
2019-05-30 15:55 ` Trond Myklebust
2019-05-30 16:03 ` Darrick J. Wong
2019-05-30 16:28 ` Trond Myklebust
2019-05-30 16:45 ` Darrick J. Wong
2019-05-30 15:58 ` NFS & CIFS support dedupe now?? Was: " Darrick J. Wong
2019-05-31 10:48 ` Aurélien Aptel [this message]
2019-05-31 13:28 ` Tom Talpey
2019-05-31 15:24 ` Olga Kornievskaia
2019-05-31 15:35 ` Trond Myklebust
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=87woi6yk53.fsf@suse.com \
--to=aaptel@suse.com \
--cc=anna.schumaker@netapp.com \
--cc=darrick.wong@oracle.com \
--cc=fengxiaoli0714@gmail.com \
--cc=fstests@vger.kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=sfrench@samba.org \
--cc=trond.myklebust@hammerspace.com \
--cc=xzhou@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.