Improve Path and Name Lengths section of Guide
With the actual limit of 47 bytes for the total name of the dataset, including path separators(*) it becomes essential to be able to rename dataset without loosing all it's snapshots and sub-datasets. This is doable and is supported by
zfs itself, see
zfs rename, so the only thing is needed is support for this operation in the middlewared and GUI.
- When we accessing snapshot data it is automounted by ZFS inside the dataset. The total maximum length of the mount point is 87(?) bytes, plust terminating '\0'. Out of that 87 bytes 19 are used by mandatory
.zfs/snapshot/, 21 bytes are spared on snapshot name, like
auto-20170716.1800-1y, leaving us with miserable 47 bytes for the datasets name hierarchy, including path separators. No wonder that frequently users can't access snapshots deep in the hierarchy.
This limitation should be lifted in the FreeBSD 12.0 up to 1024 bytes, but meanwhile...
Doc team should document this limitation more thoroughly, as current http://doc.freenas.org/11/intro.html#path-and-name-lengths doesn't explain all consequences of the bad dataset name selection.
#11 Updated by Timothy Moore II over 1 year ago
- Status changed from Unscreened to Done
- Needs QA changed from Yes to No
- Needs Doc changed from Yes to No
- Needs Merging changed from Yes to No
Ported previously missing notes about ZFS byte limitations into the angulargui branch of the guide: https://github.com/freenas/freenas-docs/pull/386. If further changes are needed, please leave a comment here or open a new issue.