Date: Mon, 28 Nov 2022 17:16:32 +0000 From: bugzilla-noreply@freebsd.org To: riscv@FreeBSD.org Subject: [Bug 268044] NUL-byte FS corruption using QCOW2 image for RISC-V Message-ID: <bug-268044-40250@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D268044 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 aft= er 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 th= at are written have modification timestamps and the NULs can be viewed in vi as ^@. Whatever is causing this also affects the filesystem metadata, since o= ften 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/Lates= t/ results in a successful, stable system that does not exhibit the NUL corrup= tion problem. GOOD: FreeBSD-14.0-CURRENT-riscv-riscv64.raw.xz 520071464 2022-Nov-23 11:29 --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-268044-40250>