ONTAP Discussions

Undocumented cifs options

SCHLEGELM
3,904 Views

Hi,

 

could anyone please explain what these two options are for:

 

cifs.home_dir.generic_share_access_level 3
cifs.home_dir.generic_share_access_warn on

 

I can't access my homedir via \\filer\~ and i wonder if it has something to do with these undocumented options.

\\filer\%username% works.

 

Its a FAS2520 with ONTAP8.2.2

 

Markus

1 ACCEPTED SOLUTION

georgevj
3,862 Views

Please see the command manual page reference for data ontap 8.2.2 for details about these options.

You may access the following link to see the options man page.

https://library.netapp.com/ecmdocs/ECMP1511537/html/man1/na_options.1.html

 

I have copied the relevant text here.

 

 

cifs.home_dir.generic_share_access_warn
Controls the genertion of EMS message when clients attempt to access any of the to generic homedir shares ( "~", "cifs.homedir" or "~cifs.homedir"). Note that even if this option is set to "off", an EMS will be generated when Data ONTAP detects an actual attempt to perform an unsafe access.

Default: on

Effective: Immediately

Persistence: Remains in effect across system reboots

cifs.home_dir.generic_share_access_level
Controls access to generic homedir share named "~", "cifs.homedir" or "~cifs.homedir"

If this options is set to 0, all access using generic home directory share name is denied. Using a value of 0 prevents any possibility of a client with multiple connections, for example a Windows Terminal Server or Citrix, from granting incorrect access to other users of the same generic homedir share who may have files or directories named the same.

When this option is set to 1, access using generic home directory share name is always allowed. Set this option to 1, if you are sure there is no possibility of more than one user on the same client accessing the generic home directory share at the same time.

Setting this option to 2 allows restricted use of the generic home directory share name. Data ONTAP tries to detect conflicting access patterns and reject them. If the clients are SMB 2.1 aware, they are protected from compatibility issues by allowing only one user from a client to access using a particular generic home directory share name. All further attempts to access the same share name from same client by different users are rejected. If the clients are not SMB 2.1 aware, Data ONTAP tries to minimize the compatibility issues by disabling opportunistic locks (aka oplocks) on the files under the generic home directory share. Lack of opportunistic locks can result in performance degradation.

The value 3 for this option behaves similar to value 2 for SMB 2.1 aware clients, but rejects access to clients that are not SMB 2.1 aware. This setting avoids all compatibility issues and provides restricted access to the generic home directory share.

Default: 3

Values: 0, 1, 2, 3

Effective: Immediately

Persistence: Remains in effect across system reboots

If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.
Cannot find the answer you need? No need to open a support case - just CHAT and we’ll handle it for you.

View solution in original post

1 REPLY 1

georgevj
3,863 Views

Please see the command manual page reference for data ontap 8.2.2 for details about these options.

You may access the following link to see the options man page.

https://library.netapp.com/ecmdocs/ECMP1511537/html/man1/na_options.1.html

 

I have copied the relevant text here.

 

 

cifs.home_dir.generic_share_access_warn
Controls the genertion of EMS message when clients attempt to access any of the to generic homedir shares ( "~", "cifs.homedir" or "~cifs.homedir"). Note that even if this option is set to "off", an EMS will be generated when Data ONTAP detects an actual attempt to perform an unsafe access.

Default: on

Effective: Immediately

Persistence: Remains in effect across system reboots

cifs.home_dir.generic_share_access_level
Controls access to generic homedir share named "~", "cifs.homedir" or "~cifs.homedir"

If this options is set to 0, all access using generic home directory share name is denied. Using a value of 0 prevents any possibility of a client with multiple connections, for example a Windows Terminal Server or Citrix, from granting incorrect access to other users of the same generic homedir share who may have files or directories named the same.

When this option is set to 1, access using generic home directory share name is always allowed. Set this option to 1, if you are sure there is no possibility of more than one user on the same client accessing the generic home directory share at the same time.

Setting this option to 2 allows restricted use of the generic home directory share name. Data ONTAP tries to detect conflicting access patterns and reject them. If the clients are SMB 2.1 aware, they are protected from compatibility issues by allowing only one user from a client to access using a particular generic home directory share name. All further attempts to access the same share name from same client by different users are rejected. If the clients are not SMB 2.1 aware, Data ONTAP tries to minimize the compatibility issues by disabling opportunistic locks (aka oplocks) on the files under the generic home directory share. Lack of opportunistic locks can result in performance degradation.

The value 3 for this option behaves similar to value 2 for SMB 2.1 aware clients, but rejects access to clients that are not SMB 2.1 aware. This setting avoids all compatibility issues and provides restricted access to the generic home directory share.

Default: 3

Values: 0, 1, 2, 3

Effective: Immediately

Persistence: Remains in effect across system reboots

If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.
Cannot find the answer you need? No need to open a support case - just CHAT and we’ll handle it for you.
Public