From 7def94164ae6c18d84e40f00db2e2b74a7662b35 Mon Sep 17 00:00:00 2001 From: Marian Csontos Date: Tue, 5 May 2020 10:20:18 +0200 Subject: [PATCH] build: make generate (cherry picked from commit bcc149048440dce5fc7962f88ed523469dd39a32) --- man/lvconvert.8_pregen | 63 ++++++++++++++++++++++++++++++++++++++++++++++++++ man/lvcreate.8_pregen | 53 ++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 116 insertions(+) diff --git a/man/lvconvert.8_pregen b/man/lvconvert.8_pregen index b676e72..7440984 100644 --- a/man/lvconvert.8_pregen +++ b/man/lvconvert.8_pregen @@ -163,6 +163,18 @@ lvconvert - Change logical volume layout .ad b .br .ad l + \fB--raidintegrity\fP \fBy\fP|\fBn\fP +.ad b +.br +.ad l + \fB--raidintegrityblocksize\fP \fINumber\fP +.ad b +.br +.ad l + \fB--raidintegritymode\fP \fIString\fP +.ad b +.br +.ad l \fB-r\fP|\fB--readahead\fP \fBauto\fP|\fBnone\fP|\fINumber\fP .ad b .br @@ -982,6 +994,28 @@ Poll LV to continue conversion. .br - +Add or remove data integrity checksums to raid images. +.br +.P +\fBlvconvert\fP \fB--raidintegrity\fP \fBy\fP|\fBn\fP \fILV\fP\fI_raid\fP +.br +.RS 4 +.ad l +[ \fB--raidintegritymode\fP \fIString\fP ] +.ad b +.br +.ad l +[ \fB--raidintegrityblocksize\fP \fINumber\fP ] +.ad b +.br +[ COMMON_OPTIONS ] +.RE +.br +.RS 4 +[ \fIPV\fP ... ] +.RE +- + Common options for command: . .RS 4 @@ -1405,6 +1439,35 @@ Repeat once to also suppress any prompts with answer 'no'. .ad b .HP .ad l +\fB--raidintegrity\fP \fBy\fP|\fBn\fP +.br +Enable or disable data integrity checksums for raid images. +.ad b +.HP +.ad l +\fB--raidintegrityblocksize\fP \fINumber\fP +.br +The block size to use for dm-integrity on raid images. +The integrity block size should usually match the device +logical block size, or the file system block size. +It may be less than the file system block size, but not +less than the device logical block size. +Possible values: 512, 1024, 2048, 4096. +.ad b +.HP +.ad l +\fB--raidintegritymode\fP \fIString\fP +.br +Use a journal (default) or bitmap for keeping integrity checksums consistent +in case of a crash. The bitmap areas are recalculated after a crash, so corruption +in those areas would not be detected. A journal does not have this problem. +The journal mode doubles writes to storage, but can improve performance for +scattered writes packed into a single journal write. +bitmap mode can in theory achieve full write throughput of the device, +but would not benefit from the potential scattered write optimization. +.ad b +.HP +.ad l \fB-r\fP|\fB--readahead\fP \fBauto\fP|\fBnone\fP|\fINumber\fP .br Sets read ahead sector count of an LV. diff --git a/man/lvcreate.8_pregen b/man/lvcreate.8_pregen index a80f9f5..be8e783 100644 --- a/man/lvcreate.8_pregen +++ b/man/lvcreate.8_pregen @@ -187,6 +187,18 @@ lvcreate - Create a logical volume .ad b .br .ad l + \fB--raidintegrity\fP \fBy\fP|\fBn\fP +.ad b +.br +.ad l + \fB--raidintegrityblocksize\fP \fINumber\fP +.ad b +.br +.ad l + \fB--raidintegritymode\fP \fIString\fP +.ad b +.br +.ad l \fB-r\fP|\fB--readahead\fP \fBauto\fP|\fBnone\fP|\fINumber\fP .ad b .br @@ -425,6 +437,18 @@ Create a raid LV (a specific raid level must be used, e.g. raid1). [ \fB--[raid]maxrecoveryrate\fP \fISize\fP[k|UNIT] ] .ad b .br +.ad l +[ \fB--raidintegrity\fP \fBy\fP|\fBn\fP ] +.ad b +.br +.ad l +[ \fB--raidintegritymode\fP \fIString\fP ] +.ad b +.br +.ad l +[ \fB--raidintegrityblocksize\fP \fINumber\fP ] +.ad b +.br [ COMMON_OPTIONS ] .RE .br @@ -1420,6 +1444,35 @@ Repeat once to also suppress any prompts with answer 'no'. .ad b .HP .ad l +\fB--raidintegrity\fP \fBy\fP|\fBn\fP +.br +Enable or disable data integrity checksums for raid images. +.ad b +.HP +.ad l +\fB--raidintegrityblocksize\fP \fINumber\fP +.br +The block size to use for dm-integrity on raid images. +The integrity block size should usually match the device +logical block size, or the file system block size. +It may be less than the file system block size, but not +less than the device logical block size. +Possible values: 512, 1024, 2048, 4096. +.ad b +.HP +.ad l +\fB--raidintegritymode\fP \fIString\fP +.br +Use a journal (default) or bitmap for keeping integrity checksums consistent +in case of a crash. The bitmap areas are recalculated after a crash, so corruption +in those areas would not be detected. A journal does not have this problem. +The journal mode doubles writes to storage, but can improve performance for +scattered writes packed into a single journal write. +bitmap mode can in theory achieve full write throughput of the device, +but would not benefit from the potential scattered write optimization. +.ad b +.HP +.ad l \fB-r\fP|\fB--readahead\fP \fBauto\fP|\fBnone\fP|\fINumber\fP .br Sets read ahead sector count of an LV. -- 1.8.3.1