Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 438 by
shardeb...@gmail.com: Using s3fs 1.75 or 1.77 - Not
mounting on boot consistently - AWS EC2
http://code.google.com/p/s3fs/issues/detail?id=438
Detailed description of observed behavior:
In trying to resolve the issue with timestamps on the files in the cache
being incorrect with v1.71, I've installed 1.75 and 1.77 on an EC2 instance
and cannot consistently get the instance to boot with the bucket mounted,
in either version. It works sometimes, but, not always.
I reinstalled 1.71 and it will consistently mount, with all settings the
same.
Are there any known issues with mounting with these versions? All
dependencies apps seem to be current.
As soon as I re-install 1.71 it mounts every time on boot, with no other
changes.
What steps will reproduce the problem - please be very specific and
detailed. (if the developers cannot reproduce the issue, then it is
unlikely a fix will be found)?
===================================================================
The following information is very important in order to help us to help
you. Omission of the following details may delay your support request or
receive no attention at all.
===================================================================
Version of s3fs being used (s3fs --version):
1.75 or 1.77
Version of fuse being used (pkg-config --modversion fuse):
2.9.3
System information (uname -a):
Linux ip-10-179-58-188 3.10.42-52.145.amzn1.x86_64 #1 SMP Tue Jun 10
23:46:43 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
Distro (cat /etc/issue):
s3fs command line used (if applicable):
Tried this in the /etc/rc.local:
/usr/bin/s3fs abms-static-dev /opt/ABMS -o noatime -o allow_other -o
uid=91 -o gid=48 -o use_cache=/var/cache/s3fs -o default_acl=read-write -o
nonempty -o nosuid -o nodev
and
mount -a (this works fine on 1.71 - but, neither commands work for 1.75
or 1.77 consistently)
/etc/fstab entry (if applicable):
s3fs#abms-static-dev /opt/ABMS fuse
rw,noatime,nosuid,nodev,allow_other,nonempty,uid=91,gid=48,use_cache=/var/cache/s3fs
0 0
s3fs syslog messages (grep s3fs /var/log/syslog):
There is nothing in /var/log/messages with the newer versions, after
boot.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings