linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Zdenek Kabelac <zkabelac@redhat.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Testing ThinLVM metadata exhaustion
Date: Mon, 25 Apr 2016 11:54:11 +0200	[thread overview]
Message-ID: <571DE943.40204@redhat.com> (raw)
In-Reply-To: <c01a4d679e96185c56352648cb6159fc@assyoma.it>

On 25.4.2016 10:59, Gionatan Danti wrote:
> Il 23-04-2016 10:40 Gionatan Danti ha scritto:
>> On 22/04/2016 16:04, Zdenek Kabelac wrote:
>>>
>>>
>>> I assume you miss newer kernel.
>>> There was originally this bug.
>>>
>>> Regards
>>>
>>> Zdenek
>>
>> Hi Zdenek,
>> I am running CentOS 6.7 fully patched, kernel version
>> 2.6.32-573.22.1.el6.x86_64
>>
>> Should I open a BZ report for it is RH aware of the problem on RH/CentOS 6.7?
>>
>> Thanks.
>
> Hi,
> sorry for the bump, by I really like to understand if current RHEL6 and RHEL7
> kernels are affected by this serious bug and, if it is the case, if Red Hat is
> aware of that.
>
> I understand this is not the better place to ask about a specific
> distribution, but I see many RedHat peoples here ;)
>
> If this really is the wrong place, can someone point me to the right one (RH
> Bugzilla?).
> Thanks.
>

bugzilla.redhat.com

Anyway - 6.8 will likely be your solution.

Thin-provisioning is NOT supposed to be used at 'corner' cases - we improve 
them, but older version simply had more of them as there was always clearly 
communicated do not over-provision if you can't provide the space.

Out-of-space  is not equal if you run out of your filesystem space - you can't 
expect things will continue to work nicely - the cooperation of block layer 
with filesystem and metadata resilience are continually improved.

We have actually even seen users 'targeting' to hit full-pool as a part of 
regular work-flow - bad bad plan...

Regards

Zdenek

  reply	other threads:[~2016-04-25  9:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-18 14:25 [linux-lvm] Testing ThinLVM metadata exhaustion Gionatan Danti
2016-04-22 13:12 ` Gionatan Danti
2016-04-22 14:04   ` Zdenek Kabelac
2016-04-23  8:40     ` Gionatan Danti
2016-04-25  8:59       ` Gionatan Danti
2016-04-25  9:54         ` Zdenek Kabelac [this message]
2016-04-25 16:52           ` Gionatan Danti
2016-04-26  7:11           ` Gionatan Danti
2016-04-27 11:11             ` Gionatan Danti
2016-05-03 10:05               ` Gionatan Danti

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=571DE943.40204@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).