dfs_volinfo_t

Contains information about a NetWare volume

Service:Direct File System

Defined In:dfs.h

Structure

  typedef struct{
     size_t   VolumeAllocationUnitSizeInBytes;
     size_t   VolumeSizeInAllocationUnits;
     size_t   VolumeSectorSize;
     int      AllocationUnitsUsed;
     int      AllocationUnitsFreelyAvailable;
     int      AllocationUnitsInDeletedFilesNotAvailable;
     int      AllocationUnitsInAvailableDeletedFiles;
     int      NumberOfPhysicalSegmentsInVolume;
     size_t   PhysicalSegmentSizeInAllocationUnits[64];
  } dfs_volinfo_t;

Fields

VolumeAllocationUnitSizeInBytes: Specifies the number of bytes contained in a block allocated by the OS (this can be 4K, 8K, 16K, 32K, or 64K).
VolumeSizeInAllocationUnits: Specifies the number of blocks of the size indicated in the parameter above that are contained in a volume (the volume total size can be calculated with these two parameters).
VolumeSectorSize: Specifies the size of each sector on a volume (currently only a sector size of 512 bytes is supported by the OS).
AllocationUnitsUsed: Specifies the number of blocks on a volume used with current non-deleted files.
AllocationUnitsFreelyAvailable: Specifies the number of blocks currently available for file allocation.
AllocationUnitsInDeletedFilesNotAvailable: Specifies the number of blocks on a volume which compose files that have been deleted but for which the necessary time has not yet elapsed before they can be purged or moved to the AllocationUnitsFreelyAvailable category.
AllocationUnitsInAvailableDeletedFiles: Specifies the number of blocks which compose files deleted for which the required time has expired prior to being purged, but which have not yet been purged or moved to the AllocationUnitsFreelyAvailable category.
NumberOfPhysicalSegmentsInVolume: Specifies the number of physical volume segments that are linked to form a volume.
PhysicalSegmentSizeInAllocationUnits: Specifies an array that specifies the number of blocks in each volume segment, of which a maximum of 64 are allowed per volume. This also allows an application process to determine at what point in the logical volume block number a transition takes place from one volume segment to another. This information is needed by applications doing specific file allocation.