Skip to content

[BUG] Laptop fails to suspend with rclone FUSE mounts, storage service stuck in fuse_statfs #2060

Description

@muratcyberfu

Step 1. Before you submit

  • I have read the above instructions and am sure that this is supposed to be posted here.
  • I've successfully updated to the latest versions following the updating guide.
  • I've successfully updated the system packages to the latest.
  • I've ticked the checkboxes without reading their contents

Step 2. Version info

Version info
Packages: not on Arch

Dots: not installed

Shell: version helper not available

Quickshell:
    Quickshell 0.3.1 (revision 2d3b3e9c70ef380dff751b61d334dc88df016c29, distributed by Unset)

Local copy of shell found:
    Last merged upstream commit: unknown
    Last local commit: 6d3e6a9 (feat(lock): allow toggling password visibility (#1960))

Step 3. Describe the issue

Hi, I'm not sure this is the right place to report this, so feel free to point me elsewhere. I spent a while digging through my logs after my laptop refused to wake up one evening, and the trail seems to lead to the storage service in the Caelestia plugin. Sharing what I found in case it's useful.

Setup

Apple Silicon MacBook, Fedora Asahi Remix 44, kernel 7.1.13-402.asahi.fc44
Quickshell 0.3.1
Two rclone FUSE mounts in my home directory (pCloud and a WebDAV server), running as user services with --vfs-cache-mode writes

When I close the lid, suspend fails and systemd-logind retries it in a loop. The journal shows a qs task in uninterruptible sleep inside fuse_statfs, and the kernel freezer giving up on it.

Workaround

Mounting rclone with --vfs-disk-space-total-size pins the total so statfs can be answered without a network round trip. I've only just applied it so I can't claim it's fully confirmed, but the statfs no longer depends on the backend being reachable.

Logs
systemd-sleep[166529]: Failed to freeze unit 'user.slice': Connection timed out
kernel: PM: suspend entry (s2idle)
kernel: Freezing user space processes failed after 20.004 seconds (1 tasks refusing to freeze, wq_busy=0):
kernel: task:qs              state:D stack:0     pid:2075  tgid:2075  ppid:1951
kernel: Call trace:
kernel:  __schedule+0x2b0/0x730
kernel:  schedule+0x3c/0xe8
kernel:  request_wait_answer+0xc0/0x250 [fuse]
kernel:  __fuse_simple_request+0x204/0x360 [fuse]
kernel:  fuse_statfs+0xf8/0x150 [fuse]
kernel:  statfs_by_dentry+0x64/0xa0
kernel:  user_statfs+0x74/0xf8
kernel:  __do_sys_statfs+0x44/0x98
kernel:  el0_svc+0x40/0x198
kernel:  el0t_64_sync+0x1b0/0x1b8
systemd-sleep[166529]: Failed to put system to sleep. System resumed again: Device or resource busy

Reminder

  • I agree that it's usually impossible for others to help me without my logs.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions