I'm setting up a demo k8s cluster for use with [MinIO storage system](https://min.io). I've encountered issues with the nodes running on LXC/LXD with Ubuntu 22.04. [According to one of the MinIO project members](https://github.com/minio/directpv/issues/919), the failures are due to non-standard arguments supported for XFS. Does anyone know if this is true and how to check or correct it? It seems like the default kernel for the LXD Ubuntu22.04 VM is based on 5.15 and with some modifications for kvm. It seems like XFS is working on some level, but may not support all arguments used by [DirectPV](https://github.com/minio/directpv) for setting up the storage drives
Unable to setup due to invalid arg with XFS
Code:
root@ubuntu-k3s-homelab-4:~# uname -a
Linux ubuntu-k3s-homelab-4 5.15.0-1062-kvm #67-Ubuntu SMP Wed Jun 19 13:44:51 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
# Create test xfs filesystem, showing reflink supported
root@ubuntu-k3s-homelab-4:~# mkfs.xfs /dev/sde
meta-data=/dev/sde isize=512 agcount=4, agsize=2752512 blks
= sectsz=512 attr=2, projid32bit=1
= crc=1 finobt=1, sparse=1, rmapbt=0
= reflink=1 bigtime=0 inobtcount=0
data = bsize=4096 blocks=11010048, imaxpct=25
= sunit=0 swidth=0 blks
naming =version 2 bsize=4096 ascii-ci=0, ftype=1
log =internal log bsize=4096 blocks=5376, version=2
= sectsz=512 sunit=0 blks, lazy-count=1
realtime =none extsz=4096 blocks=0, rtextents=0
Discarding blocks...Done.
root@ubuntu-k3s-homelab-4:~# mount /dev/sde /mnt/test
root@ubuntu-k3s-homelab-4:~# df -hT /mnt/test/
Filesystem Type Size Used Avail Use% Mounted on
/dev/sde xfs 42G 332M 42G 1% /mnt/testUnable to setup due to invalid arg with XFS
Code:
➜ ~ kubectl directpv discover
Discovered node 'ubuntu-k3s-homelab-3' ✔
Discovered node 'ubuntu-k3s-homelab-4' ✔
Discovered node 'ubuntu-k3s-homelab-5' ✔
Discovered node 'ubuntu-k3s-homelab-kubernetes-2' ✔
┌─────────────────────┬──────────────────────┬───────┬─────────┬────────────┬────────────────────┬───────────┬─────────────┐
│ ID │ NODE │ DRIVE │ SIZE │ FILESYSTEM │ MAKE │ AVAILABLE │ DESCRIPTION │
├─────────────────────┼──────────────────────┼───────┼─────────┼────────────┼────────────────────┼───────────┼─────────────┤
│ 8:0$lEwxKEUO56Nv... │ ubuntu-k3s-homelab-4 │ sda │ 42 GiB │ - │ QEMU QEMU_HARDDISK │ YES │ - │
│ 8:32$guHrIB+MilW... │ ubuntu-k3s-homelab-4 │ sdc │ 42 GiB │ - │ QEMU QEMU_HARDDISK │ YES │ - │
│ 8:48$6v3flv4STNc... │ ubuntu-k3s-homelab-4 │ sdd │ 42 GiB │ - │ QEMU QEMU_HARDDISK │ YES │ - │
│ 8:64$2M83bdXhXgW... │ ubuntu-k3s-homelab-4 │ sde │ 42 GiB │ - │ QEMU QEMU_HARDDISK │ YES │ - │
│ 8:16$xIJClQ3ZRhX... │ ubuntu-k3s-homelab-5 │ sdb │ 190 GiB │ - │ QEMU QEMU_HARDDISK │ YES │ - │
│ 8:32$CYsmluXJnIB... │ ubuntu-k3s-homelab-5 │ sdc │ 190 GiB │ - │ QEMU QEMU_HARDDISK │ YES │ - │
│ 8:48$dmx9SRkh27g... │ ubuntu-k3s-homelab-5 │ sdd │ 190 GiB │ - │ QEMU QEMU_HARDDISK │ YES │ - │
│ 8:64$qbOcPZbdJTY... │ ubuntu-k3s-homelab-5 │ sde │ 190 GiB │ - │ QEMU QEMU_HARDDISK │ YES │ - │
└─────────────────────┴──────────────────────┴───────┴─────────┴────────────┴────────────────────┴───────────┴─────────────┘
➜ ~ kubectl directpv init drives.yaml --dangerous
█████████████████████████████████████░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ 50%
Processing initialization request '8045f27a-e55b-4f64-8a64-b25b6dd8efa5' for node 'ubuntu-k3s-homelab-5' ∙∙∙
Processing initialization request 'e91bb963-9d67-4d7f-b05e-6d16e8765076' for node 'ubuntu-k3s-homelab-4' ∙∙∙
Error; unable to initialize devices; context deadline exceeded
➜ ~ kubectl logs -f node-server-vv5f9 -n directpv -c node-controller
I0725 19:01:24.975211 7952 reflector.go:289] Starting reflector *v1beta1.DirectPVNode (5m0s) from k8s.io/client-go@v0.28.11/tools/cache/reflector.go:229
I0725 19:01:24.975447 7952 reflector.go:325] Listing and watching *v1beta1.DirectPVNode from k8s.io/client-go@v0.28.11/tools/cache/reflector.go:229
I0725 19:01:25.075027 7952 controller.go:141] node controller synced and ready
E0725 19:01:25.372691 7952 event.go:310] "unable to create initrequest event handler" err="unable to mount; invalid argument"
E0725 19:01:25.372940 7952 main.go:147] "unable to execute command" err="initrequest controller stopped"