From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi0-f43.google.com ([209.85.218.43]:34032 "EHLO mail-oi0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750872AbcFYQZi (ORCPT ); Sat, 25 Jun 2016 12:25:38 -0400 Received: by mail-oi0-f43.google.com with SMTP id s66so152694153oif.1 for ; Sat, 25 Jun 2016 09:25:38 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <15415597-7f29-396e-8425-8cbbeb32e897@crc.id.au> <4e1bff4c-3cfc-4391-d093-8293bf29e795@crc.id.au> <47f587fd-b553-5ed7-ac38-202bf7297350@crc.id.au> From: Chris Murphy Date: Sat, 25 Jun 2016 10:25:37 -0600 Message-ID: Subject: Re: Trying to rescue my data :( To: Steven Haigh Cc: Btrfs BTRFS Content-Type: text/plain; charset=UTF-8 Sender: linux-btrfs-owner@vger.kernel.org List-ID: On Fri, Jun 24, 2016 at 10:19 PM, Steven Haigh wrote: > > Interesting though that EVERY crash references: > kernel BUG at fs/btrfs/extent_io.c:2401! Yeah because you're mounted ro, and if this is 4.4.13 unmodified btrfs from kernel.org then that's the 3rd line: if (head->is_data) { ret = btrfs_del_csums(trans, root, node->bytenr, node->num_bytes); So why/what is it cleaning up if it's mounted ro? Anyway, once you're no longer making forward progress you could try something newer, although it's a coin toss what to try. There are some issues with 4.6.0-4.6.2 but there have been a lot of changes in btrfs/extent_io.c and btrfs/raid56.c between 4.4.13 that you're using and 4.6.2, so you could try that or even build 4.7.rc4 or rc5 by tomorrowish and see how that fairs. It sounds like there's just too much (mostly metadata) corruption for the degraded state to deal with so it may not matter. I'm really skeptical of btrfsck on degraded fs's so I don't think that'll help. -- Chris Murphy