Page MenuHomeFreeBSD

Handbook - ZFS rework
Needs RevisionPublic

Authored by carlavilla on Sat, Jul 11, 5:49 PM.
Tags
None
Referenced Files
F162763387: D58175.id181823.diff
Thu, Jul 16, 2:50 PM
F162714924: D58175.diff
Thu, Jul 16, 2:20 AM
F162700901: D58175.id.diff
Wed, Jul 15, 10:37 PM
F162696671: D58175.diff
Wed, Jul 15, 9:26 PM
Unknown Object (File)
Wed, Jul 15, 6:16 PM
Unknown Object (File)
Wed, Jul 15, 6:12 PM
Unknown Object (File)
Tue, Jul 14, 4:39 PM
Unknown Object (File)
Tue, Jul 14, 3:28 PM
Subscribers

Details

Summary
  • Add RAID-Z expansion, dRAID, special vdevs, hot spares with zfsd, TRIM, pool checkpoints, block cloning, fast dedup, bookmarks, holds, resumable/corrective send, project quotas, direct I/O, and boot environments
  • Add Jails and ZFS crossref target, encryption key loading at boot (zfskeys), and a Pool Properties section
  • Rewrite Tuning to drop removed sysctls (scrub_delay, vdev.cache.size, arc.meta_limit, …); delete the obsolete ZFS-on-i386 section
  • Switch examples to ada device names and GPT partitions
  • Fix the inverted reservation terminology entry, zfs scrub → zpool scrub, stale checksum/compression algorithm lists, and EOL version framing

Diff Detail

Repository
R9 FreeBSD doc repository
Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

Amazing to read through this rewrite. It is a much needed and substantial rewrite/update of most of the chapter. I only found this small nit.
Make sure to reference Bug 287148, Bug 261212, and maybe even Bug 263321. Thank you very much!

documentation/content/en/books/handbook/zfs/_index.adoc
970

Can you use ada0 ... for the device names in this example as well for consistency?

carlavilla marked an inline comment as done.
carlavilla added inline comments.
documentation/content/en/books/handbook/zfs/_index.adoc
970

Done, thanks!

Excellent, then let's have this in the handbook. Approved!

This revision is now accepted and ready to land.Sun, Jul 12, 9:34 AM

One nit.

documentation/content/en/books/handbook/zfs/_index.adoc
106

What about NVMe? The names are different too.

This revision now requires changes to proceed.Sun, Jul 12, 10:42 AM

One nit.

NVMe is a good point for a future improvement, but I don't think it's a blocker for this change.

documentation/content/en/books/handbook/zfs/_index.adoc
106

What about NVMe? The names are different too.

NVMe is a good point for a future improvement, but I don't think it's a blocker for this change.