From: Ric Wheeler <rwheeler@redhat.com>
To: Paul Cuzner <pcuzner@redhat.com>, James <purpleidea@gmail.com>
Cc: device-mapper development <dm-devel@redhat.com>,
Gluster Devel <gluster-devel@nongnu.org>
Subject: Re: [Gluster-devel] Puppet-Gluster+ThinP
Date: Sun, 20 Apr 2014 16:59:30 -0700 [thread overview]
Message-ID: <53545F62.8060001@redhat.com> (raw)
In-Reply-To: <1420171478.1325442.1397081884591.JavaMail.zimbra@redhat.com>
On 04/09/2014 03:18 PM, Paul Cuzner wrote:
>
> I'm really interested in the thinp best practices too. gluster-deploy has had
> thinp support for a while now - and I asked the question about best practices
> a while back - but nothing came back..
>
> Hopefully - you're timing is better than mine!
>
> cc'ing Rajesh since the thinp is all about snapshot enablement.
The amount of space you set aside is very much workload dependent (rate of
change, rate of deletion, rate of notifying the storage about the freed space).
Keep in mind with snapshots (and thinly provisioned storage, whether using a
software target or thinly provisioned array) we need to issue the "discard"
commands down the IO stack in order to let the storage target reclaim space.
That typically means running the fstrim command on the local file system (XFS,
ext4, btrfs, etc) every so often. Less typically, you can mount your local file
system with "-o discard" to do it inband (but that comes at a performance
penalty usually).
There is also a event mechanism to help us get notified when we hit a target
configurable watermark ("help, we are running short on real disk, add more or
clean up!").
Definitely worth following up with the LVM/device mapper people on how to do
this best,
Ric
>
> --------------------------------------------------------------------------------
>
> *From: *"James" <purpleidea@gmail.com>
> *To: *"Gluster Devel" <gluster-devel@nongnu.org>
> *Sent: *Thursday, 10 April, 2014 3:13:40 AM
> *Subject: *[Gluster-devel] Puppet-Gluster+ThinP
>
> Okay,
>
> Here's a first draft of puppet-gluster w/ thin-p. This patch includes
> documentation updates too! (w00t!)
>
> https://github.com/purpleidea/puppet-gluster/tree/feat/thinp
>
> FYI: I'll probably rebase this branch.
> FYI: Somewhat untested. Read the commit message.
>
> Comments welcome :)
>
> I'm most interested to hear about if everyone is pleased with the way I
> run the thin-p lv command. I think this makes the most sense, but let me
> know if anyone has improvements. Also I'd love to hear about what the
> default values for the parameters should be, but that's a one line
> patch, so no rush for me.
>
> Cheers,
> James
>
next parent reply other threads:[~2014-04-20 23:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1397056420.4190.93.camel@freed>
[not found] ` <1420171478.1325442.1397081884591.JavaMail.zimbra@redhat.com>
2014-04-20 23:59 ` Ric Wheeler [this message]
[not found] ` <53545F62.8060001-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-04-21 0:11 ` Puppet-Gluster+ThinP James
2014-04-21 0:44 ` [Gluster-devel] Puppet-Gluster+ThinP Ric Wheeler
[not found] ` <535469F9.7050605-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-04-24 5:59 ` Puppet-Gluster+ThinP James
2014-04-24 12:03 ` [Gluster-devel] Puppet-Gluster+ThinP Lukáš Czerner
2014-04-22 14:30 ` David Teigland
[not found] ` <20140422143018.GA25966-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-04-24 5:59 ` [dm-devel] Puppet-Gluster+ThinP James
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=53545F62.8060001@redhat.com \
--to=rwheeler@redhat.com \
--cc=dm-devel@redhat.com \
--cc=gluster-devel@nongnu.org \
--cc=pcuzner@redhat.com \
--cc=purpleidea@gmail.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.