Path: utzoo!utgpu!cunews!bnrgate!brtph3!brchh104!brchs1!bnr.ca!rice.edu!sun-spots-request
From: tep%galt.UUCP@ucsd.edu (Tom Perrine)
Newsgroups: comp.sys.sun
Subject: 3.5 vs. 4.1.1 NFS?
Keywords: SunOS
Message-ID: <1608@brchh104.bnr.ca>
Date: 13 Feb 91 22:03:00 GMT
Sender: news@brchh104.bnr.ca
Organization: Sun-Spots
Lines: 31
Approved: Sun-Spots@rice.edu
X-Original-Date: 8 Feb 91 01:03:50 GMT
X-Sun-Spots-Digest: Volume 10, Issue 31, message 13
X-Note: Submissions: sun-spots@rice.edu, Admin: sun-spots-request@rice.edu

Systems involved:
	tots	Sun-3/180, SunOS 3.5.1, SMD drives on Xylogics controllers
	eds1	SPARCstation IPC, SunOS 4.1.1, SCSI drives

We have successfully NFS mounted the eds1 (4.1.1) filesystems on tots
(3.5) with no problems.

However, when we mounted the tots filesystems on eds1, we got a corrupt
filesystem on tots (lost+found in the filesystem had an entry with the
inode number of lostfound and a screwed-up link count).  We cannot prove
that this was a result of the 3.5 to 4.1 mount, but we are suspicious.

Is anyone mounting 3.5 filesystems on 4.1.1 machines?  I looked through
all of the "Read THIS First"s, and the Release Notes, and I didn't see any
notes on incompatibilities between the versions.

I know that heavy NFS traffic from the IPC to the 3/180 could cause load
problems, but the filesystem in question is only used for reading mail and
news.

(Tots is our mail hub and exports /usr/spool/mail. All mail is delivered
via SMTP from the client machines to tots, none of the mail clients ever
write mail into the spool directory.)

We are not using the automounter.

Tom Perrine (tep)                       |Internet: tep@tots.Logicon.COM
Logicon                                 |UUCP: sun!suntan!tots!tep
Tactical and Training Systems Division  |
San Diego CA                            |GENIE: T.PERRINE
"Harried: with preschoolers"            |+1 619 455 1330