emo/thin-provisioning-tools
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

thin_dump: support optional block# with --metadata-snap to allow for default snapshot stored in metadata to be used; update manual page

Browse Source
This commit is contained in:
Heinz Mauelshagen
2013-07-19 11:48:15 +02:00
parent d7c1f91c97
commit dd1e4c1233
3 changed files with 54 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
man8/thin_dump.8
View File

@@ -23,9 +23,12 @@ Print output in XML or human readable format.
.IP "\fB\-r, \-\-repair\fP".
.IP "\fB\-m, \-\-metadata_snap\fP block#".
Dump metadata snapshot created by device-mapper thin provisioning target at block#
.IP "\fB\-m, \-\-metadata_snap\fP [block#]".
Dump metadata snapshot created by device-mapper thin provisioning target.
If block is not provided, access the default metadata snapshot created by
the thin provisioning device-mapper target, else try the one at block#.
See the thin provisioning target documentation on how to create or release
a metadata snapshot.
.IP "\fB\-h, \-\-help\fP".
Print help and exit.
@@ -44,6 +47,13 @@ to standard output in XML format:
.sp
.B thin_dump /dev/vg/metadata
Dumps the thin provisioning metadata snapshot on logical volume /dev/vg/metadata
to standard output in human readable format (not processable by
.B thin_restore(8)
):
.sp
.B thin_dump --format human_readable --metadata-snap /dev/vg/metadata
.SH DIAGNOSTICS
.B thin_dump
returns an exit code of 0 for success or 1 for error.