From: "Stuart D. Gathman" <stuart@bmsi.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] What is holding back clustered snapshotting?
Date: Tue, 5 Jan 2010 15:17:58 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.64.1001051515490.9847@bmsred.bmsi.com> (raw)
In-Reply-To: <20100105200125.GA24123@esri.com>
On Tue, 5 Jan 2010, Ray Van Dolson wrote:
> > Setting up the shapshot is just a matter of locking and coordination.
> > However, writes to the origin or snapshot (may) require allocating a
> > cluster, copying the origin data, then writing the origin. All of
> > this coordinated with all the machines using the VG. Apart from some
> > cleven invention, this requires global locking on many writes. This
> > is just too inefficient.
>
> Writeable snapshots I guess would be a challenge. But even read only
> snapshots would be great as it would theoretically make backing up
> large, clustered filesystems simpler.
Even read-only snapshots have to handle writes to the origin. And
anytime any machine writes a new cluster to the origin, all machines need their
cluster maps updated so that reads don't pick up the wrong cluster.
--
Stuart D. Gathman <stuart@bmsi.com>
Business Management Systems Inc. Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flammis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.
next prev parent reply other threads:[~2010-01-05 20:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-05 19:11 [linux-lvm] What is holding back clustered snapshotting? Madison Kelly
2010-01-05 19:30 ` Stuart D. Gathman
2010-01-05 20:01 ` Ray Van Dolson
2010-01-05 20:17 ` Stuart D. Gathman [this message]
2010-01-05 19:35 ` Ray Van Dolson
2010-01-05 22:52 ` Jonathan Brassow
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=Pine.LNX.4.64.1001051515490.9847@bmsred.bmsi.com \
--to=stuart@bmsi.com \
--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 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).