From owner-freebsd-stable@FreeBSD.ORG Fri Nov 8 13:06:23 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id D90D4877 for ; Fri, 8 Nov 2013 13:06:23 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from dec.sakura.ne.jp (dec.sakura.ne.jp [210.188.226.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7826B2820 for ; Fri, 8 Nov 2013 13:06:23 +0000 (UTC) Received: from fortune.joker.local (180-198-98-49.nagoya1.commufa.jp [180.198.98.49]) (authenticated bits=0) by dec.sakura.ne.jp (8.14.2/8.14.2/[SAKURA-WEB]/20080708) with ESMTP id rA8D6F4V075351 for ; Fri, 8 Nov 2013 22:06:16 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) Date: Fri, 8 Nov 2013 22:06:15 +0900 From: Tomoaki AOKI To: freebsd-stable@freebsd.org Subject: Re: 10.0-BETA3: Unable to access files on SMB share Message-Id: <20131108220615.b17a7bda1c7c04ebbb53da92@dec.sakura.ne.jp> In-Reply-To: <527BB9E2.2060300@bsdforen.de> References: <20131107211935.fef3a2498632fe8da5cf08c6@dec.sakura.ne.jp> <527BB9E2.2060300@bsdforen.de> Organization: Junchoon corps X-Mailer: Sylpheed 3.3.0 (GTK+ 2.24.19; amd64-portbld-freebsd9.2) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Nov 2013 13:06:23 -0000 I already noticed your PR bin/183153, but as I mentioned in The FreeBSD Forums and my forget-me-nots page (http://www.dec.sakura.ne.jp/~junchoon/machine/freebsd-e.html), it has another solution. You can try setting WITH_LIBICONV="YES" in /etc/src.conf and rebuilding world. It works at least for me. (I need some ports requiring libiconv.) Anyway, I tried your patch with mine in new VM running stable/10 amd64, r257814. Looks working fine. Next I'll need trying your patch with WITH_LIBICONV="YES" in /etc/src.conf to make assure they safely coexist. Fortunately, I noticed my patch is committed to head as r257841. But MFC (to stable/10 only, stable/9 and earlier doesn't need it) schedule doesn't shown in commit log message. Did it work for you? On Thu, 07 Nov 2013 17:03:46 +0100 Dominic Fandrey wrote: > On 07/11/2013 13:19, Tomoaki AOKI wrote: > > Sorry for breaking thread. I've read this ML via pipermail and > > subscribed just now for this. > > > > I'm surprised to know that smbfs was working on r255453. > > > > For me, as I already sent PR kern/182963 and posted a thread in The > > FreeBSD Forums, smbfs was not properly working in r255138 and later. > > Same as stable/10, while r255136 (in head) works OK. > > > > In my case, applying the diff I attached to kern/182963 fixes the issue. > > The diff modifies timeout values in 2 lines, as r255138 changes > > sb_timeo in struct sockbuf from int (unit of time is hz) to sbintime_t > > (unit of time is 1/10^33 in seconds, as time in seconds is stored in > > upper half of __int64_t), but sys/netsmb/smb_trantcp.c doesn't chase it. > > smbfs works for me but very unreliably. Timing may well be the issue > here, so I think I will test that patch. > > Please also note my fix for iconv support: > http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/183153 > > -- > A: Because it fouls the order in which people normally read text. > Q: Why is top-posting such a bad thing? > A: Top-posting. > Q: What is the most annoying thing on usenet and in e-mail? > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > -- 青木 知明 [Tomoaki AOKI] junchoon@dec.sakura.ne.jp MXE02273@nifty.com