Examine this output captured on an NFS server:
# mount | grep export
/dev/sdc1 on /export type ext3 (rw)
/dev/sdc2 on /export/share2 type ext3 (rw)
# cat /etc/exports
/export (*ro)
You mounted the /export filesystem on an NFS client using the command:
# mount NFS_SERVER:/export/mnt
What is the result of listing the files in /mnt/share2 on the NFS client?
A.
It lists any files stored in the share2 directory in the /dev/sdc1 partition of the NFS server.
B.
It lists any files stored in the root directory in the /dev/sdc2 partition of the NFS server.
C.
It results in a permission denied error.
D.
It results in a stale NFS handle error.
E.
It produces no output.
Explanation:
Answer: E
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/5/html/Deployment_Guide/sect-Using_the_mount_Command-Mounting-Bind.html
A
ls /mnt/share2
It’s “E”. “nohide” and “crossmnt” appear to be the defaults, but note this text from the man exports man page:
The nohide option is currently only effective on single host
exports. It does not work reliably with netgroup, subnet, or
wildcard exports.
I think it’s the D option,
as:
on the NFS_Server server is mounted:
# mount | grep export
/ dev / sdc1 on / export type ext3 (rw)
/ dev / sdc2 on / export / share2 type ext3 (rw)
cat / etc / exports
/ export (* ro)
And in the NFS client, you try to mount:
mount NFS_SERVER: / export / mnt
The / export / mnt path does not exist in the NFS_SERVER, so it gives an error