| To: | xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Re: LVM snapshot and log record CRC mismatch |
| From: | Eric Sandeen <sandeen@xxxxxxxxxxx> |
| Date: | Thu, 26 May 2016 12:39:32 -0500 |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <5746DB30.5040006@xxxxxxxxxx> |
| References: | <ab81e19cd6fce41f9d63cdd3695c80f7@xxxxxxxxxx> <20160524221205.GM21200@dastard> <57455645.5040608@xxxxxxxxxx> <20160526122315.4112f713@xxxxxxxxxxxxxxxxxxxx> <5746DB30.5040006@xxxxxxxxxx> |
| User-agent: | Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 |
On 5/26/16 6:17 AM, Gionatan Danti wrote: > 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? Nope, you are correct. lvm snapshots handle fs quiesce. -Eric |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH 3/5] fuse: Propagate dentry down to inode_change_ok(), Miklos Szeredi |
|---|---|
| Next by Date: | Re: [PATCH 09/15] fs: iomap based fiemap implementation, Bob Peterson |
| Previous by Thread: | Re: LVM snapshot and log record CRC mismatch, Gionatan Danti |
| Next by Thread: | [PATCH] xfs: fix broken multi-fsb buffer logging, Brian Foster |
| Indexes: | [Date] [Thread] [Top] [All Lists] |