CACHE_DUMP(8) System Manager's Manual CACHE_DUMP(8)NAME
cache_dump - dump cache metadata from device or file to standard output
SYNOPSIS
cache_dump [options] {device|file}
DESCRIPTION
cache_dump dumps binary cache metadata created by the device-mapper cache target on a device or file to standard output for analysis or
postprocessing in XML format. XML formated metadata can be fed into cache_restore (see cache_restore(8)) in order to put it back onto a
metadata device (to process by the device-mapper target) or file.
-r, --repair
Repair the metadata whilst dumping it.
-h, --help
Print help and exit.
-V, --version
Output version information and exit.
EXAMPLES
Dumps the cache metadata on logical volume /dev/vg/metadata to standard output in XML format:
cache_dump /dev/vg/metadata
EXAMPLES
Dumps the cache metadata on logical volume /dev/vg/metadata whilst repairing it to standard output in XML format:
cache_dump --repair /dev/vg/metadata
DIAGNOSTICS
cache_dump returns an exit code of 0 for success or 1 for error.
SEE ALSO cache_check(8)cache_repair(8)cache_restore(8)AUTHOR
Joe Thornber <ejt@redhat.com>
Heinz Mauelshagen <HeinzM@RedHat.com>
Red Hat, Inc. Thin Provisioning Tools CACHE_DUMP(8)
Check Out this Related Man Page
CACHE_CHECK(8) System Manager's Manual CACHE_CHECK(8)NAME
cache_check - repair cache metadata on device or file
SYNOPSIS
cache_check [options] {device|file}
DESCRIPTION
cache_check checks cache metadata created by the device-mapper cache target on a device or file.
OPTIONS -q, --quiet
Suppress output messages, return only exit code.
-h, --help
Print help and exit.
-V, --version
Output version information and exit.
--super-block-only
Only check the superblock is present.
--skip-mappings
Skip checking of the block mappings which make up the bulk of the metadata.
--skip-hints
Skip checking of the policy hint values metadata.
--skip-discards
Skip checking of the discard bits in the metadata.
EXAMPLE
Analyses and repairs cache metadata on logical volume /dev/vg/metadata:
cache_check /dev/vg/metadata
The device may not be actively used by the target when running.
DIAGNOSTICS
cache_check returns an exit code of 0 for success or 1 for error.
SEE ALSO cache_dump(8)cache_repair(8)cache_restore(8)AUTHOR
Joe Thornber <ejt@redhat.com>
Heinz Mauelshagen <HeinzM@RedHat.com>
Red Hat, Inc. Thin Provisioning Tools CACHE_CHECK(8)
Just was wondering how many CD's are required to install RedHat 8. I thought I remember reading that only the first 3 are needed. The last 2 are just source code.
Then talking with from friends, they said all 5 are needed.
What's the correct number?
Thanks!
primal (2 Replies)
How can I find out with a C program, on which RedHat version the program is being ran ? I do know through compilation variables that I'm on RedHat but so far cannot find out which one.
Currently the closest I got was to invoke an ls or cat through syscall for the release or motd files.
... (5 Replies)
Hello,
I have a special problem. I have a file in 8 bit and would like to convert the whole database to 16Bit unicode.
The mapping file has the following structure:
The mapper is provided as a zip file
The target file to be converted contains data in English and 8 bit Urdu mapping, a... (4 Replies)
I've never seen this, is it normal for 11.2? Anyway to change it back to dumping metadata or is this simply an overly verbose message I may ignore?
kernel without ZFS metadata (4 Replies)