Return to BSD News archive
Newsgroups: comp.unix.bsd Path: sserve!manuel!munnari.oz.au!mips!mips!sdd.hp.com!elroy.jpl.nasa.gov!ucla-cs!ucla-mic!pita!scott From: scott@pita.cns.ucla.edu (Scott Burris) Subject: dump and DAT [Was: Re: kdb kgdb and dump] Message-ID: <scott.709402866@pita> Keywords: dump Nntp-Posting-Host: pita.cns.ucla.edu References: <cproto.709305090@marsh> <1992Jun24.100204.20563@mnemosyne.cs.du.edu> Date: 24 Jun 92 09:40:40 PDT Lines: 29 csc228@lancaster.ac.uk (Bruce J. Keeler) writes: >I too had problems with dump - well rdump actually, though much worse than >hung processes. When I tried it trashed the root partition. Has anyone else >had this problem? Unfortunately I no longer have a 386BSD setup up so I can't >give you sample output (not sure if I would even if I did still have a setup!) >Off the top of my head, I think it mumbled something about bad disklabels, >so that would be the area to look to. [Hand shoots up, waves widely in the air...] Yes, I too have trashed my root partition in an attempt to use dump to a borrowed Maynard 525MB SCSI drive. Got a number of wd: extra interrupt messages and a bad disk label message. Had to restore from a multifloppy tar that was, ahem, 2 months old. On a backup related note, I now have an Archive DAT drive working with Pace's SCSI driver. The drive will work fine in SCSI-1 mode. I had to make some changes to get it to work in SCSI-2 mode. I'm not planning on posting the diffs since I'd like to sync up the 0.1 release when it comes out. The problem relates to the drive rejecting mode selects when it has gone into unit attention following power-on. -- ---------- Scott Burris UCLA Campus Network Services cnetslb@oac.ucla.edu (213) 206-4860 - OR - scott@pita.cns.ucla.edu