linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Oliver Rath <rath@mglug.de>
To: linux-lvm@redhat.com
Subject: [linux-lvm] SOLVED [was Re: What todo if metadata grows faster than pool data]
Date: Fri, 24 Oct 2014 17:20:41 +0200	[thread overview]
Message-ID: <544A6E49.9040200@mglug.de> (raw)
In-Reply-To: <20141024141849.GB29345@redhat.com>

Hi Mike!

Im using lvim 2.02.110 with kernel 3.16.


Am 24.10.2014 um 16:18 schrieb Mike Snitzer:
> On Fri, Oct 24 2014 at 10:08am -0400,
> You'll want to grow the metadata volume.  Newer versions of the
> dm-thinp kernel code and lvm2 userspace code make this possible.
>
> See the "Manually manage free metadata space of a thin pool LV" section
> of the lvmthin.7 manpage in a recent lvm2 release.

Hour hint to the tmvthin-manpage was right:

lvextend -L+96M dmivg/winthinpool_tmeta

worked!

Now Metadata is safe:

  --- Logical volume ---
  LV Name                winthinpool
  VG Name                dmivg
  LV UUID                gDGkhM-jGQq-hSuZ-g4CZ-JtcQ-JcdX-DqD7bi
  LV Write Access        read/write
  LV Creation host, time dmicn20, 2014-10-07 23:54:45 +0200
  LV Pool metadata       winthinpool_tmeta
  LV Pool data           winthinpool_tdata
  LV Status              available
  # open                 73
  LV Size                930,00 GiB
  Allocated pool data    50,85%
  Allocated metadata     45,91%
  Current LE             238080
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           252:18


Tfh!

Oliver

      reply	other threads:[~2014-10-24 15:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-24 14:08 [linux-lvm] What todo if metadata grows faster than pool data Oliver Rath
2014-10-24 14:18 ` Mike Snitzer
2014-10-24 15:20   ` Oliver Rath [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=544A6E49.9040200@mglug.de \
    --to=rath@mglug.de \
    --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).