On Thu, Oct 11, 2018 at 10:47:31AM +0500, Mikhail Gavrilov wrote: > When I researched the most fragmented files, I found that xfs_bmap > stuck at the file /home/mikhail/.steam/steam.pipe. Stuck, or just taking a long time? > Can you look why it happens? > > $ xfs_bmap -V > xfs_bmap version 4.18.0 > > > Here backtrace of xfs_bmap process: > (gdb) thread apply all bt full > > Thread 1 (Thread 0x7fe0a8c86880 (LWP 21024)): > #0 0x00007fe0a92f649f in __libc_open64 It's in the kernel open() syscall opening the file. userspace tracing won't tell you what is going on at this point. Is there anything in dmesg? what is the output of `cat /proc/<pid>/stack` for the xfs_io process that is running the bmap command? What output ends up in dmesg after running 'echo w > sysrq-trigger'? Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx
