From: "armani" <armani@codevel.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Newbie to snapshot
Date: Sun May 18 09:58:01 2003 [thread overview]
Message-ID: <002001c31d4d$eebf5630$6c7745cb@codevel> (raw)
In-Reply-To: 3EC788E9.9020701@adelphia.net
Thanks for toby's explainations!
==
Eventually I create a new snapshot of my LV partition.
But I have another problem with the snapshot of LV.
That is how much snapshot I could create for my LV partition ?
As I know some commercial software could create 254 snapshots for one LV
such as IBM.
So I try to create another snapshot for LV by issuing the following command:
This is my first snapshot for /dev/Vol1/LV1
[root@met root]# lvcreate --size 100M -s -nsnapshot /dev/Vol1/LV1
lvcreate -- WARNING: the snapshot will be automatically disabled once it
gets full
lvcreate -- INFO: using default snapshot chunk size of 64 KB for
"/dev/Vol1/snapshot"
lvcreate -- doing automatic backup of "Vol1"
lvcreate -- logical volume "/dev/Vol1/snapshot" successfully created
I tried to create another snapshot for /dev/Vol1/LV1
[root@met root]# lvcreate --size 100M -s -nsnapshot1 /dev/Vol1/LV1
lvcreate -- WARNING: the snapshot will be automatically disabled once it
gets full
lvcreate -- INFO: using default snapshot chunk size of 64 KB for
"/dev/Vol1/snapshot1"
lvcreate -- doing automatic backup of "Vol1"
lvcreate -- logical volume "/dev/Vol1/snapshot1" successfully created
And how can I estimate the sizes and counts for them ?
Is there any rules or principles to formalize the procedures ?
> A snapshot will only capture what you have in the fs at the moment you
-- snip --
> -toby
-- Armani Liao
next prev parent reply other threads:[~2003-05-18 9:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-18 5:41 [linux-lvm] Newbie to snapshot armani
2003-05-18 8:21 ` Toby
2003-05-18 9:58 ` armani [this message]
2003-05-20 2:36 ` Heinz J . Mauelshagen
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='002001c31d4d$eebf5630$6c7745cb@codevel' \
--to=armani@codevel.com \
--cc=linux-lvm@sistina.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