From 405ec516abbae42f205328ffc1bd7b38cbdd45da Mon Sep 17 00:00:00 2001 From: bunder2015 Date: Mon, 29 Jan 2018 18:10:32 -0500 Subject: [PATCH] Fix zpool-features(5) large_block inconsistency Large_blocks feature activation was not consistent with man page, which erroneously stated that the feature was active when the recordsize was increased past the stock 128KB. It actually becomes active when data is written to the dataset. Reviewed-by: Giuseppe Di Natale Reviewed by: George Melikov Reviewed-by: Brian Behlendorf Signed-off-by: bunder2015 Closes #6275 Closes #7093 --- man/man5/zpool-features.5 | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/man/man5/zpool-features.5 b/man/man5/zpool-features.5 index a23f3aed4..72a6c57b1 100644 --- a/man/man5/zpool-features.5 +++ b/man/man5/zpool-features.5 @@ -455,8 +455,8 @@ DEPENDENCIES extensible_dataset The \fBlarge_block\fR feature allows the record size on a dataset to be set larger than 128KB. -This feature becomes \fBactive\fR once a \fBrecordsize\fR property has been -set larger than 128KB, and will return to being \fBenabled\fR once all +This feature becomes \fBactive\fR once a dataset contains a file with +a block size larger than 128KB, and will return to being \fBenabled\fR once all filesystems that have ever had their recordsize larger than 128KB are destroyed. .RE