Interesting. I think this may not be a bad idea. Thanks for the info.

On Monday, March 3, 2014, Jean-Tiare LE BIGOT <[email protected]>
wrote:

> To get consistent RBD live snapshots, you may want to first freeze the
> guest filesystem (ext4, btrfs, xfs) with a tool like [fsfreeze]. It will
> basically flush the FS state to disk and blocking any future write access
> while maintaining Read accesses.
>
> [fsfreeze] http://manpages.courier-mta.org/htmlman8/fsfreeze.8.html
>
> On 02/28/2014 11:27 PM, Gregory Farnum wrote:
>
>> RBD itself will behave fine with whenever you take the snapshot. The
>> thing to worry about is that it's a snapshot at the block device
>> layer, not the filesystem layer, so if you don't quiesce IO and sync
>> to disk the filesystem might not be entirely happy with you for the
>> same reasons that it won't be happy if you pull the power plug on it.
>> -Greg
>> Software Engineer #42 @ http://inktank.com | http://ceph.com
>>
>>
>> On Fri, Feb 28, 2014 at 2:12 PM, Greg Poirier <[email protected]>
>> wrote:
>>
>>> According to the documentation at
>>> https://ceph.com/docs/master/rbd/rbd-snapshot/ -- snapshots require
>>> that all
>>> I/O to a block device be stopped prior to making the snapshot. Is there
>>> any
>>> plan to allow for online snapshotting so that we could do incremental
>>> snapshots of running VMs on a regular basis.
>>>
>>> _______________________________________________
>>> ceph-users mailing list
>>> [email protected]
>>> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
>>>
>>>  _______________________________________________
>> ceph-users mailing list
>> [email protected]
>> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
>>
>>
> --
> Jean-Tiare, shared-hosting team
> _______________________________________________
> ceph-users mailing list
> [email protected]
> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
>
_______________________________________________
ceph-users mailing list
[email protected]
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com

Reply via email to