Truncate/Trim file name

#### What is the problem you are having with rclone?
The current source location has deeply nested hierarchies and in some cases long basename/filenames. When copying files across to a OneDrive encrypted remote, it generates the error Failed to copy: invalidRequest: pathIsTooLong: Path exceeds maximum length.

Flattening the hierarchy or changing file names isn't an option given the sheer volume of files including operational knowledge associated with the structures.

Is there a way to truncate or trim file names so that they don't hit the ceiling limit e.g. 143 characters?

If not, what other native options are available in rclone?

What is your rclone version (output from rclone version)

rclone v1.53.2

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

Microsoft Windows 10 Professional version 1909 Build 18636.1110

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

Microsoft OneDrive

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

rclone.exe --transfers=2 --checkers=2 --stats 10s --progress --bwlimit 8M --checksum --log-file=rclone_log.txt --log-level DEBUG copy --exclude Dir/** LocalPath EncryptedRemote:/

A log from the command with the -vv flag

Failed to copy: invalidRequest: pathIsTooLong: Path exceeds maximum length

For reference:

Also encrypted remotes makes the file name even longer due to the file and path naming.

ncw shortly touched upon it here

How to encrypt the filenames.
Choose a number from below, or type in your own value
 1 / Don't encrypt the file names.  Adds a ".bin" extension only.
   \ "off"
 2 / Encrypt the filenames see the docs for the details.
   \ "standard"
 3 / Very simple filename obfuscation.
   \ "obfuscate"

We've been working on a 4th option - "compressed" but that won't be ready for a while.

Thanks @St0rm and @ncw.

A post on chunkers suggests that it can result in longer than expected file names. Would this be a contributing issue?

Is there an option to utilize it as an alternative?

Chunking also increases the path length a bit - not hugely.

Thanks @ncw. Would you recommend changing the chunking configuration to validate if the path length remains an issue? If yes, what settings do you suggest?

You can change --chunker-name-format to shorten filenames a little bit if you want.

Thanks @ncw. If using --chunker-name-format does rclone's configuration need to change? At the moment, the settings are a OneDrive remote and an encrypted remote.

Perhaps I misunderstood - you don't need that unless you've configured a chunker backend.

Righto @ncw. To clarify, do you mean that chunkers have not effect unless a chunker backend has been configured?

Assuming there is no other option including obscuring filenames, can rclone decompress remote files or traverse them? For example, if a 7z or zip archive is copied across to a remote, can rclone open the archive (without extracting)? This is so that if users wish to search for files with longer names that have been compressed, they are able to do so without first downloading the archive and then uncompressing it.

Alternatively, is it possible to assign shortened aliases to files with longer names?

i have large .7z files in cloud, and i am able to extract a single file without downloading the entire .7z
i use a rclone mount so that the .7z appears as local file.

@asdffdsa, if the 7z archive is extracted on a remote, does it remain encrypted? Secondly, would it not increase the storage utilization?

same as with any .7z file.
once mounted, the .7z looks and acts like a local file and behaves the same.

my .7z are always encrypted.
so if i want to extract a single file from the mount to my local computer, i will be asked for the password.
no need to decrypt the entire .7z, no need to download the entire .7z

If the 7z archive isn't encrypted but the remote is, would the extraction remain encrypted? I'm assuming it does.

How are you maintaining a list of files and the archive they belong to? I'm attempting to find a balanced solution that an average user could follow with a few simple steps.

if you extract a file from that non-crypted .7z which is inside a rclone crypted remote to another location in that remote, then yes, the extract file is crypted by rclone.

i create the .7z files locally, as backups of local files then upload them to rclone.
i can extract file(s) as needed.

Thanks @asdffdsa. Assuming no local copies are maintained as storage is an issue and a 7z archive is copied across to an encrypted remote, what would you recommend so that a catalog of the list of files is known for a given archive?

well, if that archive was local, what would you do?

Archives aren't typically created locally nor for backups. The only reason it is being explored at the moment is because of the longer file names.

That is correct.

You can mount the backend and then use something to look in the zip - it shouldn't have to download the zip. I did make a backend which does this for zip files which I haven't released yet.

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