linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Xen <xen@dds.nl>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: Zdenek Kabelac <zkabelac@redhat.com>
Subject: Re: [linux-lvm] auto umount at thin meta 80%
Date: Tue, 24 May 2016 18:16:27 +0200	[thread overview]
Message-ID: <54a610e7877911e94d1384c01cc3eac8@dds.nl> (raw)
In-Reply-To: <aeba9dc1-e51f-a68d-c0d9-28c606368eb6@redhat.com>

Zdenek Kabelac schreef op 23-05-2016 10:40:

> At this moment -   any failure in  'lvresize' execution leads to
> immediate umount - tool went ballistic and so takes 'drastic' action
> to prevent further
> damage.

I was more worried about why a default sized (auto-created) meta volume 
would fill up almost completely after 3 hours of use.

> See here again:
> 
> https://www.redhat.com/archives/linux-lvm/2016-May/msg00064.html

That message is empty, there is nothing in it.

My computer automatically deletes it when messages such as these come 
by.

It's just a failsafe against time wasting and all that.

Maybe LVM could learn from it, but then it deletes volumes maybe too :p.

Regards lol.


> ATM there is some new code which unconditionally always connects to 
> lvmetad
> even it's not necessary at all - and it's potential source of many 
> other
> troubles - so fixes here are in progress  -   set 'use_lvmetad=0'  if
> it's still a problem in your case.

Right. Well I haven't been able to use my cache again, the SSD seems 
faulty. But. I haven't utilized it to the same extent yet. But. It's now 
at about 17% of the original value (I mean what was 100% back then). 
It's just 4x the size. I can't have stuff like this happening you know. 
I just created it at 4x the default size. Maybe it will work for a 
while.

Regards.

      reply	other threads:[~2016-05-24 16:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-22 17:07 [linux-lvm] auto umount at thin meta 80% Xen
2016-05-23  8:40 ` Zdenek Kabelac
2016-05-24 16:16   ` Xen [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=54a610e7877911e94d1384c01cc3eac8@dds.nl \
    --to=xen@dds.nl \
    --cc=linux-lvm@redhat.com \
    --cc=zkabelac@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).