From: Ian Gordon <ian.gordon@strath.ac.uk>
To: linux-lvm@redhat.com
Subject: [linux-lvm] lvm thinpool metadata spare resizing
Date: Thu, 16 Apr 2015 08:51:29 +0100 [thread overview]
Message-ID: <552F6A01.7080003@strath.ac.uk> (raw)
Hello,
When I manually resized my thinpool's metdata lv with
lvextend -L +200M vg/tp_tmeta
it did not resize the lvol0_pmspare metadata spare lv.
Is this a problem for automatic recovery (or am I worrying too much)?
I can't manually resize the metadata spare lv because I get an error
"Can't resize internal logical volume lvol0_pmspare". Is there a way of
recreating the metadata spare lv?
Cheers,
--
Ian Gordon,
Department of Computer and Information Sciences,
University of Strathclyde.
Tel: 0141 548 3592 Fax: 0141 548 4523 Room: LT1307
The University of Strathclyde is a charitable body, registered in
Scotland, with registration number SC015263.
next reply other threads:[~2015-04-16 7:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 7:51 Ian Gordon [this message]
2015-04-16 16:38 ` [linux-lvm] lvm thinpool metadata spare resizing 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=552F6A01.7080003@strath.ac.uk \
--to=ian.gordon@strath.ac.uk \
--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).