Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SYS out of disk space

Status
Not open for further replies.

niki43

IS-IT--Management
May 23, 2002
21
US
I am moving all unnessary files from this server to another but what is the best way to clean up a sys vol. on novell is there something that will remove all deleted files and reorganize the files?
 
Depends on what you store on there. If it is just system files, you better be careful about what you delete.

What size is your SYS file, 2Gb or larger would be my suggestion (4Gb my recommendation for a 5.x server). -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------
 
This is an old system upgraded from 3.11 alot of data base files and storage for users personel directories. The server was not partitioned so that files can be stored other than in the sys directory. Mostly what I was looking for is a utility like defrag or a file purge. I have checked and the purge deleted files is already on auto for the system. Size of sys is 17gig
 
Are you assigning Print Queues to the SYS volume? When I see our SYS volume get filled up, it's almost always caused by huge print queues.

Each time someone prints to a network printer, the request is submitted in the form of a file that gets stored in the queue for that printer. The server sees something in that printer's queue and tells the printer about it. When there's a problem (the printer isn't online, or the printer isn't being seen by the server, and so on), the printer's queue never gets emptied out. Requests keep getting stored in the print queue. That fills up the space on the volume that the print queue is on.

If that's the case, the solution is simple. Look in the queue folders for the print queues and start by deleting the files that are in the folders that take up the most space.

Of course, once you get the print queues back down to their proper size, you need to figure out what caused the queue to get so full, or it'll happen again!

 
Once you have deleted all necessary files, dismount the volumes and run a VREPAIR against them. Make sure you select the option, Purge Deleted FIles.

Good Luck!
 
I don't have any print queues, and I have cleared all log files. I have a problem with dismounting the sys vol. with I try it goes through the process ok and gives me a message of "Server_1 TTS Shut Down because backout volume SYS was Dismounted" but at this point it does not give me a cursor to go into vrepair, I then have to shut power off to get past this. Can I make the system boot back up with out mounting the sys vol???
 
Yes you can. At your DOS prompt, run:

SERVER -NS

This will start the server without running STARTUP.NCF or AUTOEXEC.NCF. When it boots, it should boot to the : prompt. Just LOAD VREPAIR from there. -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------
 
I am having a problem getting to my dos prompt, it looks like the system is set up to boot right to novell and because I can't dismount my sys vol. Do I need to boot from a boot disk to edit the autoexec.exe file ? Or am I just having a dumb moment and am over looking some thing???
 
The box has to boot to some flavor of DOS so that server.exe can be run. Yes, a DOS boot disk can be used to get to a c:\ prompt. Or you can try the F5 key as the systems finishes its POST.
 
Thanks for the F5 tip that got me to the dos prompt. But now when I try to run Vrepair I get the following error messages : Loader can not find public symbol :Write file for module Vrepair. and after that a whole long list of Loader can not find public symbol: ect. ect. ect.

This thing will drive me nuts yet.
 
you probably need to set the path to your c:\nwserver or whatever directory your server.exe and other related files are located. Then after you run server -ns, you can do a load c:vrepair

 
Yes I had to set the path to c:\nwserver to get vrepair to even try to start, this is the location for server.exe. I still cant get past the loader cant find public symbol problem.
 
What Service Pack are you running? -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top