Hi,

Getting s3fs command to work was pretty straightforward:

• get fuse 2.9.2 SRPM from CentOS 7 and rebuild it on a CentOS 6: fuse now meets s3fs minimum version requirement (sadly CentOS 6's fuse doesn't)
• follow s3fs-fuse documentation to compile s3fs
• use s3fs command to mount - success

Now, the tricky and dirty part: fstab

• Try to mount the very same bucket from fstab: FAIL
• Use basic mount command (not mount.fuse): FAIL
• Use mount.fuse command: success. Yeah, tricky, indeed.

In short: I tried several syntax in fstab with no luck. The "deprecated" "s3fs#mybucket" with a "fuse" type, or the "actual" (I presume) syntax with "mybucket" and "fuse.s3fs" type where not working either.

Analysing strace gave me some clue:

stat("/sbin/mount.fuse.s3fs", 0x7ffc83e991c0) = -1 ENOENT (No such file or directory)
stat("/sbin/mount.fuse", 0x7ffc83e991c0) = -1 ENOENT (No such file or directory)
rt_sigprocmask(SIG_BLOCK, ~[TRAP SEGV RTMIN RT_1], NULL, 8) = 0
stat("/sbin/mount.fuse.s3fs", 0x7ffc83e99190) = -1 ENOENT (No such file or directory)
stat("/sbin/mount.fuse", 0x7ffc83e99190) = -1 ENOENT (No such file or directory)
mount("s3fs#mybucket", "/srv/mymountpoint", "fuse.s3fs", MS_MGC_VAL|MS_NOATIME, "max_stat_cache_size=100001,stat_"...) = -1 EINVAL (Invalid argument)

Now, the dirty part: ln -s /usr/sbin/mount.fuse /sbin/mount.fuse solves the fstab problem...
That's ugly, I know... If you have any suggestion, feel free to share :)