nerdexam
Broadcom-VMware

2V0-622 · 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 df -h reports 0 bytes for an NFS datastore, it indicates ESXi cannot communicate with the NFS server and therefore cannot retrieve capacity metadata.

Section 3 – Configure and Administer vSphere 6.5 Storage

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

(37 responses)
  • A
    81% (30)
  • B
    5% (2)
  • C
    3% (1)
  • D
    11% (4)

Why each option

When df -h reports 0 bytes for an NFS datastore, it indicates ESXi cannot communicate with the NFS server and therefore cannot retrieve capacity metadata.

AThe NFS server on which the datastore resides is down.Correct

When the NFS server is unreachable or down, ESXi loses the ability to query the server for filesystem statistics such as total capacity and free space. Without a valid response from the server, the datastore capacity is reported as 0 bytes because no data can be returned.

BThe datastore was mounted as Read/Write.

Mounting an NFS datastore as Read/Write is the standard configuration and has no impact on capacity reporting - ESXi can query filesystem size regardless of write permissions.

CThe datastore was mounted as Read-Only.

A Read-Only NFS mount restricts write access but does not prevent ESXi from querying the server for capacity statistics, so size would still be reported correctly.

DThe datastore was created with NFS version 4.1.

NFS version 4.1 is a fully supported protocol in vSphere and does not inherently cause capacity to report as 0 - connectivity loss, not protocol version, is the cause of this symptom.

Concept tested: NFS datastore capacity reporting and server availability

Source: https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-storage/GUID-5432F52B-1D27-46E3-BD86-3D9B3602E5D0.html

Topics

#NFS datastore#df -h#zero capacity#NFS server availability

Community Discussion

No community discussion yet for this question.

Full 2V0-622 Practice