VirtualBox

Changes between Initial Version and Version 1 of Ticket #20294


Ignore:
Timestamp:
Apr 8, 2021 8:30:02 PM (3 years ago)
Author:
Klaus Espenlaub
Comment:

You provided a lot of useful information, but a key item is missing: VBox.log (if you use default layout then it's in ~/VirtualBox VMs/<vmname>/Logs), showing the affected VM run.

The logging from the guest side points at I/O timeouts, which are outside the control of VirtualBox in the general case. The VBox.log file would allow to tell more what happened on the host side. It is odd that the AHCI emulation does not recover from these timeouts properly. Known to work unless the host's disk is unresponsive.

It is clear that you're not running out of disk space on the host (or in the VM). Your understanding of dynamic images is correct, they save on how much space is consumed on the host and grow up to the selected capacity.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #20294 – Description

    initial v1  
    77Here's what the host thinks of the partition where the VDI is located:
    88
     9{{{
    910Filesystem                         1K-blocks        Used   Available  Really_Available Use% Mount_Point
    1011/dev/sda8                         1735405656   485065980  1250569508        1250339676  28% /export/home
     12}}}
    1113
    1214The guest thinks it's VDI is:
    1315
     16{{{
    1417Filesystem     1K-blocks     Used Available Use% Mounted on
    1518/dev/sda2        1992552   164592   1706720   9% /
     
    1922/dev/sda5       65478188   751092  61355272   2% /var
    2023/dev/sda6       65478188   936844  61169520   2% /opt
    21 
     24}}}
    2225
    2326Which is considerably less than 384GB.
     
    2528Additionally, the guest is throwing numerous messages like these:
    2629
    27 
     30{{{
    2831[   23.180382] 06:32:17.603879 main     VBoxService 6.1.18_Fedora r142142 (verbosity: 0) linux.amd64 (Mar  2 2021 00:00:00
    2932) release log
     
    5255[ 7872.666963] ata1.00: cmd 61/00:60:c8:93:2b/0a:00:12:00:00/40 tag 12 ncq dma 1310720 ou
    5356                        res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    54 
     57}}}
    5558
    5659
    5760and:
    5861
    59 
     62{{{
    6063[ 7872.721207] ata1.00: status: { DRDY }
    6164[ 7872.721577] ata1.00: failed command: READ FPDMA QUEUED
     
    7477[ 7873.041133] ata1.00: device reported invalid CHS sector 0
    7578[ 7873.041646] ata1.00: device reported invalid CHS sector 0
    76 
     79}}}
    7780
    7881
    7982and:
    8083
    81 
     84{{{
    8285[49175.522760] EXT4-fs (sda8): failed to convert unwritten extents to written extents -- potential data loss!  (inode 2621957, error -30)
    8386[49175.526567] EXT4-fs (sda8): failed to convert unwritten extents to written extents -- potential data loss!  (inode 2621958, error -30)
    8487[49175.530010] EXT4-fs (sda8): failed to convert unwritten extents to written extents -- potential data loss!  (inode 2621961, error -30)
    85 
     88}}}
    8689
    8790Of course there are more of all of these messages available in a file. I'm not sure how I would attach a file to this mailing list though.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy