Borg mount options with autofs?

[Hexasoft]

Hi,

I'm using Borg 1.1.9 on a up-to-date Debian 10 (borgbackup package from the OS).
I want borgfs being available with autofs, which works fine:
DIR -fstype=fuse.borgfs,ro :/PATH/TO/REPO
Then (in my case) using 'ls /misc/DIR' will show the Borg backup content.

But I want to use 'strip-components' option (to remove useless initial path) on this mount, but I can't set this option here. Trying:
DIR -fstype=fuse.borgfs,ro,strip-components=4 :/PATH/TO/REPO
just makes the mount fail, whereas using this same option directly works fine, i.e.:
borg mount --strip-components 4 /PATH/TO/REPO /root/mnt/

I also tried to replace the "-" with a "_" without success.

So my question/suggestion:

• is there any way to perform this
• and if not it seems it would be a good feature to add

Regards,
-- Y.

[ThomasWaldmann]

you can't just use arbitrary borg options as mount option.

but seems like a valid use case, so at least strip-components should be made working.

[Hexasoft]

Ok, fine. I will wait next release (in the meanwhile I hard-coded the option in fuse.py as it is on a dedicated server).
Thanks.

[oemunoz]

Autofs abuse

• /mnt/autofs/backup/borg is the path to my borgs backups (btrfs)

# Btrfs
btrfs    -fstype=btrfs                             :UUID="63ab1cba-d6a8-40b6-b3f6-xxxxxx"
borg     -fstype=btrfs,subvol=/@borg               :UUID="63ab1cba-d6a8-40b6-b3f6-xxxxxxx"

# Borg
icinga        -fstype=fuse.borgfs,allow_other,nodev,nosuid          :"/mnt/autofs/backup/borg::baltazar_180729_icinga_180901_200111121405"
baltazar_home -fstype=fuse.borgfs,allow_other,nodev,nosuid          :"/mnt/autofs/backup/borg::baltazar_180729_home_191124093925"

PD:
Some unknow log on syslog, when I go to directory, but works...

key "borg::baltazar_180729_home_191124093925" not found in map source(s).

borg --version
borg 1.1.10