From: Ming Zhang <mingz@ele.uri.edu>
To: linux-lvm@redhat.com
Subject: [linux-lvm] relocate on write for snapshot
Date: Fri, 19 Nov 2004 11:39:07 -0500 [thread overview]
Message-ID: <1100882347.2984.32.camel@localhost.localdomain> (raw)
Hi, I wonder if there are any thought about a relocate on write policy
for snapshot instead of copy on write policy used now?
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.
i know later remove a snaphot will be a little trouble, but there must
be some way to get around it.
just a rough thought, any comment?
ming
next reply other threads:[~2004-11-19 16:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-19 16:39 Ming Zhang [this message]
2004-11-19 17:05 ` [linux-lvm] relocate on write for snapshot Clint Byrum
2004-11-19 17:19 ` Nils Juergens
2004-11-19 17: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=1100882347.2984.32.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