From: Mike Williams <mike@gaima.co.uk>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] inconsistent metadata
Date: Tue Oct 14 13:14:01 2003 [thread overview]
Message-ID: <200310141906.39855.mike@gaima.co.uk> (raw)
In-Reply-To: <200310092100.11002.mike@gaima.co.uk>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thursday 09 October 2003 21:00, Mike Williams wrote:
> Can someone suggest a course of action to get at my data, please?
> I just need to iron out this kink in the road and my life long devotion to
> LVM will be complete! :)
I took a leap of faith and vgcfgbackup'd, and vgcfgrestore'd, and now I have
my data back! w00t
- --
Mike Williams
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQE/jDsvInuLMrk7bIwRAuy8AJ43UCJxWsAVKlhPrUy7EWic3aWxNwCdHgE7
H6tb/+MGGYiBa7nIvXESOjo=
=dsOr
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2003-10-14 13:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-10 8:15 [linux-lvm] inconsistent metadata Mike Williams
2003-10-10 13:43 ` Alasdair G Kergon
2003-10-11 6:17 ` Mike Williams
2003-10-14 13:14 ` Mike Williams [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-01 13:51 [linux-lvm] Inconsistent metadata Marius Gravdal
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=200310141906.39855.mike@gaima.co.uk \
--to=mike@gaima.co.uk \
--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