From: dkwo <dkwo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: runit-void: fix issue with fsck on mounted partitions
Date: Sun, 05 May 2024 16:44:02 +0200 [thread overview]
Message-ID: <20240505144402.37B5E22302@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-50192@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 525 bytes --]
New comment by dkwo on void-packages repository
https://github.com/void-linux/void-packages/pull/50192#issuecomment-2094836728
Comment:
With `bdev_allow_write_mounted=true`, the behavior is as before.
Without it, it prints the same message
```
fsck.ext4: Device or resource busy while trying to open /dev/mapper/cryptroot-root
Filesystem mounted or opened exclusively by another program?
```
and then it continues (without fsck-ing other partitions like /boot).
So this seems to work as expected in my simple setup.
next prev parent reply other threads:[~2024-05-05 14:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-04 20:18 [PR PATCH] " classabbyamp
2024-05-04 20:18 ` [PR PATCH] [Updated] " classabbyamp
2024-05-04 20:21 ` classabbyamp
2024-05-05 12:26 ` classabbyamp
2024-05-05 14:19 ` classabbyamp
2024-05-05 14:44 ` dkwo [this message]
2024-05-05 14:46 ` dkwo
2024-05-05 15:48 ` classabbyamp
2024-05-05 16:04 ` [PR PATCH] [Merged]: " 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=20240505144402.37B5E22302@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).