Library Table of Contents Index Previous Page (Alt-p) Next Page (Alt-n) Comments

Understanding read-only bits

What a read-only bit is  Top

The read-only bit is a bit that is set on a file-by-file basis to reflect whether a file is writable (disabled) or read-only (enabled).

Which clients set a read-only bit  Top

CIFS clients that use MS-DOS and Windows can set a per-file read-only bit. NFS clients do not set a per-file read-only bit, because NFS clients do not have any protocol operations that use a per-file read-only bit.

When Data ONTAP can set a read-only bit  Top

Data ONTAP can set a read-only bit on a file when a CIFS client that uses MS-DOS or Windows creates that file. Data ONTAP can also set a read-only bit when a file is shared between NFS clients and CIFS clients. Some software, when used by NFS clients and CIFS clients, requires the read-only bit to be enabled.

How Data ONTAP keeps appropriate permissions on shared files  Top

For Data ONTAP to keep the appropriate read and write permissions on a file shared between NFS clients and CIFS clients, it treats the read-only bit according to the following rules:

Deleting files with the read-only bit set  Top

Windows does not allow you to delete a file with the read-only bit enabled. Some multiprotocol source control applications require UNIX delete semantics; files for these applications also cannot be deleted when the read-only bit is enabled.

To allow deletion of files using UNIX delete semantics when the read-only bit is enabled, complete the following step.

Step

Action

1

Enter the following command:

options cifs.perm_check_ro_del_ok on

This option is turned off by default.

Library Table of Contents Index Previous Page (Alt-p) Next Page (Alt-n) Comments