From owner-freebsd-current Thu Nov 21 11:20:33 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D449337B401 for ; Thu, 21 Nov 2002 11:20:31 -0800 (PST) Received: from conure.mail.pas.earthlink.net (conure.mail.pas.earthlink.net [207.217.120.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 909B043E42 for ; Thu, 21 Nov 2002 11:20:31 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0097.cvx40-bradley.dialup.earthlink.net ([216.244.42.97] helo=mindspring.com) by conure.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 18EwsH-0007lh-00; Thu, 21 Nov 2002 11:20:29 -0800 Message-ID: <3DDD31AE.92C08AD6@mindspring.com> Date: Thu, 21 Nov 2002 11:19:10 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: kalts@estpak.ee Cc: freebsd-current@freebsd.org Subject: Re: smbfs problems References: <20021121130830.GB1907@tiiu.internal> <20021121132223.GA2076@tiiu.internal> 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 Vallo Kallaste wrote: > Sorry forgot to add one detail. Althought dd'ing the same file to > smbfs mount works, it'll sometimes modify the file being copied > (size is different). It doesn't happen reliably, sometimes the file > is copied fine, sometimes not. At the times the file isn't copied > right there's an error message: > > root:vallo# dd if=testfile of=/mnt/vallo/test1 > dd: /mnt/vallo/test1: Bad address > 9356+0 records in > 9355+0 records out > 4789760 bytes transferred in 20.350003 secs (235369 bytes/sec) > > It seems to me that adding conv=sync flag to dd removes the > abovementioned failure case. 10 tries of dd with this flag added did > fine. The 'conv-sync' flag to 'dd' pads the operation out to a record boundary, if the input of the operation is not a full record in length. This observation is consistent with an incomplete final write, for lack of data. Probably this has to do with the TCP_PUSH option and/or the SMB server's connection flags. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message