Latest bk 2.5;
Just booted with NFS root and noticed these new error messages in dmesg:
NFS: server cheating in read reply: count 4096 > recvd 1000
NFS: giant filename in readdir (len 0xcb2d2053)!
Anybody know what this means?
Andrew Walrond
>>>>> " " == Andrew Walrond <[email protected]> writes:
> Latest bk 2.5; Just booted with NFS root and noticed these new
> error messages in dmesg:
> NFS: server cheating in read reply: count 4096 > recvd 1000
> NFS: giant filename in readdir (len 0xcb2d2053)!
> Anybody know what this means?
It means that the client can only see 1000 out of a promised 4096
bytes. Either the client or the server has a bug. A tcpdump should
sort it out.
Cheers,
Trond
Andrew Walrond, Mon, Feb 10, 2003 17:16:23 +0100:
> Latest bk 2.5;
2.5.70 here
> Just booted with NFS root and noticed these new error messages in dmesg:
>
> NFS: server cheating in read reply: count 4096 > recvd 1000
> NFS: giant filename in readdir (len 0xcb2d2053)!
>
I have almost the same, but without the "server cheating":
16:12:06 NFS: giant filename in readdir (len c8f2d9f0)!
got this by doing "find /mnt -type f | xargs cat > /dev/null".
The server is 2.4.20-ck4 (Con Kolivas patches: aavm, preempt, lolatency).
Also seen something about 7 min later (the find was still running):
16:19:22 nfs: server server1 not responding, still trying
16:19:25 nfs: server server1 OK
The "server1" (my desktop machine) was doing almost nothing at this time
and felt ok (still does).
-alex