Help !!! NSS Volume Verify 1

[phart]

System: Netware 6.5 sp4

I have been recieving broadcast messages about errors on one of my nss pools. I just ran nss /poolverify="name" and recived errors that Named tree entries != Named objects and Named tree entries exist with no object anlong with other warnings.

1) Does this mean that I need to run nss /poolrebuild="name" (everything I have read says this is very dangerous)?

2) After exiting out of the Maintenance Screen I can not mount the nss pool it is in maintenance mode. I tried to us nss /poolactivate="name" but response is that it can not change pool to active status.

 

[sstoppel]

on the debug screen does it give more info as to why it cannot change the pool to active?

 

[phart]

Yes, I just saw where it stated to enter nss /errorcode=20810 and nss /errorcode=20880 to obtain more information and when I do I do not understand the more information.

Error = zERR_VOLUME_SHOULD_NOT_ACTIVATE (20810)
Error = zERR_POOL_CONSUMER_PREVENTED

 

[LawnBoy]

Don't do a poolrebuild, you can lose everything! SP4 had issues with that, SP4b fixed it.
TID 2972385

http://www.novell.com/support/searc...iceId=&dialogID=17934915&stateId=0 0 17944479

Aside - I hate the way Novell has reorganized their knowledgebase. Took me forever to find that document, and I knew what I was looking for.

 

[phart]

Thank you. That is what I had been reading and was afraid of. I have installed the update and I now need to wait until I can restart the server. After that will I need to do a poolrebuild or is it still dangerous?

 

[marvhuffaker]

make sure you're on the latest service pack AND Nss code, then rebuild only if you still have problems or symptoms.

Marvin Huffaker, MCNE

http://www.redjuju.com

 

[phart]

Is there nothing similar to vrepair in Nss that is not this dangerous. With vrepair it would correct bad pointers and orphaned files without this "am I going to loose all of my data

 

[marvhuffaker]

So have you updated your server, and are you still seeing problems? There is no point in even continuing this discussing if you haven't updated. SP4 has known defects in the NSS code. That's why Novell released SP4A shortly after.

Rebuilding is NOT going to kill all of your data (Unless you leave your server at the SP4 level). It is possible that whatever files are corrupted may be toasted when you run a rebuild, but that is not any different than when you lose corrupted files when running vrepair (or scandisk on windows).

Marvin

Marvin Huffaker, MCNE

http://www.redjuju.com

 

[ghilly]

Another point that I have seen is when some customers see an error coming up whilst doing the rebuild, they exit out of the rebuild. This is bad news, the pool will stay in maintenance mode. You must let the rebuild complete, despite the message that indicates you may lose data, after all that was why you ran the rebuild in the first place wasn't it?

Gordon