From: James Pearson <james-p@moving-picture.com>
To: nfs@lists.sourceforge.net
Subject: File system cache corruptions?
Date: Wed, 06 Oct 2004 17:40:58 +0100 [thread overview]
Message-ID: <4164201A.8020005@moving-picture.com> (raw)
Very occasionally we get problems where by an application on an NFS
server fails to load on one NFS client - for example just had one which
fails when you try to run it:
/path/to/nfs/mounted/binary: relocation error:
/path/to/nfs/mounted/shared/object.so: symbol , version GLIBC_2.0 not
defined in file libpthread.so.0 with link time reference
I 'fixed' the problem by running a simple tool on the client that just
grabs memory - and hence flushes any cached files.
The application in question hasn't changed in months.
In this case, the client is running Fedora Core 1 with a 2.4.22 based
kernel (with Trond's NFS client patches), but we've seen similar
problems with Redhat 7.2 based machines with a variety of kernel.org
2.4.X based kernels.
Any ideas on what may be causing this?
James Pearson
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2004-10-06 16:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-06 16:40 James Pearson [this message]
2004-10-06 17:45 ` File system cache corruptions? Trond Myklebust
2004-10-07 8:57 ` James Pearson
-- strict thread matches above, loose matches on Subject: below --
2004-10-06 17:58 Lever, Charles
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=4164201A.8020005@moving-picture.com \
--to=james-p@moving-picture.com \
--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.