NotifySetAllocationSize Event

Fires when a file's allocation size has been changed.

Syntax

// CBFilterNotifySetAllocationSizeEventArgs carries the CBFilter NotifySetAllocationSize event's parameters.
type CBFilterNotifySetAllocationSizeEventArgs struct {...}

func (args *CBFilterNotifySetAllocationSizeEventArgs) FileName() string
func (args *CBFilterNotifySetAllocationSizeEventArgs) AllocationSize() int64
func (args *CBFilterNotifySetAllocationSizeEventArgs) Status() int32
func (args *CBFilterNotifySetAllocationSizeEventArgs) ResultCode() int32
func (args *CBFilterNotifySetAllocationSizeEventArgs) SetResultCode(value int32)

// CBFilterNotifySetAllocationSizeEvent defines the signature of the CBFilter NotifySetAllocationSize event's handler function.
type CBFilterNotifySetAllocationSizeEvent func(sender *CBFilter, args *CBFilterNotifySetAllocationSizeEventArgs)

func (obj *CBFilter) GetOnNotifySetAllocationSizeHandler() CBFilterNotifySetAllocationSizeEvent
func (obj *CBFilter) SetOnNotifySetAllocationSizeHandler(handlerFunc CBFilterNotifySetAllocationSizeEvent)

Remarks

This event fires when the allocation size of the file specified by FileName has been changed.

Applications only need to handle this event if they've added a standard filter rule that includes the FS_NE_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.

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, set it to a non-zero value to report an appropriate error. Note, however, that this event fires after the operation has already completed, so reporting an error won't actually affect the operation itself. Please refer to the Error Reporting and Handling topic for more information.

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