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.6 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED 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 76E21C2D0B1 for ; Fri, 7 Feb 2020 06:16:43 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 46C9B20838 for ; Fri, 7 Feb 2020 06:16:43 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="HEsLIy/O" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726738AbgBGGQm (ORCPT ); Fri, 7 Feb 2020 01:16:42 -0500 Received: from mail-ot1-f52.google.com ([209.85.210.52]:38642 "EHLO mail-ot1-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726465AbgBGGQm (ORCPT ); Fri, 7 Feb 2020 01:16:42 -0500 Received: by mail-ot1-f52.google.com with SMTP id z9so1099868oth.5 for ; Thu, 06 Feb 2020 22:16:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=o/VfNf/UtaEsWN57i9UtjxYqGxloDz5/jH6sJ1RkrnQ=; b=HEsLIy/ODnRQJwtuI9MtGRfKPVvP4nBDYWbHtlf1j56bzQlnfWicEtLXX8GsSNdGGH Aq+7UVa2VUFyBGauD/I2xbyXr/xtgqQdwNGMB/MVPkdLVQEUudCCasesTh4y1EBrO3Ej hL/jKEtICtpfUtlM1SQNZgVXRnAVe834g94u5LQCnBQMpuWs7JQt/vDKTBPvYOr7QLLA 0BQdnoLASk80+sjwLGh4d/JAvBr12C+YDQ/7GbSdl/V8hdl7JIpceb3xaJzeQA+0TVGZ td/I5gXhyQZdrJN3RJZdyO3qjNgBct7xuqMKlu6aGI2GxCN+Qv2fl64lu/15QwPhYLQW fXcw== 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:content-transfer-encoding; bh=o/VfNf/UtaEsWN57i9UtjxYqGxloDz5/jH6sJ1RkrnQ=; b=sk7TTep4RhuLNCKwkn3JydnMlIv4S4tsctVQYJBUAZnn/Kx1J9xjBZHRigh96N7eQK ey0DHNzySPTKeFZySfP7ZD9w1H5DAB3ZjE3VeFVDhk6crImRozy7QAqjcnagrxeFhw6x I+YBtvUVNGlGAXITAboEmN8UThEHLEW4uyt4aKlFX32W49crwzPRy7VTH0RUO5m2Yhwi ASRXpevm5/53Az2MlMYyWdProf6o7SWY/f+Pd9niAZ0zTivWdUVkVDryYJbBxYJH/s0p syOYhXK1qY2LZwhFc+lAFyb4W+oyxx2svZyvS48d/9fAJ/8Pg+GXggR7G/hor+SByRy6 7b/A== X-Gm-Message-State: APjAAAVo6NotnBbZ8xIuWSgkR3S+6oZ1JP/5SSVEgFuu1qZUneW0sbSg VDvgIxqUxORMzBf/sn8YD42UGRzBA7nNvHg4JZNTP3vX X-Google-Smtp-Source: APXvYqwPcoMLeD4EC3ctrsWczoE4bTQ2iJgWdDOWDyT1WvTcsuzGav6gvvFz9HkxAKKTw3CF5QrReDF66UfxUCJ8QaE= X-Received: by 2002:a05:6830:1e95:: with SMTP id n21mr1521505otr.25.1581056200971; Thu, 06 Feb 2020 22:16:40 -0800 (PST) MIME-Version: 1.0 References: <6cea6393-1bb0-505e-b311-bff4a818c71b@gmx.com> In-Reply-To: From: Chiung-Ming Huang Date: Fri, 7 Feb 2020 14:16:29 +0800 Message-ID: Subject: Re: How to Fix 'Error: could not find extent items for root 257'? To: Qu Wenruo Cc: Btrfs Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Sender: linux-btrfs-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-btrfs@vger.kernel.org Qu Wenruo =E6=96=BC 2020=E5=B9=B42=E6=9C=887=E6=97= =A5 =E9=80=B1=E4=BA=94 =E4=B8=8B=E5=8D=8812:00=E5=AF=AB=E9=81=93=EF=BC=9A > > All these subvolumes had a missing root dir. That's not good either. > I guess btrfs-restore is your last chance, or RO mount with my > rescue=3Dskipbg patchset: > https://patchwork.kernel.org/project/linux-btrfs/list/?series=3D170715 > Is it possible to use original disks to keep the restored data safely? I would like to restore the data of /dev/bcache3 to the new btrfs RAID0 at the first and= then add it to the new btrfs RAID0. Does `btrfs restore` need metadata or someth= ing in /dev/bcache3 to restore /dev/bcache2 and /dev/bcache4? /dev/bcache2, ID: 1 Device size: 9.09TiB Device slack: 0.00B Data,RAID1: 3.93TiB Metadata,RAID1: 2.00GiB System,RAID1: 32.00MiB Unallocated: 5.16TiB /dev/bcache3, ID: 3 Device size: 2.73TiB Device slack: 0.00B Data,single: 378.00GiB Data,RAID1: 355.00GiB Metadata,single: 2.00GiB Metadata,RAID1: 11.00GiB Unallocated: 2.00TiB /dev/bcache4, ID: 5 Device size: 9.09TiB Device slack: 0.00B Data,single: 2.93TiB Data,RAID1: 4.15TiB Metadata,single: 6.00GiB Metadata,RAID1: 11.00GiB System,RAID1: 32.00MiB Unallocated: 2.00TiB Regards, Chiung-Ming Huang