public inbox for lvm2-cvs@sourceware.org
help / color / mirror / Atom feed
From: mbroz@sourceware.org
To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org
Subject: LVM2 ./WHATS_NEW scripts/lvm_dump.sh
Date: Mon, 02 Jul 2007 20:18:00 -0000 [thread overview]
Message-ID: <20070702201838.25506.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: mbroz@sourceware.org 2007-07-02 20:18:38
Modified files:
. : WHATS_NEW
scripts : lvm_dump.sh
Log message:
Add kernel and device-mapper targets versions report to lvmdump.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.644&r2=1.645
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/scripts/lvm_dump.sh.diff?cvsroot=lvm2&r1=1.5&r2=1.6
--- LVM2/WHATS_NEW 2007/07/02 11:17:20 1.644
+++ LVM2/WHATS_NEW 2007/07/02 20:18:38 1.645
@@ -1,5 +1,6 @@
Version 2.02.27 -
================================
+ Add kernel and device-mapper targets versions report to lvmdump.
Don't use index and rindex functions marked by SUSv3 as legacy.
Fix vgsplit if splitting all PVs from VG.
Fix lvmdiskscan volume reporting when run in the lvm shell
--- LVM2/scripts/lvm_dump.sh 2007/04/25 14:49:27 1.5
+++ LVM2/scripts/lvm_dump.sh 2007/07/02 20:18:38 1.6
@@ -18,6 +18,7 @@
CUT=cut
DATE=date
BASENAME=basename
+UNAME=uname
# user may override lvm and dmsetup location by setting LVM_BINARY
# and DMSETUP_BINARY respectively
@@ -131,6 +132,10 @@
$LVM lvs --version >> $dir/versions 2>> $log
echo "DEVICE MAPPER VERSION:" >> $dir/versions
$DMSETUP --version >> $dir/versions 2>> $log
+echo "KERNEL VERSION:" >> $dir/versions
+$UNAME -a >> $dir/versions 2>> $log
+echo "DM TARGETS VERSIONS:" >> $dir/versions
+$DMSETUP targets >> $dir/versions 2>> $log
myecho "Gathering dmsetup info..."
log "$DMSETUP info -c > $dir/dmsetup_info 2>> $log"
next reply other threads:[~2007-07-02 20:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-02 20:18 mbroz [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-01-06 18:03 mbroz
2008-08-28 10:40 mbroz
2007-10-02 16:09 mornfall
2007-10-02 15:48 mornfall
2007-08-09 9:53 pcaulfield
2007-04-25 14:49 bmr
2006-11-23 17:23 agk
2006-10-05 18:42 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=20070702201838.25506.qmail@sourceware.org \
--to=mbroz@sourceware.org \
--cc=lvm-devel@redhat.com \
--cc=lvm2-cvs@sourceware.org \
/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 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).