public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "S." <sb56637@gmail.com>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>, linux-btrfs@vger.kernel.org
Subject: Re: Upgraded from Buster to Bullseye, unmountable Btrfs filesystem
Date: Wed, 10 Nov 2021 19:18:31 -0500	[thread overview]
Message-ID: <4f7be37a-502c-6ee1-2519-29b84810999c@gmail.com> (raw)
In-Reply-To: <1f4db1f5-2f37-0074-cbe8-e78ba7836587@gmx.com>

On 11/10/21 18:46, Qu Wenruo wrote:
> So it means, we still need btrfs-progs to repair it.
> 
> Thus I believe you still need to prepare a build environment for it.
> 
> For the worst case, I could try to build a static btrfs-progs for you if
> you could provide the "uname -a" output.

Thanks for your time and patience. If you have time for a static build of btrfs-progs I would be very grateful.
# uname -a
Linux OpenMediaVault 5.10.0-9-marvell #1 Debian 5.10.70-1 (2021-09-30) armv5tel GNU/Linux

  reply	other threads:[~2021-11-11  0:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-10  2:17 Upgraded from Buster to Bullseye, unmountable Btrfs filesystem S.
2021-11-10  2:33 ` Qu Wenruo
2021-11-10  2:55 ` S.
2021-11-10  3:34   ` Qu Wenruo
2021-11-10  4:30   ` S.
2021-11-10  7:01     ` Qu Wenruo
2021-11-10 14:01       ` S.
2021-11-10 23:46         ` Qu Wenruo
2021-11-11  0:18           ` S. [this message]
2021-11-11  0:58             ` Qu Wenruo
2021-11-11  2:29               ` S.
     [not found]               ` <e19518ec-a885-4a1d-1dda-a5be645a1d73@gmail.com>
     [not found]                 ` <73fb26b3-932c-9592-bced-6a3fda3456f0@gmx.com>
     [not found]                   ` <fdcac254-e169-7aba-7a12-c828aaab3231@gmail.com>
2021-11-12  0:06                     ` Qu Wenruo
2021-11-11  5:22         ` S.
2021-11-11  6:20           ` Rosen Penev
2021-11-11 14:26             ` S.
2021-11-12 15:18     ` S.

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=4f7be37a-502c-6ee1-2519-29b84810999c@gmail.com \
    --to=sb56637@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