TeamAmaze / TeamAmaze/AmazeFileManager

Incorrect "Insufficient space" error on copy or move

Open
#3,626 1 comment 1 reaction 1 assignee View on GitHub

@TranceLove is already working on this.

Since Nov 20, 2022.

Area-Ssh/Scp/Sftp Issue-Bug
Dominant language
Kotlin
Stars
6.4k
Forks
1.7k
Avg merge
3d 9h
Merged PRs (30d)
1

Description

Describe the bug
I am accessing a remote filesystem via SFTP. This is an NFS filesystem which is backed by BTRFS on the NFS server. When I attempt to copy or move any file it tells me "Insufficient space", despite the fact that there is over 800GB free according to df, and that these files are smaller than 1GB. I have not experienced this issue on regular BTRFS filesystems accessed over SFTP, only when NFS is involved. I have not tested with other types of filesystems.

To Reproduce
Steps to reproduce the behavior:

  1. Open an SFTP connection
  2. Browse to a mounted NFS filesystem (backed by BTRFS in my case)
  3. Attempt to copy or move any file
  4. See a toast that says "Insufficient space"

Expected behavior
The copy or move should succeed. Moves would preferably perform a rename (SSH_FXP_RENAME) rather than a copy-and-delete.

Smartphone

  • Device: Google Pixel 5a
  • OS: Android 13
  • Rooted: Yes, Magisk
  • Version: 3.8.2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.