sigoden/dufs
1
0
Fork 0
mirror of https://github.com/sigoden/dufs.git synced 2026-04-08 16:49:02 +03:00
Code Issues 8 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #638] Possible file descriptors leak #386

New Issue
Closed
opened 2026-04-08 16:52:31 +03:00 by zhus · 2 comments
zhus commented 2026-04-08 16:52:31 +03:00
Owner
Copy Link

Originally created by @iyesin on GitHub (Oct 22, 2025).
Original GitHub issue: https://github.com/sigoden/dufs/issues/638

Problem

During the huge backup initiated from Android's SeedVault, I started getting 500 No file descriptors available (os error 24) error. After the first occurrence of this error, backup process stalled and no files were uploaded. I ran lsof -p $(pidof dufs) | wc -l just to validate that dufs process was utilizing all 1024 file descriptors that was available for my user.

Configuration

The program was started with the following command line:
dufs --port 45045 --allow-upload --allow-delete --allow-search --allow-symlink --compress none /media/user/store

Log

22025-10-21T18:12:34+02:00 INFO - 192.168.1.3 "HEAD /.SeedVaultAndroidBackup/aaaabbbbccccdddd.sv/92/92d9a9ce4f69d07d54f16a757a970eb664c046aaaaabbbbccccddddeeeeffff0" 200
2025-10-21T18:12:34+02:00 INFO - 192.168.1.3 "PUT /.SeedVaultAndroidBackup/aaaabbbbccccdddd.sv/92/92d9a9ce4f69d07d54f16a757a970eb664c046aaaaabbbbccccddddeeeeffff0" 201
2025-10-21T18:12:34+02:00 INFO - 192.168.1.3 "PUT /.SeedVaultAndroidBackup/aaaabbbbccccdddd.sv/0b/0bdaf1249cb9750fda68f01a15e822adb560c860000aaaabbbbccccddddeeeef" 201
2025-10-21T18:12:34+02:00 ERROR - 192.168.1.3 "HEAD /.SeedVaultAndroidBackup/aaaabbbbccccdddd.sv/0b/0bdaf1249cb9750fda68f01a15e822adb560c860000aaaabbbbccccddddeeeef" 500 No file descriptors available (os error 24)
2025-10-21T18:12:34+02:00 ERROR - 192.168.1.3 "PUT /.SeedVaultAndroidBackup/aaaabbbbccccdddd.sv/f3/f3a233d5431db15e14b574b5affde6acaf8f37311110000aaaabbbbccccdddde" 500 No file descriptors available (os error 24)
2025-10-21T18:12:34+02:00 ERROR - 192.168.1.3 "PUT /.SeedVaultAndroidBackup/aaaabbbbccccdddd.sv/10/10672631960e847e494fc54f0aaeef4d53ef667222211110000aaaabbbbccccd" 500 No file descriptors available (os error 24)
2025-10-21T18:12:35+02:00 ERROR - 192.168.1.3 "PUT /.SeedVaultAndroidBackup/aaaabbbbccccdddd.sv/78/788a787a18e2ca156d0b2b2090a65e1e2b728ba3333222211110000aaaabbbbc" 500 No file descriptors available (os error 24)
2025-10-21T18:12:35+02:00 ERROR - 192.168.1.3 "PUT /.SeedVaultAndroidBackup/aaaabbbbccccdddd.sv/3e/3e9a640afc8198311214977173909c95b1777d744443333222211110000aaaab" 500 No file descriptors available (os error 24)
2025-10-21T18:12:36+02:00 ERROR - 192.168.1.3 "PUT /.SeedVaultAndroidBackup/aaaabbbbccccdddd.sv/3a/3a8b197bcc4a3286c9a4ad602d3a538ea9d654b555544443333222211110000a" 500 No file descriptors available (os error 24)

Environment Information

  • Dufs version: 0.45.0
  • Browser/Webdav info: Seedvault 12-3.0 on LineageOS 19.1
  • OS info: Debian GNU/Linux 13 (trixie) on 6.12.48+deb13-amd64
  • Proxy server (if any): none
