https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291002
Bug ID: 291002
Summary: ZFS error created on otherwise running and sane
system.
Product: Base System
Version: 15.0-STABLE
Hardware: amd64
OS: Any
Status: New
Severity: Affects Many People
Priority: ---
Component: kern
Assignee: [email protected]
Reporter: [email protected]
So... I've been able to reproduce this at least 3 times:
The actions of baloo (kde plasma file indexer) create errors on ZFS. I see:
NAME STATE READ WRITE CKSUM
zhit ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
gpt/zhit0a ONLINE 0 0 218
gpt/zhit1a ONLINE 0 0 218
errors: Permanent errors have been detected in the following files:
zhit/home/dgilbert/.local@zfs-auto-snap_frequent-2025-11-13-11h45:/share/baloo/index
zhit/home/dgilbert/.local@zfs-auto-snap_frequent-2025-11-13-13h30:/share/baloo/index
zhit/home/dgilbert/.local@zfs-auto-snap_frequent-2025-11-13-12h30:/share/baloo/index
/home/dgilbert/.local/share/baloo/index
zhit/home/dgilbert/.local@zfs-auto-snap_frequent-2025-11-13-13h45:/share/baloo/index
zhit/home/dgilbert/.local@zfs-auto-snap_frequent-2025-11-13-12h45:/share/baloo/index
zhit/home/dgilbert/.local@zfs-auto-snap_frequent-2025-11-13-12h15:/share/baloo/index
zhit/home/dgilbert/.local@zfs-auto-snap_frequent-2025-11-13-11h30:/share/baloo/index
zhit/home/dgilbert/.local@zfs-auto-snap_frequent-2025-11-13-13h15:/share/baloo/index
I can hear your first question... is this the media?
Both drives (4T SN850X (WD black) nvme) say:
Media and Data Integrity Errors: 0
Both drives are at 0% used. No other operations seem to cause this problem.
It's always baloo ... although by # of operations, Baloo is the major spend.
Moving on. The indexed space is large:
zhit/home/dgilbert 3.2T 13G
3.2T 0% /home/dgilbert
zhit/home/dgilbert/.local 3.2T 19G
3.2T 1% /home/dgilbert/.local
zhit/home/dgilbert/tmp 3.2T 22G
3.2T 1% /home/dgilbert/tmp
zhit/home/dgilbert/.thunderbird 3.2T 14G
3.2T 0% /home/dgilbert/.thunderbird
zhit/home/dgilbert/.cache 3.2T 7.3G
3.2T 0% /home/dgilbert/.cache
yhit/retro 16T 1.7G
16T 0% /home/dgilbert/retro
yhit/dgilbert 16T 5.6G
16T 0% /home/dgilbert/yhit
yhit/games/wine_c 16T 1.0G
16T 0% /home/dgilbert/.wine/drive_c
yhit/nextcloud 18T 1.3T
16T 7% /home/dgilbert/nextcloud
vr:/home/dgilbert 3.9T 535G
3.3T 14% /d/vr/dgilbert
That last nfs mount is referenced by symlink, and I'm pretty sure it's being
indexed. I've seen the index as large as 50G
zhit is the 2 4T nvmes (and where the index is stored and where the bad files
show up). yhit is 4x 10T spinning rust with a 2T nvme index and log.
dmesg is here: https://termbin.com/6ppe
System is:
FreeBSD hit.dclg.ca 15.0-BETA5 FreeBSD 15.0-BETA5
releng/15.0-n280912-69c726c15077 GENERIC amd64
--
You are receiving this mail because:
You are the assignee for the bug.
