Error after changing chunk size

Help and Support
1

What is the problem you are having with rclone?

ReadFileHandle.Read error: low level retry 8/10: unexpected EOF

I am having the same issue as this post:
/t/readfilehandle-read-error-low-level-retry-1-10-eof/16338/3

I accidently changed the chunk size without knowing it was going to cause issues.
Now the mount hangs and becomes unresponsive,
I reverted the chuck size back but still having issues
I read on the above post to clear the db cache with the following command: --cache-db-purge but i do not know how to do it and if it will delete the data in the google drive.
I'm new to rclone and i want to check here how to fix it safely.

What is your rclone version

rclone v1.48.0 - Forced via Plexguide install

Which OS you are using and how many bits

Ubuntu 64bit

Which cloud storage system are you using?

Google Drive

The command you were trying to run

--cache-db-purge

The rclone config contents with secrets removed.

#------------------------------------------
#PGClone| Visit https://pgblitz.com
#------------------------------------------
[gdrive]
client_id = 232*********.apps.googleusercontent.com
client_secret = ************
type = drive
token = {"access_token":"************

[gcrypt]
type = crypt
remote = gdrive:/encrypt
filename_encryption = standard
directory_name_encryption = true
password = ************
password2 = ************

[tdrive]
client_id = ************.apps.googleusercontent.com
client_secret = ************
type = drive
token = {"access_token":"ya29.************
team_drive = 0A************PVA

[tcrypt]
type = crypt
remote = tdrive:/encrypt
filename_encryption = standard
directory_name_encryption = true
password = ************
password2 = ************

[GDSA01]
type = drive
scope = drive
service_account_file = /opt/appdata/plexguide/.blitzkeys/GDSA01
team_drive = 0A************PVA

[GDSA01C]
type = crypt
remote = GDSA01:/encrypt
filename_encryption = standard
directory_name_encryption = true
password = ************
password2 = ************

[GDSA02]
type = drive
scope = drive
service_account_file = /opt/appdata/plexguide/.blitzkeys/GDSA02
team_drive = 0A************PVA

[GDSA02C]
type = crypt
remote = GDSA02:/encrypt
filename_encryption = standard
directory_name_encryption = true
password = ************
password2 = ************

[GDSA03]
type = drive
scope = drive
service_account_file = /opt/appdata/plexguide/.blitzkeys/GDSA03
team_drive = 0A************PVA

[GDSA03C]
type = crypt
remote = GDSA03:/encrypt
filename_encryption = standard
directory_name_encryption = true
password = ************
password2 = ************

[GDSA04]
type = drive
scope = drive
service_account_file = /opt/appdata/plexguide/.blitzkeys/GDSA04
team_drive = 0A************PVA

[GDSA04C]
filename_encryption = standard
directory_name_encryption = true
password = ************
password2 = ************

[GDSA02]
type = drive
scope = drive
service_account_file = /opt/appdata/plexguide/.blitzkeys/GDSA02
team_drive = 0A************PVA

[GDSA02C]
type = crypt
remote = GDSA02:/encrypt
filename_encryption = standard
directory_name_encryption = true
password = ************
password2 = ************

[GDSA03]
type = drive
scope = drive
service_account_file = /opt/appdata/plexguide/.blitzkeys/GDSA03
team_drive = 0A************PVA

[GDSA03C]
type = crypt
remote = GDSA03:/encrypt
filename_encryption = standard
directory_name_encryption = true
password = ************
password2 = ************

[GDSA04]
type = drive
scope = drive
service_account_file = /opt/appdata/plexguide/.blitzkeys/GDSA04
team_drive = 0A************PVA

[GDSA04C]
type = crypt
remote = GDSA04:/encrypt
filename_encryption = standard
directory_name_encryption = true
password = ************
password2 = ************

[pgunion]
type = union
remotes = gdrive: tdrive: gcrypt: tcrypt: /mnt/move
2

That's an extremely old version so you'd want to update that.

The cache backend is being phased out and is beta and has a ton of bugs and really should not be used.

Changing the chunk size just causes the old chunks to be invalid. Nothing would be delete from your Google Dirve. You can ran cache-db-purge to clean the chunks.

You should check out the new vfs cache mode full that replaces the old cache backend.

3

Thank you for replying!
I cant update that version as its hard-coded into the plexguide install
how exactly do i run that command ?
when i type it in the command line it states command not found.
Sorry, new to this

4

That guide is ancient and really should not be used are you getting an old, unsupported version.

I have no idea what commands you are running to get a mount.

You'd stop the mount and you can just remove the cache as I don't know where it is or you can add --cache-db-purge to your mount command, run it, let it out mount, stop it and remove that flag.

The cache backend is deprecated as it has lots of bugs and should not be used.

5

Its all automated so i got no idea.
The flag, does it go in the rconfig.env ?

uagent=rclone/v1.55
vfs_ll=NOTICE
vfs_bs=16M
vfs_rcs=64M
vfs_rcsl=2048M
vfs_cm=writes
vfs_cma=1h
vfs_cms=off
vfs_dct=5m
vfs_t=8
vfs_mt=750G
vfs_c=16
6

I have no idea how plexguide works so you may want to check with them as it's all not supported here.

7

I will see if anyone can help from there.
in the mean time. What would a normal mount command look like so i can see if i can find it?
Also. if i build a new vm would i still get the same issue as its on the google drive end or is it only on this vm i changed the chunk size on ?

8

The mount command I use is here but would only work on a recent version of rclone.

https://github.com/animosity22/homescripts/blob/master/systemd/rclone.service

The configuration is local so it only effects the machine you are on. If you build a new machine, it has no idea you've done that so it would not impact anything.

9

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.