From: Dave Chinner <david@fromorbit.com>
To: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: xfs_bmap stuck at ~/.steam/steam.pipe file
Date: Thu, 11 Oct 2018 17:00:27 +1100 [thread overview]
Message-ID: <20181011060027.GP6311@dastard> (raw)
In-Reply-To: <CABXGCsPMXLbPJdAFq79Fmby3y89s=o7F-tf_+zSo_RsJXjaRaA@mail.gmail.com>
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@fromorbit.com
next prev parent reply other threads:[~2018-10-11 13:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 5:47 xfs_bmap stuck at ~/.steam/steam.pipe file Mikhail Gavrilov
2018-10-11 6:00 ` Dave Chinner [this message]
2018-10-11 6:20 ` Mikhail Gavrilov
2018-10-11 7:15 ` Dave Chinner
2018-10-11 7:59 ` Mikhail Gavrilov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181011060027.GP6311@dastard \
--to=david@fromorbit.com \
--cc=linux-xfs@vger.kernel.org \
--cc=mikhail.v.gavrilov@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.