NetApp Community Update
This site will enter Read Only mode on July 23 as we prepare to move to a new platform. You will still be able to view content, but posting and replying will be temporarily disabled.
We're excited to launch our new Community experience on July 30 and more information will follow soon.
Stay connected during the transition - Join our Discord community today.

Network and Storage Protocols

Files become inaccessible when marked as offline on Netapp CIFS shares.

MohitD
5,133 Views

Has anyone seen this issue? Setting offline flag on a file over CIFS makes it unaccessible. We reied this on 8.2.2 7-mode and 8.3.1 cluster mode. 

 

Description

Setting the offline flag on a file in a Netapp CIFS share corrupts the file's NTFS security (ACLs and owner), rendering that file inaccessible to all users. If you then manually try to change the owner or add ACLs on this file, you get an “Access denied” error.

 

Repro steps:

On any Windows desktop,

  1. Map a Netapp CIFS share.
  2. Create a file in this share.
  3. Verify that it has valid ACLs and owner.
    • Right click on the file and select Properties.
    • Go to the ‘Security’ tab and click on Advanced.
    • Verify that the owner and permission entries are valid.
  4. Open Powershell and run the following commands:
    • $file = Get-Item <File-Path>
      • Use the full network path for <File-Path>.
    • $file.Attributes = $file.Attributes -bor [System.IO.FileAttributes]::Offline
      • This sets the offline flag on the file. You should see a grey ‘X’ on the file’s icon, indicating that it’s an offline file.
      • Run $file.Attributes to confirm if Offline attribute is set.
  5. Try opening the file. 
    • You will get an ‘Access denied’ error.
  6. Now check the permission entries and owner of this file.
    • Permission entries list will be empty and you’ll see ‘Unable to display owner’ for the owner.
  7. Try changing the owner or adding a permission entry.
    • You will get an ‘Access denied’ error.
1 REPLY 1

Sahana
5,025 Views

Hi,

 

Please check the junction path. Also refer Microsoft article Offline File Synchronization.

If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.
Public