on_after_set_allocation_size Event
Fires after a file's allocation size is changed.
Syntax
class CBFilterAfterSetAllocationSizeEventParams(object): @property def file_name() -> str: ... @property def allocation_size() -> int: ... @property def status() -> int: ... @status.setter def status(value) -> None: ... @property def file_context() -> int: ... @file_context.setter def file_context(value) -> None: ... @property def handle_context() -> int: ... @handle_context.setter def handle_context(value) -> None: ... @property def result_code() -> int: ... @result_code.setter def result_code(value) -> None: ... # In class CBFilter: @property def on_after_set_allocation_size() -> Callable[[CBFilterAfterSetAllocationSizeEventParams], None]: ... @on_after_set_allocation_size.setter def on_after_set_allocation_size(event_hook: Callable[[CBFilterAfterSetAllocationSizeEventParams], None]) -> None: ...
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 nt_status_to_win_32_error method. Please note that this event won't fire for failed requests unless the process_failed_requests 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 None.)
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.