From: Leho Kraav <leho@kraav.com>
To: Ilya Dryomov <idryomov@gmail.com>
Cc: Daniel J Blueman <daniel@quora.org>,
Linux BTRFS <linux-btrfs@vger.kernel.org>,
Liu Bo <liubo2009@cn.fujitsu.com>
Subject: Re: btrfs 3.2.2 -> 3.3.1 upgrade finally ate babies, some advice?
Date: Tue, 10 Apr 2012 18:31:57 +0300 [thread overview]
Message-ID: <4F84526D.1070207@kraav.com> (raw)
In-Reply-To: <20120410090718.GA2345@zambezi.lan>
On 10.04.2012 12:07, Ilya Dryomov wrote:
> On Tue, Apr 10, 2012 at 01:19:54AM +0200, David Sterba wrote:
>>
>> IIRC somebody reported similar problem recently. It basically means
>> there's an inconsistent balance state. Adding Ilya to CC.
>
> Leho, so you just mount with discard patch and run 'btrfs fi balance
> <mnt>', correct ?
>
> The problem is that you have balance state on disk (from trying to run
> balance earlier w/o discard patch) but we are failing to pick it up on
> mount.
>
> Could you please post the entire dmesg and the output of
> 'btrfs-debug-tree -d<dev>' somewhere ?
>
> Could you also apply the debug patch below, mount your fs and send me
> dmesg output (no need to run balance, just mount) ?
>
Your understanding of situation based on above is correct.
Yes I can do all the stuff, but it's going to take until next week,
since I'm travelling and I can't risk BUG-ing my server remotely.
next prev parent reply other threads:[~2012-04-10 15:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-09 14:35 btrfs 3.2.2 -> 3.3.1 upgrade finally ate babies, some advice? Daniel J Blueman
2012-04-09 14:44 ` Leho Kraav
2012-04-09 14:54 ` Daniel J Blueman
2012-04-09 19:07 ` Martin Steigerwald
2012-04-09 20:58 ` Leho Kraav
2012-04-09 21:32 ` Leho Kraav
2012-04-09 23:19 ` David Sterba
2012-04-10 9:07 ` Ilya Dryomov
2012-04-10 15:31 ` Leho Kraav [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-04-09 13:24 Leho Kraav
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=4F84526D.1070207@kraav.com \
--to=leho@kraav.com \
--cc=daniel@quora.org \
--cc=idryomov@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=liubo2009@cn.fujitsu.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.