From: Zdenek Kabelac <zkabelac@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] thin_check called with wrong path during "vgchange -ay"
Date: Thu, 26 Nov 2015 18:14:08 +0100 [thread overview]
Message-ID: <56573DE0.4070407@redhat.com> (raw)
In-Reply-To: <565734C4.5020402@windriver.com>
Dne 26.11.2015 v 17:35 Chris Friesen napsal(a):
> Hi,
>
> I'm hoping this is a known issue. I'm trying to use thin provisioning with
> openstack cinder.
>
> If I run "vgchange -ay cinder-volumes" manually, it complains:
>
> 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)!
>
> If I run thin_check on /dev/mapper/cinder-volumes-cinder-volumes-pool_tmeta it
> complains that the file doesn't exist:
>
>
> controller-0:/home/wrsroot# thin_check
> /dev/mapper/cinder-volumes-cinder-volumes-pool_tmeta
> Couldn't stat dev path
>
>
> The actual file name is
> /dev/mapper/cinder--volumes-cinder--volumes--pool_tmeta (note the
> double-hyphens) and if I run thin_check on that then it seems happy:
>
> controller-0:/home/wrsroot# thin_check
> /dev/mapper/cinder--volumes-cinder--volumes--pool_tmeta
> examining superblock
> examining devices tree
> examining mapping tree
> checking space map counts
>
>
> Does anyone know why thin_check is being called with the wrong filename?
>
> For what it's worth, here's my lvm version:
> controller-0:/home/wrsroot# lvm version
> LVM version: 2.02.95(2) (2012-03-06)
This was early version with thin_check call support - and had a bug
in path building fixed in 2.02.96.
Anyway please switch to some version from this year - ideally upstream...
Zdenek
prev parent reply other threads:[~2015-11-26 17:14 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
2015-11-26 17:14 ` Zdenek Kabelac [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=56573DE0.4070407@redhat.com \
--to=zkabelac@redhat.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 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.