Guild icon
S3Drive
Community / support / (Android) App crashed during sync and now I can't even use --resync since I can't delete .lck file
Avatar
Hello everyone. I'm using S3Drive with rclone+Proton. In one of my syncs the android program crashed, which honestly wouldn't be a big deal but seems like I need to delete the .lck file to sync again, but I can't do it since I'm using a non-rooted device and I can't access that folder. I've read this can be fixed with the --max-lock parameter but I have no idea how to set it up. Any ideas on how to delete the file or how to reconfigure this sync to add the --max-lock parameter would be greatly appreciated. (btw I've already deleted cache, deleted the entire sync and re-added it but this error persists). Failed 6 times. Last error: Exception: prior lock file found: /data/user/0/com.s3.drive.file.explorer.storage.cloud.manager/files/rclone/.cache/proton..storage_emulated_0_ProtonDriveS3Sync.lck Tip: this indicates that another bisync run (of these same paths) either is still running or was interrupted before completion. If you're SURE you want to override this safety feature, you can delete the lock file with the following command, then run bisync again: rclone deletefile "/data/user/0/com.s3.drive.file.explorer.storage.cloud.manager/files/rclone/.cache/proton..storage_emulated_0_ProtonDriveS3Sync.lck" Stack: pid: 23019, tid: 531565368576, name 2.ui os: android arch: arm64 comp: yes sim: no build_id: 'cde83d067117e2e2ccbd75ad13cefacb' isolate_dso_base: 797893a000, vm_dso_base: 797893a000 isolate_instructions: 7978d20a40, vm_instructions: 7978d0a000 #00 abs 0000007979609e93 virt 0000000000ccfe93 _kDartIsolateSnapshotInstructions+0x8e9453 <asynchronous suspension> #01 abs 0000007979606a53 virt 0000000000ccca53 _kDartIsolateSnapshotInstructions+0x8e6013 <asynchronous suspension>
Avatar
Hi @George_MD Thanks for your feedback, we'll try to prioritize this issue and provide a way to cleanup the lock file in a release, by the end of next week. Not sure at this stage if it's going to be emergency remedy as simple as allowing to delete the whole: rclone/.cache directory within the app scope directory, or something more sophisticated (which would allow to target the specific lock file).
Avatar
Found out that if I create new syncs with the exact same name as the .lck ones it will keep failing, so as an emergency workaround I made a new sync with a different name. So for now any failed sync with its established name is "locked out". (edited)
Avatar
Avatar
George_MD
Found out that if I create new syncs with the exact same name as the .lck ones it will keep failing, so as an emergency workaround I made a new sync with a different name. So for now any failed sync with its established name is "locked out". (edited)
Thanks for letting me know. We've got a solution (that is we detect the lock from the error message and provide user an option to delete it) already, it's awaiting release, which will likely happen in the mid of next week. (edited)
👍 1
Avatar
Hi @George_MD, This is to let you know that we've released an option to delete the lock file in a: [1.12.5] - 2025-05-17 release. By any chance, can you please confirm that it works for you once lock issue happen? I guess in next turn we could try troubleshooting why your app crashes, whether it was temporary memory/OOM issue or anything else. Thanks! (edited)
Exported 5 message(s)
Timezone: UTC+0