On Sun, Apr 6, 2008 at 9:45 PM, Doug Rabson <[EMAIL PROTECTED]> wrote:
> This patch should fix the problem. Sorry for the inconvenience.
It works fine now, thank you very much!
Tz-Huan
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.or
On 6 Apr 2008, at 11:48, Tz-Huan Huang wrote:
On Sun, Apr 6, 2008 at 5:53 PM, Doug Rabson <[EMAIL PROTECTED]> wrote:
One thing I did notice is that the client appears to be trying to
connect
to the server on tcp port 751 and the server is rejecting that
connection.
I'm not sure I trust the
On 6 Apr 2008, at 11:30, Tz-Huan Huang wrote:
On Sun, Apr 6, 2008 at 5:21 PM, Doug Rabson <[EMAIL PROTECTED]> wrote:
Could you possibly try again with 'tcpdump -w -s 1500' - the
packets
were truncated which made it difficult to analyse.
Sure, it's available here:
http://w.csie.org/~tzh
On Sun, Apr 6, 2008 at 5:53 PM, Doug Rabson <[EMAIL PROTECTED]> wrote:
> One thing I did notice is that the client appears to be trying to connect
> to the server on tcp port 751 and the server is rejecting that connection.
> I'm not sure I trust the output of sockstat - could you show me the outp
On Sun, Apr 6, 2008 at 5:21 PM, Doug Rabson <[EMAIL PROTECTED]> wrote:
>
> Could you possibly try again with 'tcpdump -w -s 1500' - the packets
> were truncated which made it difficult to analyse.
Sure, it's available here:
http://w.csie.org/~tzhuan/tmp/tcpdump2.raw
Thanks,
Tz-Huan
___
On 6 Apr 2008, at 09:58, Tz-Huan Huang wrote:
On Sun, Apr 6, 2008 at 3:45 PM, Doug Rabson <[EMAIL PROTECTED]> wrote:
It would be useful to get a packet trace from tcpdump (e.g. tcpdump
-w
) that shows what happens on the wire when the linux client
fails to
lock a file on the freebsd serv
On 6 Apr 2008, at 09:58, Tz-Huan Huang wrote:
On Sun, Apr 6, 2008 at 3:45 PM, Doug Rabson <[EMAIL PROTECTED]> wrote:
It would be useful to get a packet trace from tcpdump (e.g. tcpdump
-w
) that shows what happens on the wire when the linux client
fails to
lock a file on the freebsd serv
On Sun, Apr 6, 2008 at 3:45 PM, Doug Rabson <[EMAIL PROTECTED]> wrote:
>
> It would be useful to get a packet trace from tcpdump (e.g. tcpdump -w
> ) that shows what happens on the wire when the linux client fails to
> lock a file on the freebsd server.
Since the nfs server is in production now,
On 6 Apr 2008, at 07:38, Tz-Huan Huang wrote:
On Sun, Apr 6, 2008 at 2:05 PM, Rong-en Fan <[EMAIL PROTECTED]> wrote:
On Sun, Apr 6, 2008 at 1:18 PM, Tz-Huan Huang <[EMAIL PROTECTED]>
wrote:
Hi,
Thanks for your suggestion, but we don't accept this workaround.
After doing binary searching, I
On Sun, Apr 6, 2008 at 2:05 PM, Rong-en Fan <[EMAIL PROTECTED]> wrote:
> On Sun, Apr 6, 2008 at 1:18 PM, Tz-Huan Huang <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > Thanks for your suggestion, but we don't accept this workaround.
> >
> > After doing binary searching, I find that this commit bre
On Sun, Apr 6, 2008 at 1:18 PM, Tz-Huan Huang <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Thanks for your suggestion, but we don't accept this workaround.
>
> After doing binary searching, I find that this commit break the working
> lockd:
>
> http://lists.freebsd.org/pipermail/cvs-src/2008-March/089
Hi,
Thanks for your suggestion, but we don't accept this workaround.
After doing binary searching, I find that this commit break the working lockd:
http://lists.freebsd.org/pipermail/cvs-src/2008-March/089037.html
I have rolled back the lockd.c to 1.20 in our nfs server and it works
fine as b
I have the similar problem when FreeBSD 7 client + FreeBSD 6 server.
Now, I use ' mount_nfs -L' on the client to do local locking only. Of
course, it may cause other problem.
2008/4/2, Tz-Huan Huang <[EMAIL PROTECTED]>:
>
> Hi,
>
> We have one nfs server (Mar 27's 7-stable, AMD64) and many clien
Hi,
We have one nfs server (Mar 27's 7-stable, AMD64) and many clients.
One of the client is also 7-stable(Mar 30's, i386), and others are Debian
Linux. The problem is that the fcntl lock works fine on FreeBSD client
but not on linux ones.
We have tested the linux server + linux client, and they
14 matches
Mail list logo
