Re: Should we split the network filesystem setup into two phases?
From: Aurélien Aptel <hidden>
Date: 2018-08-16 20:23:14
Also in:
ceph-devel, linux-cifs, linux-fsdevel, linux-nfs, linux-security-module, lkml
Steve French [off-list ref] writes:
In cifs we attempt to match new mounts to existing tree connections (instances of connections to a \\server\share) from other mount(s) based first on whether security settings match (e.g. are both Kerberos) and then on whether encryption is on/off and whether this is a snapshot mount (smb3 previous versions feature). If neither is mounted with a snaphsot and the encryption settings match then we will use the same tree id to talk with the server as the other mounts use. Interesting idea to allow mount to force a new tree id.
We actually already have this mount option in cifs.ko, it's "nosharesock".
What was the NFS mount option you were talking about? Looking at the nfs man page the only one that looked similar was "nosharecache"
Cheers, -- Aurélien Aptel / SUSE Labs Samba Team GPG: 1839 CB5F 9F5B FB9B AA97 8C99 03C8 A49B 521B D5D3 SUSE Linux GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)