Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!udel!haven!wam.umd.edu!mikec
From: mikec@wam.umd.edu (Michael D. Callaghan)
Newsgroups: comp.sys.next
Subject: New Device Locking Problem
Message-ID: <1991Apr8.231511.24125@wam.umd.edu>
Date: 8 Apr 91 23:15:11 GMT
Sender: usenet@wam.umd.edu (USENET Posting)
Organization: University of Maryland at College Park
Lines: 26
Originator: mikec@wor.umd.edu
Nntp-Posting-Host: wor

Here's a new one for you!

I watched my Cube boot just now, and saw something pretty scary.

	Device Busy (trying to attach the swapfile) !!!

What would cause the swapfile to be busy?

I just ran checkswap -v, and got:
..exit_code = 0

which means 

	possible exit codes are as follows:

       	   FSR_NONE       0    /* disk not present */


I'm no expert, but I think that's not good.


-- 
MikeC
_________________________________________________________
Michael D. Callaghan, MDC Designs, University of Maryland
mikec@wam.umd.edu