Andreas Hasenack

Right, that's the error I saw in master earlier. With 7f75d320f6d8ac7ec5185b2145da87f698aec273, it builds fine with gcc 14.2.0, thanks!

That could have been ext4, btrfs, or zfs even, depending on what I used that day in the test container.

Here are some tests with different filesystems. ext4: ``` andreas@nsnx2:~/scandir$ touch testdir/2foo andreas@nsnx2:~/scandir$ touch testdir/1foo andreas@nsnx2:~/scandir$ touch testdir/3foo andreas@nsnx2:~/scandir$ ./scandir testdir/ Opening directory testdir/ with opendir() Navigating testdir/ with readdir()...

I used this: ```c #include #include #include #include #include #include int main(int argc, char *argv[]) { const char *path; DIR *dir_stream; struct dirent *dir_entry; char *dir_name; struct dirent **namelist; int...

Thanks to Athos Ribeiro, here is a much simpler version that I force-pushed.

In my case, the directory is empty: ``` $ sudo ls -lah /var/snap/lxd/common/lxd/logs/j-armhf-vm/ total 8.0K drwx------ 2 root root 4.0K Aug 28 19:59 . drwx------ 14 root root 4.0K Aug...

I do have this in `/var/snap/lxd/common/lxd/logs/lxd.log`: ``` time="2024-08-28T19:59:15Z" level=warning msg="Unable to use virtio-fs for config drive, using 9p as a fallback" err="Architecture unsupported" instance=j-armhf-vm instanceType=virtual-machine project=default ```

I think it's the same as issue #30080 which was closed due to missing information/logs.

Issue #30154 was fixed, and all my sessions are now verified via the recovery key. I'm really not eager to go through that verification again. I understand you need logs....