From: Gionatan Danti <g.danti@assyoma.it>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] thin handling of available space
Date: Tue, 3 May 2016 15:15:45 +0200 [thread overview]
Message-ID: <5728A481.6080600@assyoma.it> (raw)
In-Reply-To: <57288EB8.9020303@redhat.com>
On 03/05/2016 13:42, Zdenek Kabelac wrote:
>
> Danger with having 'disable' options like this is many distros do decide
> themselves about best defaults for their users, but Ubuntu with their
> issue_discards=1 shown us to be more careful as then it's not Ubuntu but
> lvm2 which is blamed for dataloss.
>
> Options are evaluated...
>
Very true. "Sane defaults" is one of the reason why I (happily) use
RHEL/CentOS as hypervisors and other critical tasks.
>
>
> What's wrong with 'lvs'?
> This will give you the available space in thin-pool.
>
Oh, absolutely nothing wrong with lvs. I used "lsblk" only as an example
of the block device/layer exposing some (lack of) features to upper layer.
One note about the continued "suggestion" to use BTRFS. While for
relatively simple use case it can be ok, for more demanding
(rewrite-heavy) scenarios (eg: hypervisor, database, ecc) it performs
*really* bad, even when "nocow" is enabled.
I had much more fortune, performance wise, with ZFS. Too bad ZoL is an
out-of-tree component (albeit very easy to install and, in my
experience, quite stable also).
Anyway, ThinLVM + XFS is an extremely good combo in my opinion.
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
--
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:[~2016-05-03 13:15 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <929635034.3140318.1461840230292.JavaMail.yahoo.ref@mail.yahoo.com>
2016-04-28 10:43 ` [linux-lvm] thin handling of available space matthew patton
2016-04-28 18:20 ` Xen
2016-04-28 18:25 ` Xen
2016-04-29 11:23 ` Zdenek Kabelac
2016-05-02 14:32 ` Mark Mielke
2016-05-03 9:45 ` Zdenek Kabelac
2016-05-03 10:41 ` Mark Mielke
2016-05-03 11:18 ` Zdenek Kabelac
2016-05-03 10:15 ` Gionatan Danti
2016-05-03 11:42 ` Zdenek Kabelac
2016-05-03 13:15 ` Gionatan Danti [this message]
2016-05-03 15:45 ` Zdenek Kabelac
2016-05-03 12:42 ` Xen
[not found] <799090122.6079306.1462373733693.JavaMail.yahoo.ref@mail.yahoo.com>
2016-05-04 14:55 ` matthew patton
2016-05-03 18:19 Xen
[not found] <1614984310.1700582.1462280490763.JavaMail.yahoo.ref@mail.yahoo.com>
2016-05-03 13:01 ` matthew patton
2016-05-03 15:47 ` Xen
2016-05-04 0:56 ` Mark Mielke
[not found] <1870050920.5354287.1462276845385.JavaMail.yahoo.ref@mail.yahoo.com>
2016-05-03 12:00 ` matthew patton
2016-05-03 14:38 ` Xen
2016-05-04 1:25 ` Mark Mielke
2016-05-04 18:16 ` Xen
[not found] <1684768750.3193600.1461851163510.JavaMail.yahoo.ref@mail.yahoo.com>
2016-04-28 13:46 ` matthew patton
[not found] <518072682.2617983.1461760017772.JavaMail.yahoo.ref@mail.yahoo.com>
2016-04-27 12:26 ` matthew patton
2016-04-27 21:28 ` Xen
2016-04-28 6:46 ` Marek Podmaka
2016-04-28 10:33 ` Xen
-- strict thread matches above, loose matches on Subject: below --
2016-04-23 17:53 Xen
2016-04-27 12:01 ` Xen
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=5728A481.6080600@assyoma.it \
--to=g.danti@assyoma.it \
--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).