From: Kyle Hayes <khayes@quicknet.net>
To: linux-lvm@sistina.com
Subject: [linux-lvm] snapshot questions
Date: Fri Nov 2 10:42:03 2001 [thread overview]
Message-ID: <01110208435117.08803@khayes-lin> (raw)
We are considering using LVM to do database snapshots for backups.
I have some questions that the HOWTO's etc. do not seem to answer.
My largest concerns are that we will end up with a read-only corrupt
filesystem. This seems to be a problem reported in the mailing lists.
1) how does the snapshot actually work? My understanding is that the
creation of a snapshot partition sets up a new LV on the same VG as
the "source" partition. This new partition is then used for writes to
the "source" partition. When the snapshot LV is removed, do I get
a disk IO hit as these changes are copied back to the "source" partition?
Or, does it work more like Veritas where the changed data go to the
"source" and the original values are copied to the snapshot partition?
The Veritas method is nice because dropping the snapshot partition
does not require any data copying.
2) are there any people using LVM for database snapshots? The
Whitepaper from SuSE has examples for Oracle and the HOWTO's
talk about it, but is it used in production? If so, what issues have you
found?
3) what is the overall stability of snapshot functions? I have been following
the pvmove thread with some alarm as I thought that LVM functionality was
stable at this point. Is there a place that I can see what functionality is
considered stable and what isn't? The mailing list archives do not paint a rosy
picture of snapshot functionality.
4) It seems that most of the LVM work is going into 2.4. We have not been
particularly pleased with the stability of 2.4 in general and would like to stay
with 2.2 for a while. How does the stability of LVM on 2.2 compare to 2.4?
5) I have seen references to the VFS lock patch in the mailing list. Is this
actually supported by any filesystems yet? Is it in the kernel proper?
Thanks.
Best,
Kyle
--
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
MicroTelco Services saves money on every Fax:
- Fax to email (FREE)
- Fax to PSTN based Fax (Up to 95% Savings)
- Fax Broadcasting: Send 100s of faxes to fax machines
and email addresses in the time it takes to send just one!
===========================================================
So send a fax today and let us know what you think!
For more info. visit: www.internetfaxjack.com
===========================================================
next reply other threads:[~2001-11-02 10:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-02 10:42 Kyle Hayes [this message]
2001-11-02 11:28 ` [linux-lvm] snapshot questions Andreas Dilger
2001-11-02 12:51 ` Jesus Manuel NAVARRO LOPEZ
-- strict thread matches above, loose matches on Subject: below --
2001-11-02 13:16 Kenny Gorman
2001-11-05 3:27 ` Jesus Manuel NAVARRO LOPEZ
[not found] <D880FFC9CFDBA84FA13E9B166D06A123B647FB@daedalus.kenamea.co m>
2001-11-02 13:59 ` Brent Harding
2001-11-02 15:40 ` Kyle Hayes
2001-11-02 16:39 ` Andreas Dilger
2001-11-02 18:20 ` Kyle Hayes
2001-11-05 4:38 ` Jesus Manuel NAVARRO LOPEZ
2001-11-05 10:50 ` Kyle Hayes
2001-11-05 14:21 ` Andreas Dilger
2001-11-05 4:15 ` Jesus Manuel NAVARRO LOPEZ
2001-11-02 15:58 Kenny Gorman
2001-11-02 17:04 ` Kyle Hayes
2001-11-02 17:49 Kenny Gorman
2001-11-05 10:31 ` Jesus Manuel NAVARRO LOPEZ
2007-05-06 5:32 [linux-lvm] Snapshot questions Ed Martin
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=01110208435117.08803@khayes-lin \
--to=khayes@quicknet.net \
--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).