From: Chris Mason <chris.mason@fusionio.com>
To: Joeri Vanthienen <mail@joerivanthienen.be>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: WARNING: at fs/btrfs/extent_map.c:78 free_extent_map+0x6e/0x90 [btrfs]() [linux 3.8.0]
Date: Mon, 4 Mar 2013 09:39:56 -0500 [thread overview]
Message-ID: <20130304143956.GA3822@shiny.masoncoding.com> (raw)
In-Reply-To: <CAPsrAuCMLi2m-3_vSE+FZLwMEDRhHDLoM0qnJAw0tYgcqsr=Og@mail.gmail.com>
On Mon, Mar 04, 2013 at 07:06:05AM -0700, Joeri Vanthienen wrote:
> Some more maybe usefull information. After reboot, the btrfs raid10
> filesystem is unmountable.
> I'm now running the test without enhanceIO from IO.
>
> linux-testsan:~ #btrfs device scan --all-devices
> [ 881.520686] device fsid 21b0cd45-019d-4e83-bf2f-053eaaf8b380 devid
> 2 transid 10 /dev/sdd
> [ 881.522907] device fsid 21b0cd45-019d-4e83-bf2f-053eaaf8b380 devid
> 1 transid 14 /dev/sdc
> [ 901.949559] device fsid 21b0cd45-019d-4e83-bf2f-053eaaf8b380 devid
> 4 transid 14 /dev/sdf
> [ 901.949962] device fsid 21b0cd45-019d-4e83-bf2f-053eaaf8b380 devid
> 3 transid 14 /dev/sde
> [ 901.950367] device fsid 21b0cd45-019d-4e83-bf2f-053eaaf8b380 devid
> 2 transid 10 /dev/sdd
> [ 901.952572] device fsid 21b0cd45-019d-4e83-bf2f-053eaaf8b380 devid
> 1 transid 14 /dev/sdc
> linux-testsan:~ # btrfsck /dev/sde
> Check tree block failed, want=858902528, have=858836992
This is telling us the device returned the wrong block. It could be
because the device really read from the wrong place, or perhaps it is
because the correct block was never written.
Please let us know if you're still seeing this without enhanceIO
involved. I haven't tried enhanceIO yet, so I'm not sure how well it
supports btrfs.
-chris
next prev parent reply other threads:[~2013-03-04 14:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-04 8:19 WARNING: at fs/btrfs/extent_map.c:78 free_extent_map+0x6e/0x90 [btrfs]() [linux 3.8.0] Joeri Vanthienen
2013-03-04 13:50 ` Joeri Vanthienen
2013-03-04 14:06 ` Joeri Vanthienen
2013-03-04 14:39 ` Chris Mason [this message]
2013-03-04 15:08 ` Joeri Vanthienen
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=20130304143956.GA3822@shiny.masoncoding.com \
--to=chris.mason@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=mail@joerivanthienen.be \
/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.