When an inode becomes invalid, the filesystem is considered as corrupted.
Reproduce cases:
vm$ apk add lsblk e2fsprogs-extra util-linux filecontainer$ QEMU-img create -f qcow2 disk.qcow2 2G# Switch from VM console to QEMU monitor: Ctrl + A C
# Plug disk to VM
(qemu) drive_add 0 file=disk.qcow2,media=disk,if=none,id=mydrive
(qemu) device_add virtio-blk-pci,drive=mydrive,id=mydevice
# Switch from QEMU monitor to VM console: Ctrl + A C
# Check if disk added
vm$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
vda 253:0 0 2G 0 diskvm$ fdisk /dev/vda
(fdisk) o # create a new empty DOS partition table
(fdisk) w # write changes
vm$ fdisk /dev/vda
(fdisk) n # add a new partition
# partition type: primary partition
# partition number: (default)
# first sector: (default)
# last sector: +1G
(fdisk) w # write changes
vm$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
vda 253:0 0 2G 0 disk
└─vda1 253:1 0 1G 0 partvm$ mkfs.ext4 /dev/vda1
vm$ fsck -fn /dev/vda1vm$ mkdir /mnt/vda1
vm$ mount /dev/vda1 /mnt/vda1The inode link count is the number of filenames or hard links that point to the inode. An inode with a zero link count is known as an orphaned file. The fsck considers an orphaned file as a incomplete deletion error.
vm$ echo 'Hello A' > /mnt/vda1/file_avm$ umount /mnt/vda1vm$ debugfs -w /dev/vda1
(debugfs) ls -l
# inode filetype & mode link_count uid gid size last modification name
# (octal)
11 100644 (1) 0 0 8 13-Sep-2026 10:04 file_a
# filetype & mode: 100644
# 10 (file type), 0 (special permission), 644 (owner,group,other permissions)
(debugfs) show_inode_info file_a
Links: 1(debugfs) set_inode_field file_a links_count 0
(debugfs) show_inode_info file_a
Links: 0vm$ fsck -fn /dev/vda1
/dev/vda1: WARNING: Filesystem still has errorsTODO…
TODO…