From: AJ Lewis <lewis@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] naming conventions of vgcfg-backups?
Date: Tue, 21 Aug 2001 07:13:33 -0500 [thread overview]
Message-ID: <20010821071333.B16248@sistina.com> (raw)
In-Reply-To: <29386.998395265@www26.gmx.net>; from grobe@gmx.net on Tue, Aug 21, 2001 at 02:01:05PM +0200
[-- Attachment #1: Type: text/plain, Size: 1321 bytes --]
On Tue, Aug 21, 2001 at 02:01:05PM +0200, Lars Grobe wrote:
> After resizing, I have to restore my previous lvm configuration. I'm just
> not sure about the default naming of the backups?
>
> Am I right that <vgname>.conf is the current config (which is in use now -
> and which is wrong), while <vgname>.conf.1.old is the previous (which I have
> to restore) and <vgname>.[2345].old are the older backups?
That should be correct I believe, but you could probably take a look at the
timestamp on the file to verify when it was created. Depending upon which
tools you've used, the first couple might be with the current config or a
variant.
--
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 bad random number generator: 1, 1, 1, 1, 1, 4.33e+67, 1, 1, 1...
-----End Obligatory Humorous Quote------------------------------------------
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2001-08-21 12:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-21 12:01 [linux-lvm] naming conventions of vgcfg-backups? Lars Grobe
2001-08-21 12:13 ` AJ Lewis [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-08-21 12:42 Lars Grobe
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=20010821071333.B16248@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.