Issue 449 in s3fs: Files created with dd either directly on the s3f3 mounted volume or copied to it are 0k in size

[s3...@googlecode.com]

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

New issue 449 by yawke...@gmail.com: Files created with dd either directly
on the s3f3 mounted volume or copied to it are 0k in size
https://code.google.com/p/s3fs/issues/detail?id=449

Files created with dd either directly on the s3f3 mounted volume or copied
to it are 0k in size


When I attempt to create some dummy test data with either the fallocate or
dd command on the s3fs mounted volume, the resulting file is 0k in size no
matter what size I try to make it.

If I create the file on a local partition using dd of fallocate, the file
is created with the correct size. However, when I attempt to copy it to the
s3fs mounted volume, the file size is 0k.

I am able to other local files from the system to the s3fs mounted volume
and the size is reported correctly.


===================================================================
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):
Amazon Simple Storage Service File System V1.78 with OpenSSL

Version of fuse being used (pkg-config --modversion fuse):
2.9.2

System information (uname -a):


Linux ip-xxx-xxx-xxx-xxx 3.13.0-36-generic #63-Ubuntu SMP Wed Sep 3
21:30:07 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

Distro (cat /etc/issue):
Ubuntu 14.04.1 LTS \n \l

s3fs command line used (if applicable):
sudo dd if=/dev/zero of=1m.img bs=1 count=0 seek=1M

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

ubuntu@ip-xxx-xxx-xxx-xxx:/mnt/s3$ grep s3fs /var/log/syslog
Jan 22 19:46:37 ip-xxx-xxx-xxx-xxx s3fs: init v1.78 (OpenSSL)
ubuntu@ip-xxx-xxx-xxx-xxx:/mnt/s3$

Any suggestions would be greatly appreciated. Thank you!

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