Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 15 Nov 2005 22:37:34 -0600 (CST)
From:      David Kelly <dkelly@hiwaay.net>
To:        FreeBSD-gnats-submit@FreeBSD.org
Subject:   bin/89100: premature EOF with ftpd on some large files
Message-ID:  <20051116043734.B848A69B3@Grumpy.DynDNS.org>
Resent-Message-ID: <200511160440.jAG4eMSl090665@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help

>Number:         89100
>Category:       bin
>Synopsis:       premature EOF with ftpd on some large files
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Nov 16 04:40:21 GMT 2005
>Closed-Date:
>Last-Modified:
>Originator:     David Kelly
>Release:        FreeBSD 6.0-STABLE i386
>Organization:
>Environment:
System: FreeBSD Grumpy.DynDNS.org 6.0-STABLE FreeBSD 6.0-STABLE #2: Sun Nov 13 19:23:43 CST 2005 dkelly@Grumpy.DynDNS.org:/usr5/obj/usr/src/sys/OPUS i386


	
>Description:

Using ftpd to send large files often results in: "226 Transfer finished
due to premature end of file."

For several days thought the problem was related to geom_vinum as most
of my big files are on a striped vinum volume whose creation dates back
to 5.0. Largely because /bin/cp could read the files correctly, write to
the simple volume on /dev/ad0s1f, and then ftpd had no problem reading
the file.

Then I started having the same problem with large files on /dev/ad0s1f
(/usr). The common denominator is ftpd.

ftp> get bigfile /dev/null
local: /dev/null remote: bigfile
229 Entering Extended Passive Mode (|||56427|)
150 Opening BINARY mode data connection for 'bigfile' (4700241920 bytes).
226 Transfer finished due to premature end of file.
405274624 bytes received in 00:08 (46.06 MB/s)
ftp> quit

% dc
10 i 16 o
4700241920 p
118280000
405274624 p
18280000

Every time I pay attention the received file is exactly 4G short. Doesn't
matter if it is written to /dev/null, differnt filesystem, or same
filesystem.

	
>How-To-Repeat:

Once a file is a problem it is always a problem in the same place. I
have not been able to create a large file which immediately has this
problem. Have not tested every large file immediately after creation,
only find this problem the next day or two.

Seems I have this problem with every file written with 5.4 on the
geom_vinum filesystem.

	
>Fix:

No permanent cure but ftpd has been able to read every fresh copy made
with /bin/cp.

	


>Release-Note:
>Audit-Trail:
>Unformatted:



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051116043734.B848A69B3>