3.2.4.1 Sequencing Rules

  • Article

Responding to Quota Events: If a Quota Event (section 3.2.7.1) occurs, the server MUST run (section 3.2.4.4) each Notifications (Actions) (section 3.2.1.2.1) associated with the threshold of the quota that caused the Quota Event. The server MUST NOT run any actions that cannot be associated with the threshold of the quota that caused the event. If the quota's ratio of Quota usage to Quota limit is greater than or equal to one, and if the quota's Quota limit mode is set to Hard quota, the server MUST fail the I/O operation.

Responding to Quota Usage Update Events: If a Quota Usage Update Event (section 3.2.7.2) occurs, the server MUST update the Quota usage of the quota with the size of the I/O operation. The server MUST process Quota Usage Update Events before processing Peak Quota Usage Events.

Responding to Peak Quota Usage Events: If a Peak Quota Usage Event (section 3.2.7.3) occurs, the server MUST set the Peak quota usage of the Persisted Directory Quota (section 3.2.1.2.1.1) representing the quota that caused the Peak Quota Usage Event to the current Quota usage of the quota. The server MUST also set the Peak quota usage time stamp of the Persisted Directory Quota to the current time.

Responding to File Screen Events: If a File Screen Event (section 3.2.7.4) occurs, the server MUST run (section 3.2.4.4) each Notification (Actions) (section 3.2.1.3.1) associated with the File Screen (section 3.2.1.3.1) that caused the File Screen Event. If the File screen mode is set to Hard screen, then the File Screen will block file I/O that violates the File Screen. If the File screen mode is set to Soft screen, then the File Screen will not block file I/O that violates the File Screen. If Enable file screen audit (section 3.2.1.9) is set to true, the server MUST store an audit record for each File Screen prohibited file so that the record can be scanned later and presented in a File Screen Audit report. For details about the audit log record requirements, see section 3.2.1.3.1.

Responding to Directory Creation Events: If a Directory Creation Event (section 3.2.7.5) occurs, the server MUST create a Persisted Directory Quota for the new subdirectory and add it to the List of Persisted Directory Quotas (section 3.2.1.2). The new Persisted Directory Quota MUST have the same properties as the Auto Apply Quota (section 3.2.1.2.2) that caused the Directory Creation Event, with the following exceptions:

  • The server MUST set the Folder path to the directory that caused the Directory Creation Event.

  • The server MUST set the Auto apply quota id to the ID of the Auto Apply Quota (section 3.2.1.2.2) that caused the Directory Creation Event.

  • Peak quota usage is set to zero.

  • Peak quota usage time stamp is set to the current time.

  • Quota usage is set to zero.

  • Quota state is set to incomplete.

After creating the new Persisted Directory Quota, the server MUST start a quota scan (section 3.2.1.12.4) for the new Persisted Directory Quota and add it to the List of Persisted Directory Quotas.

Responding to Directory Deletion Events: If a Directory Deletion Event (section 3.2.7.6) occurs, the server MUST remove from the associated list any of the following objects configured with the deleted directory as their Folder path:

Any non-persisted objects with the deleted directory configured as their Folder path MUST NOT be changed. Any persisted or non-persisted object where the deleted directory is a value in the namespace roots of the object MUST NOT be changed. Any Persisted Auto Apply Quota where the deleted directory is a value of the Exclude folders MUST NOT be changed.

Responding to Directory Rename Events: If a Directory Rename Event (section 3.2.7.7) occurs, the server MUST update the Folder path of any Persisted Directory Quotas, Persisted Auto Apply Quota, Persisted File Screens, or Persisted File Screen Exceptions where the Folder path equals the old directory path, to the new directory path, without any manual configuration changes from the client. Any non-persisted objects with the renamed directory configured as their Folder path MUST NOT be changed. Any persisted or non-persisted object where the renamed directory is a value in the namespace roots of the object MUST NOT be changed. Any Persisted Auto Apply Quota where the renamed directory is a value of the Exclude folders MUST NOT be changed.

Responding to Volume Discovery Events: If a Volume Discovery Event (section 3.2.7.8) occurs, the server MUST add the volume to the Volume List (section 3.2.1). If the server has previously stored Persisted Directory Quotas on that volume, the server MUST concatenate the List of Persisted Directory Quotas with the Persisted Directory Quotas on the volume. If the server has previously stored Persisted Auto Apply Quota on that volume, the server MUST concatenate the List of Persisted Auto Apply Quotas with the Persisted Auto Apply Quota on the volume. If the server has previously stored Persisted File Screens on that volume, the server MUST concatenate the List of Persisted File Screens with the Persisted File Screens on the volume. If the server has previously stored Persisted File Screen Exceptions on that volume, the server MUST concatenate the List of Persisted File Screen Exceptions with the Persisted File Screen Exceptions on the volume.

Responding to Volume Removal Events: If a Volume Removal Event (section 3.2.7.9) occurs, the server MUST remove the volume from the Volume List. If there are any Persisted Directory Quotas with a Folder path on the volume, the server MUST remove the Persisted Directory Quota from the List of Persisted Directory Quotas. If there are any Persisted Auto Apply Quotas with a path on the volume, the server MUST remove the Persisted Auto Apply Quota from the List of Persisted Auto Apply Quotas. If there are any Persisted File Screens with a path on the volume, the server MUST remove the Persisted File Screen from the List of Persisted File Screens. If there are any Persisted File Screen Exceptions with a path on the volume, the server MUST remove the Persisted File Screen Exceptions from List of Persisted File Screen Exceptions. Any Non-Persisted Directory Quotas, Non-Persisted Auto Apply Quotas, Non-Persisted File Screens, or Non-Persisted File Screen Exceptions that have a Folder path on the removed volume MUST NOT be removed from any lists of non-persisted objects they are a member of.