diff options
| author | Mike Snitzer <snitzer@redhat.com> | 2013-05-13 15:56:47 -0400 |
|---|---|---|
| committer | Mike Snitzer <snitzer@redhat.com> | 2013-05-13 15:56:47 -0400 |
| commit | 8ad7865b421459553a05e220f992ba2d26bd60e6 (patch) | |
| tree | ad509cd502678495f7dbbef2cb2aa2558d7b50a0 /WHATS_NEW | |
| parent | 6fc67f5509fda25a91536fbeeb7099f8327ff3d8 (diff) | |
| download | lvm2-8ad7865b421459553a05e220f992ba2d26bd60e6.tar.gz | |
Fix alignment of PV data area if detected alignment less than 1 MB
This fixes a long standing regression since LVM2 2.02.74 (commit 4efb1d9c,
"Update heuristic used for default and detected data alignment.")
The default PE alignment could be used (via MAX()) even if it was
determined that the device's MD stripe width, or minimal_io_size or
optimal_io_size were not factors of the default PE alignment (either 64K
or the newer default of 1MB, etc). This bug would manifest if the
default PE alignment was larger than the overriding hint that the
device provided (e.g. default of 1MB vs optimal_io_size of 768K).
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
Diffstat (limited to 'WHATS_NEW')
| -rw-r--r-- | WHATS_NEW | 1 |
1 files changed, 1 insertions, 0 deletions
@@ -1,5 +1,6 @@ Version 2.02.99 - =================================== + Fix alignment of PV data area if detected alignment less than 1 MB (2.02.74). Fix memory resource leak in memlocking error path. Fix premature DM version checking which caused useless mapper/control access. Add "active" LV reporting field to show activation state. |