From owner-freebsd-current Sat Nov 23 20: 1:31 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 688D437B401 for ; Sat, 23 Nov 2002 20:01:30 -0800 (PST) Received: from smtp02.iprimus.net.au (smtp02.iprimus.net.au [210.50.76.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5469443E3B for ; Sat, 23 Nov 2002 20:01:29 -0800 (PST) (envelope-from tim@robbins.dropbear.id.au) Received: from dilbert.robbins.dropbear.id.au ([210.50.218.1]) by smtp02.iprimus.net.au with Microsoft SMTPSVC(5.0.2195.5600); Sun, 24 Nov 2002 15:01:16 +1100 Received: from dilbert.robbins.dropbear.id.au (aw1sxw8315x9c24h@localhost [127.0.0.1]) by dilbert.robbins.dropbear.id.au (8.12.6/8.12.6) with ESMTP id gAO41DEi090192 for ; Sun, 24 Nov 2002 15:01:14 +1100 (EST) (envelope-from tim@dilbert.robbins.dropbear.id.au) Received: (from tim@localhost) by dilbert.robbins.dropbear.id.au (8.12.6/8.12.6/Submit) id gAO41Cmo090191 for current@FreeBSD.ORG; Sun, 24 Nov 2002 15:01:13 +1100 (EST) (envelope-from tim) Date: Sun, 24 Nov 2002 15:01:12 +1100 From: Tim Robbins To: current@FreeBSD.ORG Subject: Re: smbfs workaround Message-ID: <20021124150112.A90113@dilbert.robbins.dropbear.id.au> References: <20021124143440.A88845@dilbert.robbins.dropbear.id.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20021124143440.A88845@dilbert.robbins.dropbear.id.au>; from tjr@FreeBSD.ORG on Sun, Nov 24, 2002 at 02:34:40PM +1100 X-OriginalArrivalTime: 24 Nov 2002 04:01:17.0228 (UTC) FILETIME=[23926EC0:01C2936E] 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 On Sun, Nov 24, 2002 at 02:34:40PM +1100, Tim Robbins wrote: > I'd appreciate it if the people who were experiencing problems with > smbfs could try this patch and let me know how it goes. > > The patch adds two sysctls, net.smb.readwritex and net.smb.reqdatasize. > readwritex controls whether LARGE_READX and LARGE_WRITEX requests are > used, and is off by default. reqdatasize controls the maximum number of > bytes of data to request from the user with each read request, and it > defaults to a fairly conservative value of 4096. > > Setting readwritex to 0 makes smbfs work when the server OS is Windows XP. > Setting reqdatasize to 4096 makes it work when the server OS is > FreeBSD 4.7-RELEASE-p2 w/ Samba 2.2.3a. > > This patch is just a temporary workaround, of course. I have not been > able to track down the real problem. I should note that reqdatasize=4096 works for reading files, but not writing them. reqdatasize=1024 allows files to be written, but it looks like they are getting corrupted. Could this be a bug in the mbuf or mchain code or a change in semantics that netsmb has not been updated for? Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message