s3fs mount reports an error, prompting: s3fs: unable to access MOUNTPOINT /backup/fileserver/: Transport endpoint is not connected
s3fs appfiles.v1 /backup/fileserver/ -o passwd_file=/etc/passwd-s3fs -o url=http://192.168.12.30 -o uid=1002,gid=1002 -o use_path_request_style
s3fs: unable to access MOUNTPOINT /backup/fileserver/: Transport endpoint is not connected
How to Solve this error:
1, confirm whether the network link ok.
can ping through.
2, whether the port is open
telnet 192.168.12.30 80
port can be passed, that is not a network problem caused.
3, ls /backup/fileserver/
error message: ls: cannot access fileserver: Transport endpoint is not connected
It is good that there is an error, because ls will not report an error for an empty directory, but this error means that the directory is still mounted, but the link is not available.
Checking the process, the process hangs. I suspect that the process is hung, but the directory is not unmounted.
4. Manually unmount
No error is reported, good, that means the inference is correct.
5, mount test
s3fs appfiles.v1 /backup/fileserver/ -o passwd_file=/etc/passwd-s3fs -o url=http://192.168.12.30 -o uid=1002,gid=1002 -o use_path_request_ style
No error was reported, ok! The troubleshooting process is over. This means that the problem is caused by the lack of unmounting.
6, confirm whether it is mounted up:
df -hT Filesystem Type Size Used Avail Use% Mounted on devtmpfs devtmpfs 7.8G 0 7.8G 0% /dev tmpfs tmpfs 7.8G 0 7.8G 0% /dev/shm tmpfs tmpfs 7.8G 819M 7.0G 11% /run tmpfs tmpfs 7.8G 0 7.8G 0% /sys/fs/cgroup /dev/vda1 xfs 15G 4.8G 11G 32% / /dev/vdb xfs 100G 4.0G 97G 4% /backup tmpfs tmpfs 1.6G 0 1.6G 0% /run/user/0 s3fs fuse.s3fs 16E 0 16E 0% /backup/recordfiles tmpfs tmpfs 1.6G 0 1.6G 0% /run/user/1000 s3fs fuse.s3fs 16E 0 16E 0% /backup/fileserver
Check that it is already there. Mount ok The whole process is over.
- [Solved] Internal error XFS_WANT_CORRUPTED_GOTO at line 1635 of file fs/xfs/libxfs/xfs_alloc.c.
- [Solved] Centos Mount Error: XFS: log mount mount/recovery failed : error -117
- Ubuntu Run Error: not syncing : VFS: Unable to mount root
- The solution to the crash loop back off error of coredns in k8s deployment
- You might want to save ‘/run/in itramf s/rdsosreport.txt“ to a USB stick or bootaf ter mounting
- [Solved] Mount error: Mount: unknown filesystem type ‘defaults’
- [Solved] Samba Mount Error: mount error(22): Invalid argument
- [Solved] minio Failed to Upload File Error: The difference between the request time and the server‘s time is too large.
- [Solved] Docker Install Error: [Errno 14] curl#60 – Peer‘s Certificate issuer is not recognized
- Docker -v Directory Mount (How to Use)
- [Solved] httpd:httpd:Could not reliably determine the server‘s fully qualif domain name,using ::1 for Se
- [Solved] mongod: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No s
- [Solved] sed -i error: sed: -e expression #1, char 44: invalid reference \1 on `s’ command’s RHS
- How to Fix Ubuntu(Linux) mount error(22)
- [Solved] chroot: failed to run command ‘mount’: Exec format error
- [Solved] Ubuntu16.4Install vcs2016 Error: mount.vboxsf: mounting failed with the error: Invalid argument
- Ubuntu: rabbitmq reports an error; Solution error: unable to connect to node rabbit@localhost : nodedown
- [Solved] WSUS client access server exception error – 0x8024401f
- How to Solve Error: “Hdaudio hdaudioc0d2: unable to bind codec”
- [Soled] MTPuTTY error: unable to run putty the system cannot find the specified file