Running unstable (sid). Have pure-ftpd server (1.0.21-8) running on a Debian Etch system.
Server mounted as follows: curlftpfs -o user=user:password etch /mnt

When mounted, the 'mount' command shows:
/dev/hda1 on / type ext3 (rw,errors=remount-ro)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
procbususb on /proc/bus/usb type usbfs (rw)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
curlftpfs#ftp://etch/ on /mnt type fuse (rw,nosuid,nodev)

All commands run as root

Problem 1:
Attempt to copy a 1 MB file from local fs to server with command 'cp file1M /mnt/' results in error
message "cp: cannot create regular file `/mnt/file1M': No such file or directory". The command
results in a 0 byte file on the server. This happens if file doesn't exist on server. A 2nd
attempt to copy the file succeeds once the 0 byte file exists on the server, and subsequent copy
operations for the same file work as long as the file exists. Deleting the file on the server, and
then runing same copy command results in the same error as above.

Problem 2:
Copying the same 1M file from server to local fs works, but time to copy varies wildy from
almost instantaneous (< .1 sec based on time command) to 1 minute. In this case, it doesn't seem
to matter if the file already exists on the local fs or not.

I had similar problems running Lenny, and upgraded to sid/unstable to try the newer version of curlftpfs.
I can provide additional information if needed.

tags 499153 +confirmed
thanks

I has verified the problem. This bug occurs when ftp server is pure-ftpd.

The bug occurs when ftp client request to transfer data(stor filename)
and the transfer is not finished yet,
and ftp client run command *site chmod filename mode* .

The command site chmod result in ftp server disconnect to client.

The detail of my diagnose by telnet and netcat can find here[1].
In my opinion, this bug should be pureftp's bug.
I will file a bug against pureftp. Whether fix this bug or not depends
on developer of curlftpfs and pureftp.

[1] http://lists.debian.org/debian-mentors/2008/09/msg00220.html

tags 499153 +confirmed

installing package curlftpfs_0.9.1-3+b2 solves the problem.

You mean downgrading the curlftpfs package solves the problem?

My curlftpfs, currently v0.9.2-1, still exhibit such problem:

< 220---------- Welcome to Pure-FTPd [privsep] [TLS] ----------
...
< 150 Accepted data connection
* Re-using existing connection! (#0) with host ...
* Connected to ftp.host.com (207.210.86.xxx) port 21 (#0)
* Request has same path as previous transfer
* Remembering we are in dir ""
< 550 Could not change perms on test.txt: No such file or directory
* QUOT string not accepted: SITE CHMOD 660 test.txt
* Connection #0 to host ftp.host.com left intact
ftpfs: operation ftpfs_chmod failed because Operation not permitted
* Re-using existing connection! (#0) with host ftp.host.com
* Connected to ftp.host.com (207.210.86.xxx) port 21 (#0)
* Request has same path as previous transfer
* Connect data stream passively
< 227 Entering Passive Mode (207,210,86,xxx,187,141)
*   Trying 207.210.86.xxx... * connected
* Connecting to 207.210.86.xxx (207.210.86.xxx) port 48013
< 150 Accepted data connection
* Maxdownload = -1
* Remembering we are in dir ""
< 226-Options: -a -l
< 226 6 matches total
* Connection #0 to host ftp.host.com left intact
ftpfs: operation ftpfs_getattr failed because No such file or directory
* Remembering we are in dir ""
< 226-0 Kbytes used (0%) - authorized: 6144000 Kb
< 226 File successfully transferred
* Uploaded unaligned file size (0 out of 4294967295 bytes)
* Connection #0 to host ftp.host.com left intact
< 221-Goodbye. You uploaded 0 and downloaded 0 kbytes.

You mean downgrading the curlftpfs package solves the problem?

My curlftpfs, currently v0.9.2-1, still exhibit such problem:

< 220---------- Welcome to Pure-FTPd [privsep] [TLS] ----------
...
< 150 Accepted data connection
* Re-using existing connection! (#0) with host ...
* Connected to ftp.host.com (207.210.86.xxx) port 21 (#0)
* Request has same path as previous transfer
* Remembering we are in dir ""
< 550 Could not change perms on test.txt: No such file or directory
* QUOT string not accepted: SITE CHMOD 660 test.txt
* Connection #0 to host ftp.host.com left intact
ftpfs: operation ftpfs_chmod failed because Operation not permitted
* Re-using existing connection! (#0) with host ftp.host.com
* Connected to ftp.host.com (207.210.86.xxx) port 21 (#0)
* Request has same path as previous transfer
* Connect data stream passively
< 227 Entering Passive Mode (207,210,86,xxx,187,141)
*   Trying 207.210.86.xxx... * connected
* Connecting to 207.210.86.xxx (207.210.86.xxx) port 48013
< 150 Accepted data connection
* Maxdownload = -1
* Remembering we are in dir ""
< 226-Options: -a -l
< 226 6 matches total
* Connection #0 to host ftp.host.com left intact
ftpfs: operation ftpfs_getattr failed because No such file or directory
* Remembering we are in dir ""
< 226-0 Kbytes used (0%) - authorized: 6144000 Kb
< 226 File successfully transferred
* Uploaded unaligned file size (0 out of 4294967295 bytes)
* Connection #0 to host ftp.host.com left intact
< 221-Goodbye. You uploaded 0 and downloaded 0 kbytes.

Hi,

I have been investigating this bug too. It seems to be a pure-ftpd bug:
the server returns before the uploaded file is complete. curlftpfs then
tries to examine the uploaded file, which isn't present giving an ENOENT
error.

Later versions of pure-ftpd seem OK. I have just tested against
pure-ftpd 1.0.24 and curlftpfs 0.9.2-1 works fine with that.

There is an entry in the pure-ftpd changelog for version 1.0.22 which
seems a likely fix:

 - Don't respond to server that an upload succeeded before the temporary
   file has been renamed.

I also can confirm that curlftpfs 0.9.1 works for me against the older,
buggy pure-ftpd.

Mark

Dear Customer,

FedEx courier was unable to contact you for your parcel delivery.

Download postal receipt attached to e-mail!

All the best,
Marvin Barton,
Station Manager.

Dear Customer,

UPS courier was unable to contact you for your parcel delivery.

Review the document that is attached to this e-mail!

With thanks and appreciation,
Jamie Pace,
UPS Delivery Manager.

Ich beabsichtige, Ihnen einen Teil meines Vermögens als freiwillige finanzielle Spende an Sie zu geben. Reagieren Sie auf partake.contact meine E-Mail (wang.jianlin@yandex.com)
Wang Jianlin
Wanda Gruppe

Diese E-Mail fordert Sie strikt auf, sich für eine große Investition mit
mir zusammenzutun, um weitere Informationen zu erhalten.
Mit freundlichen Grüßen,
Khvostova Zhanna