linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Btrfs balance bug
Date: Thu, 3 Oct 2013 11:45:31 +0000 (UTC)	[thread overview]
Message-ID: <pan$a0456$a7c238f0$83bcabb4$dcdfc7c5@cox.net> (raw)
In-Reply-To: CADef55pBMJ-oeOLy9Z3AeP7iRyFqm6fNfuS8BNm0qbDk876SwQ@mail.gmail.com

Slava Barinov posted on Thu, 03 Oct 2013 08:50:06 +0400 as excerpted:

> Good day.
> 
>   I've got a failure with btrfs balance. In fact I started btrfs balance
>   /btr and got a total filesystem freeze. After I tried applying balance
>   pause or balance cancel the following crashdump appeared and btrfs
>   tool freezed.
>   Reboot changed nothing: I've got totally the same crashdump.
>   So I mounted filesystem with skip_balance option and tried to cancel
>   balance. It worked. Then I performed a btrfsck on my fs and it found
>   nothing suspicious. So I believe it is just a balance bug. I suppose
>   that could be because of lack of free space on device but should not
>   filesystem reject balancing instead of crashing?
> 
> [  117.078876] btrfs: continuing balance

> ------------[ cut here ]------------
> [  152.195487] kernel BUG at fs/btrfs/relocation.c:1055!
> [  152.198432] invalid opcode: 0000 [#1] SMP

> # btrfs --version Btrfs v0.20-rc1-358-g194aa4a
> 
> Kernel is just 3.11.3-gentoo. -ray is my machine config and several
> custom modules which are not loaded now.

Greetings fellow gentooer! =:^)


IIRC balances bugging out with invalid opcode 0000, but working properly 
on a fresh boot, were a known issue on 3.11.  I know I had the problem 
here.

I /believe/ that issue was fixed by a patch that went in between 3.12-rc1 
and 3.12-rc2, and I /think/ the same patch is queued for stable, but due 
to a miscommunication with Greg KH where he was waiting on the btrfs 
folks who were waiting on him, the btrfs patches for stable didn't make 
it into 3.11.3.  However, it /should/ be in the /next/ set 3.11-stable 
release, as they uncrossed their signals and GKH said he'd pull them this 
time.  (You can see the thread for the crossed signals just a couple days 
ago I think, on this list.  Of course the thread for that patch and the 
reports of problems without it will be back a bit further...)

-- 
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:[~2013-10-03 11:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-03  4:50 Btrfs balance bug Slava Barinov
2013-10-03 11:45 ` Duncan [this message]
2013-10-03 11:56   ` Holger Hoffstaette
2013-10-03 13:48     ` Duncan

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$a0456$a7c238f0$83bcabb4$dcdfc7c5@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;
as well as URLs for NNTP newsgroup(s).