Catastrophic data loss with Ubuntu 21.04 guest

[AA]

See also #20763

Following this:

`Jan 15 21:35:14 ubuntu CRON[1188952]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Jan 15 21:37:35 ubuntu kernel: [1355482.810724] ata3.00: exception Emask 0x0 SAct 0x8000000 SErr 0x0 action 0x6 frozen Jan 15 21:37:35 ubuntu kernel: [1355482.810769] ata3.00: failed command: WRITE FPDMA QUEUED Jan 15 21:37:35 ubuntu kernel: [1355482.810786] ata3.00: cmd 61/10:d8:90:a0:53/00:00:00:00:00/40 tag 27 ncq dma 8192 out Jan 15 21:37:35 ubuntu kernel: [1355482.810786] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 15 21:37:35 ubuntu kernel: [1355482.810824] ata3.00: status: { DRDY } Jan 15 21:37:35 ubuntu kernel: [1355482.810839] ata3: hard resetting link Jan 15 21:37:37 ubuntu kernel: [1355485.044289] ata3: SATA link down (SStatus 1 SControl 300) Jan 15 21:37:42 ubuntu kernel: [1355490.294132] ata3: hard resetting link Jan 15 21:37:45 ubuntu kernel: [1355492.509352] ata3: SATA link down (SStatus 1 SControl 300) Jan 15 21:38:07 ubuntu kernel: [1355497.707142] ata3: hard resetting link `

the filesystem in dmesg reports: ` [1359528.850122] systemd-journald[284]: Failed to write entry (22 items, 739 bytes), ignoring: Read-only file system [1359528.851568] systemd-journald[284]: Failed to write entry (22 items, 750 bytes), ignoring: Read-only file system [1359528.852924] systemd-journald[284]: Failed to write entry (22 items, 739 bytes), ignoring: Read-only file system [1359528.854644] systemd-journald[284]: Failed to write entry (22 items, 750 bytes), ignoring: Read-only file system [1359528.856205] systemd-journald[284]: Failed to write entry (22 items, 739 bytes), ignoring: Read-only file system [1359528.857528] systemd-journald[284]: Failed to write entry (22 items, 750 bytes), ignoring: Read-only file system [1359528.858951] systemd-journald[284]: Failed to write entry (22 items, 739 bytes), ignoring: Read-only file system [1359528.860305] systemd-journald[284]: Failed to write entry (22 items, 750 bytes), ignoring: Read-only file system [1359528.862256] systemd-journald[284]: Failed to write entry (22 items, 739 bytes), ignoring: Read-only file system `

and the filesystem is unbootable, fsck requires run by hand, and probably some files are corrupt.

Linux ubuntu 5.11.0-41-generic #45-Ubuntu SMP Fri Nov 5 11:37:01 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux 12:34 No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 21.04 Release: 21.04 Codename: hirsute

[AA]

399:06:16.930950 TM: Giving up catch-up attempt at a 60 008 804 977 ns lag; new total: 167 585 247 534 313 ns
399:06:27.352981 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 10 seconds ago
399:06:27.353248 VMMDev: GuestHeartBeat: Guest is alive (gone 10 448 010 274 ns)
399:06:27.397799 AHCI#0: Port 0 reset
399:06:31.997535 VD#0: Cancelling all active requests
399:06:42.294104 AHCI#0: Port 0 reset
399:06:50.981044 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 8 seconds ago
399:06:59.893905 VMMDev: GuestHeartBeat: Guest is alive (gone 17 599 850 863 ns)

[AA]

Jan 15 21:35:14 ubuntu CRON[1188952]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 15 21:37:35 ubuntu kernel: [1355482.810724] ata3.00: exception Emask 0x0 SAct 0x8000000 SErr 0x0 action 0x6 frozen
Jan 15 21:37:35 ubuntu kernel: [1355482.810769] ata3.00: failed command: WRITE FPDMA QUEUED
Jan 15 21:37:35 ubuntu kernel: [1355482.810786] ata3.00: cmd 61/10:d8:90:a0:53/00:00:00:00:00/40 tag 27 ncq dma 8192 out
Jan 15 21:37:35 ubuntu kernel: [1355482.810786]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Jan 15 21:37:35 ubuntu kernel: [1355482.810824] ata3.00: status: { DRDY }
Jan 15 21:37:35 ubuntu kernel: [1355482.810839] ata3: hard resetting link
Jan 15 21:37:37 ubuntu kernel: [1355485.044289] ata3: SATA link down (SStatus 1 SControl 300)
Jan 15 21:37:42 ubuntu kernel: [1355490.294132] ata3: hard resetting link
Jan 15 21:37:45 ubuntu kernel: [1355492.509352] ata3: SATA link down (SStatus 1 SControl 300)
Jan 15 21:38:07 ubuntu kernel: [1355497.707142] ata3: hard resetting link

[1359528.850122] systemd-journald[284]: Failed to write entry (22 items, 739 bytes), ignoring: Read-only file system
[1359528.851568] systemd-journald[284]: Failed to write entry (22 items, 750 bytes), ignoring: Read-only file system
[1359528.852924] systemd-journald[284]: Failed to write entry (22 items, 739 bytes), ignoring: Read-only file system
[1359528.854644] systemd-journald[284]: Failed to write entry (22 items, 750 bytes), ignoring: Read-only file system
[1359528.856205] systemd-journald[284]: Failed to write entry (22 items, 739 bytes), ignoring: Read-only file system
[1359528.857528] systemd-journald[284]: Failed to write entry (22 items, 750 bytes), ignoring: Read-only file system
[1359528.858951] systemd-journald[284]: Failed to write entry (22 items, 739 bytes), ignoring: Read-only file system
[1359528.860305] systemd-journald[284]: Failed to write entry (22 items, 750 bytes), ignoring: Read-only file system
[1359528.862256] systemd-journald[284]: Failed to write entry (22 items, 739 bytes), ignoring: Read-only file system

[AA]

[67446.570212] e1000 0000:00:03.0 enp0s3: Detected Tx Unit Hang
                 Tx Queue             <0>
                 TDH                  <4>
                 TDT                  <c>
                 next_to_use          <c>
                 next_to_clean        <4>
               buffer_info[next_to_clean]
                 time_stamp           <1010023fc>
                 next_to_watch        <5>
                 jiffies              <101002597>
                 next_to_watch.status <0>
[67450.267251] e1000 0000:00:03.0 enp0s3: Detected Tx Unit Hang
                 Tx Queue             <0>
                 TDH                  <1c>
                 TDT                  <1f>
                 next_to_use          <1f>
                 next_to_clean        <1c>
               buffer_info[next_to_clean]
                 time_stamp           <101002814>
                 next_to_watch        <1e>
                 jiffies              <101002933>
                 next_to_watch.status <0>

[AA]

As I mentioned, I believe this is related to #20763 which in turn might be showing up when the Mac OS X host is under load with disk access (including to attached USB drives).