From: Tracy R Reed <treed@ultraviolet.org>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] pvcreate problem on new IDE disk
Date: Tue Apr 22 07:12:01 2003 [thread overview]
Message-ID: <20030420212233.B18402@ultraviolet.org> (raw)
In-Reply-To: <20030421000714.A30038@uk.sistina.com>; from agk@uk.sistina.com on Mon, Apr 21, 2003 at 12:07:15AM +0100
[-- Attachment #1: Type: text/plain, Size: 1262 bytes --]
On Mon, Apr 21, 2003 at 12:07:15AM +0100, Alasdair G Kergon spake thusly:
> Two things to check first:
> Make sure that /dev/hdd2 exists and that other programs can
> write/read it;
brw-rw---- 1 root disk 22, 66 Mar 14 2002 /dev/hdd2
> Run 'vgscan' and then try the pvcreate again.
> [vgscan needs running after new devices are added]
home:/# vgscan
Reading all physical volumes. This may take a while...
Found volume group "system" using metadata type lvm1
home:/# pvcreate /dev/hdd2
Failed to read existing physical volume '/dev/hdd2'
Physical volume "/dev/hdd2" successfully created
It still says "failed to read" etc. but then says successfully created.
Hmm...
home:/# vgextend system /dev/hdd2
Volume group "system" successfully extended
Ok, looks like it is working ok. Now another problem...
home:/# pvmove
Command not implemented yet.
Ugh...looks like LVM1 had it but LVM2 does not yet. Has this changed since
my version?
LVM version: 1.95.10 (2002-05-31)
Even if pvmove is still nonexistant I guess I can put the new disk in another
VG, create LV's over there, and manually copy the data over.
Thanks for the help!
--
Tracy Reed http://www.ultraviolet.org
[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]
next prev parent reply other threads:[~2003-04-22 7:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-20 17:43 [linux-lvm] pvcreate problem on new IDE disk Tracy R Reed
2003-04-20 18:07 ` Alasdair G Kergon
2003-04-22 7:12 ` Tracy R Reed [this message]
2003-04-23 11:44 ` Heinz J . Mauelshagen
2003-04-21 5:33 ` Steffen Koch
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=20030420212233.B18402@ultraviolet.org \
--to=treed@ultraviolet.org \
--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 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.