All of lore.kernel.org
 help / color / mirror / Atom feed
From: bill gates <framingnoone@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Updated to new kernel, and btrfs suddenly refuses to mount home directory fs.
Date: Tue, 8 Mar 2022 13:05:19 -0600	[thread overview]
Message-ID: <CALPV6DsfOQHyQ2=+3pKF3ZfavL21fgthQS+=HStEfMQbhZU50g@mail.gmail.com> (raw)

So, I recently attempted to upgrade from Linux kernel 4.19.82 to
5.15.23, and I'm getting a critical error in dmesg about a corrupt
leaf (and no mounting of /home allowed with the options I'm aware of)

[ 396.218964] BTRFS critical (device sda2): corrupt leaf: root=1
block=10442806968320 sl
ot=8 ino=6, invalid location key objectid: has 1 expect 6 or [256,
18446744073709551360]
or 18446744073709551604
[ 396.218967] BTRFS error (device sda2): block=10442806968320 read
time tree block corru
ption detected


Interestingly. that 18446... number is a power of 2, looks like maybe
a bit flip? dmesg, uname, etc included in pastebin below. "btrfs
check" found no problems with fs on either kernel version. Would like
to figure out how to fix this, if possible.

https://pastebin.com/0ESPU9Z6

Thank you for any assistance,
-- Laurence Michaels.

             reply	other threads:[~2022-03-08 19:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-08 19:05 bill gates [this message]
2022-03-08 21:45 ` Updated to new kernel, and btrfs suddenly refuses to mount home directory fs Chris Murphy
2022-03-08 23:48 ` Qu Wenruo
2022-03-09  1:09   ` bill gates
2022-03-09  3:00     ` Qu Wenruo
     [not found]       ` <CALPV6DvuD5Tn_mepbVPcWkbNA-s9Nj-jc1dsY8Cm5KOrYfbu0Q@mail.gmail.com>
2022-03-09  4:33         ` Fwd: " bill gates
     [not found]         ` <8120882e-d5ce-d8d8-fc5a-1a9b2e3eb39a@gmx.com>
2022-03-09  5:21           ` bill gates
2022-03-09  6:56             ` Qu Wenruo
2022-03-09  7:28               ` bill gates
2022-03-09  7:35                 ` 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='CALPV6DsfOQHyQ2=+3pKF3ZfavL21fgthQS+=HStEfMQbhZU50g@mail.gmail.com' \
    --to=framingnoone@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.