From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:43649) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xr3e5-0003ka-U6 for qemu-devel@nongnu.org; Wed, 19 Nov 2014 06:42:06 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Xr3e1-0008Dt-HP for qemu-devel@nongnu.org; Wed, 19 Nov 2014 06:42:01 -0500 Received: from mx1.redhat.com ([209.132.183.28]:35206) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xr3e1-0008Dl-4q for qemu-devel@nongnu.org; Wed, 19 Nov 2014 06:41:57 -0500 Message-ID: <546C8200.4070800@redhat.com> Date: Wed, 19 Nov 2014 12:41:52 +0100 From: Paolo Bonzini MIME-Version: 1.0 References: <2A6E6B95B6E5C146ACE8440760E58185BDC31A5E@EXCHANGESERVER.schefczyk.local> <546C782E.9070803@redhat.com> <2A6E6B95B6E5C146ACE8440760E58185BDC31C30@EXCHANGESERVER.schefczyk.local> In-Reply-To: <2A6E6B95B6E5C146ACE8440760E58185BDC31C30@EXCHANGESERVER.schefczyk.local> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Subject: [Qemu-devel] "File too large" error from "qemu-img snapshot" (was Re: AW: Bug Repoting Directions Request) List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Prof. Dr. Michael Schefczyk" , qemu-devel On 19/11/2014 12:39, Prof. Dr. Michael Schefczyk wrote: > Dear Paolo, >=20 > thank you very much for your prompt reply. Hi, please keep the replies on the mailing list. I've added the qemu-devel mailing list, where more people should be able to see the message and hopefully reply with something helpful. Also, how do you do the backups? Paolo > For example, I have a guest named "gatewayb72.img" where the backup fai= led. If I thereafter try to create or delete a snapshot, the following re= ply occurs on the command line: >=20 >=20 > [root@linuxhost2 kvm02]# qemu-img snapshot -d gatewayb72 /kvm02/gateway= b72.img > qemu-img: Could not open '/kvm02/gatewayb72.img': Could not read snapsh= ots: File too large >=20 >=20 > If I want to reboot that machine, I get the following error: >=20 >=20 > Fehler beim Starten der Domain: Interner Fehler: Prozess wurde w=E4hren= d der Verbindungsaufnahme zum Monitor beendet : qemu-kvm: -drive file=3D/= kvm02/gatewayb72.img,if=3Dnone,id=3Ddrive-virtio-disk0,format=3Dqcow2,cac= he=3Dnone: could not open disk image /kvm02/gatewayb72.img: Could not rea= d snapshots: File too large >=20 >=20 > Traceback (most recent call last): > File "/usr/share/virt-manager/virtManager/asyncjob.py", line 100, in = cb_wrapper > callback(asyncjob, *args, **kwargs) > File "/usr/share/virt-manager/virtManager/asyncjob.py", line 122, in = tmpcb > callback(*args, **kwargs) > File "/usr/share/virt-manager/virtManager/domain.py", line 1220, in s= tartup > self._backend.create() > File "/usr/lib64/python2.7/site-packages/libvirt.py", line 698, in cr= eate > if ret =3D=3D -1: raise libvirtError ('virDomainCreate() failed', d= om=3Dself) > libvirtError: Interner Fehler: Prozess wurde w=E4hrend der Verbindungsa= ufnahme zum Monitor beendet : qemu-kvm: -drive file=3D/kvm02/gatewayb72.i= mg,if=3Dnone,id=3Ddrive-virtio-disk0,format=3Dqcow2,cache=3Dnone: could n= ot open disk image /kvm02/gatewayb72.img: Could not read snapshots: File = too large >=20 >=20 > Based on the facts I can see, the file is not too large. When reading t= he first error, the file size was 13.8 GB, while the limit is 14.5 GB. Th= e same does also happen with files which are only, for example 6 GB big, = while their limit is also 14.5 GB. Therefore, I think that the "file too = large" really stands for something else. >=20 > Can I provide any additional information? >=20 > Regards, >=20 > Michael > ___________________________________________________________=20 > Technische Universit=E4t Dresden > Fakult=E4t Wirtschaftswissenschaften > Lehrstuhl f=FCr Entrepreneurship und Innovation > Prof. Dr. Michael Schefczyk > D-01062 Dresden=20 > =20 > Fon: +49-3 51-4 63-3 68 81=20 > Fax: +49-3 51-4 63-3 68 83=20 > www.gruenderlehrstuhl.de >> Since some months ago, I am facing the problem, that backups fail=20 >> unpredictably. A failed backup does not generate a backup file and=20 >> thereafter, snapshots can no longer be created or deleted and the=20 >> guest cannot be started anymore. The resulting error message is "File=20 >> too large". >=20 > Who is reporting the "File too large" error? Can you please include th= e error in full detail? >=20 > Paolo >=20