linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc MERLIN <marc@merlins.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: kernel BUG at fs/btrfs/extent_io.c:1884!
Date: Thu, 20 Sep 2012 20:46:52 -0700	[thread overview]
Message-ID: <20120921034652.GA871@merlins.org> (raw)
In-Reply-To: <20120920171747.GG26105@merlins.org>

On Thu, Sep 20, 2012 at 10:17:47AM -0700, Marc MERLIN wrote:
> I had a btrfs built on top of 5 drives (dmcrypt devices).
> 
> The drive then died while I was writing to the filesystem and my system
> crashed and rebooted:
> 
> [384555.534020] sd 10:0:0:0: rejecting I/O to offline device                    
> [384555.535057] sd 10:0:0:0: rejecting I/O to offline device                    
> [384556.666885] ------------[ cut here ]------------                            
> [384556.667909] sd 10:0:0:0: [sdj] Synchronizing SCSI cache                     
> [384556.677509] kernel BUG at fs/btrfs/ctree.c:3451!                            
> [384556.682551] invalid opcode: 0000 [#1] PREEMPT SMP                           
> [384556.687878] CPU 2                                                           
> 
 
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 is more of a problem since I can't backup my filesystem (source is
ext4 and destination is btrfs).

Any suggestion on what went wrong here?

Thanks,
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/

  reply	other threads:[~2012-09-21  3:46 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 ` Marc MERLIN [this message]
2012-09-21  3:51   ` kernel BUG at fs/btrfs/extent_io.c:1884! cwillu
2012-09-21  4:11     ` Marc MERLIN
2012-09-21  3:53   ` Liu Bo
2012-09-21  4:57   ` Stefan Behrens
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=20120921034652.GA871@merlins.org \
    --to=marc@merlins.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).