From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: Kai Herlemann <btrfs@linux.kai-herlemann.de>,
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 08:32:25 -0400 [thread overview]
Message-ID: <145e6e59-42d6-ca9b-1bfa-5f0249e930be@gmail.com> (raw)
In-Reply-To: <CADN-S7MzE=6x25DK0XOPzfBGCEpTjdUSokBkuCPGhCvCURzLPg@mail.gmail.com>
On 2017-04-01 05:48, Kai Herlemann wrote:
> Hi,
> I have on my ext4 filesystem some sparse files, mostly images from
> ext4 filesystems.
> Is btrfs-convert (4.9.1) able to deal with sparse files or can that
> cause any problems?
I would tend to agree with some of the other people who have commented
here, but with a slight twist:
If you just want to test BTRFS short-term, then in-place conversion is
fine. The moment you decide to keep using BTRFS for production systems,
you should be creating new filesystems instead of doing in-place conversion.
There are a couple of reasons for this:
1. In-place conversion will give you an inherently sub-optimal on-disk
data layout. You'll need some extra work to remedy this, and because of
that extra work, it will generally not be any quicker to convert
in-place than to create a new filesystem. You can of course choose not
to fix this, but performance will likely suffer. (This can also be
slightly mitigated by making sure to defragment the filesystem before
conversion).
2. Slightly related to 1, btrfs-convert can leave behind artifacts from
the conversion itself that may cause issues later.
3. Tying in with both 1 and 2, there's very little testing done on
converted filesystems. You are therefore by definition more likely to
run into bugs or other issues.
4. In-place conversion is inherently risky. If something goes wrong,
you're going to have to restore from a backup anyway.
next prev parent reply other threads:[~2017-04-03 12:32 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
2017-04-07 3:26 ` Duncan
2017-04-03 1:04 ` Qu Wenruo
2017-04-03 12:32 ` Austin S. Hemmelgarn [this message]
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=145e6e59-42d6-ca9b-1bfa-5f0249e930be@gmail.com \
--to=ahferroin7@gmail.com \
--cc=btrfs@linux.kai-herlemann.de \
--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 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.