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.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
