From: Terry Bates <tbates@mainframe.ca>
To: nfs@lists.sourceforge.net
Subject: Problem with nfs data caching?
Date: Wed, 25 Feb 2004 13:37:15 -0800 [thread overview]
Message-ID: <403D158B.124C2469@mainframe.ca> (raw)
We are experiencing a problem which seems to be related to data caching
on our linux nfs clients;
Using Mental Ray, we render picture to an NFS mounted filesystem (I have
tried both SGI and Auspex file servers). We have an inhouse application
which we use to view the rendered pictures. If you attempt to view a
picture which has not completely finished rendering, you get a plain
grey window. Once that situation has happened, you cannot view that
picture from that machine until you umount and mount that filesystem
again. You can view it from other machines however.
Most of our machines are running RedHat 7.2 with a 2.4.7-10 kernel and
nfs-utils-0.3.1-13.
I have tried using RedHat 8.0 with a 2.4.18-14, 2.4.20-28, and most
recently 2.6.2 kernel, and nfs-utils-1.0.1-2. Same result. Here the
line from the /etc/fstab file for the filesystem that I'm testing on:
holly:/images_temp /images_temp nfs
rw,bg,rsize=32768,wsize=32768
I don't have this problem with any of our Irix clients.
Terry
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2004-02-25 21:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-25 21:37 Terry Bates [this message]
2004-02-25 21:45 ` Problem with nfs data caching? Steve Wampler
2004-02-25 22:10 ` trond.myklebust
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=403D158B.124C2469@mainframe.ca \
--to=tbates@mainframe.ca \
--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.