From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:58009) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e0ToE-0007n8-Ag for qemu-devel@nongnu.org; Fri, 06 Oct 2017 10:41:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1e0ToB-0002zD-5H for qemu-devel@nongnu.org; Fri, 06 Oct 2017 10:41:02 -0400 Received: from indium.canonical.com ([91.189.90.7]:47326) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1e0ToA-0002xu-Vf for qemu-devel@nongnu.org; Fri, 06 Oct 2017 10:40:59 -0400 Received: from loganberry.canonical.com ([91.189.90.37]) by indium.canonical.com with esmtp (Exim 4.86_2 #2 (Debian)) id 1e0To9-0008Q2-5H for ; Fri, 06 Oct 2017 14:40:57 +0000 Received: from loganberry.canonical.com (localhost [127.0.0.1]) by loganberry.canonical.com (Postfix) with ESMTP id 1B7302E80CC for ; Fri, 6 Oct 2017 14:40:57 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Date: Fri, 06 Oct 2017 14:30:14 -0000 From: Daniel Berrange <1721788@bugs.launchpad.net> Reply-To: Bug 1721788 <1721788@bugs.launchpad.net> Sender: bounces@canonical.com References: <150729895903.22243.5921581973131047310.malonedeb@gac.canonical.com> Message-Id: <150730021408.8281.13104272267482208285.malone@wampee.canonical.com> Errors-To: bounces@canonical.com Subject: [Qemu-devel] [Bug 1721788] Re: Failed to get shared "write" lock with 'qemu-img info' List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org I've just noticed, however, that '--force-share' appears totally undocumented in both CLI help output and the man page. So that's certainly something that should be fixed -- = You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1721788 Title: Failed to get shared "write" lock with 'qemu-img info' Status in QEMU: New Bug description: When running 'qemu-img info test.qcow2' while test.qcow2 is currently used by a Qemu process, I get the error qemu-img: Could not open 'test.qcow2': Failed to get shared "write" lock. = Why does displaying information about a disk image need a write lock for = the file? Steps to reproduce: qemu-img create -f qcow2 test.qcow2 10M qemu-system-x86_64 -nographic -drive file=3Dtest.qcow2 qemu-img info test.qcow2 The above was tested with Qemu version 2.10.0 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1721788/+subscriptions