--no-modtime flag in fstab entry; relevance for google drive

[ventolin]

STOP and READ USE THIS TEMPLATE NO EXCEPTIONS - By not using this, you waste your time, our time and really hate puppies. Please remove these two lines and that will confirm you have read them.

What is the problem you are having with rclone?

• I don't know how to add the --no-modtime flag to an /etc/fstab rclone mount entry, or whether this is possible to begin with.
• I don't know whether --no-modtime will improve performance of a google drive mount, as only S3 is mentioned in the docs.

Run the command 'rclone version' and share the full output of the command.

rclone v1.68.1
- os/version: ubuntu 24.04 (64 bit)
- os/kernel: 6.8.0-35240528-generic (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.23.1
- go/linking: static
- go/tags: none

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

Google Drive

Please run 'rclone config redacted' and share the full output. If you get command not found, please make sure to update rclone.

[cloudp]
type = crypt
remote = gdrive_raw:cloudp/
password = XXX

[documents]
type = crypt
remote = gdrive:documents/
password = XXX

[gdrive]
type = crypt
remote = gdrive_raw:container/
password = XXX

[gdrive_raw]
type = drive
client_id = XXX
client_secret = XXX
scope = drive.file
token = XXX
team_drive =
pacer_min_sleep = 10ms
pacer_burst = 200

[newp]
type = crypt
remote = rawpool:.newp/
password = XXX

[rawpool]
type = alias
remote = /mnt/rawpool
### Double check the config for sensitive info before posting publicly

[asdffdsa (jojothehumanmonkey)]

welcome to the forum,

@ventolin

only S3 is mentioned in the docs
--no-modtime will improve performance of a google drive mount,

with s3, it takes an extra api call to get the modtime, which takes time and can incur extra charges?
fwiw, i would not do that, should not make a difference with gdrive.

@ventolin

I don't know how to add the --no-modtime flag to an /etc/fstab rclone mount entry, or whether this is possible to begin with.

it is confusing.
--no-modtime would become no_modtime

[ventolin]

Great, thanks for the comprehensive answer! In that case, I'll steer clear of it.