check/debug if you are able to mount in verbose mode
# S3 doesn't have normal file atributes & owners like in linux, so to make it accessible for `clickhouse`# user we need to fix the owners and attributes.# 1. check uid / gid of clickhouse user first, you will need them in later commands (in uid / gid)
id -u clickhouse
id -g clickhouse
# I've met that problem when changing bucket to us-west2: https://github.com/s3fs-fuse/s3fs-fuse/issues/666#issuecomment-475407515
s3fs bucketname /s3fsmount/ -o dbglevel=info -f -o url=https://s3-us-west-2.amazonaws.com -o allow_other -o umask=227 -o uid=111 -o gid=115 -o noatime
# or - even more verbose:# s3fs bucketname /s3fsmount/ -o dbglevel=debug -f -o curldbg -o url=https://s3-us-west-2.amazonaws.com -o allow_other -o umask=227 -o uid=111 -o gid=115# you can just leave it running attached to some terminal and to all FS checks in another window.# press Ctrl+C to exit that, after you see that everything is mounted & working
After it's working - you can add the entry to /etc/fstab (to mount filesystem everytime when system starts)
#edit /etc/fstab - add a line:
s3fs#bucketname /s3fsmount fuse _netdev,allow_other,umask=227,uid=111,gid=115,noatime 0 0
# other samples (also with cache)
#s3fs#s3fsmount /s3fsmount fuse _netdev,allow_other,umask=227,uid=111,gid=115,url=https://s3-us-west-2.amazonaws.com,use_cache=/root/cache 0 0
after that do
# to mount all disks in fstab
mount -a
# check if mounted:
df -h
...
s3fs 256T 0 256T 0% /s3fsmount
# to unmount the disk
umount /s3fsmount