You need to migrate a UFS file system named /production_ufs to a ZFS file system named /production_ufs. The /production_ufs file system cannot be taken down or be out of production during the…

Question

Options

• ACreate a snapshot of the UFS file system.
• BCreate a new Boot Environment.
• CMirror the existing UFS file system by using SVM.
• DCreate the new ZFS file system by using zfs create import to import data from the existing UFS file
• ECreate the new zfs file system by using the zfs create -o shadow.

• A
  3% (1)
• B
  8% (3)
• C
  5% (2)
• E
  85% (33)

Explanation

ZFS Shadow Migration (zfs create -o shadow=<source>) is specifically designed for exactly this scenario: it creates a new ZFS filesystem that transparently pulls data from a live source (including UFS) in the background, allowing both filesystems to remain accessible simultaneously until migration completes - perfectly satisfying both requirements.

Why the distractors fail:

• A (UFS snapshot): fssnap creates a frozen, point-in-time read-only image - it captures a moment, not a live continuous copy, so changes after the snapshot are missed.
• B (Boot Environment): beadm manages OS root environments for patching/upgrades; it has no role in migrating arbitrary data filesystems like /production_ufs.
• C (SVM mirror): SVM mirroring duplicates at the block level - the result is still a UFS filesystem, not a ZFS one. It mirrors, it doesn't convert.
• D (zfs create import): This command syntax does not exist in ZFS. zfs import is for importing ZFS pools from other hosts, not ingesting UFS data.

Memory tip: Think of the -o shadow option as casting a shadow - just like your shadow silently mimics your movements without interrupting you, ZFS shadow migration silently mirrors the source filesystem in the background while production keeps running. If you see "live UFS → ZFS with zero downtime," the answer is always shadow migration.

No community discussion yet for this question.