Venky Shankar

Command output fields are available in document - https://github.com/ceph/ceph/pull/45949/files#diff-45f83f814dee15dc10b8025029c5400a50e6c8972d5b6a795b62d62e0b278986R100

The mount syntax changes have been kept backward compatible. The old syntax _should_ work with newer kernels.

@ygg-drop dmesg and running mount helper with verbose flag would help debug what's going on.

> And mount command in verbose mode: > > ``` > [root@worker-12 /]# mount -v -t ceph 192.168.21.11,192.168.21.12,192.168.21.13:/ /mnt -o 'name=admin,secretfile=/tmp/auth.key,_netdev,fs=cephfs' > parsing options: rw,name=admin,secretfile=/tmp/auth.key,fs=cephfs,_netdev > mount.ceph: options "name=admin,mds_namespace=cephfs". >...

> @vshankar It hangs for a bit and then returns to prompt dmesg relevant messages: > > ``` > [691243.945358] libceph: mon1 (1)192.168.21.12:6789 session established > [691243.945750] libceph: mon1 (1)192.168.21.12:6789...

> @vshankar yes indeed, with mount command i can manually mount it on worker node OK. Is the same command run by ceph-csi plugin? Can you enable mount helper debugging...

> > mount helper debugging when its being run by ceph-csi? > > sorry, can you point out where to look how to enable debug by ceph-csi ? I have...

> I wonder whats the `cat /proc/mounts | grep ceph` output where the mount succeeds at the command-line /proc/mounts has the record to the cephfs mount as mentioned in this...

@Informize Without debug logs from a failed mount instance, its hard to tell what's going on.

> This is all the debug information that i have. Is there a way how to get extra debug information ? I see there is also another github issue related...