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: Tue, 06 Jan 2009 18:03:00 -0000 [thread overview]
Message-ID: <20090106180258.24201.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: mbroz@sourceware.org 2009-01-06 18:02:58
Modified files:
. : WHATS_NEW
scripts : lvm_dump.sh
Log message:
Fix lvmdump /sys listing to include virtual devices directory.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.1015&r2=1.1016
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/scripts/lvm_dump.sh.diff?cvsroot=lvm2&r1=1.13&r2=1.14
--- LVM2/WHATS_NEW 2008/12/22 09:04:35 1.1015
+++ LVM2/WHATS_NEW 2009/01/06 18:02:57 1.1016
@@ -1,5 +1,6 @@
Version 2.02.44 -
====================================
+ Fix lvmdump /sys listing to include virtual devices directory.
Add "--refresh" functionality to vgchange and vgmknodes.
Check for maximal LV size when wiping device.
Calculate mirror log size instead of using 1 extent.
--- LVM2/scripts/lvm_dump.sh 2008/08/28 10:40:44 1.13
+++ LVM2/scripts/lvm_dump.sh 2009/01/06 18:02:58 1.14
@@ -197,7 +197,8 @@
log "$LS -laR /dev > \"$dir/dev_listing\" 2>> \"$log\""
myecho "Gathering /sys/block listing..."
-log "$LS -laR /sys/block > \"$dir/sysblock_listing\""
+log "$LS -laR /sys/block > \"$dir/sysblock_listing\" 2>> \"$log\""
+log "$LS -laR /sys/devices/virtual/block >> \"$dir/sysblock_listing\" 2>> \"$log\""
if (( $metadata )); then
myecho "Gathering LVM metadata from Physical Volumes..."
next reply other threads:[~2009-01-06 18:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-06 18:03 mbroz [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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=20090106180258.24201.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).