From: John Rowe <rowe@excc.ex.ac.uk>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Is LVM safe?
Date: Mon, 20 Jun 2005 15:34:05 +0100 [thread overview]
Message-ID: <1119278045.18965.2.camel@volt> (raw)
In-Reply-To: <d45c7b521930741fc78fef25d061f74b@anderedomain.de>
Thanks, this is more or less what I've been trying:
#vgscan --mknodes -vv
Setting global/locking_type to 1
Setting global/locking_dir to /var/lock/lvm
File-based locking enabled.
Wiping cache of LVM-capable devices
Wiping internal cache
Reading all physical volumes. This may take a while...
Finding all volume groups
/dev/md0: size is 0 sectors
/dev/hda1: size is 417627 sectors
/dev/hda1: No label detected
/dev/hda2: size is 40965750 sectors
/dev/hda2: No label detected
/dev/hda3: size is 6136830 sectors
/dev/hda3: No label detected
/dev/hda4: size is 265056435 sectors
/dev/hda4: lvm2 label detected
/dev/cdrom: open failed: No medium found
Finding all logical volumes
# vgchange -ay -vv
Setting global/locking_type to 1
Setting global/locking_dir to /var/lock/lvm
File-based locking enabled.
Finding all volume groups
/dev/hda1: No label detected
/dev/hda2: No label detected
/dev/hda3: No label detected
/dev/hda4: lvm2 label detected
But it doesn't seem to find anything!
John
next prev parent reply other threads:[~2005-06-20 14:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-20 12:02 [linux-lvm] Is LVM safe? John Rowe
2005-06-20 13:17 ` Rainer Krienke
2005-06-20 13:26 ` Erik Ohrnberger
2005-06-20 13:35 ` Andy Smith
2005-06-20 13:49 ` John Rowe
2005-06-20 14:09 ` Philipp Riegger
2005-06-20 14:34 ` John Rowe [this message]
2005-06-20 14:42 ` AJ Lewis
2005-06-20 15:00 ` John Rowe
2005-06-20 15:12 ` AJ Lewis
2005-06-20 15:27 ` John Rowe
2005-06-20 15:45 ` AJ Lewis
2005-06-20 16:10 ` Eric Hopper
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=1119278045.18965.2.camel@volt \
--to=rowe@excc.ex.ac.uk \
--cc=linux-lvm@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 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 NNTP newsgroup(s).