mark@intek01.UUCP (Mark McWiggins) (05/12/89)
We've just added NFS to our System V 386 box. It mostly works fine connected to our Sun network (a 3/260 server and two 3/60 nodes), with the following annoying exceptions: (1) I can't dump the System V filesystem with Sun's "rdump" command: #mark rdump 0csf 600 stud.hoss:/dev/nrst8 /crank/usr DUMP: Date of this level 0 dump: Wed May 3 16:14:35 1989 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /crank/usr to /dev/nrst8 on host stud.hoss DUMP: (This should not happen)bread from /crank/usr [block 16]: count=-8192, got=-1 DUMP: bad sblock magic number DUMP: The ENTIRE dump is aborted. I presume the Sun dump software only knows about 4.2 type filesystems. Is this the case? Is there something else I'm doing wrong? Is there another place I can get a dump program that works? Surely people must be doing this sort of thing. (2) I can't mount the System V filesystem from the Sun server. I get: #stud.hoss mount -vat nfs mount: intek01:/ on /crank: No such device mount: giving up on: /crank /crank/usr2 /crank/usr Yet I can FTP to intek01 just fine, and I can mount intek01:/ from both of the Sun clients. I notice that I have biod's running on the client and not on the server, and I thought that might be the problem. But I try and run biod 4 on the server, and no biod's show up when I do 'ps aux'. Nor do I get an error message. Thanks in advance for any help on this. Mark McWiggins Integration Technologies, Inc. (Intek) (206) 455-9935 uunet!intek01!mark