The officially official Devuan Forum!

sjox

Member

Registered: 2025-09-16

Posts: 3  

Inode No. 12

With the new update (Debian 13.2) an updated Cups is also included!
This installs a file "dnssd" in the directory "/usr/lib/cups/backend-available/" and two further hard links
in the directory "/usr/lib/cups/backend"! (dnssd and mdns). The Inode was 12!
Of course you can view these files or directories using "ls -li"!
But that changes after a reboot!
If I try to list this directory on my PC using "ls -l" I get the message: "The structure must be cleaned up"!
(dnssd is only displayed with ? and the file system is shot!!)
Then I get the message for each following command: "input/output error"
A following "fsck.ext4 -y -f /dev/nvme0n1p3" reports "invalid inode 12".

(I noticed this problem due to an AIDE check - after this check the filesystem was shot!)

The question now is how a simple "ls -l" can shoot the whole file system?
(It must be because of the Inode 12!)
I helped myself by simply reinstalling cups using "--reinstall".
This gave the file (and the two hardlinks) another inode!
However, if I install Cups a third time - Inode 12 is active again!
Therefore, 12 is always preferred - except for this inode is already in use!
I was also able to replicate this with other files.
For example, as soon as I copy a normal text file into this directory, this file had the inode 12!
With the command "find / -inum 12" I also found other system files!

Now my questions:
Why is it that Inode 12 is awarded?
Apparently, this is only intended for system-related files!
Also, this behavior occurs in others or I am the only one

---

He who asks is a fool for five minutes. He who does not ask remains a fool forever.
- Chinese proverb

g4sra

Member

Registered: 2018-12-12

Posts: 76  

Re: Inode No. 12

find / -xdev -inum 12