000-221 · Question #174
Which option explains why a user-created local filesystem does not automatically mount when the system boots?
The correct answer is C. The mount filesystem attribute is missing in /etc/filesystems. In AIX, the 'mount' attribute in the /etc/filesystems stanza controls whether a filesystem is automatically mounted at boot time.
Question
Which option explains why a user-created local filesystem does not automatically mount when the system boots?
Options
- ANo port is specified for mountd in/etc/services.
- BThe filesystem does not belong to a mount group.
- CThe mount filesystem attribute is missing in /etc/filesystems.
- DThe portmap daemon is not configured to start in /etc/inetd.conf.
How the community answered
(20 responses)- A5% (1)
- B15% (3)
- C75% (15)
- D5% (1)
Why each option
In AIX, the 'mount' attribute in the /etc/filesystems stanza controls whether a filesystem is automatically mounted at boot time.
The mountd port in /etc/services is relevant to NFS remote mounts over the network and has no bearing on local JFS or JFS2 filesystem auto-mount behavior.
Mount groups in AIX control the order in which filesystem stanzas are processed and are not a prerequisite for a filesystem to mount automatically at boot.
The /etc/filesystems file in AIX contains a stanza for each filesystem, and the 'mount' attribute within that stanza must be set to 'true' or 'automatic' for the filesystem to be mounted during system initialization. When a user creates a local filesystem manually, this attribute may not be added to the stanza automatically, preventing auto-mount at boot.
The portmap daemon is part of the RPC infrastructure used by NFS and other network services and is completely unrelated to mounting local filesystems during system startup.
Concept tested: AIX /etc/filesystems mount attribute for boot-time auto-mount
Source: https://www.ibm.com/docs/en/aix/7.3?topic=files-etcfilesystems-file
Topics
Community Discussion
No community discussion yet for this question.