| To: | Gionatan Danti <g.danti@xxxxxxxxxx> |
|---|---|
| Subject: | Re: LVM snapshot and log record CRC mismatch |
| From: | Emmanuel Florac <eflorac@xxxxxxxxxxxxxx> |
| Date: | Thu, 26 May 2016 13:34:22 +0200 |
| Cc: | Dave Chinner <david@xxxxxxxxxxxxx>, xfs@xxxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <5746DB30.5040006@xxxxxxxxxx> |
| Organization: | Intellique |
| References: | <ab81e19cd6fce41f9d63cdd3695c80f7@xxxxxxxxxx> <20160524221205.GM21200@dastard> <57455645.5040608@xxxxxxxxxx> <20160526122315.4112f713@xxxxxxxxxxxxxxxxxxxx> <5746DB30.5040006@xxxxxxxxxx> |
Le Thu, 26 May 2016 13:17:04 +0200
Gionatan Danti <g.danti@xxxxxxxxxx> Ã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@xxxxxxxxxxxxxx>
| +33 1 78 94 84 02
------------------------------------------------------------------------
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: LVM snapshot and log record CRC mismatch, Gionatan Danti |
|---|---|
| Next by Date: | [PATCH] xfs: fail ->bmap for reflink inodes, Christoph Hellwig |
| Previous by Thread: | Re: LVM snapshot and log record CRC mismatch, Gionatan Danti |
| Next by Thread: | Re: LVM snapshot and log record CRC mismatch, Gionatan Danti |
| Indexes: | [Date] [Thread] [Top] [All Lists] |