From: Forza <forza@tnonline.net>
To: Neko-san <nekoNexus@proton.me>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
Hugo Mills <hugo@carfax.org.uk>
Subject: Re: [Help Please] Missing FIle Permissions Irrecoverably
Date: Fri, 27 May 2022 23:08:45 +0200 (GMT+02:00) [thread overview]
Message-ID: <98b7da2.8b0b192.1810759a875@tnonline.net> (raw)
In-Reply-To: <wztQTaGfQNKnobWabVzov7npkcVSeXD2Zth69WUFRit2NRq61hMN6a7t6R9mJntS0kyDryBabwpzmP4_q4nsO8y9WnUX35nOJ3ZF0agom9M=@proton.me>
Hello,
---- From: Neko-san <nekoNexus@proton.me> -- Sent: 2022-05-23 - 08:05 ----
> I had accidentally forgot to re-add the mailing list to the recipients regarding this; I have attached a dmesg log regarding this...
> I had attempted to downgrade the btrfs-progs package to 5.16.2 from 5.17 in an attempt to alleviate the problem but... that didn't work. :/
> I'm at my wits-end and I need my PC to work, as most do...
>
>
You are having some corruption in your filesystem. The dmesg indicates that btrfs can't find data where it expects it to.
Support is given by the community as and when they can and want to. If you want help a little quicker you can try with the #btrfs IRC channel. There is a Web client at https://web.libera.chat/#btrfs
Did you have some power loss or over temperature issues with the nvme drive before these problems?
Best is to try to boot with a live usb and run a 'btrfs check --readonly' on the unmounted drive. Check cannot reliably run on a mounted filesystem.
Forza
next prev parent reply other threads:[~2022-05-27 21:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 21:13 [Help Please] Missing FIle Permissions Irrecoverably Neko-san
2022-05-20 21:27 ` Hugo Mills
[not found] ` <VHT1Yf4pw4jirz6QjpYj6bPb1zvJ06WStOXc4w1mSC1A7DsH5YQq-mqvzkzZSZriBXwCHuyF11thmlcgSLYFGaBeHGuA5XliXPJVJ3eXItE=@proton.me>
[not found] ` <J6n7dr0d6RAArHrDWGrU_uNQsM56Npqpp_tuyXoY7q4rS_2dPzmd4sH14t_w-n_tE80HWdjyUKY2SqwV-iFwBoa55dLfJ3WI7LVsrjTRTVw=@proton.me>
[not found] ` <uDip5WTKD2tJ6uP8N0eW91dNpbSShUrHBHPLczGV4l__Z_Wem9uWnG_pCYqcYjren8Gx8Va0iS3AGvCEiFTAC33Lgx_gOMs9KVqb1dh_lnc=@proton.me>
2022-05-23 6:05 ` Neko-san
2022-05-27 17:48 ` Neko-san
2022-05-27 21:08 ` Forza [this message]
2022-06-08 14:09 ` Neko-san
2022-06-13 16:46 ` Neko-san
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=98b7da2.8b0b192.1810759a875@tnonline.net \
--to=forza@tnonline.net \
--cc=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=nekoNexus@proton.me \
/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