zpool tips — authorized ZFS pool literacy

Snapshot

Tip checklist (authorized only)

1. Confirm you may run zpool on the lab host (syllabus box you own; pool create needs root/CAP on lab devices).
2. Prefer documenting who / why / ticket before any pool create/destroy — never wipe production disks without change control.
3. Record short factual notes; quote short Evidence (pool name + health + vdev label — never secrets).
4. Optional: dataset list peer → zfs-list-tips.
5. Optional: block-tree peer → lsblk-tips.
6. Prefer disposable lab VMs and throwaway loop/file vdevs for pool drills; quote non-secret labels afterward as Evidence.
7. Prefer zpool list / zpool status read-back before and after authorized create — refuse unauthorized foreign-disk cookbooks.
8. Stop at literacy — no attack or unauthorized disk-bypass cookbooks.

Allowed framing

• Classroom labs reviewing zpool list / zpool status then selected lab zpool create on authorized disposable hosts.
• Binding short factual notes as Evidence (pool name + health + vdev — no secrets).
• Documenting expected vs observed pool rows for authorized notes.
• Comparing zpool ↔ zfs-list / lsblk / mdadm / blkid / btrfs-subvolume peer tip pages under one binder.
• Testing syllabus-approved lab pool create only when change control authorizes that drill on lab resources.

Scope we will not cover

• No crack/pirate/keygen via zpool.
• No intentional unauthorized pool create against foreign disks.
• No secret-theft or credential harvesting against hosts you do not own.
• No cookbooks that use zpool as an attack step against production without authorization.
• No zpool framed as a disk-bypass against systems you do not own.

Beginner path (authorized only)

1. Obtain one syllabus-approved disposable lab host with OpenZFS available.
2. Prefer throwaway file/loop vdevs before any pool-create drill.
3. With authorization, run zpool list / zpool status; optional authorized zpool create labpool <lab-vdev>; quote selected pool/health labels as Evidence.
4. Optional: peer tip pages above when the syllabus asks.
5. Stop at literacy — no attack or unauthorized disk-bypass cookbooks.

Practical notes for authorized labs

• zpool manages pools/vdevs — keep Evidence labels distinct from zfs-list-tips dataset listings.
• Pair with mdadm-tips when the syllabus contrasts software RAID vs ZFS pool layouts.
• zpool status is a great read-only drill — document selected health/vdev labels without dumping unrelated privileged state.
• Prefer documenting pool names, health, and vdev labels the syllabus authorized.
• Never commit pool dumps with secrets or proprietary disk serials to git — even for labs.

FAQ-aligned refusals (quick)

• Foreign-disk pool create → refuse.
• Unauthorized disk-bypass / hostile-wipe attack cookbooks → refuse.
• Attack/credential-theft framing → refuse.

For legal, authorized and educational use only.

FAQ

Sources