From: Peter Lieven <pl@kamp.de>
To: Christian Theune <ct@flyingcircus.io>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel@nongnu.org, qemu-stable@nongnu.org,
mdroth@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH] qga: ignore EBUSY when freezing a filesystem
Date: Fri, 3 Feb 2017 09:36:54 +0100 [thread overview]
Message-ID: <f3aa837e-70de-91e9-c82f-6a7dd2907fb0@kamp.de> (raw)
In-Reply-To: <2BB6EFE6-C476-4A48-AFC9-52B9B9F8433F@flyingcircus.io>
Am 03.02.2017 um 09:22 schrieb Christian Theune:
> Hi,
>
>> On 3 Feb 2017, at 09:20, Peter Lieven <pl@kamp.de <mailto:pl@kamp.de>> wrote:
>>
>> If you try to THAW an unfrozen FS you get EINVAL.
>>
>> The current code thaws until an error is returned.
>>
>>
>> So it should work as is.
>>
>>
>> If you feel uncomfortable with the EBUSY approach. The other idea would
>>
>> be to track all devices which have been successfully frozen and skip consecutive
>>
>> tries to freeze them.
>
> Which will be subject to race conditions as other processes may call freeze/thaw on any device. Those are completely out of our control.
That will always be out of control. If we freeze the FS and another process thaws it, we snapshot an unfrozen fs and believe it is frozen.
I think the EBUSY approach is fine. If I look at the documentation of the thaw in the code it seems that the behaviour of the linux kernel changed. It seems
that it was possible to call FIFREEZE multiple times on an FS and this required multiple FITHAWs to unfreeze it.
Peter
next prev parent reply other threads:[~2017-02-03 8:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-31 15:36 [Qemu-devel] [PATCH] qga: ignore EBUSY when freezing a filesystem Peter Lieven
2017-02-02 21:41 ` Paolo Bonzini
2017-02-03 8:18 ` Christian Theune
2017-02-03 8:20 ` Peter Lieven
2017-02-03 8:22 ` Christian Theune
2017-02-03 8:36 ` Peter Lieven [this message]
2017-02-03 18:31 ` Paolo Bonzini
2017-02-17 13:02 ` Peter Lieven
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=f3aa837e-70de-91e9-c82f-6a7dd2907fb0@kamp.de \
--to=pl@kamp.de \
--cc=ct@flyingcircus.io \
--cc=mdroth@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).