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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

NSS Internal Volume (POOLNAME_IV_) reports running out of diskspace 1

Status
Not open for further replies.

mfranco

MIS
Dec 31, 2001
34
US
Hi,

I am running Netware 6.5 with SP7. I received a Novell Popup message with the following message.

NSS-2.70-5003: NSS Volume VDS01/SYS_IV_almost out of disk space.

At first I thought this was telling me that my SYS Volume was out of space, but it has about 600MB of free space ( sure it could be more, but it's not full so that's the important part). I did some searching online and found this TID


I read it over and am confused by it. First off, would this be the folder the error message is referring to:

\\VDS01\_ADMIN\Manage_NSS\Volume\SYS_IV_

If it is, I see files like, DirInfo.xml, FileEvents.xml, ModifiedFilesList.xml, TrusteeInfo.xml, UserInfo.xml, and VolumeInfo.xml.

Each file is 1,024KB and dated 1/5/09. The TID talks about freeing up blocks and that one or more of the user files must be deleted. Am I supposed to delete these files? Are they automatically regenerated? Any insight would be very helpful because I am very lost at this point.

Thank you.
 
That's a little tricky to understand, but shy of deleting user files on one of the volumes in the pool, try doing a purge of all deleted files on one of the volumes in the pool and see if that helps.
 
Everything in the _ADMIN folder is generated automatically when you start the server.> You should not modify or delete anything from it, and I doubt that doing so will fix your problem. From reading your posted link, I did not come to the same conclusion that you did, don't delete those files.

I bet you have tons and tons of files that are deleted but have never been purged. You could purge your volumes and probably resolve this problem. This could especially be true if your server holds an application that creates lots of small temporary files that get continually created and deleted.

If you open up Windows Explorer, and at the root of the volume, Right Click, Properties... You should have a tab with a Pie chart showing disk usage for the volume. If a majority of it is RED, you need to purge. Red means deleted files not purged.

Also, if you have multiple volumes in your NSS pool, you'll need to check each one.





Marvin Huffaker, MCNE
Marvin Huffaker Consulting, Inc.
A Novell Platinum Partner
 
Thanks, I had a feeling the _ADMIN files/folders should be left alone and I just wanted to make sure.

I have 2 NSS pools. The first one is called SYS and contains only the sys volume, the second is called DATA and has my VOL1 and VOL2 with user data. I checked and my VOL1 had a lot of purgable files. Thinking about it I realized it had been a long time since I purged. So I ran PURGEVOLUME SYS and purged the few purgable files that were found on there yesterday and today I did the same thing for VOL1 and VOL2.

Hopefully that fixes my problem, the error message only seemed to pop up once a day, so I will have to wait and see what happens. I will post back once I find out.

Thanks!
 
I want a star too (boo hoo).

And I quote myself. "try doing a purge of all deleted files on one of the volumes in the pool and see if that helps."

Marv be usurpin' my glory.
 
Just being smart - a gold star won't buy me a burger for dinner or anything else for that matter.
 
LOL very true.

Well thanks to all, the error messages have been gone and not come back for the past several days. Purging all the volumes seems to have helped. I am going to have to remember to do that more often.

Just wondering, even though there was space on all the volumes, purging seemed to fix my problem. Does that mean there a maximum amount of purgable files that can be stored before that error message starts to pop up? I'm wondering if I hit that max and that was the reason for the error.

thanks again!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top