From: Filipe Manana <fdmanana@gmail.com>
To: Timofey Titovets <nefelim4ag@gmail.com>
Cc: Diagon <kernel.boxy@xoxy.net>, linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Copying between lzo compressed BtrFS's: de/re-compressing.
Date: Fri, 15 Jan 2016 12:25:51 +0000 [thread overview]
Message-ID: <CAL3q7H7pQ576qKqknWEA2Trgu4hn_6SV00vm2fLwz=_MJ8Nw2Q@mail.gmail.com> (raw)
In-Reply-To: <CAGqmi76EQ1NYFhp7hdwdrP0VTNXdSYgePje036UGRWDnUV=EWw@mail.gmail.com>
On Fri, Jan 15, 2016 at 9:56 AM, Timofey Titovets <nefelim4ag@gmail.com> wrote:
> 2016-01-15 12:00 GMT+03:00 Diagon <kernel.boxy@xoxy.net>:
>> I'm copying a large number of files between two lzo compressed BtrFS
>> filesystems on different drives mounted on the same machine. It appears
>> that the files are being de/re-compressed. Is there a way avoid this?
>
> If you just copy files, files will be decompressed while reading and
> recompressed while writing
> For avoiding this, you must use send receive feature
No, send/receive does not avoid decompression on the send side nor
re-compression at the receiving side. The receiving side writes the
data from a send stream, which is uncompressed, to the destination
filesystem using standard system calls like write/pwrite.
>
>
> --
> Have a nice day,
> Timofey.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Filipe David Manana,
"Reasonable men adapt themselves to the world.
Unreasonable men adapt the world to themselves.
That's why all progress depends on unreasonable men."
next prev parent reply other threads:[~2016-01-15 12:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-15 9:00 Copying between lzo compressed BtrFS's: de/re-compressing Diagon
2016-01-15 9:56 ` Timofey Titovets
2016-01-15 12:25 ` Filipe Manana [this message]
2016-01-15 12:28 ` Timofey Titovets
2016-01-17 20:42 ` Diagon
2016-01-17 21:27 ` Chris Murphy
2016-01-17 21:57 ` Diagon
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='CAL3q7H7pQ576qKqknWEA2Trgu4hn_6SV00vm2fLwz=_MJ8Nw2Q@mail.gmail.com' \
--to=fdmanana@gmail.com \
--cc=kernel.boxy@xoxy.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=nefelim4ag@gmail.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;
as well as URLs for NNTP newsgroup(s).