From: Marc Joliet <marcec@gmx.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs partition converted from ext4 becomes read-only minutes after booting: WARNING: CPU: 2 PID: 2777 at ../fs/btrfs/super.c:260 __btrfs_abort_transaction+0x4b/0x120
Date: Wed, 17 Jun 2015 21:41:00 +0200 [thread overview]
Message-ID: <20150617214100.467a0cd7@thetick> (raw)
In-Reply-To: <20150617174630.GM16468@merlins.org>
[-- Attachment #1: Type: text/plain, Size: 773 bytes --]
Am Wed, 17 Jun 2015 10:46:30 -0700
schrieb Marc MERLIN <marc@merlins.org>:
> I tried ext4 to btrfs once a year ago and it severely mangled my
> filesystem.
> I looked at it as a cool feature/hack that may have worked some time ago, but
> that no one really uses anymore, and that may not work right at this
> point.
Just another data point: when I switched to btrfs in the middle of last year I
used btrfs-convert on two file systems (an SSD and my backup partition on a
USB 3.0 HDD), and it worked in both cases (i.e., no data loss). I did see some
strange balance issues (see the ML archives), but IIRC nothing really serious.
--
Marc Joliet
--
"People who think they know everything really annoy those of us who know we
don't" - Bjarne Stroustrup
[-- Attachment #2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-06-17 19:41 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-12 12:19 btrfs partition converted from ext4 becomes read-only minutes after booting: WARNING: CPU: 2 PID: 2777 at ../fs/btrfs/super.c:260 __btrfs_abort_transaction+0x4b/0x120 Robert Munteanu
2015-06-17 17:46 ` Marc MERLIN
2015-06-17 19:41 ` Marc Joliet [this message]
2015-06-18 11:05 ` Robert Munteanu
2015-06-25 4:16 ` Marc MERLIN
2015-06-25 12:08 ` Vytautas D
[not found] ` <CABE5tBasBsycy_+q=RZj1dpqsLTREJTA72F-ZwNLt=kLX6wXhg@mail.gmail.com>
2015-06-25 21:09 ` Marc MERLIN
2015-06-17 18:48 ` Jeff Mahoney
2015-06-18 11:08 ` Robert Munteanu
2015-06-26 1:54 ` Qu Wenruo
2015-06-26 2:08 ` Qu Wenruo
2015-07-09 3:09 ` Chris Murphy
2015-07-09 10:52 ` Vytautas D
[not found] ` <CAO5K3OcA1_Z4-jvv_2C0StBkOr++_vUX4kOspY8cuhnX2t3z_A@mail.gmail.com>
2015-07-09 21:38 ` Chris Murphy
2015-07-10 0:34 ` Qu Wenruo
2015-07-10 0:45 ` Chris Murphy
2015-07-10 4:45 ` Qu Wenruo
2015-07-14 23:29 ` Chris Murphy
2015-07-26 21:47 ` Robert Munteanu
2015-07-30 13:16 ` Robert Munteanu
2015-07-31 2:08 ` Qu Wenruo
2015-07-31 13:38 ` Robert Munteanu
2015-08-03 0:54 ` Qu Wenruo
2015-08-03 1:22 ` Qu Wenruo
2015-08-03 7:45 ` Robert Munteanu
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=20150617214100.467a0cd7@thetick \
--to=marcec@gmx.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;
as well as URLs for NNTP newsgroup(s).