Optional
availableAvailable size in bytes
Optional
errorIf there are non-critical errors while extracting metadata, those errors may be added to this field.
Optional
fstypeThe type of file system on the volume, like ext4
, apfs
, or ntfs
.
Note: on Windows this may show as "ntfs" for remote filesystems, as that is how the filesystem is presented to the OS.
Optional
isIndicates if this volume is primarily for system use (e.g., swap, snap loopbacks, EFI boot, or only system directories).
Note: This is a best-effort classification and is not 100% accurate.
Optional
labelThe name of the partition
Optional
mountPath to the device or service that the mountpoint is from.
Examples include /dev/sda1
, nfs-server:/export
,
//username@remoteHost/remoteShare
, or //cifs-server/share
.
May be undefined for remote volumes.
Optional
mountThe name of the mount. This may match the resolved mountPoint.
Mount location (like "/" or "C:").
Optional
protocolProtocol used to access the share.
Does the protocol seem to be a remote filesystem?
Optional
remoteIf remote, the ip or hostname hosting the share (like "rusty" or "10.1.1.3")
Optional
remoteIf remote, the name of the share (like "homes")
Optional
remoteIf remote, may include the username used to access the share.
This will be undefined on NFS and other remote filesystem types that do authentication out of band.
Optional
sizeTotal size in bytes
Optional
statusOn Windows, returns the health status of the volume.
Note that this is only available on Windows, as both Linux and macOS are
prohibitively expensive, requiring forking fsck -N
or diskutil verifyVolume
.
If there are non-critical errors while extracting metadata, those error messages may be added to this field (say, from blkid or gio).
VolumeHealthStatuses for values returned by Windows.
Optional
uriWe can sometimes fetch a URI of the resource (like "smb://server/share" or "file:///media/user/usb")
Optional
usedUsed size in bytes
Optional
uuidUUID for the volume, like "c9b08f6e-b392-11ef-bf19-4b13bb7db4b4".
On windows, this may be the 128-bit volume UUID, but if that is not available, like in the case of remote volumes, we fallback to the 32-bit volume serial number, rendered in lowercase hexadecimal.
Metadata associated to a volume.
See
https://en.wikipedia.org/wiki/Volume_(computing)