public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: yahoo <mentadent47@yahoo.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: fsck operational error
Date: Thu, 22 May 2025 23:29:36 +0200	[thread overview]
Message-ID: <83e0ab86-7cda-4e16-8729-f659071deec0@yahoo.com> (raw)
In-Reply-To: <ba734653-0330-493a-af07-aeae459b76a7@yahoo.com>

Il 22/05/25 22:02, yahoo ha scritto:
> Il 22/05/25 20:13, Dale ha scritto:
>> yahoo wrote:
>> Is this a driver we should all disable or do you have a different use
>> case than most?  I ask because mine is on as well.  Given the large
> 
> DON'T DISABLE IT!
> 

Sorry, I just re-read what I wrote and the stuff below does not make 
sense, I'm mixing up unmounted and read-write/read-only. I need to 
understand better what's going on.

"Don't disable it" is the only correct answer.

raffaele

> fsck must be executed on unmounted filesystem and for 'root fs' that 
> normally happens only during boot. On my system the order of init 
> services is:
> 
> - kernel starts and mounts root fs in read only mode
> - OpenRc starts
> ...
> 1. fsck service (this checks the root fs)
> 2. root service (this remounts the root fs in read/write mode)
> ...
> 
> If you disable that option when the fsck service runs it finds the root 
> fs mounted read-only, fails and does not check the root fs _ever_. Not a 
> good idea!
> 


  reply	other threads:[~2025-05-22 21:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <41040b25-52a7-484a-9261-1f115f2d5818.ref@yahoo.com>
2024-09-21 16:16 ` [gentoo-user] fsck operational error ralfconn
2025-04-09 16:38   ` [gentoo-user] " ralfconn
2025-04-09 22:08     ` Michael
2025-05-22 17:16     ` yahoo
2025-05-22 18:13       ` Dale
2025-05-22 20:02         ` yahoo
2025-05-22 21:29           ` yahoo [this message]
2025-05-22 22:08             ` Dale

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=83e0ab86-7cda-4e16-8729-f659071deec0@yahoo.com \
    --to=mentadent47@yahoo.com \
    --cc=gentoo-user@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox