What condition would cause this to occur?

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?

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?

A.
The NFS server on which the datastore resides is down.

B.
The datastore was mounted as Read/Write.

C.
The datastore was mounted as Read-Only.

D.
The datastore was created with NFS version 4.1.

Explanation:
Explanation/Reference:



Leave a Reply 4

Your email address will not be published. Required fields are marked *


Echo

Echo

I was thinking C?

VIguy

VIguy

Ready-Only would still allow the host to see information that is presented by the device. A datastore that is showing up as 0 bytes is unable to report back to the host, most likely because it is down.

Dude

Dude

As a vmware certified professional we can tell someone that something is down. What a freakin joke.

andy75

andy75

It’s not that obvious… In my lab, NFS datastore (DS) was down when ESX booted up and the “df” command didn’t list it at all (despite it was a known DS to vCS and other ESX hosts).
After the NFS server was brought up and, after a few minutes (to let ESX recognize it) down again, ESX entered APD mode while the output from “df” got frozen. Upon APD expiration (140 sec by default), “df” showed the NFS DS as 0 (zero) capacity indeed.