From: Ming Zhang <mingz@ele.uri.edu>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] relocate on write for snapshot
Date: Fri, 19 Nov 2004 12:56:59 -0500 [thread overview]
Message-ID: <1100887019.2984.37.camel@localhost.localdomain> (raw)
In-Reply-To: <20041119171933.GA1417@trip.muon.local>
On Fri, 2004-11-19 at 12:19, Nils Juergens wrote:
> On Fri, 19.11.04, Ming Zhang <mingz@ele.uri.edu> wrote:
>
> > instead of copy old one to snapshot, overwrite old one with new one, 2
> > writes and 1 reads. it is possible that write new data to a usused
> > location directly.
>
> Since you have to delete the snapshot (and I don't think they live very long
> on most systems) you don't gain anything (because you have copy the changes
> back from the snapshot), but you make the cases of more than one snapshot
> and (possibly) read-write snapshots a lot harder, maybe not in CPU or IO,
> but certainly in code complexity, which is a thing you never do to gain
> a bit of performance.
>
on some systems that mainly for disaster recovery purpose, there will be
a lot of snapshots available for a lv. this can make the recovery much
easier.
> > i know later remove a snaphot will be a little trouble, but there must
> > be some way to get around it.
>
> Yes, you have to do the work you saved a couple of minutes earlier :)
>
a dedicated snapshot merge process can solve this.
> just my EUR 0.02,
thanks. discussion always can make thing clarified.
> Nils
prev parent reply other threads:[~2004-11-19 17:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-19 16:39 [linux-lvm] relocate on write for snapshot Ming Zhang
2004-11-19 17:05 ` Clint Byrum
2004-11-19 17:19 ` Nils Juergens
2004-11-19 17:56 ` Ming Zhang [this message]
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=1100887019.2984.37.camel@localhost.localdomain \
--to=mingz@ele.uri.edu \
--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