> How does that "unclean start" looks like?
hmm let me explain, the Router (cli-based) don't start-up correctly, staring
but, the interfaces will stay still down (not possible to bring up), the used
Protocol not propagate (you dont see any answer), the cli prompt freez and come
with a little luck back 10-15min later, the "system" are 100% unusable. The
CPU+Memory usage are almost in sleepingstate with some normal rashes.
> "Stopping and restarting" means stopping and restarting the VM running on
> that image?
Stop the Image on running Proxmox env. from running process, wipe the conifig,
from image config, and re-start the QCow image, with a bit more luck, they
possible will boot up correctly,
like Interface starting up, Protocol are propagate and and and
> i don't know what you mean by 'defragment'. Qcow2 is known for accumulating
> unused
> space over time, but that would just make it > more bloated (and possibly
> somewhat
> slower?). But it won't prevent it from working properly.
Yes, i am with you, but while searching, I kept coming across such views and
thought,
I'm probably not the last with such problems. I have also seen that Qemu has
arrived
V. 10.x, presumably such problem has already been recognised here!?
Also found this, never used because it is also somewhat illogical, but!?
- https://github.com/zhangyoujia/qcow2-defrag/releases/tag/v0.01
yes more or often you use the image, they slower becomes, if comparing this
with a
fresh image, i have no such of delays. To create a new image each time takes
time,
and here i want to ask if there is another way to "CleanUP" this in a shorted
way.
but I would like to thank you for your quick answer which I have tried to
precise here
hopefully until the next content, thanks greetings
M
-----Ursprüngliche Nachricht-----
Von: [email protected] <[email protected]>
Gesendet: Sonntag, 15. Juni 2025 09:46
An: Maurizio Caloro <[email protected]>
Cc: [email protected]
Betreff: Re: qcow2 maintanance
On Sun, Jun 15, 2025 at 07:45:55AM +0200, Maurizio Caloro wrote:
> Hello
>
> Please, do you also have experience with Qcow2 files?`
>
>
>
> now that I have about 15-20 qcow2 files, they are becoming more and
> more susceptible to an unclean start.
How does that "unclean start" looks like?
> I have to stop and restart them again and again. Do you also have such
> experiences and is it possible to
"Stopping and restarting" means stopping and restarting the VM running on that
image?
> 'defragment' these files again, even if this would not be necessary
> with SSD discs ?
I don't know what you mean by 'defragment'. Qcow2 is known for accumulating
unused space over time, but that would just make it more bloated (and possibly
somewhat slower?). But it won't prevent it from working properly.
And this has probably *nothing* to do with your storage hardware (i.e.
SSD or not).
> When the qcow2 file is recreated, it runs correctly again for a while,
> but then it starts having problems drop by drop
You will have to give us more details for anyone to have a chance to help you
find the problem.
When it fails: how do you know it failed? Do you have error messages?
Log files? etc.
Cheers
--
tomás
