From: Zdenek Kabelac <zkabelac@redhat.com>
To: lvm-devel@redhat.com
Subject: [PATCH] automatic snapshot extension with dmeventd (BZ 427298)
Date: Fri, 15 Oct 2010 14:55:37 +0200 [thread overview]
Message-ID: <4CB84F49.9020602@redhat.com> (raw)
In-Reply-To: <87aamffz2u.fsf@twilight.int.mornfall.net.>
Dne 15.10.2010 13:57, Petr Rockai napsal(a):
> Zdenek Kabelac <zkabelac@redhat.com> writes:
>
>>> + if (policy_threshold >= 100)
>>> + return 1; /* nothing to do */
>>
>> For some really large sizes - even 1% could be a huge amount of disk space -
>> so maybe some users would like to see floating number support here?
>
> I'd open a separate bug for that, if you really think so. I tend to
> disagree. (Btw. there's no single float config option in LVM today --
> even though there is theoretical support for that, it's probably not
> tested at all.)
>
Yes - we do not currently use floats in lvm.conf. Another version could be, to
allow setting also in some absolute sizes - i.e.
snapshot_autoextend_free = 100MB
snapshot_autoextend_size = 200MB
Ok - I've tested the patch - and it seems to be working.
So ACK from my side.
What I see as a problem for the future is how to resolve settings per each
snapshot as current 'global' version - one setting for all snapshots is IMHO
quite limiting.
Zdenek
next prev parent reply other threads:[~2010-10-15 12:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-05 13:51 [PATCH] automatic snapshot extension with dmeventd (BZ 427298) Petr Rockai
2010-10-05 17:44 ` Petr Rockai
2010-10-07 13:10 ` [PATCH] let dmeventd unmount invalid snapshots (BZ 189462) Petr Rockai
2010-10-07 19:23 ` Alasdair G Kergon
2010-10-20 22:50 ` Petr Rockai
2010-10-29 11:49 ` Petr Rockai
2010-10-29 12:44 ` Petr Rockai
2010-10-29 13:34 ` Zdenek Kabelac
2010-10-14 9:51 ` [PATCH] automatic snapshot extension with dmeventd (BZ 427298) Zdenek Kabelac
2010-10-15 11:57 ` Petr Rockai
2010-10-15 12:55 ` Zdenek Kabelac [this message]
2010-10-15 14:15 ` Alasdair G Kergon
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=4CB84F49.9020602@redhat.com \
--to=zkabelac@redhat.com \
--cc=lvm-devel@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.