Description of problem:
When we mount the CIFS protocol without mentioning version, it autonegotiated to the highest supported version of SMB2/3 but when we check the from "mount" command it still shows the default version ( which is version 1.0 from man page )
Version-Release number of selected component (if applicable):
# rpm -qa | grep -i kernel
How reproducible: Always
Steps to Reproduce:
1. mount the gluster volume with CIFS protocol
# mount -t cifs -o username=root,password=foobar \\\\<IP of Gluster>\\gluster-testvol_replicated /mnt/testvol_replicated_cifs
2. check the version
# mount | grep -i cifs
\\<IP of Gluster>\gluster-testvol_replicated on /mnt/testvol_replicated_cifs type cifs (rw,relatime,vers=default,cache=strict,username=root,domain=,uid=0,noforceuid,gid=0,noforcegid,addr=<IP of Gluster>,file_mode=0755,dir_mode=0755,soft,nounix,serverino,mapposix,rsize=1048576,wsize=1048576,echo_interval=60,actimeo=1)
3. In above o/p, vers=default which is misleading the user. It should show the correct version
vers=default which is misleading the user
vers=default which is misleading the user. It should show the correct version
*** This bug has been marked as a duplicate of bug 1588912 ***
> Can we keep bug it open to track the necessary changes required in man
> mount.cifs(8) to reflect this auto negotiation mechanism? As of now it is
> misleading to state that v1.0 is the default even though it is not used.
> Accordingly bug summary can be adjusted to convey the intend.
Yes, we can. I will re-open it. But I think it's clearer that file a new bug about the description for "vers" in man mount.cifs(8). Such as "The default since v4.13.5 is for the client and server to negotiate the highest possible version greater than or equal to 2.1. In kernels prior to v4.13, the default was 1.0. For kernels between v4.13 and v4.13.5 the default is 3.0.".