When I try to run bisync I get the error message that rclone can't create a file system
Run the command 'rclone version' and share the full output of the command.
rclone v1.65.0
- os/version: Microsoft Windows 11 Home 23H2 (64 bit)
- os/kernel: 10.0.22631.2861 (x86_64)
- os/type: windows
- os/arch: amd64
- go/version: go1.21.4
- go/linking: static
- go/tags: cmount```
#### Which cloud storage system are you using? (eg Google Drive)
OneDrive
#### The command you were trying to run (eg `rclone copy /tmp remote:tmp`)
<!-- You should use 3 backticks to begin and end your paste to make it readable. -->
#### Please run 'rclone config redacted' and share the full output. If you get command not found, please make sure to update rclone.
<!-- You should use 3 backticks to begin and end your paste to make it readable. -->
[QuickAccess]
type = onedrive
token = XXX
drive_id = XXX
drive_type = business
#### A log from the command that you were trying to run with the `-vv` flag
2023/12/14 10:44:27 Failed to create file system for "QuickAccess:": didn't find section in config file
But QuickAccess is in the config file as can be seen in the results of rclone config redact... How can it not be there? I tried running the command without the : and that didn't work...
Blessings
2023/12/15 10:50:03 DEBUG : Creating backend with remote "QuickAccess:"
2023/12/15 10:50:03 DEBUG : Using config file from "U:\\Settings\\Rclone\\config"
2023/12/15 10:50:03 DEBUG : OneDrive root '': Token expired but no uploads in progress - doing nothing
2023/12/15 10:50:03 DEBUG : QuickAccess: Loaded invalid token from config file - ignoring
2023/12/15 10:50:03 DEBUG : Saving config "token" in section "QuickAccess" of the config file
2023/12/15 10:50:03 DEBUG : Keeping previous permissions for config file: -rw-rw-rw-
2023/12/15 10:50:03 DEBUG : QuickAccess: Saved new token in config file
2023/12/15 10:50:04 DEBUG : Graeme @ WI: OneNote file not shown in directory listing
2023/12/15 10:50:04 ERROR : : error listing: unknown object type <nil>
2023/12/15 10:50:04 DEBUG : 7 go routines active
2023/12/15 10:50:04 Failed to lsf with 2 errors: last error was: error in ListJSON: unknown object type <nil>```
When I deleted the offending file that apparently is a problem for this command as well I got this:
```2023/12/15 10:53:56 DEBUG : rclone: Version "v1.65.0" starting with parameters ["rclone" "lsf" "QuickAccess:" "--config" "U:\\Settings\\Rclone\\config" "-vv"]
2023/12/15 10:53:56 DEBUG : Creating backend with remote "QuickAccess:"
2023/12/15 10:53:56 DEBUG : Using config file from "U:\\Settings\\Rclone\\config"
Apps/
Attachments/
###
2023/12/15 10:53:57 DEBUG : 5 go routines active```
I took out the list of personal files that are in the cloud.
As before I got the same output 2023/12/15 12:03:30 Failed to create file system for "QuickAccess:": didn't find section in config file
Should I in fact have QuickAccess and not QuickAccess:?
This seemed to work a little further once before? The output is:
2023/12/15 12:05:36 Failed to bisync: prior lock file found: C:\Users\Graeme\AppData\Local\rclone\bisync\C__Users_Graeme_QuickAccess..U__Documents_OneDrive1"_--config_U__Settings_Rclone_config_-vv.lck```
2023/12/15 12:05:36 Failed to bisync: prior lock file found: C:\Users\Graeme\AppData\Local\rclone\bisync\C__Users_Graeme_QuickAccess..U__Documents_OneDrive1"_--config_U__Settings_Rclone_config_-vv.lck```
You may already know this, but -- this error indicates that Bisync thinks a previous bisync process (of these two paths) is still running, and it is locking you out intentionally for safety. This can sometimes happen if a prior run was interrupted before it could finish. (More info)
If you're sure it's a false positive, you can override it by simply deleting the file and trying again. This should do it:
I tried the same command after deleting the problematic file. I was able to run size correctly but running the bisync gave the same error result. From the other input it seems that running it without the : is not correct in this case and therefore there is no need to remove the file that was given as a lock file.
I don't know how to resolve this issue.
I managed to reproduce this just now (on Windows only), and I think the problem is the trailing slash at the end of "U:\Documents\OneDrive1\". Windows uses \ instead of the / used by most other OSs, and I think it is confusing Bisync. Can you give it a try without the trailing slash and let me know if it solves the problem? If so, this is something I'd like to fix in a future version.
Glad to hear it! I will open an issue to improve this going forward -- should be an easy fix.
Yes and no... I think "beta" and "advanced command" are better descriptions for it than "experimental", for reasons I described in more detail here. Bisync sat unmaintained for quite awhile after it lost its original maintainer, and the label was deserved at that time, but now I have taken it on and am actively patching a lot of the old bugs, like the one you just discovered I hope that bisync can graduate from "beta" in the not-too-distant future. Until then, some caution is certainly warranted (and it doesn't replace the need for a good backup system), but I think the log warning is a bit hyperbolic at this point. I've been using it in production myself for quite awhile now without any major incidents. (I do find small bugs from time to time, but then I fix them )
The one thing I will say is that it's definitely important to read the manual in detail and make sure you understand how it works, as sometimes people come to bisync with assumptions from other sync tools and are surprised to learn that bisync does some things differently!
