From: Chiung-Ming Huang <photon3108@gmail.com>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: Btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: How to Fix 'Error: could not find extent items for root 257'?
Date: Mon, 10 Feb 2020 14:50:41 +0800 [thread overview]
Message-ID: <CAEOGEKHARKKSYMEU5kbswA7-PjxT9xAOomktG32h9RS6aYUVjA@mail.gmail.com> (raw)
In-Reply-To: <49cc4e6d-07c0-aea0-e753-6a6262e4dedb@gmx.com>
Qu Wenruo <quwenruo.btrfs@gmx.com> 於 2020年2月7日 週五 下午3:16寫道:
>
>
>
> On 2020/2/7 下午2:16, Chiung-Ming Huang wrote:
> > Qu Wenruo <quwenruo.btrfs@gmx.com> 於 2020年2月7日 週五 下午12:00寫道:
> >>
> >> 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=skipbg patchset:
> >> https://patchwork.kernel.org/project/linux-btrfs/list/?series=170715
> >>
> >
> > 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 something
> > in /dev/bcache3 to restore /dev/bcache2 and /dev/bcache4?
>
> Devid 1 (bcache 2) seems OK to be missing, as all its data and metadata
> are in RAID1.
>
> But it's strongly recommended to test without wiping bcache2, to make
> sure btrfs-restore can salvage enough data, then wipeing bcache2.
>
> Thanks,
> Qu
Is it possible to shrink the size of bcache2 btrfs without making
everything worse?
I need more disk space but I still need bcache2 itself.
Regards,
Chiung-Ming Huang
> >
> > /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
> >
>
next prev parent reply other threads:[~2020-02-10 6:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 10:18 How to Fix 'Error: could not find extent items for root 257'? Chiung-Ming Huang
2020-02-05 10:29 ` Qu Wenruo
2020-02-05 15:29 ` Chiung-Ming Huang
2020-02-05 19:38 ` Chris Murphy
2020-02-06 3:11 ` Chiung-Ming Huang
[not found] ` <CAEOGEKHf9F0VM=au-42MwD63_V8RwtqiskV0LsGpq-c=J_qyPg@mail.gmail.com>
[not found] ` <f2ad6b4f-b011-8954-77e1-5162c84f7c1f@gmx.com>
2020-02-06 4:13 ` Chiung-Ming Huang
2020-02-06 4:35 ` Qu Wenruo
2020-02-06 6:50 ` Chiung-Ming Huang
2020-02-07 3:49 ` Chiung-Ming Huang
2020-02-07 4:00 ` Qu Wenruo
2020-02-07 6:16 ` Chiung-Ming Huang
2020-02-07 7:16 ` Qu Wenruo
2020-02-10 6:50 ` Chiung-Ming Huang [this message]
2020-02-10 7:03 ` Qu Wenruo
2020-02-15 3:47 ` Chiung-Ming Huang
2020-02-15 4:29 ` Qu Wenruo
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=CAEOGEKHARKKSYMEU5kbswA7-PjxT9xAOomktG32h9RS6aYUVjA@mail.gmail.com \
--to=photon3108@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
/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).