[Bug 268044] NUL-byte FS corruption using QCOW2 image for RISC-V

From: <bugzilla-noreply_at_freebsd.org>
Date: Mon, 28 Nov 2022 17:16:32 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268044

            Bug ID: 268044
           Summary: NUL-byte FS corruption using QCOW2 image for RISC-V
           Product: Base System
           Version: CURRENT
          Hardware: riscv
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: riscv
          Assignee: riscv@FreeBSD.org
          Reporter: fbb@tril.bespin.org

This issue is for the following image specifically:

BAD:
FreeBSD-14.0-CURRENT-riscv-riscv64.qcow2.xz     520116860       2022-Nov-23
11:18

I tried it on 2 different versions of QEMU (5.2.0 and 6.1.0) on 2 different
host machines.  The symptom is it will boot and seem to work.  But soon after
writing to some files, files will begin to have a string of NUL bytes
overwriting the beginning of the files, corrupting the files.  The files that
are written have modification timestamps and the NULs can be viewed in vi as
^@.  Whatever is causing this also affects the filesystem metadata, since often
the entire root FS becomes unmountable due to corruption.

Using the RAW image from the same directory
https://download.freebsd.org/snapshots/VM-IMAGES/14.0-CURRENT/riscv64/Latest/
results in a successful, stable system that does not exhibit the NUL corruption
problem.
GOOD:
FreeBSD-14.0-CURRENT-riscv-riscv64.raw.xz       520071464       2022-Nov-23
11:29

-- 
You are receiving this mail because:
You are the assignee for the bug.