Which server/client do you except linux ?
----- Original Message -----
From: "Alon Altman" <[EMAIL PROTECTED]>
To: "Linux-IL" <[EMAIL PROTECTED]>
Sent: Friday, November 23, 2001 6:58 AM
Subject: NFSS and time problem


> Hi,
>   I have two problems in my home network, and I'm not sure if they're
related.
> I have a client PC which mounts /home as an NFS share on the server. Once
in
> a while, all access to the mounted directory is stalled and the following
> data is transferred on the network:
>
> 06:45:23.270071 192.168.1.2.1402759134 > 192.168.1.1.2049: 100 null (DF)
> 06:45:23.271049 192.168.1.1.2049 > 192.168.1.2.1402759134: reply ok 24
null (DF)
> 06:45:23.271105 192.168.1.2.1302095838 > 192.168.1.1.2049: 1100 write fh
96,1/197709 960 bytes @ 0x04019e000 (DF)
> 06:45:24.670061 192.168.1.2.1302095838 > 192.168.1.1.2049: 1100 write fh
96,1/197709 960 bytes @ 0x04019e000 (DF)
> 06:45:27.470062 192.168.1.2.1302095838 > 192.168.1.1.2049: 1100 write fh
96,1/197709 960 bytes @ 0x04019e000 (DF)
> 06:45:33.070065 192.168.1.2.1302095838 > 192.168.1.1.2049: 1100 write fh
96,1/197709 960 bytes @ 0x04019e000 (DF)
> 06:45:44.270083 192.168.1.2.1419536350 > 192.168.1.1.2049: 100 null (DF)
> 06:45:44.270563 192.168.1.1.2049 > 192.168.1.2.1419536350: reply ok 24
null (DF)
> 06:45:44.270619 192.168.1.2.1302095838 > 192.168.1.1.2049: 1100 write fh
96,1/197709 960 bytes @ 0x04019e000 (DF)
> 06:45:47.070068 192.168.1.2.1302095838 > 192.168.1.1.2049: 1100 write fh
96,1/197709 960 bytes @ 0x04019e000 (DF)
> 06:45:52.670060 192.168.1.2.1302095838 > 192.168.1.1.2049: 1100 write fh
96,1/197709 960 bytes @ 0x04019e000 (DF)
> 06:46:03.870068 192.168.1.2.1302095838 > 192.168.1.1.2049: 1100 write fh
96,1/197709 960 bytes @ 0x04019e000 (DF)
> 06:46:04.115689 192.168.1.1.2049 > 192.168.1.2.1302095838: reply ok 136
write [|nfs] (DF)
>
>   This cannot be a physical link problem, as other packets get transferred
> correctly on the same link. When this happens, it's always with NFS V3
WRITE
> calls. Any ideas?
>
>   A second, probably unrealted problem I'm having is that the system clock
> on the client machine tends to 'jump' two hours forward, while remaining
in
> the correct timezone (IST). I'm not sure if this happens only on boot or
> also on a running system.
>
>   I'm running MDK8.1.
>
>   Alon
>
> --
> This message was sent by Alon Altman ([EMAIL PROTECTED]) ICQ:1366540
> The RIGHT way to contact me is by e-mail. I am otherwise nonexistent :)
> --------------------------------------------------------------------------
> "jackpot:  you may have an unneccessary change record"
> -- message from "diff"
>
>
> =================================================================
> To unsubscribe, send mail to [EMAIL PROTECTED] with
> the word "unsubscribe" in the message body, e.g., run the command
> echo unsubscribe | mail [EMAIL PROTECTED]
>
>


=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]

Reply via email to