From: Neil Brown <neilb@suse.de>
To: Christoph Bartoschek
<bartoschek-eefaeeawk+jFLWzOrOlZPg@public.gmane.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Invisible files and input/output errors
Date: Tue, 4 Dec 2007 11:23:52 +1100 [thread overview]
Message-ID: <18260.40472.276614.78174@notabene.brown> (raw)
In-Reply-To: message from Christoph Bartoschek on Tuesday December 4
On Tuesday December 4, bartoschek-eefaeeawk+jFLWzOrOlZPg@public.gmane.org wrote:
> Hi,
>
> we use a DFS-NFS-Gateway on AIX 5.1 as our NFS-Server. This works fine most of
> the time but for four months we have strange problems. There are basically
> two issues:
>
> 1. Using "ls" in specific directories after certain idle time gives us
> an "Input/Output Error" without any results.
>
> 2. In some directories some entries are not shown. For example there is a
> directory with the subdirectory ak_fcp in it. "ls" does not show this
> directory. But it is possible to do "cd ak_fcp" and then normally work with
> it. It is also possible to access files in the directory while being in the
> parent directory: " less ak_fcp/logfile" works.
>
> Does anybody know how to get rid of the problems? The problems occur on
> several different linux versions.
Sounds a lot like directory cookie problems.
Can you get a network trace of the NFS packets.
Something like
tcpdump -s 0 -w /tmp/trace host NAME-OF-SERVER
then cause the failure while that is running.
Either compress and attach the result to an Email, or if it is too
big, stick it on a website somewhere.
NeilBrown
next prev parent reply other threads:[~2007-12-04 0:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-03 23:37 Invisible files and input/output errors Christoph Bartoschek
2007-12-04 0:23 ` Neil Brown [this message]
[not found] ` <18260.40472.276614.78174-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2007-12-04 10:06 ` Christoph Bartoschek
2007-12-05 23:31 ` Neil Brown
[not found] ` <18263.13509.397157.489566-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2007-12-06 6:22 ` Christoph Bartoschek
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=18260.40472.276614.78174@notabene.brown \
--to=neilb@suse.de \
--cc=bartoschek-eefaeeawk+jFLWzOrOlZPg@public.gmane.org \
--cc=linux-nfs@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