Files
proton-drive-linux/docs
nvrl cb38f79aa3 fix(fuse,scripts): log why a create finds no parent and fit the metadata floor to FUSE
A create that answered ENOENT left no trace in the log. It now warns
when the parent folder is no longer known, and when the parent left the
tree while its children were being listed, naming the parent inode and
the new name.

The acceptance script's metadata throughput floor was 20 operations per
second, which a FUSE mount cannot reach: each create and unlink waits for
Drive before it returns, about 350 ms apiece. On a FUSE mount the floor
is now 3 operations per second; other paths keep 20. The mount type is
read from /proc/self/mountinfo.
2026-09-29 21:22:54 +02:00
..

Documentation

For users

Page What it covers
Installation Packages, building from source, first sign-in, updating and uninstalling
User guide My files, available offline, synced folders, conflicts, Photos, sharing, Trash and versions, Computers, the search launcher, the tray
Command-line reference Every pdfs command, grouped by task, and scripting with --json
Configuration config.json, environment variables, file locations, the systemd service
Troubleshooting Diagnosing problems, common symptoms, starting over, reporting a bug
Recovering on a new computer What survives a lost machine and how to restore your synced folders
Changelog What changed in each release

For contributors

Page What it covers
Development guide Building, running and debugging from source; releasing
Architecture Crates, read and write paths, sync engine, control protocol, threads, threat model
Testing Unit tests and the FUSE acceptance suite
Translating Adding and updating translations
Roadmap Planned work and verification still owed
Bug ledger Every tracked defect with its analysis and status
UI/UX plan Design audit and notes behind the 2.x desktop app

Also see CONTRIBUTING.md and SECURITY.md in the repository root.