| UID | tech.root | title | ms.date | targetos | description | prerelease | req.construct-type | req.ddi-compliance | req.dll | req.header | req.include-header | req.kmdf-ver | req.lib | req.max-support | req.redist | req.target-min-winverclnt | req.target-min-winversvr | req.target-type | req.typenames | req.umdf-ver | req.unicode-ansi | topic_type | api_type | api_location | api_name | f1_keywords | dev_langs | helpviewer_keywords | ms.custom | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
NS:ntifs._FILE_ALLOCATED_RANGE_BUFFER |
ifsk |
FILE_ALLOCATED_RANGE_BUFFER |
10/07/2022 |
Windows |
Learn more about the FILE_ALLOCATED_RANGE_BUFFER structure. |
false |
structure |
ntifs.h |
Windows 2000 |
FILE_ALLOCATED_RANGE_BUFFER, *PFILE_ALLOCATED_RANGE_BUFFER |
|
|
|
|
|
|
|
engagement-fy23 |
FILE_ALLOCATED_RANGE_BUFFER structures are used as input and output during a FSCTL_QUERY_ALLOCATED_RANGES control code request.
On FSCTL input, contains the file offset in bytes of the start of a range of bytes in a file. FileOffset must be greater than or equal to 0.
On FSCTL output, contains the file offset in bytes from the start of the file; the start of a range of bytes to which storage is allocated. If the file is a sparse file, FileOffset can contain ranges of bytes for which storage is not allocated; these ranges will be excluded from the list of allocated ranges returned by FSCTL_QUERY_ALLOCATED_RANGES. Because an application using a sparse file can choose whether or not to allocate disk space for each sequence of 0x00-valued bytes, the allocated ranges can contain 0x00-valued bytes. This value must be greater than or equal to 0 on output.
Contains the size in bytes of the range. On FSCTL input, Length must be greater than or equal to 0. On FSCTL output, Length must be greater than 0.