public inbox for
help / color / mirror / Atom feed
Subject: LVM2/man
Date: Wed, 30 Nov 2011 22:32:00 -0000	[thread overview]
Message-ID: <> (raw)

CVSROOT:	/cvs/lvm2
Module name:	LVM2
Changes by:	2011-11-30 22:32:37

Modified files:
	man            : 

Log message:
	refer to kernel docs for target info
	FIXME thin still missing


--- LVM2/man/	2011/11/13 01:41:57	1.46
+++ LVM2/man/	2011/11/30 22:32:37	1.47
@@ -532,16 +532,13 @@
 To wait until the next event is triggered, use \fBinfo\fP to find
 the last event number.
-// FIXME Rewrite safely (a lot of work) or remove.
 Each line of the table specifies a single target and is of the form:
 .I logical_start_sector num_sectors
 .B target_type
 .RI < target_args >
-There are currently three simple target types available (linear,
-striped, error) together with more complex optional ones that implement
-e.g. snapshots and mirrors.
+Simple target types and <target_args> include: 
 .B linear
 .I destination_device start_sector
@@ -572,83 +569,49 @@
 Errors any I/O that goes to this area.  Useful for testing or
 for creating devices with holes in them.
+.B zero
+Returns blocks of zeroes on reads.  Any data written is discarded silently.
+This is a block-device equivalent of the /dev/zero character-device data sink
+described in \fBnull(4)\fP.
+More complex targets include:
 .B crypt
-.I cipher key iv_offset destination offset
-.RI [ num_params
-.RI < params >]
-Target for transparent encryption of block devices
-using the kernel crypto API.
+Transparent encryption of block devices using the kernel crypto API.
 .B delay
-.I read_device read_offset read_delay
-.RI [ write_device
-.I write_offset
-.IR write_delay ]
-Creates mapping that "delays" reads and/or writes
-to different devices.
+Delays reads and/or writes to different devices.  Useful for testing.
 .B flakey
-.I destination_device start_sector up_interval
-.I down_interval
-.RI [ num_features
-.RI [< feature_arguments >]]
-Creates the same mapping as the linear target except
-that it exhibits unreliable behaviour periodically.
-Useful for simulating failing devices for testing
+Creates a similar mapping to the linear target but
+exhibits unreliable behaviour periodically.
+Useful for simulating failing devices when testing.
 .B mirror
-.I log_type num_logargs
-.RI < logargs >
-.I num_devices
-.RI < device
-.IR offset >+
-Creates mirror mapping target for mirrored logical devices.
+Mirrors data across two or more devices.
 .B multipath
-.I num_features
-.RI < features >
-.I num_handle_args
-.RI < handle_args >
-.I num_path_groups
-.I path_group
-.RI < path_group_args1\.\.N >
-Creates multipath mapping.
-.BR raid1 | raid4 | raid5_ { la | ra | ls | rs }| raid6_ { zr | mr | nc }
-.I num_raid_params
-.RI < raid_params >
-.I num_raid_devs
-.RI < metadata_device
-.IR device >+
-Creates RAID "bridge" mapping between DM and MD.
-It allows the MD RAID drivers to be
-accessed using a device-mapper interface.
-.B snapshot
-.I origin_device cow_device persistant chunksize
-.B snapshot-merge
-.I origin_device cow_device persistant chunksize
+Mediates access through multiple paths to the same device.
+.BR raid
+Offers an interface to the kernel's software raid driver, md.
-.B snapshot-origin
-.I origin_device
-Supports device snapshots.
-.B zero
+.B snapshot
-Returns always zeroed data on reads and silently drops writes.
-This is similar behavior to /dev/zero, but as a block-device instead
-of a character device.
+Supports snapshots of devices.
+To find out more about the various targets and their table formats and status
+lines, please read the files in the Documentation/device-mapper directory in
+the kernel source tree.  
+(Your distribution might include a copy of this information in the 
+documentation directory for the device-mapper package.)

             reply	other threads:[~2011-11-30 22:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-30 22:32 agk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-02-15 12:25 prajnoha
2011-11-13  1:41 agk
2011-03-10 13:11 mbroz
2010-02-15 16:32 prajnoha
2009-11-06  1:41 agk
2009-10-22 13:12 prajnoha
2009-04-23 12:20 agk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).