LVM2/scripts lvmdump.sh

LVM2/scripts lvmdump.sh

[agk]

CVSROOT:	/cvs/lvm2
Module name:	LVM2
Changes by:	agk at sourceware.org	2010-04-14 20:03:47

Modified files:
	scripts        : lvmdump.sh 

Log message:
	touch file

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/scripts/lvmdump.sh.diff?cvsroot=lvm2&r1=1.14&r2=1.15

--- LVM2/scripts/lvmdump.sh	2009/01/06 18:02:58	1.14
+++ LVM2/scripts/lvmdump.sh	2010/04/14 20:03:46	1.15
@@ -1,7 +1,7 @@
 #!/bin/bash
 # We use some bash-isms (getopts?)
 
-# Copyright (C) 2007 Red Hat, Inc. All rights reserved.
+# Copyright (C) 2007-2010 Red Hat, Inc. All rights reserved.
 #
 # This file is part of LVM2.
 #

LVM2/scripts lvmdump.sh

[mbroz]

CVSROOT:	/cvs/lvm2
Module name:	LVM2
Changes by:	mbroz at sourceware.org	2011-06-02 09:08:16

Modified files:
	scripts        : lvmdump.sh 

Log message:
	Use append but except query for dlm locks:-)

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/scripts/lvmdump.sh.diff?cvsroot=lvm2&r1=1.17&r2=1.18

--- LVM2/scripts/lvmdump.sh	2011/06/02 09:02:03	1.17
+++ LVM2/scripts/lvmdump.sh	2011/06/02 09:08:16	1.18
@@ -146,7 +146,7 @@
 	echo "----------------------------------"
 	if [ -f /proc/cluster/dlm_locks ]
 	then
-		echo clvmd >> /proc/cluster/dlm_locks
+		echo clvmd > /proc/cluster/dlm_locks
 		cat /proc/cluster/dlm_locks
 		echo
 		echo "RESOURCE DIR:"

LVM2/scripts lvmdump.sh

[wysochanski]

CVSROOT:	/cvs/lvm2
Module name:	LVM2
Changes by:	wysochanski at sourceware.org	2011-02-01 21:39:15

Modified files:
	scripts        : lvmdump.sh 

Log message:
	Add "dmsetup ls --tree" output to lvmdump.
	
	It would be most useful to add "dmsetup ls --tree" to the commands run.
	This command helps in answering the question "which devices are actually
	underneath a given LV?"
	
	Although the info is available with other existing dmsetup commands,
	adding this command gives a much clearer summary of complex setups.
	
	Here's an example of an LVM mirror, with mirror images on partitions
	created on top of multipath devices.  The multipath devices are on
	simple block devices.  As you can see, it is easy to see the stacking
	from the "dmsetup ls --tree" output:
	
	vgmpathtest-lvmpathmir (253:14)
	??????vgmpathtest-lvmpathmir_mimage_1 (253:13)
	???  ??????mpath5p1 (253:5)
	???     ??????mpath5 (253:2)
	???        ?????? (8:16)
	???        ?????? (8:0)
	??????vgmpathtest-lvmpathmir_mimage_0 (253:12)
	???  ??????mpath6p1 (253:6)
	???     ??????mpath6 (253:3)
	???        ?????? (8:48)
	???        ?????? (8:32)
	??????vgmpathtest-lvmpathmir_mlog (253:11)
	??????mpath7 (253:4)
	?????? (8:80)
	?????? (8:64)
	VolGroup00-LogVol01 (253:1)
	?????? (202:2)
	vgtest-lvmir (253:10)
	??????vgtest-lvmir_mimage_1 (253:9)
	???  ?????? (7:1)
	??????vgtest-lvmir_mimage_0 (253:8)
	???  ?????? (7:0)
	??????vgtest-lvmir_mlog (253:7)
	?????? (7:3)
	VolGroup00-LogVol00 (253:0)
	?????? (202:2)
	
	But it is much harder to see the stacking with only the commands today
	("dmsetup info", "dmsetup status", and "dmsetup table").  We could
	piece together the stacking from "dmsetup table" but it requires
	further processing (take output from "dmsetup info to get
	map name to major/minor, then parse "dmsetup table", etc).

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/scripts/lvmdump.sh.diff?cvsroot=lvm2&r1=1.15&r2=1.16

--- LVM2/scripts/lvmdump.sh	2010/04/14 20:03:46	1.15
+++ LVM2/scripts/lvmdump.sh	2011/02/01 21:39:15	1.16
@@ -183,6 +183,7 @@
 log "\"$DMSETUP\" info -c > \"$dir/dmsetup_info\" 2>> \"$log\""
 log "\"$DMSETUP\" table > \"$dir/dmsetup_table\" 2>> \"$log\""
 log "\"$DMSETUP\" status > \"$dir/dmsetup_status\" 2>> \"$log\""
+log "\"$DMSETUP\" ls --tree > \"$dir/dmsetup_ls_tree\" 2>> \"$log\""
 
 myecho "Gathering process info..."
 log "$PS alx > \"$dir/ps_info\" 2>> \"$log\""