From: Joe Thornber <thornber@btconnect.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] rw-snapshot as an addition for lvm
Date: Mon, 30 Jul 2001 11:46:40 +0100 [thread overview]
Message-ID: <20010730114640.A739@btconnect.com> (raw)
In-Reply-To: <20010730112818.F760@jadzia.josv.com>; from josv@osp.nl on Mon, Jul 30, 2001 at 11:28:18AM +0200
On Mon, Jul 30, 2001 at 11:28:18AM +0200, Jos Visser wrote:
> The question I would have is whether rw-snapshots (or, snapshots in
> general), should be implemented in LVM or as a separate driver/layer. In
> that case, a snapshot could be taken of any block device, not only of a
> logical volume.
Yes, I've already raised this issue... and written a new standalone
driver, which will go into experimental soon :) There's a similar
argument that multi-pathing is standalone.
>
> Another interesting feature that I might add that would be handy here is
> the "dynamic LV". This would be a LV that can extend dynamically if so
> requested. The advantage of this would be that you could use the dynamic
> LV as the buffer space of a snapshot. If the snapshot requires more
> space, the LV could extend dynamically to allow for this....
There are facilities for monitoring snapshot usage. You could easily
write a script that extends the lv when it hits, say, 90 % full.
- Joe
>
> ++Jos
>
> And thus it came to pass that Joe Thornber wrote:
> (on Mon, Jul 30, 2001 at 10:57:26AM +0100 to be exact)
>
> > On Sat, Jul 28, 2001 at 06:27:41PM +0200, Anders Henke wrote:
> > > I think it's also quite interesting to have a rw-snapshot in which changes
> > > of both real and snapshot are being written to a smaller bufferspace on disk:
> > > the snapshot always represents the state of the LV when taking the snapshot,
> > > but permits changes on 'its copy'.
> >
> > See other thread in the last few days on rw snapshots; Yes, it's an
> > execellent idea.
> >
> > - Joe
> > _______________________________________________
> > linux-lvm mailing list
> > linux-lvm@sistina.com
> > http://lists.sistina.com/mailman/listinfo/linux-lvm
> > read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
>
> --
> Im verzeihen des Unverzeihlichen ist der Mensch der gottlichen Liebe am ndchtsten.
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
prev parent reply other threads:[~2001-07-30 10:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-28 16:27 [linux-lvm] rw-snapshot as an addition for lvm Anders Henke
2001-07-30 9:57 ` Joe Thornber
2001-07-30 9:28 ` Jos Visser
2001-07-30 10:46 ` Joe Thornber [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=20010730114640.A739@btconnect.com \
--to=thornber@btconnect.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.