Cannot list files in "/" dir (freeze)

Hello Community,

I having a weird bug in my current i3wm Manjaro installation.
I’m simply unable to list files or folders in the / dir. The command ls -lsa / just never returns. The cursor is blinking but the command never output anything.
It’s not that I have an error, a denied access or other (problem is the same as root).

I was able before, after a reboot, to get rid of this problem, but now it doesn’t want to disappear anymore :sweat_smile:, and I’m willing to find why.
I’m able to do some pwd, echo "abc" > /xyz.txt and cat /xyz.txt successfully, and some fdisk -l

but tab completion like /et [tab] doesn’t work, (completion works at other levels ./bob/.ssh/)
neither inxi

but I can try other versions

inxi -Fazy
  Kernel: 6.5.13-7-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
    clocksource: tsc available: acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.5-x86_64
    root=UUID=8bf163f4-80a5-45a3-bf21-0edd7eed2217 rw
    root=/dev/mapper/luks-879689be-84d7-4eb1-a134-d74897347264 apparmor=1
    security=apparmor udev.log_priority=3
  Desktop: i3 v: 4.23 info: i3bar dm: LightDM v: 1.32.0 Distro: Manjaro Linux
    base: Arch Linux
  Type: Laptop System: Dell product: Latitude 5400 v: N/A serial: <filter>
    Chassis: type: 10 serial: <filter>
  Mobo: Dell model: 0PD9KD v: A00 serial: <filter> UEFI: Dell v: 1.25.0
    date: 07/05/2023
Hang after the Bluetooth section

inxi -v7azy
Hang after the RAID section

[nb51190 root]# lsb_release -sirc
ManjaroLinux 23.1.2 Vulcan
[nb51190 root]# mhwd-kernel -li
Currently running: 6.5.13-7-MANJARO (linux65)
The following kernels are installed in your system:
   * linux65

I’m sure you have better ideas than mine, and I would be happy top try and find out.

Thank you

What about

$ find / -maxdepth 1


And what does

$ strace -tt -T ls -lsa /


1 Like


The find command list some dir in /, and hang after the /srv.

The strace also hang at the same point, but has already printed the next directory which is /keybase on my setup. I’m looking into it

I’m guessing you should check your mount points:

$ mount -l

Yes this is indeed the last mount point /keybase with the same issue

A big thanks for this @pobrn

This topic was automatically closed 3 hours after the last reply. New replies are no longer allowed.