Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 07 Nov 2013 17:03:46 +0100
From:      Dominic Fandrey <kamikaze@bsdforen.de>
To:        Tomoaki AOKI <junchoon@dec.sakura.ne.jp>, freebsd-stable@freebsd.org
Subject:   Re: 10.0-BETA3: Unable to access files on SMB share
Message-ID:  <527BB9E2.2060300@bsdforen.de>
In-Reply-To: <20131107211935.fef3a2498632fe8da5cf08c6@dec.sakura.ne.jp>
References:  <20131107211935.fef3a2498632fe8da5cf08c6@dec.sakura.ne.jp>

next in thread | previous in thread | raw e-mail | index | archive | help
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? 



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