From patchwork Wed Jun 8 22:13:13 2011 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Jonthan Brassow X-Patchwork-Id: 862742 X-Patchwork-Delegate: agk@redhat.com Received: from mx4-phx2.redhat.com (mx4-phx2.redhat.com [209.132.183.25]) by demeter2.kernel.org (8.14.4/8.14.4) with ESMTP id p58MFZ96016225 for ; Wed, 8 Jun 2011 22:15:55 GMT Received: from lists01.pubmisc.prod.ext.phx2.redhat.com (lists01.pubmisc.prod.ext.phx2.redhat.com [10.5.19.33]) by mx4-phx2.redhat.com (8.13.8/8.13.8) with ESMTP id p58MDQvI005402; Wed, 8 Jun 2011 18:13:27 -0400 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by lists01.pubmisc.prod.ext.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id p58MDKbB005506 for ; Wed, 8 Jun 2011 18:13:20 -0400 Received: from [10.0.2.15] (vpn-11-174.rdu.redhat.com [10.11.11.174]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id p58MDEIm009427 for ; Wed, 8 Jun 2011 18:13:15 -0400 From: Jonathan Brassow To: dm-devel@redhat.com Organization: Red Hat, Inc Date: Wed, 08 Jun 2011 17:13:13 -0500 Message-ID: <1307571193.18638.2.camel@f14.redhat.com> Mime-Version: 1.0 X-Scanned-By: MIMEDefang 2.68 on 10.5.11.23 X-loop: dm-devel@redhat.com Subject: [dm-devel] [PATCH 1 of 7] DM RAID: documentation updates X-BeenThere: dm-devel@redhat.com X-Mailman-Version: 2.1.12 Precedence: junk Reply-To: device-mapper development List-Id: device-mapper development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dm-devel-bounces@redhat.com Errors-To: dm-devel-bounces@redhat.com X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.2.6 (demeter2.kernel.org [140.211.167.43]); Wed, 08 Jun 2011 22:15:56 +0000 (UTC) Updates to the dm-raid.txt documentation. Add a little more information for some of the parameters of a dm-raid CTR table and add a little more clarity to how parameters are printed when 'dmsetup table' is issued. Signed-off-by: Jonathan Brassow --- dm-devel mailing list dm-devel@redhat.com https://www.redhat.com/mailman/listinfo/dm-devel Index: linux-2.6/Documentation/device-mapper/dm-raid.txt =================================================================== --- linux-2.6.orig/Documentation/device-mapper/dm-raid.txt +++ linux-2.6/Documentation/device-mapper/dm-raid.txt @@ -22,10 +22,15 @@ planned for the future.) The list of re is the same for all the current raid types. The required parameters are positional, while the optional parameters are given as key/value pairs. The possible parameters are as follows: - Chunk size in sectors. + Chunk size in sectors. This parameter is often called + "stripe size". It is the only required parameter and + must be the first parameter. [[no]sync] Force/Prevent RAID initialization [rebuild ] Rebuild the drive indicated by the index - [daemon_sleep ] Time between bitmap daemon work to clear bits + [daemon_sleep ] Time between bitmap daemon work to clear bits. A longer + time means less bitmap I/O, but potentially longer resync + time after a failure due to a less frequent clearing of + the bitmap. [min_recovery_rate ] Throttle RAID initialization [max_recovery_rate ] Throttle RAID initialization [max_write_behind ] See '-write-behind=' (man mdadm) @@ -55,9 +60,12 @@ Examples: raid4 4 2048 min_recovery_rate 20 sync\ 5 - 8:17 - 8:33 - 8:49 - 8:65 - 8:81 -Performing a 'dmsetup table' should display the CTR table used to -construct the mapping (with possible reordering of optional -parameters). +Performing a 'dmsetup table' will display the CTR table used to construct the +mapping. The optional parameters will always be printed in the order listed +above. "sync" or "nosync" will always be printed before the other arguments, +for example. If the user passes in optional arguments in a different order, +the results of 'dmsetup table' will differ from the CTR table used to construct +the mapping. Performing a 'dmsetup status' will yield information on the state and health of the array. The output is as follows: