From: Alasdair G Kergon <agk@uk.sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Instability with 2.6, recovering (meta)data?
Date: Mon Nov 10 12:56:02 2003 [thread overview]
Message-ID: <20031110185503.I16901@uk.sistina.com> (raw)
In-Reply-To: <20031109213821.GA4425@amphibian.dyndns.org>; from toad@amphibian.dyndns.org on Sun, Nov 09, 2003 at 09:38:21PM +0000
On Sun, Nov 09, 2003 at 09:38:21PM +0000, Toad wrote:
> after some operation or other (creating an LV? resizing one?) on
> LVM on 2.6, I could no longer access my LVs under 2.4/LVM1.
Likely to have been creating an LV.
The LVM2 CVS head contains a workaround for this; I'll release a new
LVM2 tarball shortly.
Alasdair
--
agk@uk.sistina.com
next prev parent reply other threads:[~2003-11-10 12:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-10 11:13 [linux-lvm] Instability with 2.6, recovering (meta)data? Toad
2003-11-10 11:47 ` Toad
2003-11-10 12:41 ` Toad
2003-11-10 17:10 ` Alasdair G Kergon
2003-11-13 18:06 ` Alasdair G Kergon
2003-11-10 13:09 ` Alasdair G Kergon
2003-11-10 12:56 ` Alasdair G Kergon [this message]
2003-11-11 14:18 ` Jose Luis Domingo Lopez
2003-11-11 14:23 ` Re[2]: " Spam
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=20031110185503.I16901@uk.sistina.com \
--to=agk@uk.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox