Fsck b4 mount #47
Open
Fsck b4 mount #47
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I'm sorry to come back to you late. Thanks for the PR, i agree, we need some sort of checking before mounting - but i don't want this to be imposed, it should come with an option to able to skip or enable it, if you are working on it i'll be glad to merge. |
bedhanger
force-pushed
the
fsck-b4-mount
branch
from
21a2b65 to
b394f9f
Compare
bedhanger
force-pushed
the
fsck-b4-mount
branch
from
b394f9f to
2d9b418
Compare
This change adds support for checking the integrity of filesystems mounted from within the initramfs. Systemd wants the filesystem on which /usr resides mounted when it finally takes over from initramfs, but does not seem to launch a systemd-fsck job for that filesystem later on, even if the filesystem is mounted ro. The result is that the /usr-hosting filesystem could go unchecked for a long time. The problem is not limited to /usr, but all early mounts mentioned in initramfs.mounts. Furthermore, fsck'ing should work on the physical device, final mounting should take into account existing symbolic or logical disk/LVM names for the purpose of enhanced readability.
bedhanger
force-pushed
the
fsck-b4-mount
branch
from
2d9b418 to
9fbfd75
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The changes add support for checking the integrity of
filesystems mounted from within the initramfs.
Systemd wants the filesystem on which /usr resides mounted when
it finally takes over from initramfs, but does not seem to
launch a systemd-fsck job for that filesystem later on, even if
the filesystem is mounted ro. The result is that the
/usr-hosting filesystem could go unchecked for a long time.
The problem is not limited to /usr, but all early mounts
mentioned in initramfs.mounts.
Furthermore, fsck'ing should work on the physical device, final
mounting should take into account existing symbolic or logical
disk/LVM names for the purpose of enhanced readability.