From: Roman Mamedov <rm@romanrm.net>
To: Andrei Borzenkov <arvidjaar@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Is btrfs-convert able to deal with sparse files in a ext4 filesystem?
Date: Mon, 3 Apr 2017 13:41:39 +0500 [thread overview]
Message-ID: <20170403134139.5737bca7@natsu> (raw)
In-Reply-To: <c5472e71-908c-3d42-ee40-73d003bfc598@gmail.com>
On Sun, 2 Apr 2017 09:30:46 +0300
Andrei Borzenkov <arvidjaar@gmail.com> wrote:
> 02.04.2017 03:59, Duncan пишет:
> >
> > 4) In fact, since an in-place convert is almost certainly going to take
> > more time than a blow-away and restore from backup,
>
> This caught my eyes. Why? In-place convert just needs to recreate
> metadata. If you have multi-terabyte worth of data copying them twice
> hardly can be faster.
In-place convert is most certainly faster than copy-away and restore, in fact
it can be very fast if you use the option to not calculate checksums for the
entire filesystem's data (btrfs-convert -d).
--
With respect,
Roman
next prev parent reply other threads:[~2017-04-03 8:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-01 9:48 Is btrfs-convert able to deal with sparse files in a ext4 filesystem? Kai Herlemann
2017-04-01 19:13 ` Sean Greenslade
2017-04-02 0:59 ` Duncan
2017-04-02 6:30 ` Andrei Borzenkov
2017-04-03 8:41 ` Roman Mamedov [this message]
2017-04-07 3:26 ` Duncan
2017-04-03 1:04 ` Qu Wenruo
2017-04-03 12:32 ` Austin S. Hemmelgarn
2017-04-07 18:24 ` Kai Herlemann
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=20170403134139.5737bca7@natsu \
--to=rm@romanrm.net \
--cc=arvidjaar@gmail.com \
--cc=linux-btrfs@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