From: Gionatan Danti <g.danti@assyoma.it>
To: Zdenek Kabelac <zkabelac@redhat.com>
Cc: Xen <list@xenhideout.nl>,
LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Snapshot behavior on classic LVM vs ThinLVM
Date: Fri, 14 Apr 2017 11:07:53 +0200 [thread overview]
Message-ID: <483184bceea4fad4baafef32408015b6@assyoma.it> (raw)
In-Reply-To: <5df13342-8c31-4a0b-785e-1d12f0d2d9e8@redhat.com>
Il 14-04-2017 10:24 Zdenek Kabelac ha scritto:
>
> But it's currently impossible to expect you will fill the thin-pool to
> full capacity and everything will continue to run smoothly - this is
> not going to happen.
Even with EXT4 and errors=remount-ro?
>
> However there are many different solutions for different problems -
> and with current script execution - user may build his own solution -
> i.e. call
> 'dmsetup remove -f' for running thin volumes - so all instances get
> 'error' device when pool is above some threshold setting (just like
> old 'snapshot' invalidation worked) - this way user will just kill
> thin volume user task, but will still keep thin-pool usable for easy
> maintenance.
>
Interesting. However, the main problem with libvirt is that its
pool/volume management fall apart when used on thin-pools. Basically,
libvirt does not understand that a thinpool is a container for thin
volumes (ie:
https://www.redhat.com/archives/libvirt-users/2014-August/msg00010.html)
--
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it
email: g.danti@assyoma.it - info@assyoma.it
GPG public key ID: FF5F32A8
next prev parent reply other threads:[~2017-04-14 9:07 UTC|newest]
Thread overview: 94+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-06 14:31 [linux-lvm] Snapshot behavior on classic LVM vs ThinLVM Gionatan Danti
2017-04-07 8:19 ` Mark Mielke
2017-04-07 9:12 ` Gionatan Danti
2017-04-07 13:50 ` L A Walsh
2017-04-07 16:33 ` Gionatan Danti
2017-04-13 12:59 ` Stuart Gathman
2017-04-13 13:52 ` Xen
2017-04-13 14:33 ` Zdenek Kabelac
2017-04-13 14:47 ` Xen
2017-04-13 15:29 ` Stuart Gathman
2017-04-13 15:43 ` Xen
2017-04-13 17:26 ` Stuart D. Gathman
2017-04-13 17:32 ` Stuart D. Gathman
2017-04-14 15:17 ` Xen
2017-04-14 7:27 ` Gionatan Danti
2017-04-14 7:23 ` Gionatan Danti
2017-04-14 15:23 ` Xen
2017-04-14 15:53 ` Gionatan Danti
2017-04-14 16:08 ` Stuart Gathman
2017-04-14 17:36 ` Xen
2017-04-14 18:59 ` Gionatan Danti
2017-04-14 19:20 ` Xen
2017-04-15 8:27 ` Xen
2017-04-15 23:35 ` Xen
2017-04-17 12:33 ` Xen
2017-04-15 21:22 ` Xen
2017-04-15 21:49 ` Xen
2017-04-15 21:48 ` Xen
2017-04-18 10:17 ` Zdenek Kabelac
2017-04-18 13:23 ` Gionatan Danti
2017-04-18 14:32 ` Stuart D. Gathman
2017-04-19 7:22 ` Xen
2017-04-07 22:24 ` Mark Mielke
2017-04-08 11:56 ` Gionatan Danti
2017-04-07 18:21 ` Tomas Dalebjörk
2017-04-13 10:20 ` Gionatan Danti
2017-04-13 12:41 ` Xen
2017-04-14 7:20 ` Gionatan Danti
2017-04-14 8:24 ` Zdenek Kabelac
2017-04-14 9:07 ` Gionatan Danti [this message]
2017-04-14 9:37 ` Zdenek Kabelac
2017-04-14 9:55 ` Gionatan Danti
2017-04-22 7:14 ` Gionatan Danti
2017-04-22 16:32 ` Xen
2017-04-22 20:58 ` Gionatan Danti
2017-04-22 21:17 ` Zdenek Kabelac
2017-04-23 5:29 ` Xen
2017-04-23 9:26 ` Zdenek Kabelac
2017-04-24 21:02 ` Xen
2017-04-24 21:59 ` Zdenek Kabelac
2017-04-26 7:26 ` Gionatan Danti
2017-04-26 7:42 ` Zdenek Kabelac
2017-04-26 8:10 ` Gionatan Danti
2017-04-26 11:23 ` Zdenek Kabelac
2017-04-26 13:37 ` Gionatan Danti
2017-04-26 14:33 ` Zdenek Kabelac
2017-04-26 16:37 ` Gionatan Danti
2017-04-26 18:32 ` Stuart Gathman
2017-04-26 19:24 ` Stuart Gathman
2017-05-02 11:00 ` Gionatan Danti
2017-05-12 13:02 ` Gionatan Danti
2017-05-12 13:42 ` Joe Thornber
2017-05-14 20:39 ` Gionatan Danti
2017-05-15 12:50 ` Zdenek Kabelac
2017-05-15 14:48 ` Gionatan Danti
2017-05-15 15:33 ` Zdenek Kabelac
2017-05-16 7:53 ` Gionatan Danti
2017-05-16 10:54 ` Zdenek Kabelac
2017-05-16 13:38 ` Gionatan Danti
2018-02-27 18:39 ` Xen
2018-02-28 9:26 ` Zdenek Kabelac
2018-02-28 19:07 ` Gionatan Danti
2018-02-28 21:43 ` Zdenek Kabelac
2018-03-01 7:14 ` Gionatan Danti
2018-03-01 8:31 ` Zdenek Kabelac
2018-03-01 9:43 ` Gianluca Cecchi
2018-03-01 11:10 ` Zdenek Kabelac
2018-03-01 9:52 ` Gionatan Danti
2018-03-01 11:23 ` Zdenek Kabelac
2018-03-01 12:48 ` Gionatan Danti
2018-03-01 16:00 ` Zdenek Kabelac
2018-03-01 16:26 ` Gionatan Danti
2018-03-03 18:32 ` Xen
2018-03-04 20:34 ` Zdenek Kabelac
2018-03-03 18:17 ` Xen
2018-03-04 20:53 ` Zdenek Kabelac
2018-03-05 9:42 ` Gionatan Danti
2018-03-05 10:18 ` Zdenek Kabelac
2018-03-05 14:27 ` Gionatan Danti
2018-03-03 17:52 ` Xen
2018-03-04 23:27 ` Zdenek Kabelac
2017-04-22 21:22 ` Zdenek Kabelac
2017-04-24 13:49 ` Gionatan Danti
2017-04-24 14:48 ` 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=483184bceea4fad4baafef32408015b6@assyoma.it \
--to=g.danti@assyoma.it \
--cc=linux-lvm@redhat.com \
--cc=list@xenhideout.nl \
--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 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.