AfterSetAllocationSize Event

Fires after a file's allocation size is changed.

Syntax

public class DefaultCbfilterEventListener implements CbfilterEventListener {
  ...
  public void afterSetAllocationSize(CbfilterAfterSetAllocationSizeEvent e) {}
  ...
}

public class CbfilterAfterSetAllocationSizeEvent {
  public String fileName;
  public long allocationSize;
  public int status;
  public long fileContext;
  public long handleContext;
  public int resultCode;
}

Remarks

This event fires after the allocation size of the file specified by FileName is changed.

Applications only need to handle this event if they've added a standard filter rule that includes the FS_CE_AFTER_SET_SIZES flag.

The AllocationSize parameter reflects the new allocation size, in bytes. A file's allocation size is typically larger than its actual size since filesystem operations often reserve space on disk before writing additional data to a file.

The Status parameter contains an NT status code that indicates the outcome of the operation; 0 indicates success. To convert this value to a Win32 error code, call the NtStatusToWin32Error method. Please note that this event won't fire for failed requests unless the ProcessFailedRequests property is enabled. Applications may change this parameter's value if they want a different NT status code to be returned.

The FileContext and HandleContext parameters are placeholders for application-defined data associated with the file and specific handle, respectively. Please refer to the Contexts topic for more information. (If the system's cache manager or memory manager initiated the operation, HandleContext may be absent, in which case it will be 0.)

The ResultCode parameter will always be 0 when the event is fired. If the event cannot be handled in a "successful" manner for some reason (e.g., a resource isn't available, security checks failed, etc.), set it to a non-zero value to report an appropriate error. Please refer to the Error Reporting and Handling topic for more information.

This event is fired synchronously; please refer to the Event Types topic for more information.