From: Stefan Majer <stefan@x-cellent.com>
To: linux-lvm@sistina.com
Subject: [linux-lvm] multiple snapshots
Date: Wed Nov 26 06:10:01 2003 [thread overview]
Message-ID: <1069848492.4436.15.camel@dom> (raw)
Hi,
Im currently working on a samba fileserver setup based on LVM2 on top of
kernel 2.4.22.
Our customer now wants to keep several snapshots (one every day) from
the main share for backup purpose. He wants to keep up to two weeks
online, that leads in 14 different snapshots for one source LV.
All of these snapshot LVs should be mountet.
The Source LV is about 1TB in Size, we have about 300Gb for snapshots
free.
Is this possible ?, did anyone else something like this before ?, how
big would the performance impact be ?
If someone can give me some hints,numbers
all would be welcome.
greetings
Stefan Majer
next reply other threads:[~2003-11-26 6:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-26 6:10 Stefan Majer [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-15 11:50 [linux-lvm] multiple snapshots Imre Gergely
2005-08-16 6:37 ` Imre Gergely
2005-08-16 7:17 ` Imre Gergely
2005-08-23 13:33 ` Imre Gergely
2005-08-23 17:13 ` Micha Holzmann
2005-08-24 13:48 ` Imre Gergely
2005-08-24 13:56 ` Ming Zhang
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=1069848492.4436.15.camel@dom \
--to=stefan@x-cellent.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;
as well as URLs for NNTP newsgroup(s).