From: David Disseldorp <ddiss@samba.org>
To: Andrei Borzenkov <arvidjaar@gmail.com>
Cc: Newbugreport <newbugreport@protonmail.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Btrfs send bloat
Date: Mon, 20 May 2019 11:20:26 +0200 [thread overview]
Message-ID: <20190520112026.385537ca@samba.org> (raw)
In-Reply-To: <275f7add-382c-bf6d-4cf8-f9823cf55daf@gmail.com>
On Sun, 19 May 2019 23:06:25 +0300, Andrei Borzenkov wrote:
> 19.05.2019 11:11, Newbugreport пишет:
> > I have 3-4 years worth of snapshots I use for backup purposes. I keep
> > R-O live snapshots, two local backups, and AWS Glacier Deep Freeze. I
> > use both send | receive and send > file. This works well but I get
> > massive deltas when files are moved around in a GUI via samba.
>
> Did you analyze whether it is client or server problem? If client does
> file copy (instead of move as you imply) may be the simplest solution
> would be to use different tool on client. If problem is on server side,
> it is something to discuss with SAMBA folks.
Samba supports copy offload via FSCTL_SRV_COPYCHUNK and
FSCTL_DUPLICATE_EXTENTS_TO_FILE, which can be translated to
BTRFS_IOC_CLONE_RANGE via the btrfs Samba VFS module.
Windows explorer and Linux (cifs.ko) are capable of using these
fsctls during copy.
See https://wiki.samba.org/index.php/Server-Side_Copy for details.
Cheers, David
next prev parent reply other threads:[~2019-05-20 9:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-19 8:11 Btrfs send bloat Newbugreport
2019-05-19 20:06 ` Andrei Borzenkov
2019-05-20 9:20 ` David Disseldorp [this message]
2019-05-20 10:34 ` Patrik Lundquist
2019-05-20 11:15 ` Newbugreport
2019-05-20 11:58 ` Austin S. Hemmelgarn
2019-05-20 12:14 ` Patrik Lundquist
2019-05-20 12:40 ` Btrfs remote reflink with Samba David Disseldorp
2019-05-20 20:33 ` Patrik Lundquist
2019-05-20 22:50 ` Chris Murphy
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=20190520112026.385537ca@samba.org \
--to=ddiss@samba.org \
--cc=arvidjaar@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=newbugreport@protonmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox