any attempt to list the contents of the directory /home/user/rclone fails with the error message:
ls: reading directory ‘rclone’: I/O error
When that error happens, I see the following output from the “mount” command:
2019/02/07 17:09:45 DEBUG : /: Attr:
2019/02/07 17:09:45 DEBUG : /: >Attr: attr=valid=1m0s ino=0 size=0 mode=drwxr-xr-x, err=
2019/02/07 17:09:45 DEBUG : /: ReadDirAll:
2019/02/07 17:09:45 DEBUG : : Re-reading directory (27h39m48.69929782s old)
2019/02/07 17:09:46 DEBUG : oblnuslpfer7n4vrseo5s1svvs: Skipping undecryptable dir name: Bad PKCS#7 padding - not all the same
2019/02/07 17:09:46 DEBUG : mmcljiv7nbck26c1a16sc5rgus: Skipping undecryptable dir name: Bad PKCS#7 padding - too long
2019/02/07 17:09:46 DEBUG : duifoftrp05tcvnivp1qoqcmi8: Skipping undecryptable dir name: Bad PKCS#7 padding - too long
2019/02/07 17:09:46 DEBUG : 043cqpc8rkn0jvccoaldr792bc: Skipping undecryptable dir name: Bad PKCS#7 padding - too long
2019/02/07 17:09:46 DEBUG : up5dm2fj19f3qjmd3tsm6roqb8: Skipping undecryptable dir name: Bad PKCS#7 padding - too long
2019/02/07 17:09:46 DEBUG : 2f00ni6569sro0cg2493p2b9bs: Skipping undecryptable dir name: Bad PKCS#7 padding - too long
2019/02/07 17:09:46 DEBUG : /: >ReadDirAll: item=26, err=
Here is my redacted .rclone.conf:
[foo]
type = drive
client_id = [redacted]apps.googleusercontent.com
client_secret = [redacted]
token = {“access_token”:"[redacted]",“token_type”:“Bearer”,“refresh_token”:"[redacted]",“expiry”:“2019-02-07T14:13:13.781805284-07:00”}
team_drive =
[crypt]
type = crypt
remote = foo:/crypt
filename_encryption = standard
password = [redacted]
password2 = [redacted]
–max-read-ahead 200M --checkers 40 --transfers=32 all do nothing on a mount command so they can be removed as well. (max-read-ahead does something but only if you are compiling a custom kernel on your OS).
Just for fun, can you grab the latest stable ? That’s 1.45.
That error usually relates back to the passwords being off, but you are using the same machine/account to run the mount as you are doing the rclone mount?
Yes, the lsd and the mount have been run on the same machines as the same username in 3 different cases, and in each case commands like ls and lsd return results just fine, while mount just utterly fails. All of this was working a few weeks ago, but I went out of town and came back to none of my mounts working.
It is not a team drive, but I am doing directory encryption; while I don’t have that flag you mentioned specified anywhere, I believe this is why I have a password and a password2 in my .rclone.conf
After some thought, I’m pretty sure those are 8 completely empty directories in the crypt: share - I think they’re from the first attempt at setting up rclone, when I made the directories in a crypt but didn’t bother to remember the password I had used, because it was just a test to see what the items end up looking like on the Google Drive side. So those directories mount is whinging about are completely useless folders that have nothing in them. I have deleted those directories from the Google Drive side.
OK, 1.45 definitely helped uncover this mystery a little bit. The one marked as ??? above DOES show up in 1.45’s lsd output:
-1 2019-01-22 04:51:59 -1 .
That is, it’s a directory named “.”!!
I have no idea where that came from (I can guess, but I had no idea it was even possible to create something named .), but I assume this is probably what is choking up an attempt to ls the directory when it’s mounted?