Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

metastore(1) [debian man page]

metastore(1)						      General Commands Manual						      metastore(1)

NAME
metastore - stores and restores filesystem metadata SYNOPSIS
metastore ACTION [OPTION...] [PATH...] DESCRIPTION
Stores or restores metadata (owner, group, permissions, xattrs and optionally mtime) for a filesystem tree. This can be used to preserve the metadata in situations where it is usually not stored (git and tar for example) or as a tripwire like mechanism to detect any changes to metadata. Note that e.g. SELinux stores its labels in xattrs so care should be taken when applying stored metadata to make sure that system security is not compromised. ACTIONS
-c, --compare Shows the difference between the stored and real metadata. -s, --save Saves the current metadata to ./.metadata or to the specified file (see --file option below). -a, --apply Attempts to apply the stored metadata to the file system. -h, --help Prints a help message and exits. OPTIONS
-v, --verbose Causes metastore to print more verbose messages. Can be repeated more than once for even more verbosity. -q, --quiet Causes metastore to print less verbose messages. Can be repeated more than once for even less verbosity. -m, --mtime Causes metastore to also take mtime into account for the compare or apply actions. -e, --empty-dirs Also attempts to recreate missing empty directories. May be useful where empty directories are not tracked (e.g. by git or cvs). Only works in combination with the apply option. This is currently an experimental feature. -f <file>, --file <file> Causes the metadata to be saved, read from the specified file rather than ./.metadata. PATHS
If no path is specified, metastore will use the current directory as the basis for the actions. This is the recommended way of executing metastore. Alternatively, one or more paths can be specified and they will each be examined. Later invocations should be made using the exact same paths to ensure that the stored metadata is interpreted correctly. AUTHOR
Written by David Hardeman <david@hardeman.nu> May 2007 metastore(1)

Check Out this Related Man Page

VGCFGRESTORE(8) 					      System Manager's Manual						   VGCFGRESTORE(8)

NAME
vgcfgrestore - restore volume group descriptor area SYNOPSIS
vgcfgrestore [-d|--debug] [-f|--file <filename>] [--force] [-l[l]|--list] [-h|--help] [-M|--metadatatype 1|2] [-t|--test] [-v|--verbose] VolumeGroupName DESCRIPTION
vgcfgrestore allows you to restore the metadata of VolumeGroupName from a text backup file produced by vgcfgbackup. You can specify a backup file with --file. If no backup file is specified, the most recent one is used. Use --list for a list of the available backup and archive files of VolumeGroupName. OPTIONS
See lvm(8) for common options. -l, --list List files pertaining to VolumeGroupName List metadata backup and archive files pertaining to VolumeGroupName. May be used with the -f option. Does not restore VolumeGroupName. -f, --file filename Name of LVM metadata backup file Specifies a metadata backup or archive file to be used for restoring VolumeGroupName. Often this file has been created with vgcfgbackup. --force Necessary to restore metadata with thin pool volumes. WARNING: Use with extreme caution. Most changes to thin metadata cannot be reverted. You may lose data if you restore metadata that does not match the thin pool kernel metadata precisely. REPLACING PHYSICAL VOLUMES
vgdisplay --partial --verbose will show you the UUIDs and sizes of any PVs that are no longer present. If a PV in the VG is lost and you wish to substitute another of the same size, use pvcreate --restorefile filename --uuid uuid (plus additional arguments as appropriate) to initialise it with the same UUID as the missing PV. Repeat for all other missing PVs in the VG. Then use vgcfgrestore --file filename to restore the volume group's metadata. SEE ALSO
lvm(8), vgcreate(8) Sistina Software UK LVM TOOLS 2.02.105(2)-RHEL7 (2014-03-26) VGCFGRESTORE(8)
Man Page