Skip to content
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.

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

Support a minimal node kernel version for the XFS options compatibility #690

Open
jooola opened this issue Aug 8, 2024 · 0 comments · May be fixed by #747
Open

Support a minimal node kernel version for the XFS options compatibility #690

jooola opened this issue Aug 8, 2024 · 0 comments · May be fixed by #747
Assignees
Labels
enhancement New feature or request

Comments

@jooola
Copy link
Member

jooola commented Aug 8, 2024

TL;DR

Related to #648 (comment)

The node kernel may not support all options set during the mkfs.xfs command (from the csi driver image). This leads to problem when mounting the file system with incompatible features/options.

Expected behavior

To make sure the created XFS file system work on a known set of linux kernels, we might want to configure a set of options compatible with those node kernels.

For example, we want to support linux kernels >= 5.15, we can do the following:

$ cat /usr/share/xfsprogs/mkfs/lts_5.15.conf
# V5 features that were the mkfs defaults when the upstream Linux 5.15 LTS
# kernel was released at the end of 2021.

[metadata]
bigtime=1
crc=1
finobt=1
inobtcount=1
reflink=1
rmapbt=0

[inode]
sparse=1
nrext64=0

$ mkfs.xfs -f  -c options=/usr/share/xfsprogs/mkfs/lts_5.15.conf /dev/mapper/scsi-0HC_Volume_101135663
@jooola jooola added the enhancement New feature or request label Aug 8, 2024
@lukasmetzner lukasmetzner self-assigned this Oct 10, 2024
@lukasmetzner lukasmetzner linked a pull request Oct 10, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants