From: Hugo Mills <hugo@carfax.org.uk>
To: Neko-san <nekoNexus@proton.me>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [Help Please] Missing FIle Permissions Irrecoverably
Date: Fri, 20 May 2022 22:27:51 +0100 [thread overview]
Message-ID: <20220520212751.GE22627@savella.carfax.org.uk> (raw)
In-Reply-To: <LQBIObJ0wXAJiClnJItZ5QlGJPGLx5G3_cbQYB6Yle5t7wg7-MX233_rkpCs_ybzN9-DWoQBSlPD6EZRa6HDjdo6PWJjFWO0qb4XB7UsK1E=@proton.me>
On Fri, May 20, 2022 at 09:13:25PM +0000, Neko-san wrote:
> Greetings,
>
> I'm having a pretty severe issue right now where I don't have permission access to many of the files / directories on my system (namely my home folder and some others) and superuser privileges aren't helping to fix these issues. I'd really like to not have to reinstall Arch Linux just because of this... I'd appreciate assistance...
>
> I have no idea what's caused it and this is the only sensible conclusion I've been able to come to thus far...
>
> ```
> neko-san@ARCH ~> btrfs check --readonly --progress /dev/nvme0n1p2
> Opening filesystem to check...
> ERROR: /dev/nvme0n1p2 is currently mounted, use --force if you really intend to check the filesystem
You can't expect an fsck on a mounted filesystem to produce any useful output.
> neko-san@ARCH ~ [1]> btrfs check --readonly --progress --force /dev/nvme0n1p2
... and so this is useless, I'm afraid.
[snip]
> [ 1646.159335] systemd-journald[387]: Failed to rotate /var/log/journal/63f413b0af0c43ae9345a082aaf00bd3/user-1000.journal: Read-only file system
That would be a read-only filesystem, then. Most likely caused by
some serious error on the FS, which caused it to go read-only to
protect itself. You'll have to go back in dmesg to see what happened
to cause that. There's most likely a kernel oops in there at around
the same time that the systemd journal started spewing those errors.
Hugo.
--
Hugo Mills | You shouldn't anthropomorphise computers. They
hugo@... carfax.org.uk | really don't like that.
http://carfax.org.uk/ |
PGP: E2AB1DE4 |
next prev parent reply other threads:[~2022-05-20 21:27 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 [this message]
[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
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=20220520212751.GE22627@savella.carfax.org.uk \
--to=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