All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: linux-lvm@redhat.com
Subject: [linux-lvm] metadata problems while testing lvm2 git with dm_thin_pool
Date: Fri, 27 Jul 2012 14:53:00 +0200	[thread overview]
Message-ID: <50128F2C.4040308@profihost.ag> (raw)

Hello list,

lvm autogrow grows more than allowed virtual size.

Kernel: 3.5-rc7
lvm/dmeventd: up2date git version 186a2772

I created my thin disk like this:
lvcreate --poolmetadatasize 5G -L 10G -T thinvol/pool1 -V 100G --name disk1

After some autoresizing lvs looks like this:
# lvs
   LV    VG      Attr     LSize   Pool  Origin Data%  Move Log Copy% Convert
   disk1 thinvol Vwi-a-tz 100,00g pool1         22,95
   pool1 thinvol twi-a-tz  33,77g               67,97

When i copy constantly data to my device - i end up here:
# lvs
   LV    VG      Attr     LSize   Pool  Origin Data%  Move Log Copy% 
Convert
   disk1 thinvol Vwi-aotz 100,00g pool1         99,96 

   pool1 thinvol twi-a-tz 123,86g               80,71

So the pool is bigger than disk1 and the 23,86GB will never get used as 
the disk is FULL.

Is this expected?

Greets
Stefan

             reply	other threads:[~2012-07-27 12:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-27 12:53 Stefan Priebe - Profihost AG [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-07-27 12:29 [linux-lvm] metadata problems while testing lvm2 git with dm_thin_pool Stefan Priebe - Profihost AG
2012-07-27 13:09 ` Sebastian Riemer
2012-07-27 13:31   ` Stefan Priebe - Profihost AG
2012-07-27 13:49     ` Sebastian Riemer
2012-07-27 14:24     ` Zdenek Kabelac
2012-07-27 11:57 Stefan Priebe - Profihost AG
2012-07-30  9:45 ` 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=50128F2C.4040308@profihost.ag \
    --to=s.priebe@profihost.ag \
    --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.