amazon web services - s3fs: Bad file descriptor when mounting S3 bucket on EC2 instance -
i uploaded files s3 , want access them in ec2 instance. trying s3fs work. ssh'ed ec2 instance , mounted s3 bucket on local folder /mnt/s3
using:
s3fs -o allow_other -o uid=1000,gid=1000,use_cache=/home/ubuntu/cache arte-mexicano /mnt/s3
i can see files no problem, without allow_other
option. filesizes ok when use ls -l
, when try @ random text file, error:
ubuntu@some-ip:/mnt/s3/some-folder$ cat readme.md cat: readme.md: bad file descriptor
i tried opening vim no success. allow_other
option didn't solve problem.
any ideas welcome!
edit 1
asked @andrewgaul:
using double debug option (-d -d):
ubuntu@some-ip:/mnt$ s3fs -d -d -o allow_other -o uid=1000,gid=1000,use_cache=/home/ubuntu/cache arte-mexicano /mnt/s3 fuse library version: 2.9.2 nullpath_ok: 0 nopath: 0 utime_omit_ok: 0 unique: 1, opcode: init (26), nodeid: 0, insize: 56, pid: 0 init: 7.22 flags=0x0000f7fb max_readahead=0x00020000 init: 7.19 flags=0x00000019 max_readahead=0x00020000 max_write=0x00020000 max_background=0 congestion_threshold=0 unique: 1, success, outsize: 40
using double debug plus -f:
ubuntu@some-ip:/mnt$ s3fs -d -d -f -o allow_other -o uid=1000,gid=1000,use_cache=/home/ubuntu/cache arte-mexicano /mnt/s3 s3fs_check_service fuse library version: 2.9.2 nullpath_ok: 0 nopath: 0 utime_omit_ok: 0 unique: 1, opcode: init (26), nodeid: 0, insize: 56, pid: 0 init: 7.22 flags=0x0000f7fb max_readahead=0x00020000 s3fs_init init: 7.19 flags=0x00000019 max_readahead=0x00020000 max_write=0x00020000 max_background=0 congestion_threshold=0 unique: 1, success, outsize: 40 s3fs_destroy
i similar logs in both cases, don't quite know mean. both hang there until stop them ctrl+c, , neither gets mounted after that.
Comments
Post a Comment