Return to BSD News archive
Newsgroups: comp.unix.bsd Path: sserve!manuel!munnari.oz.au!uunet!mnemosyne.cs.du.edu!usenet From: csc228@lancaster.ac.uk (Bruce J. Keeler) Subject: Re: kdb kgdb and dump Message-ID: <1992Jun24.100204.20563@mnemosyne.cs.du.edu> Keywords: dump Sender: usenet@mnemosyne.cs.du.edu (netnews admin account) Organization: Confuse-a-cat Ltd. References: <cproto.709305090@marsh> Date: Wed, 24 Jun 92 10:02:04 GMT Lines: 32 In article <cproto.709305090@marsh> cproto@marsh.cs.curtin.edu.au (Computer Protocol) writes: > > >Hi there, >... >I'm desperate to get dump working. The previously suggested fix of >reducing the number of slaves to 1 doesn't work. I still have got >3 hanging dump processes. One of which is in a noninterruptable >disk i/o wait. For the moment I'm using tar but I would much >prefer dump. Any suggestions please ?!? > >Regards - Tibor Sashegyi (cproto@abel.cs.curtin.edu.au) 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. The system was a 486DX, AMI BIOS, WD1007v-se2 (I think) HD controller with 110Meg ESDI disk, 8 Meg ram. I can't remember the disklabel I used, but it worked just fine otherwise with no problems (well, after I'd commented out the 'Extra Interrupt' message from wd.c!) BTW, it trashed the root partition whether or not it was the root partition being dumped. -- Bruce J. Keeler - csc228@lancaster.ac.uk