From: Hugo Mills <hugo@carfax.org.uk>
To: Marc MERLIN <marc@merlins.org>
Cc: Chris Murphy <lists@colorremedies.com>,
Duncan <1i5t5.duncan@cox.net>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: BTRFS converted from EXT4 becomes read-only after reboot
Date: Tue, 23 May 2017 21:51:49 +0000 [thread overview]
Message-ID: <20170523215149.GA2633@carfax.org.uk> (raw)
In-Reply-To: <20170523214943.GN29894@merlins.org>
[-- Attachment #1: Type: text/plain, Size: 1066 bytes --]
On Tue, May 23, 2017 at 02:49:43PM -0700, Marc MERLIN wrote:
> On Tue, May 23, 2017 at 03:38:01PM -0600, Chris Murphy wrote:
> > > I've tried an ext4 to btrfs conversion 3 times in the last 3 years, it
> > > never worked properly any of those times, sadly.
> >
> > Since the 4.6 total rewrite? There are also recent bug fixes related
> > to convert in the changelog, it should be working now and if there are
> > problems Qu is probably interested in getting them fixed.
>
> It was a 4.9 kernel from debian.
It's the userspace tools that make the difference here (and what
Chris was referring to). Conversion has nothing to do with the kernel.
Hugo.
> The conversion looked like it worked, I rebooted ok, and then it got
> corrupted quickly after I deleted the subvolumes that had the old ext4 data.
> I've since wiped that disk and done a fresh btrfs install on it, because I
> had to get some work done :)
>
> Marc
--
Hugo Mills | Essex: a branch of philothophy.
hugo@... carfax.org.uk |
http://carfax.org.uk/ |
PGP: E2AB1DE4 |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2017-05-23 21:52 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 20:28 BTRFS converted from EXT4 becomes read-only after reboot Alexandru Guzu
2017-05-03 22:18 ` Chris Murphy
2017-05-04 3:55 ` Duncan
2017-05-23 17:00 ` Marc MERLIN
2017-05-23 21:38 ` Chris Murphy
2017-05-23 21:49 ` Marc MERLIN
2017-05-23 21:51 ` Chris Murphy
2017-05-23 21:53 ` Marc MERLIN
2017-05-23 22:02 ` Marc MERLIN
2017-05-23 21:51 ` Hugo Mills [this message]
2017-05-24 4:03 ` Andrei Borzenkov
[not found] ` <CAPktuGtqt-tVNvbxkdaEB7PshWVpDHsxfHYMujOkAvOP9aiJ6w@mail.gmail.com>
2017-05-05 15:40 ` Chris Murphy
[not found] ` <CAPktuGtTVMFcrh1QRgnXXiS9HvrKDEYK9kAumUGToY+ycaMoCA@mail.gmail.com>
2017-05-05 21:26 ` Chris Murphy
2017-05-07 17:32 ` Sean Greenslade
2017-05-08 14:16 ` Alexandru Guzu
2017-05-08 15:28 ` Sanidhya Solanki
2017-05-08 16:22 ` Sean Greenslade
2017-05-08 16:41 ` Austin S. Hemmelgarn
2017-05-08 17:01 ` Sean Greenslade
2017-05-08 18:22 ` Alexandru Guzu
2017-05-08 19:02 ` Sean Greenslade
2017-05-08 19:15 ` Alexandru Guzu
2017-05-08 19:30 ` Chris Murphy
2017-05-08 19:09 ` Chris Murphy
2017-05-08 19:05 ` Chris Murphy
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=20170523215149.GA2633@carfax.org.uk \
--to=hugo@carfax.org.uk \
--cc=1i5t5.duncan@cox.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=marc@merlins.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).