1Z0-820 · Question #60
View the Exhibit and review the zpool and ZFS configuration information from your system. Identify the correct procedure for breaking the /prod_data mirror, removing c4t0d0 and c4t2d0, and making…
The correct answer is A. zpool split pool1 pool2 c4t0d0 c4t2d0. zpool split pool1 pool2 c4t0d0 c4t2d0 is correct because zpool split is the only command designed to detach one side of a mirror and reconstitute it as an independent pool - specifying the source pool (pool1), the new pool name (pool2), and the exact vdevs to pull creates pool2…
Question
View the Exhibit and review the zpool and ZFS configuration information from your system. Identify the correct procedure for breaking the /prod_data mirror, removing c4t0d0 and c4t2d0, and making the data on c4t0d0and c4t2d0 accessible under the dev_data mount point.
Exhibit
Options
- Azpool split pool1 pool2 c4t0d0 c4t2d0
- Bzpool detach pool1 pool2
- Czpool split pool1/prod_data -n pool2/dev_data
- Dzpool split pool1 pool2 c4t0d0 c4t2d0
How the community answered
(37 responses)- A81% (30)
- B3% (1)
- C11% (4)
- D5% (2)
Explanation
zpool split pool1 pool2 c4t0d0 c4t2d0 is correct because zpool split is the only command designed to detach one side of a mirror and reconstitute it as an independent pool - specifying the source pool (pool1), the new pool name (pool2), and the exact vdevs to pull creates pool2 with those devices intact, which can then be imported and mounted at /dev_data.
Option B (zpool detach pool1 pool2) is wrong on two counts: zpool detach removes a single device from a mirror (it doesn't create a new pool), and its second argument must be a device, not a pool name.
Option C is wrong because zpool split operates on pools, not ZFS datasets or mount paths - you cannot pass pool1/prod_data or pool2/dev_data as arguments, and -n is the dry-run flag, not a rename or mount option.
Option D appears identical to A as written (likely a transcription artifact in the exhibit); in the original exam, D probably omits the vdev arguments, which would cause the split to arbitrarily assign devices rather than guaranteeing c4t0d0 and c4t2d0 land in the new pool.
Memory tip: Think of zpool split like splitting a cell - zpool split <parent> <child> [devices to take]. The parent keeps the devices you don't list; the child takes the ones you do.
Topics
Community Discussion
No community discussion yet for this question.
