https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=292959
Bug ID: 292959
Summary: spontaneous ufs errors inside vm
Product: Base System
Version: 14.3-STABLE
Hardware: amd64
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: kern
Assignee: [email protected]
Reporter: [email protected]
There is a spontaneous ufs errors inside vm reported by fsck_ffs which appears
and gone by themselves.
VM is a FreeBSD 14-stable guest. Hypervisors are QEMU in Windows 10, VPS on
Proxmox. VirtualBoŃ… and HyperV also affected (IIRC, the first obervation of
such behaviour was in 2024).
Appearance:
:loop_label
one may run something like:
> tunefs -n disable /dev/da0p3
and get:
tunefs: /dev/da0p3 is not clean - run fsck
or just run fsck_ffs and get an errors.
Then one can reboot in a singleuser mode and run something like fsck -f and get
"no errors, file system clean".
After going to multiuser situation repeated (goto loop_label).
The following below related to idle system with only base packages without any
busy services. All partitions are checked before in singleuser mode with resume
"filesystem is clean".
FreeBSD version is 14-stable from 2024 till 2026 years.
--------
>fsck /
** /dev/gpt/rtv0-vmdisk (NO WRITE)
** Last Mounted on /
** Root file system
** Phase 1 - Check Blocks and Sizes
INCORRECT BLOCK COUNT I=562404 (16 should be 8)
CORRECT? no
INCORRECT BLOCK COUNT I=641283 (8 should be 0)
CORRECT? no
INCORRECT BLOCK COUNT I=641284 (8 should be 0)
CORRECT? no
INCORRECT BLOCK COUNT I=641285 (8 should be 0)
CORRECT? no
INCORRECT BLOCK COUNT I=641292 (8 should be 0)
CORRECT? no
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
UNREF FILE I=413 OWNER=root MODE=100644
CLEAR? no
UNREF FILE I=321731 OWNER=root MODE=100644
SIZE=0 MTIME=Feb 4 13:48 2026
RECONNECT? no
CLEAR? no
UNREF FILE I=321732 OWNER=root MODE=100644
SIZE=0 MTIME=Feb 4 13:36 2026
RECONNECT? no
CLEAR? no
LINK COUNT DIR I=560897 OWNER=root MODE=41777
SIZE=512 MTIME=Feb 4 13:48 2026 COUNT 11 SHOULD BE 3
ADJUST? no
ZERO LENGTH DIR I=641283 OWNER=root MODE=41777
SIZE=0 MTIME=Feb 4 13:48 2026
CLEAR? no
ZERO LENGTH DIR I=641284 OWNER=root MODE=41777
SIZE=0 MTIME=Feb 4 13:48 2026
CLEAR? no
ZERO LENGTH DIR I=641285 OWNER=root MODE=41777
SIZE=0 MTIME=Feb 4 13:48 2026
CLEAR? no
ZERO LENGTH DIR I=641288 OWNER=root MODE=41777
SIZE=0 MTIME=Feb 4 13:48 2026
CLEAR? no
ZERO LENGTH DIR I=641289 OWNER=root MODE=41777
SIZE=0 MTIME=Feb 4 13:48 2026
CLEAR? no
ZERO LENGTH DIR I=641290 OWNER=root MODE=41777
SIZE=0 MTIME=Feb 4 13:48 2026
CLEAR? no
ZERO LENGTH DIR I=641291 OWNER=root MODE=41777
SIZE=0 MTIME=Feb 4 13:48 2026
CLEAR? no
ZERO LENGTH DIR I=641292 OWNER=root MODE=41777
SIZE=0 MTIME=Feb 4 13:48 2026
CLEAR? no
** Phase 5 - Check Cyl groups
FREE BLK COUNT(S) WRONG IN SUPERBLK
SALVAGE? no
SUMMARY INFORMATION BAD
SALVAGE? no
BLK(S) MISSING IN BIT MAPS
SALVAGE? no
12598 files, 121779 used, 1143694 free (558 frags, 142892 blocks, 0.0%
fragmentation)
--------
few seconds later
>fsck /
** /dev/gpt/rtv0-vmdisk (NO WRITE)
** Last Mounted on /
** Root file system
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
FREE BLK COUNT(S) WRONG IN SUPERBLK
SALVAGE? no
SUMMARY INFORMATION BAD
SALVAGE? no
BLK(S) MISSING IN BIT MAPS
SALVAGE? no
12585 files, 121789 used, 1143688 free (552 frags, 142892 blocks, 0.0%
fragmentation)
--------
few seconds later
> fsck /
** /dev/gpt/rtv0-vmdisk (NO WRITE)
** Last Mounted on /
** Root file system
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
UNREF FILE I=403254 OWNER=root MODE=100600
SIZE=0 MTIME=Feb 4 14:02 2026
RECONNECT? no
CLEAR? no
** Phase 5 - Check Cyl groups
12586 files, 121790 used, 1143689 free (553 frags, 142892 blocks, 0.0%
fragmentation)
--------
few seconds later
> fsck /
** /dev/gpt/rtv0-vmdisk (NO WRITE)
** Last Mounted on /
** Root file system
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
12585 files, 121790 used, 1143689 free (553 frags, 142892 blocks, 0.0%
fragmentation)
--------
repeating this more times will give an errors (mostly) and no errors (rarely).
filesystem options:
tunefs: POSIX.1e ACLs: (-a) disabled
tunefs: NFSv4 ACLs: (-N) disabled
tunefs: MAC multilabel: (-l) disabled
tunefs: soft updates: (-n) enabled
tunefs: soft update journaling: (-j) disabled
tunefs: gjournal: (-J) disabled
tunefs: trim: (-t) disabled
tunefs: maximum blocks per file in a cylinder group: (-e) 4096
tunefs: average file size: (-f) 16384
tunefs: average number of files in a directory: (-s) 64
tunefs: minimum percentage of free space: (-m) 8%
tunefs: space to hold for metadata blocks: (-k) 6400
tunefs: optimization preference: (-o) time
tunefs: volume label: (-L)
two variant of fstab options with no effect:
/dev/gpt/rtv0-vmdisk / ufs rw,sync,noatime 1 1
or
/dev/gpt/rtv0-vmdisk / ufs rw,noatime 1 1
--
You are receiving this mail because:
You are the assignee for the bug.