nerdexam
IBM

000-221 · Question #51

The /test1 filesystem was built larger than required. An effort to shrink the filesystem was made, but the resulting filesystem size is larger than the size specified. Given the following output…

The correct answer is B. The physical partition size. In AIX LVM, storage is allocated in fixed-size physical partitions, so a filesystem cannot be reduced below the nearest physical partition boundary, causing the result to be larger than the specified target size.

Storage Management

Question

The /test1 filesystem was built larger than required. An effort to shrink the filesystem was made, but the resulting filesystem size is larger than the size specified. Given the following output, what is the most likely reason?

Exhibit

000-221 question #51 exhibit

Options

  • AFragmentation of the filesystem
  • BThe physical partition size
  • CAmount of data in the filesystem
  • DVolume group status
  • EOptions chosen with the df command

How the community answered

(52 responses)
  • B
    83% (43)
  • C
    10% (5)
  • D
    2% (1)
  • E
    6% (3)

Why each option

In AIX LVM, storage is allocated in fixed-size physical partitions, so a filesystem cannot be reduced below the nearest physical partition boundary, causing the result to be larger than the specified target size.

AFragmentation of the filesystem

Filesystem fragmentation affects performance and free space layout but does not impose a minimum size granularity constraint when shrinking.

BThe physical partition sizeCorrect

AIX LVM allocates storage in fixed-size physical partitions (PPs), and the size of a logical volume must be a multiple of the physical partition size. When shrinking a filesystem, the reduction is rounded up to the nearest PP boundary, so the resulting size may exceed the specified value if the target falls between two PP multiples.

CAmount of data in the filesystem

Insufficient free space would prevent shrinking entirely, but the question states the operation succeeded - just not to the exact target size.

DVolume group status

Volume group status such as active or concurrent mode does not control the granularity of filesystem size reductions.

EOptions chosen with the df command

The df command is used to display filesystem usage and does not influence the outcome or granularity of a resize operation.

Concept tested: AIX LVM physical partition size constraints on resize

Source: https://www.ibm.com/docs/en/aix/7.3?topic=management-logical-volume-manager

Topics

#filesystem resize#physical partition size#LVM#shrink filesystem

Community Discussion

No community discussion yet for this question.

Full 000-221 Practice