From: Sander <sander@humilis.net>
To: Josef Bacik <josef@redhat.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: kernel BUG at fs/btrfs/volumes.c:2733
Date: Thu, 29 Mar 2012 16:39:29 +0200 [thread overview]
Message-ID: <20120329143929.GB29741@panda> (raw)
In-Reply-To: <20120329131638.GA1942@localhost.localdomain>
Hello Josef,
Josef Bacik wrote (ao):
> On Thu, Mar 29, 2012 at 12:52:35PM +0200, Sander wrote:
> > I can't seem to balance my btrfs filesystem. It segfaults, and gives a
> > kernel bug:
> >
> > [ 1355.139099] ------------[ cut here ]------------
> > [ 1355.139099] kernel BUG at fs/btrfs/volumes.c:2733!
> > [ 1355.149322] Internal error: Oops - BUG: 0 [#1] SMP
> > [ 1355.149322] Modules linked in:
> > [ 1355.154479] CPU: 0 Not tainted (3.3.0 #8)
> > [ 1355.162109] PC is at btrfs_balance+0x312/0xb04
> > [ 1355.166778] LR is at btrfs_run_delayed_iputs+0x2d/0xac
> > The system is a pandaboard running a plain Linus kernel 3.3.0 with a
> > btrfs filesystem, over two Intel 320 600GB ssd's, connected via usb (on
> > an usb hub), on top of md_crypt. Mount options:
> > "subvol=rootvolume,space_cache,inode_cache,compress=lzo,ssd"
> >
> > Before the balance, I deleted about 2500 snapshots and waited for the
> > btrfs kernel threads to calm down. Then I initiated a btrfs filesystem
> > scrub. Unfortunately during the scrub, the filesystem balance started.
> > Might be related.
>
> Well that's kind of cool. So 2 options
>
> 1) If you are in a hurry and need this stuff back right away run btrfs fi
> balance resume / and it should work, buuutt
>
> 2) If you aren't in a hurry I'd really like to try and reproduce this locally
> and if I can't I'd like to be able to send you patches to help me figure out how
> to fix this problem.
I am in no hurry at all. The filesystem seems just fine the way it is
(after a reboot), so there is no "stuff to get back right away". Does
the kernel bug suggest the filesystem is fubar?
I'll keep the filesystem as is (no resume) and am happy to test any
patches you have.
Sander
--
Humilis IT Services and Solutions
http://www.humilis.net
next prev parent reply other threads:[~2012-03-29 14:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 10:52 kernel BUG at fs/btrfs/volumes.c:2733 Sander
2012-03-29 13:16 ` Josef Bacik
2012-03-29 14:39 ` Sander [this message]
2012-03-29 15:44 ` Ilya Dryomov
2012-03-29 13:53 ` Ilya Dryomov
2012-03-29 15:14 ` Sander
2012-03-29 15:41 ` Ilya Dryomov
2012-03-30 17:49 ` Sander
2012-03-30 19:52 ` Ilya Dryomov
2012-03-30 20:44 ` Sander
2012-04-10 16:06 ` Ilya Dryomov
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=20120329143929.GB29741@panda \
--to=sander@humilis.net \
--cc=josef@redhat.com \
--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).