1. Forum
  2. Usenet
  3. LINUX.DEBIAN.USER

  • qcow2 maintanance

    From Maurizio Caloro@21:1/5 to All on Sun Jun 15 08:00:01 2025
    This is a multipart message in MIME format.

    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.

    I have to stop and restart them again and again. Do you also have such experiences and is it possible to

    'defragment' these files again, even if this would not be necessary with SSD discs ?



    When the qcow2 file is recreated, it runs correctly again for a while, but
    then it starts having problems drop by drop

    I'll probably write to qmeu right after this, but before I go back to a
    forum, I'll try my luck here.



    thanks


    <html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta
    http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
    /* Font Definitions */
    @font-face
    {font-family:"Cambria Math";
    panose-1:2 4 5 3 5 4 6 3 2 4;}
    @font-face
    {font-family:Aptos;}
    /* Style Definitions */
    p.MsoNormal, li.MsoNormal, div.MsoNormal
    {margin:0cm;
    font-size:11.0pt;
    font-family:"Aptos",sans-serif;
    mso-ligatures:standardcontextual;
    mso-fareast-language:EN-US;}
    span.E-MailFormatvorlage17
    {mso-style-type:personal-compose;
    font-family:"Aptos",sans-serif;
    color:windowtext;}
    .MsoChpDefault
    {mso-style-type:export-only;
    font-size:11.0pt;
    mso-fareast-language:EN-US;}
    @page WordSection1
    {size:612.0pt 792.0pt;
    margin:70.85pt 70.85pt 2.0cm 70.85pt;}
    div.WordSection1
    {page:WordSection1;}
    </style><!--[if gte mso 9]><xml>
    <o:shapedefaults v:ext="edit" spidmax="1026" />
    </xml><![endif]--><!--[if gte mso 9]><xml>
    <o:shapelayout v:ext="edit">
    <o:idmap v:ext="edit" data="1" /> </o:shapelayout></xml><![endif]--></head><body lang=DE-CH link="#467886" vlink="#96607D" style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal><span lang=DE>Hello<o:p></o:p></span></p><p class=MsoNormal><span lang=FR-CH>Please, do you
    also have experience with Qcow2 files?`<o:p></o:p></span></p><p class=MsoNormal><span lang=FR-CH><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><span lang=FR-CH>now that I have about 15-20 qcow2 files, they are becoming more and more susceptible to an
    unclean start.<o:p></o:p></span></p><p class=MsoNormal><span lang=DE>I have to stop and restart them again and again. </span><span lang=FR-CH>Do you also have such experiences and is it possible to<o:p></o:p></span></p><p class=MsoNormal><span lang=FR-CH>
    &#8216;defragment&#8217; these files again, even if this would not be necessary with SSD discs ?<o:p></o:p></span></p><p class=MsoNormal><span lang=FR-CH><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><span lang=FR-CH>When the qcow2 file is recreated, it
    runs correctly again for a while, but then it starts having problems drop by drop<o:p></o:p></span></p><p class=MsoNormal><span lang=FR-CH>I'll probably write to qmeu right after this, but before I go back to a forum, I'll try my luck here.<o:p></o:p></
    span></p><p class=MsoNormal><span lang=DE><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><span lang=DE>thanks<o:p></o:p></span></p></div></body></html>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From tomas@tuxteam.de@21:1/5 to Maurizio Caloro on Sun Jun 15 09:50:01 2025
    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

    -----BEGIN PGP SIGNATURE-----

    iF0EABECAB0WIQRp53liolZD6iXhAoIFyCz1etHaRgUCaE56LwAKCRAFyCz1etHa RlffAJ9pCglWDMgVdLdPSC8coPTe7KHJjgCfRR78R8yC8C4Sc6Bm8Qfowlw0QpQ=
    =0si2
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Maurizio Caloro@21:1/5 to Maurizio Caloro on Sun Jun 15 11:10:01 2025
    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: tomas@tuxteam.de <tomas@tuxteam.de>
    Gesendet: Sonntag, 15. Juni 2025 09:46
    An: Maurizio Caloro <maurizio@caloro.ch>
    Cc: debian-user@lists.debian.org
    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

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Maurizio Caloro@21:1/5 to Maurizio Caloro on Sun Jun 15 11:40:02 2025
    The Image is a QCow2 file, yes login possible, but not everytime.
    I dont think that this is a proxmox issue

    I am still of the opinion that Qemu from version 7 to version 10 not only makeup changes were made, like bigger Cursor, faster blinking, or other font style, I think you mean what I think now
    greetings

    -----Ursprüngliche Nachricht-----
    Von: tomas@tuxteam.de <tomas@tuxteam.de>
    Gesendet: Sonntag, 15. Juni 2025 11:28
    An: Maurizio Caloro <maurizio@caloro.ch>
    Cc: debian-user@lists.debian.org
    Betreff: Re: qcow2 maintanance

    On Sun, Jun 15, 2025 at 10:59:38AM +0200, Maurizio Caloro wrote:
    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.

    That "Router" is a VM, right? Can you log into it? Is it that what you mean by "cli based"?

    What happens if you try to get a terminal to your VM (e.g. "qm terminal <number>").

    (or "pct", I don't know yet whether yours is a VM or a container).

    In other words -- it would be nice to see the boot messages of such a failing instance. Perhaps someone more knowledgeable here knows how to do that in Proxmox.

    Cheers
    --
    tomás

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From tomas@tuxteam.de@21:1/5 to Maurizio Caloro on Sun Jun 15 11:30:01 2025
    On Sun, Jun 15, 2025 at 10:59:38AM +0200, Maurizio Caloro wrote:
    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.

    That "Router" is a VM, right? Can you log into it? Is it that what you
    mean by "cli based"?

    What happens if you try to get a terminal to your VM (e.g. "qm terminal <number>").

    (or "pct", I don't know yet whether yours is a VM or a container).

    In other words -- it would be nice to see the boot messages of such
    a failing instance. Perhaps someone more knowledgeable here knows
    how to do that in Proxmox.

    Cheers
    --
    tomás

    -----BEGIN PGP SIGNATURE-----

    iF0EABECAB0WIQRp53liolZD6iXhAoIFyCz1etHaRgUCaE6SNAAKCRAFyCz1etHa RmJNAJ9UoH4HOsN1S3XVijxOwsupwRM9DACfWVzrr+3evxUOgcSdZCamAr/RfL4=
    =kL+Z
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Maurizio Caloro@21:1/5 to All on Sun Jun 15 12:30:01 2025
    Hello

    You have not stated a problem. No one here can help you.

    On Sun, Jun 15, 2025 at 10:59:38AM +0200, Maurizio Caloro wrote:
    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.

    For completeness, "do you also have experience with Qcow2 files?"
    isn't really a question. And "qcow2 file is recreated, it runs correctly
    again for a while, but then it >starts having problems drop by drop" is not
    a problem statement. It lacks details.

    Jeff

    when I create a new QCow2 file it runs performant, no question, after some
    time this file mentioned here becomes slower and slower, and also more error-prone. Therefore I do not exclude that there 'probably' could be an option in Qemu that could improve the content of such a file.

    I think I'll just have to experiment more here, but I'd certainly be
    grateful for any insights.
    Everything around this Qcow file runs like a dream and doesn't need to be scrutinised.

    Thanks


    --
    Don't say everything you know, but always know what you are saying, that is important

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)