bill@wrangler.WLK.COM (Bill Kennedy) (03/11/91)
I'd like to hear from someone who is using the stock RFS from NCR
in release 03.00.01 along with non-NCR systems. I am encountering
some anomalous behavior working with an 80386 with Interactive
release 2.2 and an AT&T 3B2 running release 3.1.
If I mount an 80386 resource on the 3B2 they cooperate and agree
with each other with respect to file sizes, everything looks about
like it does on the local system. If I mount the same resource on
wrangler (Tower 32/400) I can't do an ls, it stops after
.: Object is remote and if I do an ls -l using some wild cards
I get each file name followed by : Object is remote but no permissions,
owner, group, or size. A dfspace with the remote resource mounted
says that 529407.99MB of 0.00MB is available when the correct size for
that file system should be 15.26MB of 40.07MB is available. If I run
a find on the remote directory I get find: huge directory and stat()
failed.
The reverse is nearly so when I have a Tower resource mounted on the
80386 or the 3B2. A dfspace complains that df: cannot statfs resource
name and statfs: Invalid argument. I can ls and ls-l and everything
looks fine except that the file sizes are positively huge. A find on
the Tower resource mounted on the 80386 or 3B2 gets the same kinds of
complaints that the others do on the Tower. None of these symptoms seem
to occur when 3B2 resources are mounted on the '386 and vice versa.
The RELDEF page 13-1 says that a Tower 4x0. 6x0 system with Release 3
cannot connect via RFS to another non-Tower system but that it can
connect to other Tower platforms and Motorola based systems with RFS.
I'll confess that life is much simpler with the Tower being the primary
rather than a secondary domain name server but it does connect and sort
of work with the other two nodes here. The RELDEF also says (and I
agree with this one) that passwords aren't tolerated. Since RELDEF says
that I can't get as far as I have, should I just be happy with what I've
got? Does anyone have any suggestions about how I might get a dufst
file system to behave any more acceptably? Please no NFS suggestions,
that's $1800 more (I'd have to get it for the 3B2 and the Tower) and all
of this comes out of my personal hide.
--
Bill Kennedy usenet {att,cs.utexas.edu,pyramid!daver}!ssbn.wlk.com!bill
internet bill@ssbn.WLK.COM or attmail!ssbn!bill