goofys
goofys copied to clipboard
kahing
a high-performance, POSIX-ish Amazon S3 file system written in Go
can not compile with go1.16 # golang.org/x/sys/unix ../../go/pkg/mod/golang.org/x/[email protected]/unix/syscall.go:83:16: undefined: unsafe.Slice ../../go/pkg/mod/golang.org/x/[email protected]/unix/syscall_linux.go:2256:9: undefined: unsafe.Slice ../../go/pkg/mod/golang.org/x/[email protected]/unix/syscall_unix.go:118:7: undefined: unsafe.Slice ../../go/pkg/mod/golang.org/x/[email protected]/unix/sysvshm_unix.go:33:7: undefined: unsafe.Slice note: module requires Go 1.17
Hi, I tried to install the package on macOS Monterey 12.6.3, but it's getting failed for both "brew" and "go" ways. Is there any solution for this version? brew failed...
Hello all, Goofys works fine with contabo object-storage :) https://contabo.com/en/object-storage/
I have discovered that when enabling Amazons new Metadata version 2 to be required instead of optional, goofys fails to mount if using instance profile role because the access key...
Now `op.Handle` is `fuseops.HandleID` which needs map HandleID to FileHandle by `fs.fileHandles` ro by `fs.dirHandles` to DirHandle. If set `op.Handle`(uint64) as pointer to FileHandle or DirHandle, the map can be...
# What happened? The memory of the goofys process keeps growing and cannot reclaim the memory via `sync;echo 3 > /proc/sys/vm/drop_caches;killall -USR1 goofys;` Use go pprof heap to analyze memory...
``` root@karmada-02-a:~# goofys --debug_fuse -f --endpoint http://rook-ceph-rgw-multisite-store.rook-ceph.svc:80 --subdomain images /mnt/oss-bucket 2024/01/12 12:31:18.258896 fuse.DEBUG Op 0x00000002 connection.go:408] OK () 2024/01/12 12:31:18.262811 main.INFO File system has been successfully mounted. 2024/01/12 12:31:31.166054 fuse.DEBUG...
fix https://github.com/kahing/goofys/issues/785 When the OS reclaims the inode of the parent directory, delete the child node from the global map
We are experiencing the following issue in our environment and we need your support to identify the cause and provide a solution. We are using the following commands to connect...
Currently, the situation I have confirmed is as follows: 1. Register aws credentials in the ~/.aws/credentials file ``` [default] aws_access_key_id= aws_secret_access_key= 2. Check whether the mount folder has been properly...
