News from Jeb! updates.rfs describes a new release which takes care of the TETSU corruption issue. I hope.
There are some details that require inspection.
Old version=4.0.63.1, 32-bit. New version=4.0.64.4, 64-bit
rfs.cfg changes required:
There are also parameters that should be present in a read-only server like maloof
The maximum number of concurrent RM loads is not limited to the sum of all MaxSMWriters (was previously unlimited)
RFS will now attempt to register with the portmap service. Note that this registration will fail if standard NFS is also running on the RFS server system. Successful registration with portmap will allow clients that cannot specify the port number and/or protocol type in the mount options to mount RFS.
"/RFS" should not be used by customers to transfer data to RFS, but is needed for special commands executed via RFSAS and CCi
This /RFS is the local mount of the RFS file system on the RFS server itself. We have found that there is a NFS problem that can cause a hang if the local mount of RFS, or any local mount of a NFS file system, is used heavily. It is caused by a deadlock in NFS cache space. We don't know the exact conditions that cause the hang. Sometimes the local mount can be used to load data for days and days without a problem, but sometimes they hang fairly quickly.You can continue to mount the RFS file system remotely from your remote client hosts and do writes and reads from there.
Modified 06-May-2011 at 10:47
http://icecube.wisc.edu/~jbellinger/StorHouse/06May2011
| Previous notes | Next notes | Main slide directory |