Open garydale opened 9 months ago
Just happened again. The exact timing was I had just installed linux-image-6.6.15-amd64 but had not rebooted when Dolphin reported that the directory I was viewing was no longer accessible. It took 2 reboots (with tune2fs setting the fsck count to 1) to be able to see the root folder again.
ls -f / and ls -f /etc both worked when the problem showed up but ls -f /keybase hung.
After a lot of frustration because the Debian/Apt keybase upgrade was failing to configure, I got the new version installed by removing the current version, rebooting so that fsck would fix the file system then installing the new version. It seems that the /keybase folder is now becoming corrupted on a regular basis.
OK, now simply running Keybase is causing the problem. The solution is to close Keybase. I discovered this when rebooting to safe mode let me see the root folder but it vanished after I logged into the GUI. Closing Keybase restored access.
I'm running Debian/Trixie on an AMD64 system. This issue has been cropping up intermittently for about a year now.
The symptom is that ls -l / hangs. I usually notice this in the folders panel of Dolphin first. It shows up after a reboot - prior to that I haven't noticed any problems. After a reboot, I may not see any folders in the folders panel and can't "ls -l /". The fix I've settled on is to "tune2fs -c 1" on the root device (in my case an mdadm raid 1 array of two nvme devices). After a reboot, it fixes whatever whatever caused the problem, although I've not seen any substantial change showing in the output from fsck.
For some background, I use UEFI boot, with 2 nvme drives each having a FAT partition and a RAID partition. The two FAT partitions are synced when the computer is shutdown so I should always have a bootable EFI partition even if one drive fails.