From: bmr@sourceware.org <bmr@sourceware.org>
To: lvm-devel@redhat.com
Subject: LVM2 ./WHATS_NEW scripts/lvm_dump.sh
Date: 25 Apr 2007 14:49:27 -0000 [thread overview]
Message-ID: <20070425144927.6140.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: bmr at sourceware.org 2007-04-25 15:49:27
Modified files:
. : WHATS_NEW
scripts : lvm_dump.sh
Log message:
Make lvm_dump.sh capture a listing of /sys/block entries.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.600&r2=1.601
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/scripts/lvm_dump.sh.diff?cvsroot=lvm2&r1=1.4&r2=1.5
--- LVM2/WHATS_NEW 2007/04/24 15:13:13 1.600
+++ LVM2/WHATS_NEW 2007/04/25 14:49:27 1.601
@@ -1,5 +1,7 @@
Version 2.02.25 -
=================================
+ Add /sys/block listings to lvm_dump.sh
+ Make lvm_dump.sh list /dev recursively
Fix thread race in clvmd.
Add scan_sector param to label_read and _find_labeller.
Make clvmd cope with quorum devices on RHEL5
@@ -11,7 +13,6 @@
Fix vgsplit for lvm1 format (set and validate VG name in PVs metadata).
Split metadata areas in vgsplit properly.
Add extra internal error checking to clvmd
- Make lvm_dump.sh list /dev recursively
Version 2.02.24 - 19th March 2007
=================================
--- LVM2/scripts/lvm_dump.sh 2007/04/19 23:06:05 1.4
+++ LVM2/scripts/lvm_dump.sh 2007/04/25 14:49:27 1.5
@@ -149,6 +149,9 @@
myecho "Gathering /dev listing..."
log "$LS -laR /dev > $dir/dev_listing 2>> $log"
+myecho "Gathering /sys/block listing..."
+log "$LS -laR /sys/block > $dir/sysblock_listing"
+
if (( $metadata )); then
myecho "Gathering LVM metadata from Physical Volumes..."
next reply other threads:[~2007-04-25 14:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-25 14:49 bmr [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-01-06 18:02 LVM2 ./WHATS_NEW scripts/lvm_dump.sh 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-07-02 20:18 mbroz
2006-11-23 17:23 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=20070425144927.6140.qmail@sourceware.org \
--to=bmr@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.