A snapshot can get one ore more "locks" from other parts in OneFS, which means deletion is deferred beyond expiration time until all locks are released. You can see whether a given snapshot has locks:  So just try it out (the OneFS simulator will do); a regular snapshot should get a lock once the triggered SyncIQ job kicks in. makes sense? -- Peter 
Hi We are planning on implementing SyncIQ policy execution based on "Whenver a snapshot of the source directory is taken", and this got me thinking: If I have a repeated snapshot schedule for, lets say every 5, 10 or 15 minutes, with an expiration set to 2 hours. What happens if, for some reason, SyncIQ misses the sync (maybe the replication target is offline) when it's supposed to? What happens if the last sync is based on the snapshot that's about to expire next? Does a snapshot with a set expiration actually really expire if the system's SyncIQ policies are based on this snapshot-chain or is there a mechanism in place that prevents expiration and automatic delete of (non SIQ type) snapshots that are still the base for SyncIQ compare+replication? This does not really get covered in Dell Isilon/PowerScale documentation... Thanks for any input!
SyncIQ run Policy when Snapshot of Source Dir is taken