Warn if a qcow (not qcow2) file is opened
Subsystems (2)
PATCH 1/1 Warn if a qcow (not qcow2) file is opened
The qcow block driver format is no longer maintained and likely contains serious data corruptors. Urge users to stay away for it, and advertise the new and improved replacement.
--- block/qcow.c | 5 +++++ 1 files changed, 5 insertions(+), 0 deletions(-)
block/qcow.c +5 -0
@@ -101,6 +101,11 @@ static int qcow_open(BlockDriverState *bs, const char *filename, int flags)return ret;if (bdrv_pread (s->hd,0 , &header,sizeof (header)) !=sizeof (header)) goto fail; + +fprintf (stderr, +"WARNING: the qcow file format is no longer supported.\n" +" Please convert your images to qcow2.\n" ); +be32_to_cpus (&header.magic);be32_to_cpus (&header.version);be64_to_cpus (&header.backing_file_offset);
Signature · 1 line
1.6.0.6
Quoted 5 lines · Avi Kivity
The qcow block driver format is no longer maintained and likely contains serious data corruptors. Urge users to stay away for it, and advertise the new and improved replacement.
Signed-off-by Avi Kivity <[email protected]>
vvfat is using qcow internally, so the warning will appear there, too. Not that warning against vvfat would be a bad thing, but this error message could be confusing.
Maybe we're lucky enough and vvfat survives a s/qcow/qcow2/, but I really never wanted to touch that code...
Kevin
Quoted 9 lines · Kevin Wolf
Quoted 6 lines · Avi Kivity
The qcow block driver format is no longer maintained and likely contains serious data corruptors. Urge users to stay away for it, and advertise the new and improved replacement.
Signed-off-by Avi Kivity <[email protected]>
Quoted 7 lines
vvfat is using qcow internally, so the warning will appear there, too. Not that warning against vvfat would be a bad thing, but this error message could be confusing.
Maybe we're lucky enough and vvfat survives a s/qcow/qcow2/, but I really never wanted to touch that code...
I'm not sure how I feel about this. Can we prove qcow is broken? Is it only broken for writes and not reads?
If we're printing a warning, does that mean we want to deprecate qcow and eventually remove it (or remove write support, at least)?
Regards,
Anthony Liguori
Quoted 17 lines · Anthony Liguori
Quoted 6 lines · Kevin Wolf
Quoted 4 lines · Avi Kivity
The qcow block driver format is no longer maintained and likely contains serious data corruptors. Urge users to stay away for it, and advertise the new and improved replacement.
Quoted 9 lines
Quoted 2 lines
Signed-off-by Avi Kivity <[email protected]>vvfat is using qcow internally, so the warning will appear there, too. Not that warning against vvfat would be a bad thing, but this error message could be confusing.
Maybe we're lucky enough and vvfat survives a s/qcow/qcow2/, but I really never wanted to touch that code...
Quoted 5 lines
I'm not sure how I feel about this. Can we prove qcow is broken? Is it only broken for writes and not reads?
If we're printing a warning, does that mean we want to deprecate qcow and eventually remove it (or remove write support, at least)?
I haven't commented on the intention of deprecating qcow1, I'm not sure either. But the bug that turned up yesterday was present for a month and nobody saw it. So I guess we can take that as a sign that qcow isn't really used that much any more.
On the other hand, I think maintaining qcow1 isn't that hard. It won't get new features, so we'll not have a whole lot of changes. We must test it from time to time. And when it comes to fixing, I think qcow1 is much easier for us than, say, VMDK.
Kevin
Quoted 8 lines · Anthony Liguori
Quoted 7 lines · Kevin Wolf
Quoted 5 lines · Avi Kivity
The qcow block driver format is no longer maintained and likely contains serious data corruptors. Urge users to stay away for it, and advertise the new and improved replacement.
Signed-off-by Avi Kivity <[email protected]>
Quoted 8 lines
Quoted 6 lines
vvfat is using qcow internally, so the warning will appear there, too. Not that warning against vvfat would be a bad thing, but this error message could be confusing.
Maybe we're lucky enough and vvfat survives a s/qcow/qcow2/, but I really never wanted to touch that code...
I'm not sure how I feel about this. Can we prove qcow is broken? Is it only broken for writes and not reads?
Well, Kevin posted a patch, so it is. It's definitely unmaintained. Given it's a qemu native format, there is no interoperability value except with old qemu versions.
Quoted 2 lines
If we're printing a warning, does that mean we want to deprecate qcow and eventually remove it (or remove write support, at least)?
Yes.
Signature · 1 line
error compiling committee.c: too many arguments to function
Quoted 8 lines
Quoted 7 lines
Quoted 4 lines
Quoted 4 lines
The qcow block driver format is no longer maintained and likely contains
serious data corruptors. Urge users to stay away for it, and advertise the new and improved replacement.I'm not sure how I feel about this. Can we prove qcow is broken? Is it only broken for writes and not reads?
Quoted 8 lines
Well, Kevin posted a patch, so it is. It's definitely unmaintained. Given it's a qemu native format, there is no interoperability value except with old qemu versions.
Quoted 2 lines
If we're printing a warning, does that mean we want to deprecate qcow and eventually remove it (or remove write support, at least)?
Yes.
IMHO there's little value in just printing a warning. Until it actually goes away, people are liable to assume we're just being paranoid/awkward and keep using it anyway.
I suggest crippling it now and, assuming noone steps up to fix+maintain it, ripping out the write support altogether at next release.
I'm assuming the readonly code is in better shape, and can be supported with relatively little effort.
Paul
Quoted 17 lines · Paul Brook
Quoted 8 lines
Quoted 7 lines
Quoted 4 lines
Quoted 4 lines
The qcow block driver format is no longer maintained and likely contains
serious data corruptors. Urge users to stay away for it, and advertise the new and improved replacement.I'm not sure how I feel about this. Can we prove qcow is broken? Is it only broken for writes and not reads?
Quoted 8 lines
Well, Kevin posted a patch, so it is. It's definitely unmaintained. Given it's a qemu native format, there is no interoperability value except with old qemu versions.
Quoted 2 lines
If we're printing a warning, does that mean we want to deprecate qcow and eventually remove it (or remove write support, at least)?
Yes.
Quoted 8 lines
IMHO there's little value in just printing a warning. Until it actually goes away, people are liable to assume we're just being paranoid/awkward and keep using it anyway.
I suggest crippling it now and, assuming noone steps up to fix+maintain it, ripping out the write support altogether at next release.
I'm assuming the readonly code is in better shape, and can be supported with relatively little effort.
I agree, if we want to phase it out we should be more discouraging than just an ignoreable warning
- Disable it in qemu, and have code which looks for qcow1 magic bytes, prints an error message telling them to use qemu-img to convert to qcow2 and exits
- Keep qcow1 in qemu-img as a source format only, to allow conversions to qcow2
Possibly have a 'configure' arg to let people re-enable full read-write it if they badly need it, but tell them it'll be gone permanently in release qemu-0.12.0
Daniel
Signature · 4 lines
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
Quoted 5 lines · Paul Brook
IMHO there's little value in just printing a warning. Until it actually goes away, people are liable to assume we're just being paranoid/awkward and keep using it anyway.
I suggest crippling it now and, assuming noone steps up to fix+maintain it, ripping out the write support altogether at next release. I'm assuming the readonly code is in better shape, and can be supported with relatively little effort.
Yes, that's what I was getting at. We need to support read-only in order to allow people to convert to qcow2.
If we're sufficiently concerned that there is data corruption in the write path, we should disable it to keep a user from shooting themselves in the foot.
Regards,
Anthony Liguori
Quoted 2 lines
Paul
Am 30.06.2009 um 15:32 schrieb Anthony Liguori:
Quoted 13 lines
Quoted 12 lines · Kevin Wolf
Quoted 5 lines · Avi Kivity
The qcow block driver format is no longer maintained and likely contains serious data corruptors. Urge users to stay away for it, and advertise the new and improved replacement.
Signed-off-by Avi Kivity <[email protected]>vvfat is using qcow internally, so the warning will appear there, too. Not that warning against vvfat would be a bad thing, but this error message could be confusing.
Quoted 6 lines
Quoted 2 lines
Maybe we're lucky enough and vvfat survives a s/qcow/qcow2/, but I really never wanted to touch that code...
I'm not sure how I feel about this. Can we prove qcow is broken? Is it only broken for writes and not reads?
If we're printing a warning, does that mean we want to deprecate qcow and eventually remove it (or remove write support, at least)?
I'm confused now. Only recently someone stepped up, saying that qcow2 was broken and that qcow should be used instead for safety reasons. Now all of a sudden, it's the exact opposite, you're even considering replacing qcow with qcow2 for vvfat and dropping qcow support.
Andreas
Quoted 4 lines · Andreas Färber
I'm confused now. Only recently someone stepped up, saying that qcow2 was broken and that qcow should be used instead for safety reasons. Now all of a sudden, it's the exact opposite, you're even considering replacing qcow with qcow2 for vvfat and dropping qcow support.
Basically, qcow1 is unmaintained. On the one hand this means that its code is rarely changed and is quite stable in that respect, on the other hand it means that nobody cares if it's broken e.g. by changes to the block layer in general. There is no breakage I know of in the current stable release, however git master has been broken for a month now.
And I'm pretty sure that qcow2 receives more testing than qcow.
Kevin
Quoted 3 lines · Avi Kivity
The qcow block driver format is no longer maintained and likely contains serious data corruptors. Urge users to stay away for it, and advertise the new and improved replacement.
Does this also print the message at the time of creating the image? (And isn't qcow the default image format?)
Amit
Quoted 7 lines · Amit Shah
Quoted 3 lines · Avi Kivity
The qcow block driver format is no longer maintained and likely contains serious data corruptors. Urge users to stay away for it, and advertise the new and improved replacement.
Does this also print the message at the time of creating the image? (And isn't qcow the default image format?)
No, I don't think the image is opened by qemu-img create, create is a different operation. And the default format is raw.
Kevin