rds95@leah.Albany.Edu (Robert Seals) (09/25/90)
Hello, We are running Ultrix 2.2 (shtumm, shtumm) on a microvax-ii, and when trying to do remote dumps to it, I am having problems. I notice there is a switch (-o) on the Ultrix rdump that specifies that the dump is incompatible with non-release 2.x dump. But when dumping from (for example) AIX release 3.1, the dump starts, and goes through all its passes, but invariably "loses connection to remote host" without any data being written to tape. I hope there is something easier than "get 4.0". rob -- -------------------------------------------------------------------------------- "Unix has its weak points, but its file system is not one of them." -Chris Torek rob rob@asrcmv.albany.edu or rds95@leah.albany.edu or rob@dinner.albany.edu I have no idea what the uucp path to me is.
grr@cbmvax.commodore.com (George Robbins) (09/26/90)
In article <3662@leah.Albany.Edu> rds95@leah.Albany.Edu (Robert Seals) writes: > > We are running Ultrix 2.2 (shtumm, shtumm) on a microvax-ii, > and when trying to do remote dumps to it, I am having problems. > I notice there is a switch (-o) on the Ultrix rdump that > specifies that the dump is incompatible with non-release 2.x > dump. > > But when dumping from (for example) AIX release 3.1, the dump > starts, and goes through all its passes, but invariably "loses > connection to remote host" without any data being written to tape. Different versions of ultrix rdump have been incompatible with different versions of other vendors rdump (sun for example). Sometimes the -o swith helped, sometimes not. First make sure that your .cshrc file doesn't type out anything when invoked remotely. I seem to recall this as being a major pitfall. If this doesn't work, you can play with the Berkely rdump or some of the gnu and other tar/backup packages seen in the sources group from time to time. -- George Robbins - now working for, uucp: {uunet|pyramid|rutgers}!cbmvax!grr but no way officially representing: domain: grr@cbmvax.commodore.com Commodore, Engineering Department phone: 215-431-9349 (only by moonlite)
rwa@cs.athabascau.ca (Ross Alexander) (09/26/90)
rds95@leah.Albany.Edu (Robert Seals) writes: [essentially, he can't get an AIX box to dump to an Ultrix 2.2 muVax] [and that the diagnostic is "lost connection to remote host"] I, too, am experiencing some problems along these lines. I recently got a DS2100 dropped into my lap (smiles modestly, waves to the crowd) and naturally I started hooking things to it. An Exabyte EXB-8200 rev 2502 was amongst the first sucesses. Naturally, my thoughts turned in the "hey, this would make a great DUMPHOST" direction. And, for a few blessed runs (under Ultrix 4.0&patch) it worked. Like a charm. I naturally went out and had a beer. The next day, I built a new kernel (in an effort to trim the fat off the generic one) and rebooted. Suddenly, no more dumphosting... the remote machines (all suns 3s & 4s) kept reporting "lost connection to remote machine - broken pipe". Yes, I patched /etc/ttys, I set up /.rhosts, "rsh <DS2100> <whatever>" runs fine from the Suns, /usr/etc/rmt seems to be present, executable, & undamaged. The really bizzare thing is that other Ultrix systems (2.3 versions) can dump to the DS2100 iff they use the rdump -o flag, but Sun boxes just can't make it work at all. Does anyone have a handle on this? My current workaround is (command executed on a sun host): sun.box# dump 0sdf 5000 150000 - /dev/XXXXX \ | rsh ds2100.box dd of=/dev/rmt0h obs=64b which works just fine, but leaves much to be desired in terms of error handling and the like. -- -- Ross Alexander rwa@cs.athabascau.ca (403) 675 6311 ve6pdq