public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "S." <sb56637@gmail.com>
To: linux-btrfs@vger.kernel.org
Cc: Rosen Penev <rosenp@gmail.com>
Subject: Re: Upgraded from Buster to Bullseye, unmountable Btrfs filesystem
Date: Thu, 11 Nov 2021 09:26:22 -0500	[thread overview]
Message-ID: <92cb15b5-e97e-10ea-acc2-fc5c1510cb38@gmail.com> (raw)
In-Reply-To: <CAKxU2N9hC8ha-M1RV27Km3p24t2Dg32t0B9JEbbStr1i+s0BqQ@mail.gmail.com>

On 11/11/21 01:20, Rosen Penev wrote:
> On Wed, Nov 10, 2021 at 9:25 PM S. <sb56637@gmail.com> wrote:
>>
>> Oh, and I forgot to report that memtester didn't find any errors. I ran it one more time too, I think I managed to request up to 210M before the OOM-killer intervened:
> I bet the actual issue is some 32-bit problem...

That's what I'm thinking too.

  reply	other threads:[~2021-11-11 14:26 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.
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. [this message]
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=92cb15b5-e97e-10ea-acc2-fc5c1510cb38@gmail.com \
    --to=sb56637@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=rosenp@gmail.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