Orphaned Inode Problem

["Stephen P. Molnar" <s.molnar@sbcglobal.net>]

I am running up to date Bookworm on my Debian platform:

Processor	AMD FX(tm)-8320 Eight-Core Processor
Memory	8026MB (5267MB used)
Machine Type	Desktop
Operating System	Debian GNU/Linux 12 (bookworm)

I have been plagued with orphaned inodes. Last night the problem cane to a head. When I reboot the computer, after an orphaned inode incident created stop, it got as far as the user login. After the return I got the Windows infamous blue screen. Restarting produced the same problem.

Fortunately, I have another SSD used to test Bookworm, before updating on the SSD that is having the problem. I can access the problem drive and am in the process of backing up files.

I ran sudo e2fsck -f/dev/sdc1 and got:

Script started on 2024-02-19 08:15:52-05:00 [TERM="xterm-256color" TTY="/dev/pts/0" COLUMNS="100" LINES="24"]
[?2004h(base) ]0;comp@AbNormal: ~comp@AbNormal:~$ sudo e2fsck -f /dev/sdc1lcaomosudo e2fsck -f /dev/sdc1
[?2004l
[sudo] password for comp:
e2fsck 1.47.0 (5-Feb-2023)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
/lost+found not found.  Create<y>? yes
Pass 4: Checking reference counts
Pass 5: Checking group summary information

/dev/sdc1: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sdc1: 7982363/121577472 files (0.3% non-contiguous), 421959365/486307328 blocks
[?2004h(base) ]0;comp@AbNormal: ~comp@AbNormal:~$ [?2004l

Comments and suggestions will be appreciated.

Thanks in advance.

-- 
Stephen P. Molnar, Ph.D.            
https://insilicochemistry.net
(614)312-7528 (c)
Skype:  smolnar1