From 9260319e7411ff8281700a532caa436f40120ec4 Mon Sep 17 00:00:00 2001 From: Christian Krinitsin Date: Fri, 30 May 2025 16:52:07 +0200 Subject: gitlab scraper: download in toml and text format --- .../target_missing/host_missing/accel_missing/1997 | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 gitlab/issues_text/target_missing/host_missing/accel_missing/1997 (limited to 'gitlab/issues_text/target_missing/host_missing/accel_missing/1997') diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1997 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1997 new file mode 100644 index 000000000..6befbccef --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1997 @@ -0,0 +1,20 @@ +Disk corruption on ARM64 (Apple Silicon) Linux VMs +Description of problem: +aarch64 Linux VMs will encounter disk corruption if they're set up with a filesystem that will notice it when it happens, e.g. BTRFS. This seems to be across the board with products, including Apple Hypervisor Framework, or just QEMU, so it very well might be an aarch64 Linux bug. +Steps to reproduce: +1. Install an aarch64 Linux VM using BTRFS as the root filesystem. ZFS might recognize silent corruption readily as well. +2. Run `stress-ng --iomix 4` +3. Check your `dmesg` and/or `btrfs check --force ` to check for filesystem corruption. +Additional information: +This is discussed in two other tickets, but I'm hoping to get more attention to the problem here. +[https://github.com/lima-vm/lima/issues/1957](https://github.com/lima-vm/lima/issues/1957) +[](https://github.com/utmapp/UTM/issues/4840) + +![Screenshot_2023-11-22_at_10.20.23_AM](/uploads/ae8ed51c7adb59933c4f7f9673dddd3d/Screenshot_2023-11-22_at_10.20.23_AM.png) + +![Screenshot_2023-11-22_at_10.20.23_AM](https://i.imgur.com/HwqrFQE.png) + +I can't seem to figure out how to upload images, but you can probably get to the image that I'm trying to share somehow... + + +``` -- cgit 1.4.1