Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 432 by
just2reg...@gmail.com: FreeBSD issues
http://code.google.com/p/s3fs/issues/detail?id=432
Detailed description of observed behavior:
I'm working with several FreeBSD servers installed on Amazon instances, now
I'm trying to mount some S3 buckets using the fuse-s3fs package, it somehow
works but I have several issues:
1. For some reason, the reported available space is 8Gb (I don't know where
that amount came from, S3 is supposed to have unlimited space (although I
realise that some specific size must be defined), anyway, I found that I
can't store more than 5Gb on the mounted filesystem, anybody knows why?
also, how can I overcome this limitation?
2. To mount the S3 bucket, I did this:
s3fs <bucket-name> /mnt -ouse_cache=/tmp,allow_other
when I execute 'df -h' I see this:
Filesystem Size Used Avail Capacity Mounted on
/dev/ada0a 9.7G 9.7G -788M 109% /
devfs 1.0K 1.0K 0B 100% /dev
/dev/xbd5p1 29G 5.5G 21G 21% /usr/local/www
df: File system /mnt does not have a block size, assuming 512.
/dev/fuse 8.0G 0B 8.0G 0% /mnt
You can see the / has 109% ! It seems the space used in S3 is counted as
space used in /, I guess I'm doing something wrong when mounting the
filesystem, anybody know what?
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):
Version of fuse being used (pkg-config --modversion fuse):
System information (uname -a):
Distro (cat /etc/issue):
s3fs command line used (if applicable):
/etc/fstab entry (if applicable):
s3fs syslog messages (grep s3fs /var/log/syslog):
--
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