Leela Gangavarapu

- Warning from provisioner pod can be neglected and this'll not be seen from next release - seems metrics from operator pod is still wonky, will take a look, however...

@amarts could you pls help here if possible?

- Well, the pool cr `metadata.name` is `standard` and the log is from storageclass `kadalu.critical` - Could you pls recheck your setup?

Hey @pantxisto, thanks for the detailed issue. - outright my thoughts go with usage of `ext4` since we test and support `xfs` I wasn't sure how well kadalu performs with...

- thanks for the update - to me it seems as a straightforward delete miss - not sure when were these PVCs removed from k8s, if the op wasn't successful...

> Some communications between pods were blocked and I unblock them. - uh oh, this should've mentioned earlier I think > mounthpath/data/brick/info/subvol - need to take a look, isn't above...

@pantxisto if your machines are stable now, pls consider closing this issue. thanks.

- when I saw only the issue summary, first thing occured to me was rook-ceph toolbox and you did mention that 😃 - I also see a couple of msgs...

- well, as a side note, Replica1 for database workload on root mount, I hope you are not looking for fault tolerance - it's a rpi and mmc storage, am...

- ah! the root partition is on ext4, currently server pods assumes xfs and maybe that's the issue - iiuc ext4 also supports xattrs however I don't want to bet...