public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Kastl <kastl@b1-systems.de>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>, 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: Fri, 20 May 2022 22:21:28 +0200	[thread overview]
Message-ID: <ea73d6b6-4e91-438e-6f9a-7377bb461bc3@b1-systems.de> (raw)
In-Reply-To: <16c8e141-f3b8-8a6b-1366-23b9dfbae343@b1-systems.de>


[-- Attachment #1.1: Type: text/plain, Size: 1148 bytes --]

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.

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)...

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

Kind Regards,
Johannes

-- 
Johannes Kastl
Linux Consultant & Trainer
Tel.: +49 (0) 151 2372 5802
Mail: kastl@b1-systems.de

B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg
http://www.b1-systems.de
GF: Ralph Dehner
Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

  reply	other threads:[~2022-05-20 20:21 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 [this message]
2022-05-21  1:10               ` Qu Wenruo
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=ea73d6b6-4e91-438e-6f9a-7377bb461bc3@b1-systems.de \
    --to=kastl@b1-systems.de \
    --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