Start a Conversation

Unsolved

This post is more than 5 years old

1836

January 9th, 2018 08:00

vnx file system with CTA archived files - unable to delete

We have a couple of filesystems that had (in the past) CTA archive runs on them with a infinite retention value set.  We cannot delete these files on the VNX and because some users have modified the file permissions we cannot even read these files or modify the permissions.  I have spoken with support and they said the unable to delete/modify is because of the infinite retention value.  We are getting ready to plan a migration off of the VNX to another platform (Unity or NetApp) but we are unsure what to do to copy these files.   Any thoughts?

Court

8.6K Posts

January 9th, 2018 14:00

You can always read/copy via NFS as root

retention has nothing to do with ability to read it - it will only deny delete or modification.

If you cannot read read a file its because of Unix access rights or CIFS ACLs and NOT because of retention state.

If my memory serves me correct you should also be able to change read permission or ACL or take ownership of a locked file.

This is easy to verify by testing and looking at the FLR activity log.

4 Posts

January 10th, 2018 04:00

Thanks Rainer.  I was able to NFS mount the file system and was able to copy the file to a different name and have permission to modify/delete the copied file.  I am unable to change permissions or owner on the original file.  As I indicated these are files archived to Centera by CTA (I am guessing that these would be the 8k stub file) that the data mover understands are not to be modified/deleted.

I was not able to find a FLR log on my VNX, any ideas where to look?

8.6K Posts

January 11th, 2018 02:00

FLR activity logs are in a directory called FLR_Logs in the root of the file system

details about the logs are in the VNX FLR manual

are you able to chown via NFS ?

4 Posts

January 11th, 2018 05:00

Rainer:   We do not have FLR turned on.  I setup my Linux VM as a root host but was not able to chown or chmod any of the protected files on the NFS file system.

4 Posts

January 12th, 2018 03:00

Yes but that was set by CTA (Cloud Tiering Application) by mistake.

8.6K Posts

January 12th, 2018 03:00

didnt you say you have ... infinite retention value ... set ?

8.6K Posts

January 15th, 2018 04:00

I'm not sure I understand

you can only have file with retention IF the file system has FLR enabled and then you have an FLR activity log

I would suggest you continue troubleshooting this with support or engage with professional service

I dont think it can be solved on a forum with the info available - most likely it would need direct access or network traces to find out whats going on

No Events found!

Top