When I make a SnapLock volume, open a CIFS share on it and try to create a new folder in it - it's automatically created & called "New Folder" (Windows default) and I cannot rename it!
Sure, I can use qtrees instead, but if there are not retention policies and auto_commit is turned off - folders placed in that share should be accessed, modified and deleted in accordance with user's privileges. Just like with files.
I can access it, delete it, but not modify it.
What's the catch? Why is a folder instantly set to read-only??
I know that this question was asked a long time back and it is already answered. However, still posting as I could find a more appropriate answer -
An important consideration for SnapLock storage is how directories are treated. Directories, once created on a SnapLock volume, cannot be renamed regardless of their access permissions. This is an important consideration when using the Microsoft Explorer tool to create a new folder. The first step Explorer takes is creating a directory called New Folder, then attempts afterward to rename this to something more useful, which is not possible on a SnapLock volume. Manually creating directories on SnapLock volumes in either the Microsoft or the UNIX environment is better handled using mkdir in a command line interface. While directories cannot be renamed, they can be deleted as long as no files committed to WORM state are contained within their hierarchy.