I have EMC Celerra NX4FC with 6.0.36-4 software. I was create file system with FLR-C function and used it several years. Today this file system not needed, i removed it share from CIFS fileserver. In process deleting filesystem from Celerra by clicking: Storage -> File Systems -> Right Click on FS ->choose "Delete" - I see this message: "The file systems selected for deletion contain at least one file system with FLR-C enabled. Protected files still exist on this file system and the file system cannot be deleted"
I don't know how to remove this file system or disable FLR (read that it can not be disabled). All my attempts change FLR attributes via FLR Toolkit software were failed, FLR Toolkit used DHSM but Celerra can not activate DHSM on FLR-enabled FS:
That wont help if he has files with infinite retention on a FLR compliance file system
For FLR enterprise the infinite retention date can be reduced – for compliance infinite really means.
We do state that clearly in our documentation “Setting the value to infinite mean that the file can never be deleted”
Only way to get rid of the fs in that case is to delete all LUNs including the DART OS and re-install the system – which of course deletes all data on it.
The FLR Toolkit was designed specifically to work with the FLR feature in Celerra (also known as Celerra WORM). CWORM works by changing the mtime on the file to the expiration date of the file and then setting the file to read only. Once the file is set to read-only, it cannot be changed until the mtime expires. FLR-E (Enterprise) allows you to then change the mtime again (to something before the current time) so that you can delete (but not modify) the file. FLR-C (Compliance) does not allow you to change the mtime once the file has been locked. The FLR Toolkit simply automates the process of setting the appropriate mtime and locking the files.
A file in an file system with file-level retention enabled is in one of three possible states: CLEAN, FLR, or EXPIRED. The administrator manages files in the FLR state by setting retention periods that, until expiration, prevent the files from being deleted. FLR files can be grouped by directory or batch process, thus enabling the administrator to manage the file archives on a file system basis, or to run a script to locate and delete files in the EXPIRED state. The administrator has the ability to delete an file system with file-level retention enabled, but cannot delete or modify files in the FLR state. The path to a file in the FLR state is also protected from modification, which means a directory on a file system with file-level retention enabled cannot be renamed or deleted unless it is empty.
Rainer is right, you can't delete the file system with file-level retention enabled. However, you can set the access time of file system to a valid time which is in the near past where the file deletion is allowed, afterwards, you can delete this file system. I recommend you to refer to the primus which I mentioned in my last thread.
Rainer_EMC
6 Operator
•
8645 Posts
1171
0
Posted July 23rd, 2014 02:00
That wont help if he has files with infinite retention on a FLR compliance file system
For FLR enterprise the infinite retention date can be reduced – for compliance infinite really means.
We do state that clearly in our documentation “Setting the value to infinite mean that the file can never be deleted”
Only way to get rid of the fs in that case is to delete all LUNs including the DART OS and re-install the system – which of course deletes all data on it.