Issue 265 in s3fs: Unable to mount to a non empty directory
s3...@googlecode.com
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 265 by cga...@gmail.com: Unable to mount to a non empty directory
http://code.google.com/p/s3fs/issues/detail?id=265
==========================
Detailed description of observed behavior:
==========================
It seems that s3fs isn't able to mount to a non empty directory. This
ability does exist in FUSE if specifying the nonempty option. This option
doesn't seem to do anything, and from the source it looks like that s3fs is
checking whether the directory is empty or not. Why isn't this deferred to
FUSE so that the nonempty option can be used? Is there some other
limitation to s3fs that prevents the use of nonempty directories?
I know that mounting to a nonempty directory is not a normal use case, but
it is a valid one. I use it all the time, and shuffling around directories
is cumbersome.
==========================================
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)?
==========================================
Try to mount a bucket to a non empty directory.
===================================================================
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.61
Version of fuse being used (pkg-config --modversion fuse):
System information (uname -a): Custom Linux Kernel
Distro (cat /etc/issue): NA
s3fs command line used (if applicable): s3fs test-bucket /opt/rpath -o
allow_others,nonempty
/etc/fstab entry (if applicable):
s3fs syslog messages (grep s3fs /var/log/syslog):
s3...@googlecode.com
Comment #1 on issue 265 by pasi.oro...@randomtargets.net: Unable to mount
Same issue here.
I'm using GIT for web development, and in order to get Drupal's files
folder into GIT and subsequently mounted as s3fs folder, I need to
put .gitignore file in files folder. And it effectively blocks mounting
S3FS.
Fuse already includes the check for non-empty folders and has the option to
mount regardless, so the functionality in s3fs is redundant. Attached two
patches to remove the functionality from S3FS. One against 1.61 and one
againts trunk.
Attachments:
s3fs-nonempty-1.61.patch 880 bytes
s3fs-nonempty-trunk.patch 880 bytes
s3...@googlecode.com
Status: Fixed
Comment #2 on issue 265 by ggta...@gmail.com: Unable to mount to a non
empty directory
http://code.google.com/p/s3fs/issues/detail?id=265
Hi,
I fixed this issue, s3fs support "nonempty" fuse option.
Please check new source code r410.
Regards,
--
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
s3...@googlecode.com
Comment #3 on issue 265 by kphan...@gmail.com: Unable to mount to a non
empty directory
http://code.google.com/p/s3fs/issues/detail?id=265
Encountered the same issue still on s3fs version 1.69 but with HTTPS. Had
an entry in the /etc/fstab like with nonempty mount option.
s3fs#s3-bucket /mnt/mount-point fuse
_netdev,allow_other,nonempty,url=https://s3.amazonaws.com 0 0
So here I am using HTTPS instead of HTTP which is the default. This fails
to mount the s3 bucket, but if I remove the 'URL' mount option, s3fs is
able to mount the s3-bucket. I was able to get it working with nonempty
mount option and without HTTPS works.
s3fs#s3-bucket /mnt/mount-point fuse _netdev,allow_other,nonempty 0 0
Thanks.
===================================================================
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):
Version of fuse being used (pkg-config --modversion fuse):
System information (uname -a):
Linux ip-10-0-0-191 3.0.0-26-virtual #42-Ubuntu SMP Wed Sep 5 09:14:37 UTC
2012 x86_64 x86_64 x86_64 GNU/Linux
Distro (cat /etc/issue):
Ubuntu 11.10
s3fs command line used (if applicable): N/A
/etc/fstab entry (if applicable):
s3fs#s3-bucket /mnt/mount-point fuse
_netdev,allow_other,nonempty,url=https://s3.amazonaws.com 0 0
s3fs syslog messages (grep s3fs /var/log/syslog): None
s3...@googlecode.com
Status: Accepted
Comment #4 on issue 265 by ggta...@gmail.com: Unable to mount to a non
empty directory
http://code.google.com/p/s3fs/issues/detail?id=265
Hi, kphane01
I'm sorry for this issue is not fixed.
s3fs has "SSL connect error" trouble now, but I'll fix it soon.
So that, I reopen this issue.
Thans.
s3...@googlecode.com
Status: Fixed
Comment #5 on issue 265 by ggta...@gmail.com: Unable to mount to a non
empty directory
http://code.google.com/p/s3fs/issues/detail?id=265
New version v1.70(r434) is updated.
It fixes this issue.
Please use this version, and if you have a trouble, please post new issue.
Thanks a lot.