From: Uday Bhaskar Sarma Seetamraju <sarma@bellatlantic.net>
To: linux-lvm@sistina.com
Subject: [linux-lvm] LVM help re:
Date: Tue, 25 Sep 2001 23:33:17 -0400 [thread overview]
Message-ID: <3BB14C7D.CDCD9F14@bellatlantic.net> (raw)
Hi,
pvscan tells me which PV belongs to which VG.
But I am wondering if the information as to
"which PVwas added to the VG in which order"
can also be determined.
In case of a disaster, the first added PV would most likely contain
all the information that's has been around longer (and so more
important!)
Sarma
P.S: An 'ls' will not tell you in which order files/subfolders were
created, but du or tar does.
P.S: Getting used to LVM reminds me of the days of early
minivax/ultrix days (my first unix impressions), where each
'rm' and 'mv' and 'cp' command was "entered" after 10
deep breaths and 2 minutes of deep thought about what
"that" command WILL do (when "entered" ofcourse!!).
Not a criticism of LVM, just that the flexibility and new-ness
of this concept lets one kill oneself so easily.
Can't speak for the world, but I can't handle this
kind of flexibilty and power.
next reply other threads:[~2001-09-26 3:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-26 3:33 Uday Bhaskar Sarma Seetamraju [this message]
2001-09-26 6:46 ` [linux-lvm] LVM help Luca Berra
2001-09-26 8:27 ` Wolfgang Weisselberg
2001-09-26 16:07 ` [linux-lvm] 1.0.1-rc2 lvcreate segfaults, pvcreate, vgcreate ok Jim Cromie
2001-09-26 16:54 ` John Marquart
2001-09-26 18:38 ` Jim Cromie
2001-09-26 18:47 ` [linux-lvm] vgscan 1.0.1-rc2 + kernel 2.4.10 Andre Margis
2001-09-27 6:03 ` svetljo
2001-09-27 15:05 ` Andre Margis
2001-09-27 15:55 ` Andreas Dilger
2001-10-01 23:44 ` Sean Burford
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=3BB14C7D.CDCD9F14@bellatlantic.net \
--to=sarma@bellatlantic.net \
--cc=linux-lvm@sistina.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox