linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Alexis Pellicier <alexis.pellicier@nds.k12.tr>
To: Jacek Konieczny <jajcus@jajcus.net>
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] snapshot an lvm disk containing ext4 partitions
Date: Sat, 25 May 2013 07:07:36 +0300	[thread overview]
Message-ID: <CACfWNia8DjxEQT3jr1v93r-rV1WP_XCPRZaY4jQqawB03unOaQ@mail.gmail.com> (raw)
In-Reply-To: <20130524204516.35a24798@lolek.nigdzie>

[-- Attachment #1: Type: text/plain, Size: 943 bytes --]

And theire is no risk to lose data?
Le 24 mai 2013 21:45, "Jacek Konieczny" <jajcus@jajcus.net> a écrit :

> On Thu, 23 May 2013 09:31:23 +0300
> Alexis <alexis.pellicier@nds.k12.tr> wrote:
> > Hello,
> >
> > I was use to snapshot an LVM volume containing ext4 partitions for
> > backup purpose. This is a disk for Xen DomU paravirtualized linux box.
> >
> > With lvm-2.02.98 and kernel  3.4.11 from opensuse 12.2 the ext4
> > partitions inside  the snapshot were clean.
> >
> > Now I've upgraded to opensuse 12.3 (kernel 3.7.10 lvm-2.02.98)
> >
> > Is lvm supposed to keep my inside ext4 partitions clean when
> > snapshotting my volume? If not is theire any way of doing this?
>
> Use read-write snapshots instead of read-only ones.
>
> The first time you mount the snapshot (read-only mount is enough)
> the journal will get replayed and the stored file-system will become
> clean.
>
> Greets,
>         Jacek
>

[-- Attachment #2: Type: text/html, Size: 1322 bytes --]

      reply	other threads:[~2013-05-25  4:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-23  6:31 [linux-lvm] snapshot an lvm disk containing ext4 partitions Alexis
2013-05-23  8:34 ` Zdenek Kabelac
2013-05-24 18:45 ` Jacek Konieczny
2013-05-25  4:07   ` Alexis Pellicier [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=CACfWNia8DjxEQT3jr1v93r-rV1WP_XCPRZaY4jQqawB03unOaQ@mail.gmail.com \
    --to=alexis.pellicier@nds.k12.tr \
    --cc=jajcus@jajcus.net \
    --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;
as well as URLs for NNTP newsgroup(s).