summaryrefslogtreecommitdiff
path: root/WHATS_NEW_DM
diff options
context:
space:
mode:
authorZdenek Kabelac <zkabelac@redhat.com>2019-08-20 12:30:25 +0200
committerZdenek Kabelac <zkabelac@redhat.com>2019-08-20 12:37:32 +0200
commit0451225c1997273ffaa36c3eb595eae7737b7dda (patch)
treecc84c94d145d7c574e0d20c20e71868696db6e9c /WHATS_NEW_DM
parenta53c157db0110e21aaa9971f0fec7ac19afe91dd (diff)
downloadlvm2-0451225c1997273ffaa36c3eb595eae7737b7dda.tar.gz
pvmove: correcting read_ahead setting
When pvmove is finished, we do a tricky operation since we try to resume multiple different device that were all joined into 1 big tree. Currently we use the infromation from existing live DM table, where we can get list of all holders of pvmove device. We look for these nodes (by uuid) in new metadata, and we do now a full regular device add into dm tree structure. All devices should be already PRELOAD with correct table before entering suspend state, however for correctly working readahead we need to put correct info also into RESUME tree. Since table are preloaded, the same table is skip and resume, but correct read ahead is now set.
Diffstat (limited to 'WHATS_NEW_DM')
0 files changed, 0 insertions, 0 deletions