You created a new zpool. Now you need to migrate the existing ZFS file system from pool1/prod to pool2/prod. You have these requirements: 1. Users must have access to the data during the migration…

Question

Options

• ASvccfg - s filesystem/shadowd:default
• BSpecify the -b <blocksize> option with the zfs create command and increase the value of <blocksize>
• CUse the -o -volblocksize=<blocksize>option with the zfs create command and increase the value of
• DSvccfg -s filesystem/zfs: default

• A
  80% (44)
• B
  11% (6)
• C
  4% (2)
• D
  5% (3)

Explanation

Option A is correct because ZFS shadow migration in Oracle Solaris is managed by the shadowd SMF service (svc:/filesystem/shadowd:default). Using svccfg -s filesystem/shadowd:default, you can modify service properties such as config/max_jobs to increase concurrency, allowing the daemon to process more migration work in parallel without taking the file system offline.

Why the distractors are wrong:

• B - The -b <blocksize> option sets the record size of a newly created ZFS dataset; it has no effect on migration daemon concurrency or shadow migration behavior.
• C - -o volblocksize applies only to ZFS volumes (zvols), not regular file systems, and again has nothing to do with the shadow migration daemon's performance settings.
• D - filesystem/zfs:default is the SMF service for the general ZFS stack, not the shadow migration daemon. Using the wrong service FMRI won't expose the shadowd concurrency properties you need to tune.

Memory tip: The key word in the question is shadow migration daemon - the service name literally contains "shadow" (filesystem/shadow**d**). When you see "shadow migration + tuning," think svccfg on the shadowd service, not the generic zfs service.

No community discussion yet for this question.