From owner-freebsd-current Sun Dec 30 19: 0:33 2001 Delivered-To: freebsd-current@freebsd.org Received: from gull.prod.itd.earthlink.net (gull.mail.pas.earthlink.net [207.217.120.84]) by hub.freebsd.org (Postfix) with ESMTP id 5537537B438 for ; Sun, 30 Dec 2001 19:00:29 -0800 (PST) Received: from dialup-209.245.132.248.dial1.sanjose1.level3.net ([209.245.132.248] helo=mindspring.com) by gull.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16KsgX-0004PP-00; Sun, 30 Dec 2001 19:00:21 -0800 Message-ID: <3C2FD4C8.1447A97E@mindspring.com> Date: Sun, 30 Dec 2001 19:00:24 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Sheldon Hearn Cc: Michal Mertl , current@freebsd.org Subject: Re: ntfs and sendfile problem (corrupted data) References: <88088.1009714357@axl.seasidesoftware.co.za> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Sheldon Hearn wrote: > On Sun, 30 Dec 2001 01:53:08 +0100, Michal Mertl wrote: > > I have ntfs partition mounted ro on current. I can read from it without > > problems. But I noticed I get corrupted data (the corrupted file has > > right size but contains mostly zeros) when using ftpd to read them. > > > > I'm pretty sure the problem is thus in sendfile(2) and/or ntfs fs support. > > See also PR bin/31692, which reports simmilar problems using ftpd and > smbfs. See my request for feedback, which ought to help verify that > it's sendfile(2) causing the problem. FreeBSD -current uses "external" mbufs. Previous versions did not. It's the new mbuf code. Look at how it gets the things that it points to. The problem is that the references are transient, and it assumes they aren't. I don't have a ready fix. You can revert the sendfile code pretty easily to the 4.3 version. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message