From: Zdenek Kabelac <zkabelac@redhat.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] LVM generates wrong low_water_mark value in thin-pool's table
Date: Fri, 12 Feb 2016 13:43:14 +0100 [thread overview]
Message-ID: <56BDD362.8020404@redhat.com> (raw)
In-Reply-To: <CAAYit8TQRuUZjjRgMUsaQWNmTGmG824KEZZ8vyNDTG=OiDbObQ@mail.gmail.com>
Dne 1.2.2016 v 10:17 M.H. Tsai napsal(a):
> Hi,
>
> I found that the <low_water_mark> parameter of thin-pool's table might be
> wrong. In kernel, the this parameter is the number of free blocks. However,
> LVM commit 99237f0908d87592815f4bdf3c239e8a108e835c sets this value as the
> number of USED blocks, according
> to activation_thin_pool_autoextend_threshold_CFG. Is that a bug?
>
Hi again
Yep bug on lvm2 size - fix has been upstreamed by this commit:
https://www.redhat.com/archives/lvm-devel/2016-February/msg00005.html
There is also some ongoing work on better lvresize support for more then 1
single LV. This will also implement better approach to resize of lvmetad which
is using different mechanism in kernel.
Lvm2 will try to follow the users wish but also be complaint with kernel
policy for free space in metadata device.
Regards
Zdenek
prev parent reply other threads:[~2016-02-12 12:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 9:17 [linux-lvm] LVM generates wrong low_water_mark value in thin-pool's table M.H. Tsai
2016-02-01 14:19 ` Zdenek Kabelac
2016-02-12 12:43 ` 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=56BDD362.8020404@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 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).