I am probably holding a piece of Erlang wrong but this was unexpected. [Screenshot_20241003_114033] Any clues?

Mine works, but I had to do :disksup.start_link before using it as I got the warning: 12:42:54.797 [warning] OS_MON (:disksup) called by pid <0.110.0>, not started

iex(8)> :disksup.get_disk_info() [ {~c"/", 488878112, 358518096, 23}, {~c"/dev", 4096, 4096, 0}, {~c"/dev/shm", 16388668, 16193968, 2}, {~c"/sys/firmware/efi/efivars", 128, 97, 22}, {~c"/run", 6555468, 6553344, 1}, {~c"/tmp", 16388672, 16303136, 1}, {~c"/boot", 1684592, 1242612, 22}, …

Hmmm, what the. Can you try starting iex as root?

no, can’t now actually. But it works for some mount points, not for the others. I could get the stats for /boot for example.

You actually have a typo: [image] hubertlepicki: iex(11)> :disksup.get_disk_info(~c"/run/user/100/") [{~c"/run/user/100/", 0, 0, 0}] Should be ~c"/run/user/1000". This is expected behavior as specified per documentation: Returns [{Path,0,0,0}] if the Path is invalid or space can’t be deter…

lmao okay you’re right, I brought nothing to the conversation

Elixir Programming Language Forum

Unexpected behaviour with :disksup.get_disk_info

Questions & Help Questions

hubertlepicki October 3, 2024, 9:44am 2

What if you add slash at the end, i.e. /root/ ?