public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Andrew Walrond <andrew@walrond.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NFS root: New error messages in latest bk
Date: 10 Feb 2003 17:57:28 +0100	[thread overview]
Message-ID: <shsfzqwxedj.fsf@charged.uio.no> (raw)
In-Reply-To: <3E47D057.4070205@walrond.org>

>>>>> " " == Andrew Walrond <andrew@walrond.org> 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

  reply	other threads:[~2003-02-10 16:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-10 16:16 NFS root: New error messages in latest bk Andrew Walrond
2003-02-10 16:57 ` Trond Myklebust [this message]
2003-05-27 12:34 ` Alex Riesen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=shsfzqwxedj.fsf@charged.uio.no \
    --to=trond.myklebust@fys.uio.no \
    --cc=andrew@walrond.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox