From: Marc MERLIN <marc@merlins.org>
To: linux-btrfs@vger.kernel.org, jbacik@fusionio.com
Subject: Re: BTRFS crash on mount with 3.4.4
Date: Thu, 2 Aug 2012 07:26:46 -0700 [thread overview]
Message-ID: <20120802142646.GA31880@merlins.org> (raw)
In-Reply-To: <20120802134003.GP17430@twin.jikos.cz>
On Thu, Aug 02, 2012 at 03:40:03PM +0200, David Sterba wrote:
> On Tue, Jul 31, 2012 at 06:01:04PM -0700, Marc MERLIN wrote:
> > On Tue, Jul 31, 2012 at 11:04:12AM -0700, Marc MERLIN wrote:
> > > My kernel crashed for some other reason, and now I can't mount my btrfs
> > > filesystem.
> > > I don't care about the data, it's backed up.
> > >
> > > I'll compile a 3.5 kernel, but is there any info you'd like off that
> > > filesystem to see why btrfs is crashing on mount?
> >
> > On the plus side, 3.5 mounted the filesystem:
> > [ 183.069179] device label btrfs_pool1 devid 1 transid 20769 /dev/mapper/test
> > [ 183.087805] btrfs: disk space caching is enabled
> > [ 183.224784] btrfs: no dev_stats entry found for device /dev/mapper/test (devid 1) (OK on first mount after mkfs)
> > [ 186.277795] Btrfs detected SSD devices, enabling SSD mode
> > [ 188.477443] btrfs: unlinked 6 orphans
> > [ 188.477451] btrfs: truncated 1 orphans
> > [ 411.837015] btrfs: unlinked 13 orphans
> > [ 414.373500] btrfs: unlinked 35 orphans
>
> there's this commit in 3.5 that looks like it fixed the problem:
>
> Author: Josef Bacik <jbacik@fusionio.com>
> AuthorDate: Wed Jun 27 15:10:56 2012 -0400
>
> Btrfs: fix tree log remove space corner case
>
> The tree log stuff can have allocated space that we end up having split
> across a bitmap and a real extent. The free space code does not deal with
> this, it assumes that if it finds an extent or bitmap entry that the entire
> range must fall within the entry it finds. This isn't necessarily the case,
> so rework the remove function so it can handle this case properly. This
> fixed two panics the user hit, first in the case where the space was
> initially in a bitmap and then in an extent entry, and then the reverse
> case. Thanks,
Indeed. Thanks for finding this David and thanks for writing this Josef :)
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/
prev parent reply other threads:[~2012-08-02 14:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 18:04 BTRFS crash on mount with 3.4.4 Marc MERLIN
2012-08-01 1:01 ` Marc MERLIN
2012-08-01 5:13 ` cwillu
2012-08-02 13:40 ` David Sterba
2012-08-02 14:26 ` Marc MERLIN [this message]
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=20120802142646.GA31880@merlins.org \
--to=marc@merlins.org \
--cc=jbacik@fusionio.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).