linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Chris Friesen <chris.friesen@windriver.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] thin_check called with wrong path during "vgchange -ay"
Date: Thu, 26 Nov 2015 10:35:16 -0600	[thread overview]
Message-ID: <565734C4.5020402@windriver.com> (raw)

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)
   Library version: 1.02.74 (2012-03-06)
   Driver version:  4.24.0


Thanks,
Chris

             reply	other threads:[~2015-11-26 16:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-26 16:35 Chris Friesen [this message]
2015-11-26 16:43 ` [linux-lvm] thin_check called with wrong path during "vgchange -ay" Alasdair G Kergon
2015-11-26 17:07   ` Chris Friesen
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=565734C4.5020402@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).