Sai Chaithanya

After digging into the issue found the root cause of not being able to mount xfs formatted LVM volumes... It was happening due to incompatibility between xfs version inside the...

This behavior is due to compatibility issues between the container and the host operating system. openebs/lvm-localpv 0.6.0 version is already erasing the fs signatures on LVM volume before creating the...

> > This behavior is due to compatibility issues between the container and the host operating system. openebs/lvm-localpv 0.6.0 version is already erasing the fs signatures on LVM volume before...

Looks like even with above `force` flag issue is the still the same... When this issue occurred following are the system logs: ```sh Sep 12 18:51:53 centos-master kernel: XFS (dm-0):...

> mount: /var/lib/kubelet/mnt/store1: wrong fs type, bad option, bad superblock on /dev/mapper/lvm-manual1, missing codepage or helper program, or other error. Above is the error I got when tried to mount...

> image: openebs/provisioner-nfs:0.7.1 and image: openebs/jiva-operator:3.0.0 Hi @mbu147, I followed the same steps as mentioned in the description and observed that permissions of `nfsshare` directory are `755` and here is...

> I noticed that it apparently only occurs when each node is under a high IO load, so that he needs to "reconnect" the mount points. Hmm..., the system might...

> @mittachaitu Does this mean a migration from one CR to new CR & finally deleting the old CR? Exactly @AmitKumarDas. Once it known that things related to new CR...

> hi @mittachaitu , do you have maybe any example when it causes an issue ? It would be good to know some example. I will try to add the...

> @mittachaitu may I ask where the issue arises ? As I understand it is because json data is differently serialized in golang ? Do you have maybe json example...