From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 302CEC2D0C0 for ; Sun, 29 Dec 2019 23:15:50 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id E144620748 for ; Sun, 29 Dec 2019 23:15:49 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=colorremedies-com.20150623.gappssmtp.com header.i=@colorremedies-com.20150623.gappssmtp.com header.b="a0wSqh3v" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726621AbfL2XLz (ORCPT ); Sun, 29 Dec 2019 18:11:55 -0500 Received: from mail-wm1-f48.google.com ([209.85.128.48]:34547 "EHLO mail-wm1-f48.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726307AbfL2XLz (ORCPT ); Sun, 29 Dec 2019 18:11:55 -0500 Received: by mail-wm1-f48.google.com with SMTP id c127so10582491wme.1 for ; Sun, 29 Dec 2019 15:11:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=colorremedies-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=THryYSdGjfStS1b218ESt5GbaOA5WU+UdN6/mNDplTA=; b=a0wSqh3vMAP7Vaxl3q3zcDM7nV8pY0PlwhdHP/i23QGkcFF8vS572NYPbbUGxYUx7V Cy/Iu2O6a5y+VyBE24T7P+roiV/WOXXKzAF+XSwcpBEcBf4KLUHUxyNZ9pQN5B5NXTqK 1j7q5P22SOAop2NqI+2A/gserZ6OL8iQHaUMppSt/S6BzoWBmCy8SbeYMX5v7EkHS10r q80vIeFq1VlRQKFMGHsSckSdYvrZ5PT4rkzL3p0Kxfj5HhuQkRTl4q91rTtEqe8lNuCN wCFHW0nmZXbMXQJXeUCq52AutFY8EHLA7ASlkJ1j1L55MSMeyFWuOpJvCrnUKpT15B5k i86w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=THryYSdGjfStS1b218ESt5GbaOA5WU+UdN6/mNDplTA=; b=Rx9AzZBDCFbvwDGqTGTv9h8j0OXykDtIkRBqy1hz4HHl35DVap3E7z489q7YUpF53J ych8hxHMwblXaC5eGHdYy2qeLhWTVzqISs2GZlTEOvdHIdJA02Dy7hAiI2iIereJsI2I zZISbi9pDMReEnHkJm8XBmyRZZgBZo7dMWobUirM57tYvFxJ1Skx1ZKOkEgT+Yd4qNu7 m1UJSYHOMHwlJeCc4JY6JSEElx0FNODcqWgbvSH+1GzpPLC0uQOO85k2hs96lUmGQKu3 LKmj/VLtnYi2Vfd9UgNqanbSJ/H6l+yRxi/eaOqK+g1IjHSo0TLDJcliiTbvZ7+6/BvG RAhw== X-Gm-Message-State: APjAAAXqkenkatPI7tovoVhedFz+cfQpvdgumS/VhBzD/QcAZVVLDOiS JKnL9yLnD43oS5ViPjyz+IBmnzyBpc4A+rtqMtkAvA== X-Google-Smtp-Source: APXvYqxoI36BEOmwOjCnbhaBUtc4hFB3L0uFniYIls3Z8yOcOENadZJce1vY0musujlUe4V4GuZqwUF78l91Tdv6UEY= X-Received: by 2002:a1c:4d03:: with SMTP id o3mr31489305wmh.164.1577661112869; Sun, 29 Dec 2019 15:11:52 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Chris Murphy Date: Sun, 29 Dec 2019 16:11:36 -0700 Message-ID: Subject: Re: read time tree block corruption detected To: Patrick Erley Cc: Chris Murphy , Btrfs BTRFS Content-Type: text/plain; charset="UTF-8" Sender: linux-btrfs-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-btrfs@vger.kernel.org On Sun, Dec 29, 2019 at 3:36 PM Patrick Erley wrote: > > K. Gotta roll a new initrd with btrfs 5.4, then will reboot into it > and grab logs of btrfs check (both iterations, against each of my > volumes). Probably be a few hours, so don't expect another follow up > until tomorrow. Thanks for chiming in. > > Would it be worth creating an image of the drive while I'm in single > user mode for faster analysis/iteration? Depends on the developer who replies. These days they usually just ask for selected dump-tree output. The image might be useful if you can't wait and want to blow away the file system and start over sooner than later. -- Chris Murphy