tep%galt.UUCP@ucsd.edu (Tom Perrine) (02/14/91)
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
sjk@cs.utexas.edu (Scott Kamin) (02/22/91)
In Message-ID: <1608@brchh104.bnr.ca>, tep%galt.UUCP@ucsd.edu (Tom Perrine) : > 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. We are mounting file systems from our 2/170 running 3.5 on our 3/80s and SPARCstations running 4.1.1 with no problems. It's been about a month and we've seen no corruption. Scott J. Kamin {ico, att!uswat} !onecom!sjk TelWatch Inc. (303) 440-4756 FAX (303) 938-6703