From: "J. Javier Maestro" <jjmaestro@ieee.org>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] LVM snapshots overflow due to initial "overhead"?
Date: Sun, 30 Nov 2008 19:19:42 +0100 [thread overview]
Message-ID: <20081130181942.GA11789@2jotas.com> (raw)
In-Reply-To: <20081130163733.GH13235@agk.fab.redhat.com>
On Nov Sun 30 2008 16:37, Alasdair G Kergon wrote:
> On Sun, Nov 30, 2008 at 05:06:48PM +0100, J. Javier Maestro wrote:
> > http://www.tldp.org/HOWTO/LVM-HOWTO/snapshots_backup.html
> > **If the snapshot size equals the origin size, it will never overflow.**
>
> That's simply inaccurate and should be corrected.
I agree with you, but it would be much more interesting to see why it is
incorrect. I mean, as I mentioned in my email, why are those chunks used
upfront? By doing that, the whole nice idea of a snapshot breaks completely.
It would be much, much better to account for that and move those chunks out
of the snapshot.
--
.''`.
: :' : J. Javier Maestro
`. `'` <jjmaestro@ieee.org>
`-
prev parent reply other threads:[~2008-11-30 18:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-30 16:06 [linux-lvm] LVM snapshots overflow due to initial "overhead"? J. Javier Maestro
2008-11-30 16:37 ` Alasdair G Kergon
2008-11-30 18:19 ` J. Javier Maestro [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=20081130181942.GA11789@2jotas.com \
--to=jjmaestro@ieee.org \
--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 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.