summaryrefslogtreecommitdiffstats
path: root/WHATS_NEW_DM
diff options
context:
space:
mode:
authorJonathan Brassow <jbrassow@redhat.com>2012-09-11 13:01:05 -0500
committerJonathan Brassow <jbrassow@redhat.com>2012-09-11 13:01:05 -0500
commita2d9b1a7e92aab78c80be0e0cbd45fde00d42aa4 (patch)
tree8c0d84f59919d5467bd84948bb6efac0db47168e /WHATS_NEW_DM
parent05131f5853e86419d9c726faa961b8d012298d9c (diff)
downloadlvm2-a2d9b1a7e92aab78c80be0e0cbd45fde00d42aa4.tar.gz
lvm2-a2d9b1a7e92aab78c80be0e0cbd45fde00d42aa4.tar.xz
lvm2-a2d9b1a7e92aab78c80be0e0cbd45fde00d42aa4.zip
cleanup: Restructure code that handles mirror resyncing
When an LV is to be resynced, the metadata areas are cleared and the LV is reactivated. This is true for mirroring and will also be true for RAID LVs. We restructure the code in lvchange_resync() so that we keep all the common steps necessary (validation of ability to resync, deactivation, activation of meta/log devices, clearing of those devices, etc) and place the code that will be divergent in separate functions: detach_metadata_devices() attach_metadata_devices() The common steps will be processed on lists of metadata devices. Before RAID capability is added, this will simply be the mirror log device (if found). This patch lays the ground-work for adding resync of RAID LVs.
Diffstat (limited to 'WHATS_NEW_DM')
0 files changed, 0 insertions, 0 deletions