Re: [Qemu-block] qcow2 images corruption

2018-02-14 Thread Nicolas Ecarnot
https://framadrop.org/r/Lvvr392QZo#/wOeYUUlHQAtkUw1E+x2YdqTqq21Pbic6OPBIH0TjZE= Le 14/02/2018 à 00:01, John Snow a écrit : On 02/13/2018 04:41 AM, Kevin Wolf wrote: Am 07.02.2018 um 18:06 hat Nicolas Ecarnot geschrieben: TL; DR : qcow2 images keep getting corrupted. Any workaround? Not

Re: [Qemu-block] qcow2 images corruption

2018-02-13 Thread Nicolas Ecarnot
Le 13/02/2018 à 16:26, Nicolas Ecarnot a écrit : >> It would be good if you could make the 'qemu-img check' output available >> somewhere. > I found this : https://github.com/ShijunDeng/qcow2-dump and the transcript (beautiful colors when viewed with "more")

Re: [Qemu-block] qcow2 images corruption

2018-02-13 Thread Nicolas Ecarnot
Le 13/02/2018 à 16:26, Nicolas Ecarnot a écrit : It would be good if you could make the 'qemu-img check' output available somewhere. I found this : https://github.com/ShijunDeng/qcow2-dump and the transcript (beautiful colors when viewed with "more") is attached : -

Re: [Qemu-block] qcow2 images corruption

2018-02-13 Thread Nicolas Ecarnot
Hello Kevin, Le 13/02/2018 à 10:41, Kevin Wolf a écrit : Am 07.02.2018 um 18:06 hat Nicolas Ecarnot geschrieben: TL; DR : qcow2 images keep getting corrupted. Any workaround? Not without knowing the cause. Actually, my main concern is mostly about finding the cause rather than correcting

Re: [Qemu-block] [ovirt-users] qcow2 images corruption

2018-02-12 Thread Nicolas Ecarnot
Hello, As I got no answer here, maybe someone could advise me a better place to find some hints about this qemu qcow2 corruption issue? Thank you -- Nicolas Ecarnot Le 07/02/2018 à 18:06, Nicolas Ecarnot a écrit : Hello, TL; DR : qcow2 images keep getting corrupted. Any workaround? Long

Re: [Qemu-block] [ovirt-users] qcow2 images corruption

2018-02-08 Thread Nicolas Ecarnot
Le 08/02/2018 à 13:59, Yaniv Kaul a écrit : On Feb 7, 2018 7:08 PM, "Nicolas Ecarnot" <mailto:nico...@ecarnot.net>> wrote: Hello, TL; DR : qcow2 images keep getting corrupted. Any workaround? Long version: This discussion has already been launched by

[Qemu-block] [ovirt-users] qcow2 images corruption

2018-02-07 Thread Nicolas Ecarnot
planning to upgrade, but we don't know when. Regards, -- Nicolas ECARNOT ___ Users mailing list us...@ovirt.org http://lists.ovirt.org/mailman/listinfo/users

[Qemu-block] qcow2 images corruption

2018-02-07 Thread Nicolas Ecarnot
planning to upgrade, but we don't know when. Regards, -- Nicolas ECARNOT

Re: [Qemu-block] qemu-img: Check failed: No space left on device

2017-09-26 Thread Nicolas Ecarnot
Le 21/09/2017 à 16:31, Stefan Hajnoczi a écrit : On Tue, Sep 19, 2017 at 12:09:06PM +0200, Nicolas Ecarnot wrote: Hello, First post here, so maybe I should introduce myself : - I'm a sysadmin for decades and currently managing 4 oVirt clusters, made out of tens of hypervisors, all are C

[Qemu-block] qemu-img: Check failed: No space left on device

2017-09-19 Thread Nicolas Ecarnot
.32-1.el7.noarch - # qemu-img info /the/relevant/logical/volume/path file format: qcow2 virtual size: 30G (32212254720 bytes) disk size: 0 cluster_size: 65536 Format specific information: compat: 0.10 refcount bits: 16 Is there a hope I'll be able to repair t

[Qemu-block] qemu-img: Check failed: No space left on device

2017-09-19 Thread Nicolas Ecarnot
.32-1.el7.noarch - # qemu-img info /the/relevant/logical/volume/path file format: qcow2 virtual size: 30G (32212254720 bytes) disk size: 0 cluster_size: 65536 Format specific information: compat: 0.10 refcount bits: 16 Is there a hope I'll be able to repair this image? -- Nicolas ECARNOT