Linux Device Mapper development
 help / color / mirror / Atom feed
From: Mikulas Patocka <mpatocka@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: LVM Snapshot Feature
Date: Mon, 4 Aug 2008 09:15:11 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0808040912350.28033@devserv.devel.redhat.com> (raw)
In-Reply-To: <1746B17C-CC23-40D7-A993-FC32CAA5BF24@gmail.com>

On Fri, 1 Aug 2008, Adam Hamsik wrote:

> On Aug,Friday 1 2008, at 9:35 AM, Bombardier, Pascal wrote:
> 
> > Hi,
> > 
> > In your opinion, does it make sense to be able to create non-persistent
> > snapshots ?
> > In the case of a filesystem backup, a non-persistent snapshot would be a
> > snapshot that we agree to lose in case of failure or reboot. If anything
> > happens, a server administrator would have to recreate a new snapshot
> > and then restart the backup.
> > In this case, I think metadata could be stored in memory instead of on
> > disk, which should improve LVM snapshot performance.
> > 
> > Is this theory wrong, and is this something which can be implemented
> > easily in the current LVM code ?
> > 
> 
> AFAIK non-persistent snapshots are already implemented see
> DM_PERSISTENT_DEV_FLAG ? I haven't look at linux kernel code how is
> it done but when I solve my lvcreate -s bug on NetBSD non-persistent
> snapshots are next :).
> 
> Regards
> 
> Adam.

Yes. They are implemented in device mapper in kernel --- but no userspace 
lvm tool can use them. You can only create them using dmsetup.

Mikulas

  reply	other threads:[~2008-08-04 13:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-01  7:35 LVM Snapshot Feature Bombardier, Pascal
2008-08-01 14:15 ` Luke S Crawford
2008-08-01 15:52 ` Adam Hamsik
2008-08-04 13:15   ` Mikulas Patocka [this message]
2008-08-06  6:08     ` haad

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.0808040912350.28033@devserv.devel.redhat.com \
    --to=mpatocka@redhat.com \
    --cc=dm-devel@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