From: wysochanski@sourceware.org <wysochanski@sourceware.org>
To: lvm-devel@redhat.com
Subject: LVM2/scripts lvmdump.sh
Date: 1 Feb 2011 21:39:15 -0000 [thread overview]
Message-ID: <20110201213915.29342.qmail@sourceware.org> (raw)
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\""
next reply other threads:[~2011-02-01 21:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-01 21:39 wysochanski [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-06-02 9:08 LVM2/scripts lvmdump.sh mbroz
2010-04-14 20:03 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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110201213915.29342.qmail@sourceware.org \
--to=wysochanski@sourceware.org \
--cc=lvm-devel@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.