From: dkwo <dkwo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [RFC] linux6.8: disable CONFIG_BLK_DEV_WRITE_MOUNTED
Date: Sat, 04 May 2024 12:53:46 +0200 [thread overview]
Message-ID: <20240504105346.499CC24E6D@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-50124@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 820 bytes --]
New comment by dkwo on void-packages repository
https://github.com/void-linux/void-packages/pull/50124#issuecomment-2094118572
Comment:
With this, in linux 6.8.9 the runit boot scripts drop to an emergency shell when checking, as at this point it's still mounted ro I think:
```
=> Checking filesystems:
fsck.ext4: Device or resource busy while trying to open /dev/mapper/cryptroot-root
Filesystem mounted or opened exclusively by another program?
Cannot continue due to errors above, starting emergency shell.
```
Typing exit resumes the boot flow. The link above mentions this case:
> However there are some setups that need this capability
> like running fsck on read-only mounted root device, modifying some
> features on mounted ext4 filesystem, and similar.
What's the best way to address this?
next prev parent reply other threads:[~2024-05-04 10:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-29 23:55 [PR PATCH] " classabbyamp
2024-04-30 0:26 ` classabbyamp
2024-05-01 9:07 ` [PR PATCH] [Merged]: " classabbyamp
2024-05-04 10:53 ` dkwo [this message]
2024-05-04 12:02 ` ahesford
2024-05-04 13:42 ` classabbyamp
2024-05-04 16:07 ` dkwo
2024-05-04 19:10 ` classabbyamp
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=20240504105346.499CC24E6D@inbox.vuxu.org \
--to=dkwo@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).