isi worm mkdir --override

Question

I see the --override option in isi worm mkdir command:

{--override | -o} { | none}

Specifies an override retention date. The override retention date is a specific date

that files committed to a WORM state within this directory are released from a WORM

state. You can only increase the retention period expiration date of WORM committed

files.

What does override option do when isi worm is creating a new SmartLock directory, where there's no WORM file in the new directory at all?

Does the override value application to new WORM file? If so how does the override value works together with the min/max/default retention period?

russ_stevenson · Accepted Answer

The --override setting will override any default or explicit retention placed on a committed file, it has no impact on empty SmartLock directories or uncommitted files.

An example of override in use:

mav1-1# isi smartlock list -l

------+-----------------+-----------+---------------------+-----------+-----------+-----------+-------------------+-----------

65536 | /ifs/smartlock1 | SmartLock | 2014-01-01 00:00:00 | 1d | None | 1w | None | On

mav1-1# isi smartlock info --path=/ifs/smartlock1/1.txt

SmartLock Info for: /ifs/smartlock1/1.txt

SmartLock Root Directory

------------------------

ID | Root Path

------+----------------

65536 | /ifs/smartlock1

SmartLock State: COMMITTED Expires: 2013-11-26 12:29:11

* Expire date currently overridden to: 2014-01-01 00:00:00

The addition of an override date will impact all existing committed files and any new files that are committed as long as the override is in place. It can be removed at any time and will impact all committed files; see example below, the same file but the override on the directory has been removed.

mav1-1# isi smartlock modify --path=/ifs/smartlock1 --override=none

!! Override date set: None

mav1-1# isi smartlock info --path=/ifs/smartlock1/1.txt

SmartLock Info for: /ifs/smartlock1/1.txt

SmartLock Root Directory

------------------------

ID | Root Path

------+----------------

65536 | /ifs/smartlock1

SmartLock State: COMMITTED Expires: 2013-11-26 12:29:11

File no longer has an override date attached. Expiration is now based on the date that was used when file was committed; default, min/max or explicit.

Min/Max are related to explicit retention when used and an override date will just place the explicit override date on that file irrespective of those settings.

jenny_lam · Answer

Hi Russ,

I want to follow up on this question again. If the --override setting has no impact on empty SmartLock directories or uncommitted files, why is the --override setting available in the "isi worm mkdir" command? What does --override setting do, when mkdir creates a new SmartLock directory containing no file to begin with?

Syntax

isi worm mkdir --path

[--default { | none | inf}]

[--override { | inf}]

[--min { | none | inf}]

[--max { | none | inf}]

[--privdel ]

[--autocommit { | none}]

[--compliance]

russ_stevenson_ · Answer

Hey Jenny,

All the isi worm mkdir --path --override does is set the override date that is set on the SL directory at create/designation time, since no files exist and nothing is committed it has no effect. Since I have not defined a default retention period, any file would expire immediately BUT b/c the directory has a defined override date set the file retention will be held to that date, if i was to remove the override the file would have expired.

But override date only has effect on committed file

1. Create a SmartLock with --override set:

wak1# isi smartlock mkdir --path=/ifs/smartlock2 --override=20500101

!! /ifs/smartlock2 is now a SmartLock root directory. Id: 65538

!! Override date set: 2050-01-01 00:00:00

!! Warning: No default retention offset specified. Files committed

!! without specified retention date will expire immediately.

!! Warning: No autocommit window specified. Files must be manually

!! committed.

wak1# isi smartlock list -l

------+-----------------+-----------+---------------------+-----------+-----------+-----------+-------------------+-----------

2. Create file:

wak1# cd /ifs/smartlock2

wak1# touch 1.txt

3. Review SmartLock status, file not committed, no override date:

wak1# isi smartlock info --path=/ifs/smartlock2/1.txt

SmartLock Info for: /ifs/smartlock2/1.txt

SmartLock Root Directory

------------------------

ID | Root Path

------+----------------

65538 | /ifs/smartlock2

SmartLock State: not committed Retention Date: Not Set

4. Commit the file:

wak1# chmod a-w /ifs/smartlock2/1.txt

5. Review SmartLock status:

wak1# isi smartlock info --path=/ifs/smartlock2/1.txt

SmartLock Info for: /ifs/smartlock2/1.txt

SmartLock Root Directory

------------------------

ID | Root Path

------+----------------

65538 | /ifs/smartlock2

6. File committed, would be expired except for the override date keeping it locked.

SmartLock State: COMMITTED Expires: 2014-01-08 15:20:23

* Expire date currently overridden to: 2050-01-01 00:00:00

wak1# date

Wed Jan 8 15:20:47 EST 2014

wak1# rm -rf /ifs/smartlock2/1.txt

rm: /ifs/smartlock2/1.txt: Read-only file system

7. If i remove the override date the file will be in an EXPIRED state now

wak1# isi smartlock modify --path=/ifs/smartlock2 --override=none

!! Override date set: None

wak1# isi smartlock list -l

------+-----------------+-----------+---------------+-----------+-----------+-----------+-------------------+-----------

wak1# isi smartlock info --path=/ifs/smartlock2/1.txt

SmartLock Info for: /ifs/smartlock2/1.txt

SmartLock Root Directory

------------------------

ID | Root Path

------+----------------

65538 | /ifs/smartlock2

8. File is expired, can be deleted

SmartLock State: COMMITTED Expired: 2014-01-08 15:20:23

9. But if I reset the override, the file will be locked again

wak1# isi smartlock list -l

------+-----------------+-----------+---------------------+-----------+-----------+-----------+-------------------+-----------

wak1# isi smartlock modify --path=/ifs/smartlock2/ --override=20201231

!! Override date set: 2020-12-31 00:00:00

wak1# isi smartlock info --path=/ifs/smartlock2/1.txt

SmartLock Info for: /ifs/smartlock2/1.txt

SmartLock Root Directory

------------------------

ID | Root Path

------+----------------

65538 | /ifs/smartlock2

SmartLock State: COMMITTED Expires: 2014-01-08 15:20:23

* Expire date currently overridden to: 2020-12-31 00:00:00

10. Unable to remove file, file locked by override date

wak1# rm -rf /ifs/smartlock2/1.txt

rm: /ifs/smartlock2/1.txt: Read-only file system

Override is just a method to force a commit/WORM status until a specific date on all file that have been committed within a SmartLock root.

Hope this clears it up,

russ

Isilon

isi worm mkdir --override

Was this post helpful?