Originally created by @iyesin on GitHub (Oct 22, 2025). Original GitHub issue: https://github.com/sigoden/dufs/issues/638 **Problem** During the huge backup initiated from Android's SeedVault, I started getting `500 No file descriptors available (os error 24)` error. After the first occurrence of this error, backup process stalled and no files were uploaded. I ran `lsof -p $(pidof dufs) | wc -l` just to validate that `dufs` process was utilizing all 1024 file descriptors that was available for my user. **Configuration** The program was started with the following command line: `dufs --port 45045 --allow-upload --allow-delete --allow-search --allow-symlink --compress none /media/user/store` **Log** ``` 22025-10-21T18:12:34+02:00 INFO - 192.168.1.3 "HEAD /.SeedVaultAndroidBackup/aaaabbbbccccdddd.sv/92/92d9a9ce4f69d07d54f16a757a970eb664c046aaaaabbbbccccddddeeeeffff0" 200 2025-10-21T18:12:34+02:00 INFO - 192.168.1.3 "PUT /.SeedVaultAndroidBackup/aaaabbbbccccdddd.sv/92/92d9a9ce4f69d07d54f16a757a970eb664c046aaaaabbbbccccddddeeeeffff0" 201 2025-10-21T18:12:34+02:00 INFO - 192.168.1.3 "PUT /.SeedVaultAndroidBackup/aaaabbbbccccdddd.sv/0b/0bdaf1249cb9750fda68f01a15e822adb560c860000aaaabbbbccccddddeeeef" 201 2025-10-21T18:12:34+02:00 ERROR - 192.168.1.3 "HEAD /.SeedVaultAndroidBackup/aaaabbbbccccdddd.sv/0b/0bdaf1249cb9750fda68f01a15e822adb560c860000aaaabbbbccccddddeeeef" 500 No file descriptors available (os error 24) 2025-10-21T18:12:34+02:00 ERROR - 192.168.1.3 "PUT /.SeedVaultAndroidBackup/aaaabbbbccccdddd.sv/f3/f3a233d5431db15e14b574b5affde6acaf8f37311110000aaaabbbbccccdddde" 500 No file descriptors available (os error 24) 2025-10-21T18:12:34+02:00 ERROR - 192.168.1.3 "PUT /.SeedVaultAndroidBackup/aaaabbbbccccdddd.sv/10/10672631960e847e494fc54f0aaeef4d53ef667222211110000aaaabbbbccccd" 500 No file descriptors available (os error 24) 2025-10-21T18:12:35+02:00 ERROR - 192.168.1.3 "PUT /.SeedVaultAndroidBackup/aaaabbbbccccdddd.sv/78/788a787a18e2ca156d0b2b2090a65e1e2b728ba3333222211110000aaaabbbbc" 500 No file descriptors available (os error 24) 2025-10-21T18:12:35+02:00 ERROR - 192.168.1.3 "PUT /.SeedVaultAndroidBackup/aaaabbbbccccdddd.sv/3e/3e9a640afc8198311214977173909c95b1777d744443333222211110000aaaab" 500 No file descriptors available (os error 24) 2025-10-21T18:12:36+02:00 ERROR - 192.168.1.3 "PUT /.SeedVaultAndroidBackup/aaaabbbbccccdddd.sv/3a/3a8b197bcc4a3286c9a4ad602d3a538ea9d654b555544443333222211110000a" 500 No file descriptors available (os error 24) ``` **Environment Information** - Dufs version: `0.45.0` - Browser/Webdav info: Seedvault 12-3.0 on LineageOS 19.1 - OS info: Debian GNU/Linux 13 (trixie) on 6.12.48+deb13-amd64 - Proxy server (if any): none
zhus closed this issue 2026-04-08 16:52:31 +03:00
zhus commented 2026-04-08 16:52:32 +03:00
Author
Owner
Copy Link

@sigoden commented on GitHub (Oct 27, 2025):

I don't think this is an issue with dufs.
It might be that your operating system's maximum file descriptor limit for users is set too low (the default is 1024). When the number of files being uploaded at the same time exceeds this limit, problems occur.

Please increase the system-wide file descriptor limit

ulimit -n 65535
<!-- gh-comment-id:3449011972 --> @sigoden commented on GitHub (Oct 27, 2025): I don't think this is an issue with dufs. It might be that your operating system's maximum file descriptor limit for users is set too low (the default is 1024). When the number of files being uploaded at the same time exceeds this limit, problems occur. Please increase the system-wide file descriptor limit ``` ulimit -n 65535 ```
zhus commented 2026-04-08 16:52:32 +03:00
Author
Owner
Copy Link

@iyesin commented on GitHub (Oct 29, 2025):

@sigoden your feedback is not very constructive. And, it does not solve the use case of mine (and, most likely, bunch of other casual users).
I have another webdav solution running for weeks in the same environment without the problem. Same user, same backup program as client, thus, it does not have the problem, I experienced with dufs.

<!-- gh-comment-id:3463515076 --> @iyesin commented on GitHub (Oct 29, 2025): @sigoden your feedback is not very constructive. And, it does not solve the use case of mine (and, most likely, bunch of other casual users). I have another webdav solution running for weeks in the same environment without the problem. Same user, same backup program as client, thus, it does not have the problem, I experienced with dufs.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
enhancement
help wanted
pull-request
Mirrored from GitHub Pull Request
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
zhus
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sigoden/dufs#386
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?