All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marian Csontos <mcsontos@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>,
	Matthes.Henning.extern@bertelsmann.de
Subject: Re: [linux-lvm] lvextend on snapshotted lv
Date: Wed, 07 May 2014 15:05:08 +0200	[thread overview]
Message-ID: <536A2F84.8040404@redhat.com> (raw)
In-Reply-To: <01D739DB1544554DB374FFC82934E6DC1D332E@GTLBMLXEN0009.bagmail.net>

On 05/07/2014 09:38 AM, Matthes.Henning.extern@bertelsmann.de wrote:
> Hello,
>
>
> why is it not possible to extend a lv, how long a snapshot of it exist.

Hello, I would say a design decision - snapshots were meant mostly for 
short-term usage e.g. while creating a backup copy of a snapshot.

If you need more flexibility have a look at thin snapshots.

Regards,

-- Marian

>
>
> Kind regards
> Mit freundlichen Gr��en
>
> Henning Matthes
>
> perl -00pe0
>
> Unix System Administration / Infrastructure Services / NMS-OSV(extern)
>
> Externe Fachkraft der:
> -------------------------------------------------
> arvato Systems GmbH
> An der Autobahn 200
> 33333 G�tersloh
>
> Phone: +49 5241 80-49591
> E-Mail: matthes.henning.extern@bertelsmann.de<mailto:matthes.henning.extern@bertelsmann.de>
>
>
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> arvato Systems GmbH: Sitz G�tersloh | Amtsgericht G�tersloh HRB 3981
> Gesch�ftsf�hrer: Birger T. Aasland | Beate Bruelheide | Dr. Michael Pesch (Vorsitzender)
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> Diese E-Mail und eventuelle Anlagen k�nnen vertrauliche und/oder rechtlich gesch�tzte Informationen enthalten. Wenn Sie
> nicht der richtige Adressat sind oder diese E-Mail irrt�mlich erhalten haben, informieren Sie bitte sofort den Absender und
> vernichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser E-Mail sind nicht gestattet.
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> This e-mail and any attachments may contain confidential and/or privileged information. If you are not the intended recipient
> (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying,
> disclosure or distribution of the material in this e-mail is forbidden.
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> Bitte denken Sie �ber Ihre Verantwortung gegen�ber der Umwelt nach, bevor Sie diese E-Mail ausdrucken!
>
>
>
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>

      reply	other threads:[~2014-05-07 13:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-07  7:38 [linux-lvm] lvextend on snapshotted lv Matthes.Henning.extern
2014-05-07 13:05 ` Marian Csontos [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=536A2F84.8040404@redhat.com \
    --to=mcsontos@redhat.com \
    --cc=Matthes.Henning.extern@bertelsmann.de \
    --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 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.