From: Stefan Behrens <sbehrens@giantdisaster.de>
To: Marc MERLIN <marc@merlins.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: kernel BUG at fs/btrfs/extent_io.c:1884!
Date: Fri, 21 Sep 2012 06:57:32 +0200 [thread overview]
Message-ID: <505BF3BC.1030304@giantdisaster.de> (raw)
In-Reply-To: <20120921034652.GA871@merlins.org>
On 09/21/2012 05:46, Marc MERLIN wrote:
> Oh my, now I'm trying again with a new drive, and a big cp from an
> existing array to a new one dies with:
> [32042.079411] ------------[ cut here ]------------
> [32042.085799] kernel BUG at fs/btrfs/extent_io.c:1884!
> [32042.092528] invalid opcode: 0000 [#1] PREEMPT SMP
> [32042.099227] CPU 1
> [32042.101095] Modules linked in:[32042.105950] raid456 async_raid6_recov async
> _pq raid6_pq async_xor xor async_memcpy async_tx ppdev lp tun autofs4 kl5kusb105
> ftdi_sio keyspan nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc rc_ati_x10 s
> nd_timer i915 usbserial snd drm_kms_helper eeepc_wmi drm ati_remote asus_wmi rc_
> core sparse_keymap
>
> int repair_io_failure(struct btrfs_mapping_tree *map_tree, u64 start,
> u64 length, u64 logical, struct page *page,
> int mirror_num)
> {
> struct bio *bio;
> struct btrfs_device *dev;
> DECLARE_COMPLETION_ONSTACK(compl);
> u64 map_length = 0;
> u64 sector;
> struct btrfs_bio *bbio = NULL;
> int ret;
>
> BUG_ON(!mirror_num); <<<<<
>
This was fixed with commit c0901581ad077004145c9ee80e843fba71c100b8 and
is included in Linux 3.6 RC1.
next prev parent reply other threads:[~2012-09-21 4:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-20 17:17 3.5.3: kernel BUG at fs/btrfs/ctree.c:3451! Marc MERLIN
2012-09-21 3:46 ` kernel BUG at fs/btrfs/extent_io.c:1884! Marc MERLIN
2012-09-21 3:51 ` cwillu
2012-09-21 4:11 ` Marc MERLIN
2012-09-21 3:53 ` Liu Bo
2012-09-21 4:57 ` Stefan Behrens [this message]
2012-09-21 5:43 ` Marc MERLIN
2012-09-23 16:16 ` crash in read_extent_buffer+0xb7/0xfb Marc MERLIN
2012-09-24 13:08 ` David Sterba
2012-09-24 14:41 ` Marc MERLIN
2012-09-24 15:37 ` David Sterba
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=505BF3BC.1030304@giantdisaster.de \
--to=sbehrens@giantdisaster.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=marc@merlins.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).