From: Olivier Bonvalet <btrfs.list@daevel.fr>
To: Chris Samuel <chris@csamuel.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: kernel BUG at fs/btrfs/extent-tree.c:5038 (linux 3.4.7)
Date: Sun, 05 Aug 2012 16:11:47 +0200 [thread overview]
Message-ID: <501E7F23.3040401@daevel.fr> (raw)
In-Reply-To: <501E3578.4030809@csamuel.org>
On 05/08/2012 10:57, Chris Samuel wrote:
> On 08/04/2012 08:41 AM, Olivier Bonvalet wrote:
>
>> Is there something I can do to fix that ? (the mount
>> option "recovery" didn't help here)
>
> I've seen someone (perhaps Marc Merlin) report that the
> 3.5.x kernel was able to mount a filesystem that 3.4.x
> couldn't, so it might be worth a shot here!
>
> Best of luck,
> Chris
Thanks for the idea, but same result :
Aug 5 16:10:12 backup2 kernel: [ 58.630481] device fsid a5dfe512-c8a3-46f0-bc8c-6365b8eccdcb devid 1 transid 110425 /dev/mapper/vg--backupplug-backup
Aug 5 16:10:12 backup2 kernel: [ 58.631346] btrfs: force zlib compression
Aug 5 16:10:12 backup2 kernel: [ 58.631357] btrfs: not using ssd allocation scheme
Aug 5 16:10:12 backup2 kernel: [ 58.631366] btrfs: enabling auto recovery
Aug 5 16:10:12 backup2 kernel: [ 58.670972] btrfs: no dev_stats entry found for device /dev/mapper/vg--backupplug-backup (devid 1) (OK on first mount after mkfs)
Aug 5 16:10:12 backup2 kernel: [ 58.674758] parent transid verify failed on 615015833600 wanted 110423 found 110424
Aug 5 16:10:12 backup2 kernel: [ 58.675090] parent transid verify failed on 615015833600 wanted 110423 found 110424
Aug 5 16:10:12 backup2 kernel: [ 58.675523] btrfs read error corrected: ino 1 off 615015833600 (dev /dev/mapper/vg--backupplug-backup sector 1209083504)
Aug 5 16:10:12 backup2 kernel: [ 58.675536] Failed to read block groups: -5
Aug 5 16:10:12 backup2 kernel: [ 58.704720] btrfs: open_ctree failed
next prev parent reply other threads:[~2012-08-05 14:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-01 19:48 kernel BUG at fs/btrfs/extent-tree.c:5038 (linux 3.4.7) Olivier Bonvalet
2012-08-02 13:22 ` David Sterba
2012-08-02 13:41 ` Olivier Bonvalet
2012-08-02 13:53 ` David Sterba
2012-08-02 16:18 ` Olivier Bonvalet
2012-08-03 22:41 ` Olivier Bonvalet
2012-08-03 23:30 ` Olivier Bonvalet
2012-08-05 8:57 ` Chris Samuel
2012-08-05 14:11 ` Olivier Bonvalet [this message]
2012-08-08 14:45 ` David Sterba
2012-08-08 16:06 ` Stefan Behrens
2012-08-27 8:49 ` Olivier Bonvalet
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=501E7F23.3040401@daevel.fr \
--to=btrfs.list@daevel.fr \
--cc=chris@csamuel.org \
--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).