Linux-Fsdevel Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Miklos Szeredi <miklos@szeredi.hu>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: linux-fsdevel@vger.kernel.org, it+linux-fsdevel@molgen.mpg.de
Subject: Re: `ls` blocked with SSHFS mount
Date: Fri, 17 Jul 2020 14:39:03 +0200 [thread overview]
Message-ID: <CAJfpegs7qxiA+bKvS3_e_QNJEn+5YQxR=kEQ95W0wRFCeunWKw@mail.gmail.com> (raw)
In-Reply-To: <874de72a-e196-66a7-39f7-e7fe8aa678ee@molgen.mpg.de>
On Fri, Jul 17, 2020 at 10:07 AM Paul Menzel <pmenzel@molgen.mpg.de> wrote:
>
> Dear Linux folks,
>
>
> On Debian Sid/unstable with Linux 5.7.6, `ls` hangs sometimes when
> accessing a directory with an SSHFS mount. Linux logs the messages below.
Several solutions:
- kill `pidof sshfs`
- umount -f $MOUNTPOINT
- echo 1 > /sys/fs/fuse/connections/$DEVNUM/abort
>
> ```
> [105591.121285] INFO: task ls:21242 blocked for more than 120 seconds.
> [105591.121293] Not tainted 5.7.0-1-amd64 #1 Debian 5.7.6-1
> [105591.121295] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
> disables this message.
> [105591.121298] ls D 0 21242 778 0x00004004
> [105591.121304] Call Trace:
> [105591.121319] __schedule+0x2da/0x770
> [105591.121326] schedule+0x4a/0xb0
> [105591.121339] request_wait_answer+0x122/0x210 [fuse]
> [105591.121349] ? finish_wait+0x80/0x80
> [105591.121357] fuse_simple_request+0x198/0x290 [fuse]
> [105591.121366] fuse_do_getattr+0xcf/0x2c0 [fuse]
> [105591.121376] vfs_statx+0x96/0xe0
> [105591.121382] __do_sys_statx+0x3b/0x80
> [105591.121391] do_syscall_64+0x52/0x180
> [105591.121396] entry_SYSCALL_64_after_hwframe+0x44/0xa9
> [105591.121400] RIP: 0033:0x7f948c1c972a
> [105591.121410] Code: Bad RIP value.
> [105591.121412] RSP: 002b:00007ffd94582dd8 EFLAGS: 00000246 ORIG_RAX:
> 000000000000014c
> [105591.121416] RAX: ffffffffffffffda RBX: 0000556c6a957cc8 RCX:
> 00007f948c1c972a
> [105591.121417] RDX: 0000000000000100 RSI: 00007ffd94582f10 RDI:
> 00000000ffffff9c
> [105591.121419] RBP: 000000000000025e R08: 00007ffd94582de0 R09:
> 000000006a95c700
> [105591.121421] R10: 000000000000025e R11: 0000000000000246 R12:
> 0000556c6a95c763
> [105591.121423] R13: 0000000000000003 R14: 00007ffd94582f10 R15:
> 0000556c6a957cc8
> ```
>
> The `ls` process cannot be killed. The SSHFS issue *Fuse sshfs blocks
> standby (Visual Studio Code?)* from 2018 already reported this for Linux
> 4.17, and the SSHFS developers asked to report this to the Linux kernel.
This is a very old and fundamental issue. Theoretical solution for
killing the stuck process exists, but it's not trivial and since the
above mentioned workarounds work well in all cases it's not high
priority right now.
Thanks,
Miklos
next parent reply other threads:[~2020-07-17 12:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <874de72a-e196-66a7-39f7-e7fe8aa678ee@molgen.mpg.de>
2020-07-17 12:39 ` Miklos Szeredi [this message]
2020-07-17 12:52 ` `ls` blocked with SSHFS mount Matthew Wilcox
2020-07-17 13:03 ` Miklos Szeredi
2022-02-18 9:41 ` Paul Menzel
2022-02-18 10:29 ` Miklos Szeredi
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='CAJfpegs7qxiA+bKvS3_e_QNJEn+5YQxR=kEQ95W0wRFCeunWKw@mail.gmail.com' \
--to=miklos@szeredi.hu \
--cc=it+linux-fsdevel@molgen.mpg.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=pmenzel@molgen.mpg.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).