On Mon, 3 Dec 2001 at 11:56am, Rafe Thayer wrote > Hi Folks, > Another question for ya. After I did an amdump to test out dumping our > disks to tape, I tried to do an amrecover to see if restoring the data > would work. It seems to work for our linux machines, but the solaris box > has some trouble. When I start up amrecover, it reports: > ... > 200 Config set to imash. > 501 No index records for host: hostname. Invalid? > Trying hostname.domainname... > 200 Dump host set to hostname.domainname > ... > > > Then I do a setdisk /etc and it reports: > > 200 Disk set to /etc. > No index records for disk for specified date > If date correct, notify system administrator > > So I figured that the index must not have been created for some reason, > but I checked that out on the server and it looks fine. Has the right > permissions and ownership. The wierd thing is, if I look into the index > files for the host that's giving me trouble, they look a little different > than the others. It looks like this: > > 06573011000/./security/dev/audio > 06573011000/./security/dev/fd0 > 06573011000/./security/dev/sr0 > 06573011000/./security/dev/st0 > 06573011000/./security/dev/st1 > ... > > Whereas for the linux hosts, the index looks like this: > > / > /CORBA/ > /CORBA/servers/ > /X11/ > ... > > (these are just the contents of /etc on each host). The version of tar on > the solaris machine is 1.13. I've heard tar can cause some problems. Do > you think that might be it? > > Thanks for your help! > > Rafe > > >
-- Joshua Baker-LePain Department of Biomedical Engineering Duke University
