From: Bryn M. Reeves <bmr@redhat.com>
To: lvm-devel@redhat.com
Subject: lvcreate -s - why specifying size for snapshot ?
Date: Fri, 20 Mar 2009 16:10:07 +0000 [thread overview]
Message-ID: <49C3BFDF.1090900@redhat.com> (raw)
In-Reply-To: <37d33d830903200847w45cee0b1xc973299627dead2f@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Sandeep K Sinha wrote:
> Hi all,
> Disk
> After hunting for relevant documents and failing to find one.
> I would like to know if its not true that the size of the snapshot
> should be equal to the original volume?
> If so, then why do we accept size for a snapshot?
>
> Or Am I missing something somewhere else?
>
The size of the snapshot governs the amount of space set aside for
storing the changes to the origin volume. E.g. if you made a snapshot
and then completely overwrote the origin the snapshot would have to be
at least as big as the origin volume to hold the changes.
You need to dimension a snapshot according to the expected level of
change. So for example a short-lived snapshot of a read-mostly volume,
e.g. /usr, would need less space than a long-lived snapshot of a volume
that sees a greater number of writes such as /home.
Snapshots can be grown after they have been created but you need to make
sure they don't fill up. If this happens the snapshot will become
invalid (since it can no longer faithfully track changes on the origin
volume).
Regards,
Bryn.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iEYEARECAAYFAknDv98ACgkQ6YSQoMYUY95s2wCfQwnpoTiHL+8xhuifVX4YGoJz
TW0Ani+qq0uDmwgAKbHAVUiwEO6MLGtN
=D2F3
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2009-03-20 16:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-20 15:47 lvcreate -s - why specifying size for snapshot ? Sandeep K Sinha
2009-03-20 16:10 ` Bryn M. Reeves [this message]
2009-03-20 16:18 ` Jonathan Brassow
2009-03-20 16:40 ` Sandeep K Sinha
2009-03-20 17:07 ` Bryn M. Reeves
2009-03-20 17:33 ` Bryn M. Reeves
2009-03-20 17:38 ` Sandeep K Sinha
2009-03-20 17:37 ` Bryn M. Reeves
2009-03-20 17:12 ` Jonathan Brassow
2009-03-20 16:15 ` Dave Wysochanski
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=49C3BFDF.1090900@redhat.com \
--to=bmr@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.