Win 10 and Onedrive

What is the problem you are having with rclone?

There are errors in program output.

What is your rclone version (output from rclone version)

rclone v1.52.2

  • os/arch: windows/amd64
  • go version: go1.14.4

Which OS you are using and how many bits (eg Windows 7, 64 bit)

WIN 10 64bit

Which cloud storage system are you using? (eg Google Drive)

onedrive

The command you were trying to run (eg rclone copy /tmp remote:tmp)

rclone --vfs-cache-mode writes --fuse-flag --VolumePrefix=\server\share mount onedrive: Z:

The rclone config contents with secrets removed.

(default config)

A log from the command with the -vv flag

The service rclone has been started.
2020/08/04 06:20:15 ERROR : VirtualBox VMs/Win10_1909_nios_svn/Win10_1909_nios_svn.vbox-tmp: Failed to calculate src hash: hash: failed to open: The system cannot find the file specified.
2020/08/04 06:20:15 ERROR : VirtualBox VMs/Win10_1909_nios_svn/Win10_1909_nios_svn.vbox-tmp: corrupted on transfer: QuickXorHash hash differ "" vs "1edec9c315762d83b13f8fcc442df9cd42177688"
2020/08/04 06:20:15 ERROR : VirtualBox VMs/Win10_1909_nios_svn/Win10_1909_nios_svn.vbox(0xc0004a6240): failed to transfer file from cache to remote: corrupted on transfer: QuickXorHash hash differ "" vs "1edec9c315762d83b13f8fcc442df9cd42177688"
2020/08/04 06:20:15 ERROR : VirtualBox VMs/Win10_1909_nios_svn/Win10_1909_nios_svn.vbox(0xc0004a6240): RWFileHandle.Flush error: failed to transfer file from cache to remote: corrupted on transfer: QuickXorHash hash differ "" vs "1edec9c315762d83b13f8fcc442df9cd42177688"
2020/08/04 06:20:15 ERROR : IO error: failed to transfer file from cache to remote: corrupted on transfer: QuickXorHash hash differ "" vs "1edec9c315762d83b13f8fcc442df9cd42177688"

hello,

can you post your config file, redacted passwords, ids and whatnot.

The rclone config contents with secrets removed.

(default config)

are you copying from the mount to local or local to the mount?

is the vm running at the time of file copy or is virtual box modifying that file at the same time you are trying to copy it?

Hello,
the config is
[onedrive]
type = onedrive
token = {"access_token":"...","expiry":"2020-08-05T07:55:12.7155175+02:00"}
drive_id = b!...
drive_type = business

are you copying from the mount to local or local to the mount?

is the vm running at the time of file copy or is virtual box modifying that file at the same time you are trying to copy it?

I am not copying any file, i only runs the machine from disk added by rclone.

not sure what you mean?

you are running the virtualbox vm on the z:?

Yes. I have large virtual machine on cload and I have to run it without mirroring to local store.

vbox-tmp and .vbox

it looks like those files changed during the time rclone was transferring it.
you might tweak the vm settings to store such file on local.

i would think that rclone is a not a good use-case for a vm hosted in the cloud.
you might get better results with the new vfs beta
https://forum.rclone.org/t/testing-for-new-vfs-cache-mode-features/16905/240

Thanks a lot I will try,
Is there any recommended command witch I shoud to use ?

Hmm still dont work.
After some days of booting it crash and vm write error, program try to acess address 0.
Will upload screens on next boot on/crash.
I used rclone-v1.52.2-283-gd786027e-vfs-beta-windows-amd64
now i am trying in debug mode.
All files was local stored only large VDI disk file was from rclone.

how large is the .vdi file?

Pure VDI has about 50 GB snapshots have next 200 GB.

that is a small vm.

is there a reason you cannot run it locally?

When it will work there will be about 50gb/week. after 2 months it will be larger as local disks.

is there a reason you cannot use a external usb hard drive or add another drive to the computer?

Becouse we can not lost one released data.

"Becouse we can not lost one released data"
not sure what you mean,

in any event, based on your own experience and my own experience, the idea of running a critical virtual server on a .vdi in the cloud using rclone mount, is not going to work reliably, if at all.

tho it is somewhat off-topic, if you want, we can discuss the different ways i would handle a similar situation.

Is there any reason to make snapshot every week?

If that the only reason there is no need to save the old snapshot, I believe 2 recent snapshot already cover what you need.

Now it looks like this:

So when i run machine it have to read all snapshots diff files.
Is there any better way ?
The point is to have all release states aviabile.

Thanks

i could be wrong, as i do not use virtualbox, but for the vm to run, it does not need to read all the snapshots.
snapshots allow you to revert the vm to a previous point in time.
the current state of the vm is inside the .vdi file

as a test,

  • create a small vm
  • take a few snapshots
  • move those snapshots to a different folder
  • shutdown the vm
  • start the vm
  • the vm should boot ok.

It boots ok but you lost your changes.
Diff file cant be from future ( it dont know what you will do after taking snapshoot ).
You have to store whole image or make diff file from frozen disk.