Volumes error on access but work? kinda?

[BrutalBirdie]

This also block using the volume as the main data directory:

[BrutalBirdie]

Seems like the setting for the mount is not being respected:

mount -l | grep -i '/mnt/volumes/5283b6c6e7c0493f97093cd9d7c17b5a'
REDACTED-sub1@REDACTED-sub1.your-storagebox.de:/home/data on /mnt/volumes/5283b6c6e7c0493f97093cd9d7c17b5a type fuse.sshfs (rw,relatime,user_id=0,group_id=0,allow_other)

It should be uid and gid 0 but is uid=1012 && gid=1013

[nebulon]

using sub-accounts with sshfs and hetzner was showing odd side-effects in the past, as mentioned in https://docs.cloudron.io/backups/#sshfs Although this is referring to backups, same applies to volumes. Best do not use sub-accounts or use cifs instead.

[jdaviescoates]

@nebulon what exactly does a "subaccount" mean in this context please?

[girish]

@jdaviescoates it's a concept in hetzner storage box - https://docs.hetzner.com/robot/storage-box/additional-users/

[BrutalBirdie]

Ahhhh okay I will try cifs with the sub-account.

[jdaviescoates]

@BrutalBirdie said in Volumes error on access but work? kinda?:

Ahhhh okay I will try cifs with the sub-account.

Out of interest, why not just no use a sub-account? Or put another way: why use a sub-account?

[BrutalBirdie]

@jdaviescoates Socialist hosting
The community pays for the server and the storage box.

If someone wants to use part of the storage box for an app or something?
Can't just give the the whole Storage Box Account, they could access data from other members of the community.
With Sub-Accounts each account has only access to his... Account.

You could also think it in a way of:
You buy a 20 TB Storage box and each 1TB is for 1x Sub-Account, 1x Cloudron, 1x App, 1x Customer. yada yada yada

Getting the picture?

[BrutalBirdie]

The CIFS version worked btw.

[jdaviescoates]

@BrutalBirdie said in Volumes error on access but work? kinda?:

Getting the picture?

Yes! Excellent