diff options
| author | Mike Snitzer <snitzer@redhat.com> | 2009-07-06 19:04:24 +0000 |
|---|---|---|
| committer | Mike Snitzer <snitzer@redhat.com> | 2009-07-06 19:04:24 +0000 |
| commit | bb6a3a960851adf00bc55e5760cf26af9a0c50be (patch) | |
| tree | edbb94cc78c29702e834048bbb142acbbff67973 /man/lvm.conf.5.in | |
| parent | 4b2cae463ed262bd2df6b104685becb2dc69707c (diff) | |
| download | lvm2-bb6a3a960851adf00bc55e5760cf26af9a0c50be.tar.gz lvm2-bb6a3a960851adf00bc55e5760cf26af9a0c50be.tar.xz lvm2-bb6a3a960851adf00bc55e5760cf26af9a0c50be.zip | |
Use the MD device's stripe-width, instead of chunk_size, to align the
data blocks of a Physical Volume that is placed directly upon an MD
device.
Diffstat (limited to 'man/lvm.conf.5.in')
| -rw-r--r-- | man/lvm.conf.5.in | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/man/lvm.conf.5.in b/man/lvm.conf.5.in index 68024b65..0e3a949d 100644 --- a/man/lvm.conf.5.in +++ b/man/lvm.conf.5.in @@ -134,8 +134,8 @@ superblocks. This doesn't always work satisfactorily e.g. if a device has been reused without wiping the md superblocks first. .IP \fBmd_chunk_alignment\fP \(em If set to 1, and a Physical Volume is placed -directly upon an md device, LVM2 will align its data blocks with the the -chunk_size exposed in sysfs. +directly upon an md device, LVM2 will align its data blocks with the +md device's stripe-width. .IP \fBdata_alignment\fP \(em Default alignment (in KB) of start of data area when creating a new Physical Volume using the \fBlvm2\fP format. |