From: Dave Jones <davej@redhat.com>
To: Alasdair G Kergon <agk@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: lvm backwards compatability
Date: Tue, 9 Jan 2007 12:54:17 -0500 [thread overview]
Message-ID: <20070109175417.GD10474@redhat.com> (raw)
In-Reply-To: <20070109151539.GW21980@agk.surrey.redhat.com>
On Tue, Jan 09, 2007 at 03:15:39PM +0000, Alasdair G Kergon wrote:
> On Mon, Jan 08, 2007 at 06:01:11PM -0500, Dave Jones wrote:
> > Did backwards compatability with old LVM metadata break intentionally
> > in 2.6.19 ? I have a volume that mounts just fine in 2.6.18,
> > but moving to 2.6.19 gets me this..
>
> No - and at first sight that's not a kernel device-mapper problem.
>
> Please grab some diagnostics:
> run the lvmdump script (present in the newest packages) or from here:
>
> http://sources.redhat.com/cgi-bin/cvsweb.cgi/~checkout~/LVM2/scripts/lvm_dump.sh?content-type=text/plain&cvsroot=lvm2
pilot error. got this working now.
thanks,
Dave
--
http://www.codemonkey.org.uk
prev parent reply other threads:[~2007-01-09 17:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-08 23:01 lvm backwards compatability Dave Jones
2007-01-09 15:15 ` Alasdair G Kergon
2007-01-09 17:54 ` Dave Jones [this message]
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=20070109175417.GD10474@redhat.com \
--to=davej@redhat.com \
--cc=agk@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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