public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Emmanuel Florac <eflorac@intellique.com>
To: Gionatan Danti <g.danti@assyoma.it>
Cc: xfs@oss.sgi.com
Subject: Re: LVM snapshot and log record CRC mismatch
Date: Thu, 26 May 2016 13:34:22 +0200	[thread overview]
Message-ID: <20160526133422.32f65920@harpe.intellique.com> (raw)
In-Reply-To: <5746DB30.5040006@assyoma.it>

Le Thu, 26 May 2016 13:17:04 +0200
Gionatan Danti <g.danti@assyoma.it> écrivait:

> >
> > You need to use xfs_freeze to make the filesystem coherent before
> > snapshot:
> >
> > xfs_freeze /dev/hypervisor/KVM_Storage
> > lvcreate -s hypervisor/KVM_Storage --name Backup_SNAP
> > xfs_freeze -u /dev/hypervisor/KVM_Storage
> > lvchange -ay -K hypervisor/Backup_SNAP
> >  
> 
> It was my understanding that filesystem freezing was automatically 
> managed by LVM, and integrated into VFS long ago.
> 
> I am missing something?

Yes, I thought that too, however it doesn't seem to be working in your
case, and freezing twice can't do any harm anyway :)

-- 
------------------------------------------------------------------------
Emmanuel Florac     |   Direction technique
                    |   Intellique
                    |	<eflorac@intellique.com>
                    |   +33 1 78 94 84 02
------------------------------------------------------------------------

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2016-05-26 11:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-24 12:58 LVM snapshot and log record CRC mismatch Gionatan Danti
2016-05-24 22:12 ` Dave Chinner
2016-05-25  7:37   ` Gionatan Danti
2016-05-26 10:23     ` Emmanuel Florac
2016-05-26 11:17       ` Gionatan Danti
2016-05-26 11:34         ` Emmanuel Florac [this message]
2016-05-30  6:33           ` Gionatan Danti
2016-05-26 17:39         ` Eric Sandeen

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=20160526133422.32f65920@harpe.intellique.com \
    --to=eflorac@intellique.com \
    --cc=g.danti@assyoma.it \
    --cc=xfs@oss.sgi.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