> Got this
>
>
> ftp> bin
> 200 Switching to Binary mode.
> ftp> get SLES-11-SP1-DVD-x86_64-GM-DVD1.iso
> local: SLES-11-SP1-DVD-x86_64-GM-DVD1.iso remote: SLES-11-SP1-DVD-
> x86_64-GM-DVD1.iso
> 229 Entering Extended Passive Mode (|||19555|)
> 150 Opening BINARY mode data connection for SLES-11-SP1-DVD-x86_64-GM-
> DVD1.iso (3036372992 bytes).
> 0%
> |
> | 4789 KB 4.67 MB/s 10:18 ETAftp: SLES-11-SP1-DVD-x86_64-GM-
> DVD1.iso: short write
> 0%
> |
> | 4789 KB 4.67 MB/s 10:18 ETA
> 426 Failure writing network stream.
> 4904488 bytes received in 00:01 (4.66 MB/s)
>
>
> Environment:
> SLES11-SP1, x86_64, JAVA_HOME=/usr/java/jdk1.6.0_22, RPMs are 1.3.0.81
> as confirmed on their web pages. Filesystem is mounted locally,
> access policy is VOLUME.
>
> A local copy works fine.
Is there any meaningful log output in /var/log/xtreemfs wrt. this problem?
> Also, if access policy is volume and mount point is 777 and mode of
> the volume at creation is 777, why can other users not see the mount
> point or access the volume?
>
It's because FUSE disallows other users access to a mount point unless
it was mounted with '-o allow_other'. Please try to mount the volume
with 'mount.xtreemfs -o allow_other ...'.
Best regards,
Jan
Thank you for your report and sorry for my late reply.
First of all I cannot reproduce your problem: Could you please give
detailed instructions how to reproduce this error, preferably using our
public demo server demo.xtreemfs.org/demo and a publicly available FTP file?
Here's what I tried so far:
# Run client in debug mode in foreground and mount demo server:
mount.xtreemfs localhost/ftp ~/mnt -d DEBUG -f
# Download a file from a FTP in another shell:
cd ~/mnt
ftp cdimage.debian.org
# use "anonymous" and "b...@bla.net" as user and password
# inside the ftp session, run:
ftp> cd /debian-cd/current/amd64/iso-dvd
ftp> get debian-6.0.3-amd64-DVD-1.iso
Download works as expected. My system is an Ubuntu 10.10 Maverick with
Fuse 2.8.5 installed and the Ubuntu "ftp" package 0.17-23.
About the error itself:
It seems "ftp" is not able to cope with the fact that a write() did
actually write less bytes than requested. Therefore it complains about
such a "short write" and stops the download.
However, the XtreemFS client itself does never do a short write: It does
always write all bytes it got from Fuse itself and retries until it
managed to write everything or returns an error.
If you enable the debug output in the client with -d DEBUG, you can see
a line for every write request received from Fuse:
xtreemfs_fuse_write /debian-6.0.3-amd64-DVD-1.iso size: 17376
Here the XtreemFS client had to write 17376 bytes. On my system these
numbers of bytes to be written were identical to the output of an strace
of the "ftp" session.
So far I don't know why the "ftp" program should see a "short write".
Have you already tried to mount it with -o directio?
Besides that, it would be great if we could reproduce the error on my
machine so that I can further look into it.
Best regards,
Michael
Unfortunately, this does not really help. I do not see any obvious
problems. However, you can see in the log, that the write() was
interrupted (see the two lines containing "INTERRUPT triggered, setting
TLS pointer" and "Caught interrupt, aborting sync request.")
I'm wondering who did interrupt the write(). I guess you did not press
Ctrl + C? So it probably comes from the "ftp" program. Can you please
check if the interrupt is issued by "ftp" after it did abort with the
"short write" error?
Besides that, please try the following two things: Test the client with
the mount options -o direct_io and --interrupt-signal=0 (each separately).
Could you please also check if you have already the latest version from
the unstable repository
(http://download.opensuse.org/repositories/home:/xtreemfs:/unstable/)?
The best way to track down this issue is if I could reproduce the error
locally. Can you tell me please which Linux distribution you are using
and what's the package version of the "ftp" program? Then I would setup
a local VM and try to reproduce the issue.
Thank you for your help,
Best regards,
Michael