xfs
[Top] [All Lists]

Re: LVM snapshot and log record CRC mismatch

To: Emmanuel Florac <eflorac@xxxxxxxxxxxxxx>
Subject: Re: LVM snapshot and log record CRC mismatch
From: Gionatan Danti <g.danti@xxxxxxxxxx>
Date: Thu, 26 May 2016 13:17:04 +0200
Cc: Dave Chinner <david@xxxxxxxxxxxxx>, xfs@xxxxxxxxxxx, Gionatan Danti <g.danti@xxxxxxxxxx>
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <20160526122315.4112f713@xxxxxxxxxxxxxxxxxxxx>
Organization: Assyoma s.r.l.
References: <ab81e19cd6fce41f9d63cdd3695c80f7@xxxxxxxxxx> <20160524221205.GM21200@dastard> <57455645.5040608@xxxxxxxxxx> <20160526122315.4112f713@xxxxxxxxxxxxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0
On 26/05/2016 12:23, Emmanuel Florac wrote:
Le Wed, 25 May 2016 09:37:41 +0200
Gionatan Danti <g.danti@xxxxxxxxxx> Ãcrivait:

The snapshot is accomplished using the following commands:

lvcreate -s hypervisor/KVM_Storage --name Backup_SNAP
lvchange -ay -K hypervisor/Backup_SNAP
mount -o nouuid /dev/hypervisor/Backup_SNAP /mnt/lvm/


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?

--
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it
email: g.danti@xxxxxxxxxx - info@xxxxxxxxxx
GPG public key ID: FF5F32A8

<Prev in Thread] Current Thread [Next in Thread>