public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Johannes Kastl <kastl@b1-systems.de>, linux-btrfs@vger.kernel.org
Subject: Re: 'btrfs rescue' command (recommended by btrfs check) fails on old BTRFS RAID1 on (currently) openSUSE Leap 15.3
Date: Sat, 21 May 2022 09:10:29 +0800	[thread overview]
Message-ID: <9941f4d1-4eb2-4efb-0e24-09b28f2e185d@gmx.com> (raw)
In-Reply-To: <ea73d6b6-4e91-438e-6f9a-7377bb461bc3@b1-systems.de>



On 2022/5/21 04:21, Johannes Kastl wrote:
> Hello Qu,
>
> On 20.05.22 at 17:14 Johannes Kastl wrote:
>
>> I am trying to build this and will test it, hopefully tomorrow. I'll
>> let you know what happens...
>
> I was able to build an RPM for Leap 15.3, based on your branch.
>
>> https://build.opensuse.org/project/show/home:ojkastl_buildservice:btrfs_debugging
>>
>
> I installed it on my Leap 15.3 system, started the fix-device-size
> and... after only a couple of seconds it was done.
>
> No errors, just one line saying that it fixed something.
>
> I could mount the filesystem directly afterwards.

Great to know that.

>
> I unmounted and am currently running a btrfscheck on the filesystem,
> based on the code from your branch. I hope the filesystem is working
> again, and I can start using it again (tomorrow, the check will take ~8
> hours)...

Hope no error from btrfsck.

>
> I doubt that this will give valuable input to fix this error in
> btrfsprogs...

At least we know the new way to fix it is working.

BTW, mind to share things like `btrfs fi usage` and `btrfs fi df` when
you can mount the fs?

Thanks,
Qu
>
> Kind Regards,
> Johannes
>

  reply	other threads:[~2022-05-21  1:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-23 18:39 'btrfs rescue' command (recommended by btrfs check) fails on old BTRFS RAID1 on (currently) openSUSE Leap 15.3 Johannes Kastl
2022-04-23 23:07 ` Qu Wenruo
2022-04-24  9:10   ` Johannes Kastl
2022-04-24  9:21     ` Qu Wenruo
2022-05-18 10:38       ` Johannes Kastl
2022-05-18 10:59         ` Qu Wenruo
2022-05-20 15:14           ` Johannes Kastl
2022-05-20 20:21             ` Johannes Kastl
2022-05-21  1:10               ` Qu Wenruo [this message]
2022-05-24  7:44                 ` Johannes Kastl

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=9941f4d1-4eb2-4efb-0e24-09b28f2e185d@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=kastl@b1-systems.de \
    --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