From: Tore Anderson <tore.anderson@redpill-linpro.com>
To: Josef Bacik <josef@redhat.com>
Cc: linux-btrfs@vger.kernel.org, Hugo Mills <hugo-lkml@carfax.org.uk>
Subject: Re: Crash in __btrfs_reserve_extent
Date: Thu, 06 Aug 2009 20:14:05 +0200 [thread overview]
Message-ID: <4A7B1D6D.6090402@redpill-linpro.com> (raw)
In-Reply-To: <20090806180432.GG3655@dhcp231-156.rdu.redhat.com>
* Josef Bacik
> What kernel are you running? I need to get a look at what code you
> are on. Thanks for the image, I'm having some trouble getting it to
> work, but I will let you know what I come up with.
I was running 2.6.29.4-167.fc11.i686.PAE at the time of the crash, and
when I've been having problems. I see that there's a new F11 kernel
out - I'll try to upgrade to that one and will let you know if there's
any change (I doubt it - there's no mention of btrfs-related changes).
Here's the output from btrfs-show, just figured out that I shouldn't
have supplied any arguments (thanks to Robert F=F6rster):
Label: none uuid: 94762921-dbc0-4faf-a4e5-f5acdaf305a8
Total devices 1 FS bytes used 15.82GB
devid 1 size 227.53GB used 227.53GB path /dev/root
I just tried to make a new image with btrfs-image from
btrfs-progs-unstable (using "btrfs-image -c 9 /dev/vg_echo/lv_root
image2.Z").
Unlike when making the first image, the file system was mounted. The
image is at <http://greed.fud.no/image2.Z> - is that any better?
Best regards,
--=20
Tore Anderson
Redpill Linpro AS - http://www.redpill-linpro.com/
Tel: +47 21 54 41 27
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-08-06 18:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-06 7:00 Crash in __btrfs_reserve_extent Tore Anderson
2009-08-06 8:53 ` Tore Anderson
2009-08-06 13:54 ` Josef Bacik
2009-08-06 14:15 ` Tore Anderson
2009-08-06 14:27 ` Josef Bacik
2009-08-06 17:41 ` Tore Anderson
2009-08-06 18:04 ` Josef Bacik
2009-08-06 18:14 ` Tore Anderson [this message]
2009-08-06 18:37 ` Josef Bacik
2009-08-06 18:49 ` Tore Anderson
2009-08-06 18:57 ` Chris Mason
2009-08-06 19:01 ` Josef Bacik
2009-08-06 19:22 ` Chris Mason
2009-08-06 22:01 ` Tore Anderson
-- strict thread matches above, loose matches on Subject: below --
2009-08-06 14:57 Robert Förster
2009-08-06 15:20 ` Josef Bacik
2009-08-06 15:36 ` Robert Förster
2009-08-07 5:10 ` Robert Förster
2009-08-06 17:15 ` Tore Anderson
2009-08-06 17:57 ` Robert Förster
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=4A7B1D6D.6090402@redpill-linpro.com \
--to=tore.anderson@redpill-linpro.com \
--cc=hugo-lkml@carfax.org.uk \
--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 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.