David Teigland c22ad12bab metadata: extend writes to zero space ... Previously, consecutive copies of metadata would have garbage data in the space between them. After metadata wrapping, the garbage would be portions of old metadata. This made analysis of the metadata area more difficult. This would happen because the start of new copy of metadata is advanced from the end of the last copy to start at the next 512 byte boundary. Zero the space between consecutive copies of metadata by extending each metadata write to end at the next 512 byte boundary. The size of the metadata itself is not extended, only the write. The buffer being written contains the metadata text followed by the necessary number of zeros.		2019-07-12 15:00:12 -05:00
..
archive.c	Merge branch 'master' into 2018-05-11-fork-libdm	2018-06-01 13:04:12 +01:00
archiver.c	separate code for setting devices from metadata parsing	2019-05-23 11:57:38 -05:00
archiver.h	build: Don't generate symlinks in include/ dir	2018-05-14 10:30:20 +01:00
export.c	metadata: extend writes to zero space	2019-07-12 15:00:12 -05:00
flags.c	Use "cachevol" to refer to cache on a single LV	2019-02-27 08:52:34 -06:00
format-text.c	metadata: extend writes to zero space	2019-07-12 15:00:12 -05:00
format-text.h	move wipe_outdated_pvs to vg_write	2019-06-07 15:54:04 -05:00
import_vsn1.c	separate code for setting devices from metadata parsing	2019-05-23 11:57:38 -05:00
import-export.h	metadata: extend writes to zero space	2019-07-12 15:00:12 -05:00
import.c	improve reading and repairing vg metadata	2019-06-07 15:54:04 -05:00
layout.h	add flags to keep track of bad metadata	2019-06-07 15:54:04 -05:00
text_export.h	coverity: fix possible resource leak of descendants_buffer in _print_historical_lv fn	2016-05-31 09:36:58 +02:00
text_import.h	doc: change fsf address	2016-01-21 12:11:37 +01:00
text_label.c	improve reading and repairing vg metadata	2019-06-07 15:54:04 -05:00