From: Chris Friesen <chris.friesen@windriver.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] thin_check called with wrong path during "vgchange -ay"
Date: Thu, 26 Nov 2015 11:07:10 -0600 [thread overview]
Message-ID: <56573C3E.3060501@windriver.com> (raw)
In-Reply-To: <20151126164353.GA5235@agk-dp.fab.redhat.com>
On 11/26/2015 10:43 AM, Alasdair G Kergon wrote:
> On Thu, Nov 26, 2015 at 10:35:16AM -0600, Chris Friesen wrote:
>> controller-0:/home/wrsroot# vgchange -ay cinder-volumes
>> Check of thin pool cinder-volumes/cinder-volumes-pool failed
>> (status:1). Manual repair required (thin_dump --repair
>> /dev/mapper/cinder-volumes-cinder-volumes-pool_tmeta)!
>
> I don't see that upstream. Try upgrading lvm2.
>
> Alasdair
I think I found it. Git commit e866931 (Improve thin_check option passing) has
"Fix dm name usage for thin pools with '-' in name." in the commit message.
Looks like it went into 2.2.96, one version after the one I'm using. Just my
luck. :)
Chris
next prev parent reply other threads:[~2015-11-26 17:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-26 16:35 [linux-lvm] thin_check called with wrong path during "vgchange -ay" Chris Friesen
2015-11-26 16:43 ` Alasdair G Kergon
2015-11-26 17:07 ` Chris Friesen [this message]
2015-11-26 17:14 ` Zdenek Kabelac
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=56573C3E.3060501@windriver.com \
--to=chris.friesen@windriver.com \
--cc=linux-lvm@redhat.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;
as well as URLs for NNTP newsgroup(s).