You have a lot of options in your command, do you know what they do and that they are needed? I know --fast-list does nothing on mount, so you can remove that at least. Also you have both --rc-no-auth and --rc-user/--rc-passwd, seems to me you don't need both, although I have no experience with rc myself.
I would try with as simple command as possible first, and then extend from that, perhaps you can find a combination of options that triggers your issue.
Ok well where would you like the log to stop? As the log file keeps filling up until I presume all the files in the upload dir have entered the queue, at which point I guess the mount point would appear? This takes hours as it seems to be uploading files as they enter the queue, this slows it down significantly so I believe it's waiting for the upload queue to be empty before it shows the mount point. If that is the case the mount point isn't likely to appear for approx a week at a guess, and the log file will continue to grow for that amount of time also.
I understand that it helps the most, but the log I posted above that file is 15gb in size, and the gui says it's going to take 17 hours to upload, which is fine but obviously I have an issue with the mount point not showing up, and would ideally like the mount point to show up before the 17 hours is up, there is several other files after this one with varying sizes, so it's going to be a very long wait to get a full log to you and my issue resolved it appears.
No you misunderstand, the providing the log is not the problem.
The problem is the amount of physical time that will have passed to get you a full log.
As I said the first file in the upload queue will take 17 hours to upload, and the files after this I don't know how long they will take to upload.
So if I can't get a full log to you for over a week? that means I just have to have a non working mount for that amount of time, does that make sense what I am trying to explain?
If you have a large set of files in your upload queue, the mount doesn't become active until the queue is cleaned out so I'd assume you stopped the mount before things cleared out.
By providing the full log in the first post, we would have arrived at that answer after the first post. Since you only gave a brief snippet in the first post, we spent some time trying to get a picture of what's going on.
So if you provide the current full log, we can show you what's going on based on the log.
@ncw Is there a reason for that? No not stopped as such, more of Windows decided it wanted to do an update and the machine rebooted whilst I was sleeping.
That's all that was in the log at the point of making the post I couldn't give you more at the time, but I did state there was a large upload queue.
Confused, I have looked at the log and can see that files are uploading, there isn't much else going on. Confused as to why there is a delay in the mount becoming active just because there is an upload queue.
hello,
some of these flags do nothing, based on your config --cache-db-path -cache-tmp-upload-path
to simply testing, remove all the flags and test with a simple command such as rclone.exe mount gdrive: Z:
if it works well, then add more flags, test and repeat until the delay happens, and then you will know which flag is causing the delay.
if the command still has the delay, then continue to diagnose the problem with that simple command.
I did that as I didn't want the uploads to take up all the transactions and leave too few for reading, so I thought I would just do 1 at a time and as I am in rush for the files to be uploaded.
How would I check that ?
There is 67 files in the upload folder, there is more in the vfs folder but I believe thats the cache.