From: AJ Lewis <lewis@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] vg gone after vgextend
Date: Tue, 10 Jul 2001 14:24:57 -0500 [thread overview]
Message-ID: <20010710142457.A3047@sistina.com> (raw)
In-Reply-To: <20010710141332.B31208@zendo.net>; from eli@zendo.net on Tue, Jul 10, 2001 at 02:13:32PM -0500
[-- Attachment #1: Type: text/plain, Size: 1273 bytes --]
On Tue, Jul 10, 2001 at 02:13:32PM -0500, Eli Criffield wrote:
> #vgcfgrestore -n rootvg /dev/hda3
> vgcfgrestore -- "/etc/lvmconf/rootvg.conf" doesn't exist
> vgcfgrestore -- a backup for volume group rootvg is not available
>
> Yeah tried that already? Is there any hope?
Have you looked in /etc/lvmconf? Are there any conf files in there? You
can specify the file to vgcfgrestore on the command line. If there isn't a
file there, don't give up hope yet. Some of the folks on this list might
still respond with other options.
Regards
--
AJ Lewis
Sistina Software Inc. Voice: 612-638-0500
1313 5th St SE, Suite 111 Fax: 612-638-0500
Minneapolis, MN 55414 E-Mail: lewis@sistina.com
http://www.sistina.com
Current GPG fingerprint = 3B5F 6011 5216 76A5 2F6B 52A0 941E 1261 0029 2648
Get my key at: http://www.sistina.com/~lewis/gpgkey
(Unfortunately, the PKS-type keyservers do not work with multiple sub-keys)
-----Begin Obligatory Humorous Quote----------------------------------------
A program is a device used to convert data into error messages.
-----End Obligatory Humorous Quote------------------------------------------
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2001-07-10 19:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-10 14:39 [linux-lvm] vg gone after vgextend Eli Criffield
2001-07-10 16:06 ` AJ Lewis
2001-07-10 16:39 ` Eli Criffield
2001-07-10 17:12 ` AJ Lewis
2001-07-10 18:57 ` Eli Criffield
2001-07-10 19:05 ` AJ Lewis
2001-07-10 19:13 ` Eli Criffield
2001-07-10 19:24 ` AJ Lewis [this message]
2001-07-10 19:47 ` Eli Criffield
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=20010710142457.A3047@sistina.com \
--to=lewis@sistina.com \
--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.