From: Sean Greenslade <sean@seangreenslade.com>
To: Kai Herlemann <btrfs@linux.kai-herlemann.de>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Is btrfs-convert able to deal with sparse files in a ext4 filesystem?
Date: Sat, 1 Apr 2017 12:13:57 -0700 [thread overview]
Message-ID: <20170401191357.GA25721@coach> (raw)
In-Reply-To: <CADN-S7MzE=6x25DK0XOPzfBGCEpTjdUSokBkuCPGhCvCURzLPg@mail.gmail.com>
On Sat, Apr 01, 2017 at 11:48:50AM +0200, 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?
>From personal experience, I would recommend not using btrfs-convert on
ext4 partitions. I attempted it on a /home partition on one of my
machines, and while it did succeed in converting, the fs it produced had
weird issues that caused transation failures and thus semi-frequent
remount-ro. Btrfs-check, scrub, and balance were all unable to repair
the damage. I ended up recreating the parition from a backup.
As far as I know, there were no sparse files on this partition, either.
Just my one data point, for whatever it's worth.
--Sean
next prev parent reply other threads:[~2017-04-01 19:14 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 [this message]
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
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=20170401191357.GA25721@coach \
--to=sean@seangreenslade.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox