Skip to content

NO-JIRA: docs/FAQ: link KCS for mixed composefs state #1939

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jbtrystram wants to merge 1 commit into
base: master
Choose a base branch
from
+4 −0
Open

NO-JIRA: docs/FAQ: link KCS for mixed composefs state #1939

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions docs/faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -582,3 +582,7 @@ metadata, that's why it's only a few megabytes in size, and it will always repor
Every version of the system will have its own unique composefs EROFS image.

With composefs, `/` is backed by `/sysroot` and any disk monitoring tools should be updated to watch the `/sysroot` mountpoint, which is the real physical root.

In some cases, after an upgrade, some nodes may have composefs enabled but not all of them. This is a known state caused by a bug in the MCO that
cause some nodes to apply the update twice, causing them to get composefs enabled sooner than other. This has no impact and will resolve itself

@Rolv-Apneseth Rolv-Apneseth May 27, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
cause some nodes to apply the update twice, causing them to get composefs enabled sooner than other. This has no impact and will resolve itself
causes some nodes to apply the update twice, causing them to get composefs enabled sooner than others. This has no impact and will resolve itself

at the next update. See this [knowledge base article](https://access.redhat.com/solutions/7139041) for more details.