From: James Pearson <james-p@moving-picture.com>
To: nfs@lists.sourceforge.net
Subject: Re: File system cache corruptions?
Date: Thu, 07 Oct 2004 09:57:54 +0100 [thread overview]
Message-ID: <41650512.1050309@moving-picture.com> (raw)
In-Reply-To: <1097084729.5245.44.camel@lade.trondhjem.org>
Trond Myklebust wrote:
> På on , 06/10/2004 klokka 18:40, skreiv James Pearson:
>
>
>>Any ideas on what may be causing this?
>
>
> Shared mmapped files tend not to be easy to keep consistent w.r.t. the
> server, because mmap pins the pages in memory.
>
> Instead of copying data into the mmapped file, it is better to create a
> new file, then rename it onto the old one (like tools such as GNU
> install do for you).
This is true (and something I do as a matter of course if I ever have to
replace/upgrade shared libraries/binaries etc), but not the case here -
the executable and its required shared libraries which are on the NFS
server have been in place and not changed for about 6 months.
There are over 100 clients using the exact same binary and shared
libraries - only one had this problem.
The server is hard mounted.
Thanks
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 prev parent reply other threads:[~2004-10-07 8:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-06 16:40 File system cache corruptions? James Pearson
2004-10-06 17:45 ` Trond Myklebust
2004-10-07 8:57 ` James Pearson [this message]
-- 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=41650512.1050309@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.