All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Felipe Alfaro Solana" <felipe_alfaro@linuxmail.org>
To: nfs@lists.sourceforge.net
Subject: Bug: 2.5.47 NFS reports giant filename in readdir
Date: Mon, 18 Nov 2002 20:21:19 +0100	[thread overview]
Message-ID: <20021118192119.12935.qmail@linuxmail.org> (raw)

Hello,

I'm currently testing kernel 2.5.47 on a RedHat 8.0 server machine, serving files through NFS among many other things. Since I'm using 2.5.47, there are several directories I'm unable to browse using NFS from my laptop running 2.4.20-rc1.

This is "/etc/exports" on the 2.5.47 machine:

/                        192.168.0.0/255.255.255.0(rw,async,no_root_squash)
/data                    192.168.0.0/255.255.255.0(rw,async,no_root_squash)

And these are the commands I use on the 2.4.20-rc1 machine to mount and browse the directory using NFS:

# mount glass:/data /net/glass/data
# cd /net/glass/data/Jpgs/Jpgs11
# ls

The last command produces an empty listing, even when the directory contains 16694 files on it. When I do a "dmesg" on my 2.4.20-rc1 machine, I see the following errors:

NFS: giant filename in readdir (len 14000000)!
NFS: giant filename in readdir (len 40404000)!
NFS: giant filename in readdir (len f000000)!

I haven't been able to find any debugging information or message on the server side. dmesg reports nothing, and all log files contain no clue about this error.

I think this must be a bug on 2.5.47 as this works great when using the latest RedHat 8.0 kernel on the server side.

I can't supply more information as I don't know exactly where to start looking.
Please, do not hesitate to contact me for further information or assistance.

Thank you very much!

Sincerely,

   Felipe Alfaro Solana

-- 
______________________________________________
http://www.linuxmail.org/
Now with POP3/IMAP access for only US$19.95/yr

Powered by Outblaze


-------------------------------------------------------
This sf.net email is sponsored by: To learn the basics of securing 
your web site with SSL, click here to get a FREE TRIAL of a Thawte 
Server Certificate: http://www.gothawte.com/rd524.html
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

             reply	other threads:[~2002-11-18 19:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-18 19:21 Felipe Alfaro Solana [this message]
2002-11-18 20:47 ` Bug: 2.5.47 NFS reports giant filename in readdir Trond Myklebust
  -- strict thread matches above, loose matches on Subject: below --
2002-11-19 17:39 Felipe Alfaro Solana
2002-11-19 18:28 ` Trond Myklebust
2002-11-19 20:17 Felipe Alfaro Solana

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=20021118192119.12935.qmail@linuxmail.org \
    --to=felipe_alfaro@linuxmail.org \
    --cc=nfs@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.