2V0-621 · Question #140
An administrator uses the df -h command and notices that an NFS datastore is reporting a capacity of 0 Bytes. What condition would cause this to occur?
The correct answer is A. The NFS server on which the datastore resides is down. When the NFS server backing a datastore is unreachable, ESXi cannot query storage capacity metrics, causing df -h to report 0 bytes for that mount.
Question
An administrator uses the df -h command and notices that an NFS datastore is reporting a capacity of 0 Bytes. What condition would cause this to occur?
Options
- AThe NFS server on which the datastore resides is down.
- BThe datastore was mounted as Read/Write.
- CThe datastore was mounted as Read-Only.
- DThe datastore was created with NFS version 4.1.
How the community answered
(55 responses)- A76% (42)
- B4% (2)
- C5% (3)
- D15% (8)
Why each option
When the NFS server backing a datastore is unreachable, ESXi cannot query storage capacity metrics, causing df -h to report 0 bytes for that mount.
When the NFS server is down or otherwise unreachable, ESXi loses the ability to communicate with the export and retrieve filesystem statistics. Because capacity data cannot be obtained from the server, the datastore reports 0 bytes - signaling that the underlying storage is inaccessible rather than genuinely empty.
Mounting a datastore as Read/Write is the standard access mode and does not affect how capacity is queried or reported by the NFS client.
A Read-Only NFS mount still allows ESXi to query and display the datastore capacity; access mode restrictions affect write operations, not stat queries.
NFS version 4.1 is a supported protocol version in vSphere and does not cause a 0-byte capacity report under normal operating conditions.
Concept tested: NFS datastore capacity reporting when server is unavailable
Source: https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-storage/GUID-CBDEB8CE-B0A2-4B5B-B8D7-6C03E2D52F49.html
Topics
Community Discussion
No community discussion yet for this question.