Issue 223 in s3fs: 'mount -o remount ...' gives 's3fs: MOUNTPOINT directory ... is not empty'

[s3...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 223 by OneStran...@gmail.com: 'mount -o remount ...' gives 's3fs:
MOUNTPOINT directory ... is not empty'
http://code.google.com/p/s3fs/issues/detail?id=223

Detailed description of observed behavior:

The summary really says it all.
When I unmount and check the contents of the directory, it really IS empty.

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)?

Works every time I've tested it so far.

===================================================================
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):
2.8.5

System information (uname -a):
Linux testserver 2.6.32-33-server #71-Ubuntu SMP Wed Jul 20 17:42:25 UTC
2011 x86_64 GNU/Linux

Distro (cat /etc/issue):
Ubuntu 10.04.3 LTS

s3fs command line used (if applicable):

/etc/fstab entry (if applicable):
s3fs#bucket /mnt/s3 fuse
rw,noauto,noatime,noexec,uid=222,gid=222,allow_other,url=https://s3.amazonaws.com
0 0

s3fs syslog messages (grep s3fs /var/log/syslog):
(nothing)

[s3...@googlecode.com]

Comment #1 on issue 223 by ben.lema...@gmail.com: 'mount -o remount ...'

gives 's3fs: MOUNTPOINT directory ... is not empty'
http://code.google.com/p/s3fs/issues/detail?id=223

I'm unable to reproduce this, what does `mount` show? Is it possible s3fs
is still running?

[s3...@googlecode.com]

Comment #2 on issue 223 by OneStran...@gmail.com: 'mount -o remount ...'

gives 's3fs: MOUNTPOINT directory ... is not empty'
http://code.google.com/p/s3fs/issues/detail?id=223

`mount` shows:
...
s3fs on /mnt/s3 type fuse.s3fs (rw,noexec,noatime,allow_other)

But that's the point, a REmount doesn't work for me on that OS. Just tried
a different VM as well, a fairly clean install of Ubuntu Lucid, not running
inside Amazon, S3FS installed by "apt-get install mime-support
libcurl4-openssl-dev libxml2 libxml2-dev" and "make install"ing
fuse-2.8.5.tar.gz and s3fs-1.61.tar.gz

Trying to give you more debug info, I tried running "s3fs -d -f bucket
/mnt/s3" in a separate window etc. etc., but the shell returned immediately
with:
---
s3fs_check_service
s3fs: HTTP: 400 - report this to the s3fs developers
---

checking the logs, I see:
---
Oct 10 17:58:34 ubuntu s3fs: curlCode: 0 msg: No error
Oct 10 17:58:34 ubuntu s3fs: responseCode: 200
Oct 10 17:58:34 ubuntu s3fs: URL is http://s3.amazonaws.com/bucket?location
Oct 10 17:58:34 ubuntu s3fs: URL changed is
http://bucket.s3.amazonaws.com?location
Oct 10 17:58:34 ubuntu s3fs: curlCode: 22 msg: HTTP response code said
error
Oct 10 17:58:34 ubuntu s3fs: responseCode: 400
---

I can try a more recent build of s3fs if you'd like. and by the way, my vm
setup reaches the internet through a squid proxy - not sure if this is
relevant.

[s3...@googlecode.com]

Updates:
Status: Fixed

Comment #3 on issue 223 by ggta...@gmail.com: 'mount -o remount ...'

gives 's3fs: MOUNTPOINT directory ... is not empty'
http://code.google.com/p/s3fs/issues/detail?id=223

Hi

v1.68 supports "noempty" mount option.
It solves this issue.

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