nerdexam
IBM

000-221 · Question #32

Given the following information, why is an error returned when trying to unmount the fitesystem /var/logs/tsm?

The correct answer is A. The child filesystem /var/logs/tsm/livelog is still mounted. In AIX, a filesystem cannot be unmounted if another filesystem is currently mounted on a subdirectory within it. The child mount point /var/logs/tsm/livelog keeps the parent busy.

Troubleshooting and Problem Determination

Question

Given the following information, why is an error returned when trying to unmount the fitesystem /var/logs/tsm?

Exhibit

000-221 question #32 exhibit

Options

  • AThe child filesystem /var/logs/tsm/livelog is still mounted.
  • BThe hd8 is still tied to the filesystem.
  • CThe filesystem is of type mount=true so cannot be unmounted while the system is running
  • DThe umount command is being run while inside the filesystem.

How the community answered

(49 responses)
  • A
    73% (36)
  • B
    4% (2)
  • C
    6% (3)
  • D
    16% (8)

Why each option

In AIX, a filesystem cannot be unmounted if another filesystem is currently mounted on a subdirectory within it. The child mount point /var/logs/tsm/livelog keeps the parent busy.

AThe child filesystem /var/logs/tsm/livelog is still mounted.Correct

AIX enforces a mount hierarchy rule where a parent filesystem cannot be unmounted while any child filesystem remains mounted beneath it. Because /var/logs/tsm/livelog is still mounted as a separate filesystem inside /var/logs/tsm, the kernel considers the parent device busy, causing umount to return an error. The child must be unmounted first before the parent can be released.

BThe hd8 is still tied to the filesystem.

hd8 is the AIX paging space logical volume, not related to /var/logs/tsm; it has no role in preventing this filesystem from unmounting.

CThe filesystem is of type mount=true so cannot be unmounted while the system is running

AIX does not have a mount=true attribute that permanently prevents unmounting at runtime; that is not a valid AIX filesystem attribute.

DThe umount command is being run while inside the filesystem.

Being inside a filesystem with your current working directory would cause a 'device busy' error on that specific filesystem, but the question identifies the child mount as the cause, and the CWD issue would apply to the filesystem the shell is inside, not necessarily its parent.

Concept tested: AIX filesystem unmount blocked by child mount

Source: https://www.ibm.com/docs/en/aix/7.3?topic=u-umount-command

Topics

#filesystem unmount#nested filesystems#mount points#umount error

Community Discussion

No community discussion yet for this question.

Full 000-221 Practice