Merged
Conversation
kvinwang
force-pushed
the
storage-fs
branch
from
cf185a2 to
f15aab5
Compare
kvinwang
force-pushed
the
storage-fs
branch
from
f15aab5 to
d0e1b3f
Compare
Collaborator
|
We should update the guest agent to expose the current storage filesystem. |
Collaborator
Author
It's already in the app-compose.json. Also put in the RTMR3 event log. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR allows the app to select using
zfsorext4as the storage filesystem.Caution
ZFS: Ensures filesystem integrity with built-in data protection features.
ext4: Provides better performance for database applications with lower overhead and faster I/O operations, but no strong integrity protection.