Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Error while balance after convert from ext4
Date: Wed, 8 Jul 2015 23:32:55 +0000 (UTC)	[thread overview]
Message-ID: <pan$cc970$278beac6$e66cdc18$1262676c@cox.net> (raw)
In-Reply-To: CAFdkf7PPbH0mw1KW2TkkF5bm=cjN2iJEOzZwVAxh0f1xzjDWuA@mail.gmail.com

Николай Овчинников posted
on Wed, 08 Jul 2015 22:38:20 +0300 as excerpted:

[Rearranged to standard quote, reply-in-context, format.  It makes 
replying and following replies on mailing lists FAR easier.]

> 2015-07-08 16:56 GMT+03:00 Chris Murphy <lists@colorremedies.com>:
>> I've reproduced this bug with a brand new ext4 system, converted with
>> btrfs-progs 4.1 and a 4.1 kernel. The conversion is OK. And btrfs check
>> is ok after conversion, after removing the ext2_saved snapshot, and
>> after defrag. The implosion happens on balance and the fs goes read
>> only.

> What about btrfsck and btrfs-image errors?

C Murphy mentioned btrfs check (saying it was fine after conversion).  
Btrfsck is now the check subcommand under the primary btrfs tool, with 
the standalone btrfsck deprecated and to be removed after a few 
transition releases.

But he didn't cover btrfs-image.  Valid point/question there.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman


  reply	other threads:[~2015-07-08 23:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-07 21:46 Error while balance after convert from ext4 Николай Овчинников
2015-07-08  0:18 ` Duncan
2015-07-08 13:56 ` Chris Murphy
2015-07-08 19:38   ` Николай Овчинников
2015-07-08 23:32     ` Duncan [this message]
2015-07-08 23:58       ` Николай Овчинников
2015-07-09  0:37     ` Chris Murphy
2015-07-09  1:55       ` 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='pan$cc970$278beac6$e66cdc18$1262676c@cox.net' \
    --to=1i5t5.duncan@cox.net \
    --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