server hangs due to volume use count incremented and not decremented due to a bug in filesys.nlm where it gets hung up trying to generate the
(Last modified: 30Jul2002)
This document (10073057) is provided subject to the disclaimer at the end of this document.
fact
netware 5.1
symptom
server hangs due to volume use count incremented and not decremented due to a bug in filesys.nlm where it gets hung up trying to generate the dos name for the os2 equivalent name.
cause
Two service processes in the two dumps look like they're the one's who INCed the VolumeUseCount trying to rename a file and then got hung up due this bug.
RescheduleLasLowWithDelay
DOSFindDirectoryEntry
DOSGenerateUniqueName
GetMaximumSubDirectoryTreeDepth
INWRenameEntry -------------------------------------------- This function incremented the VolumeUseCount
INWF3RenameFile
Case87
Name space passed in was os2. The files in question were:
# dd cc60dc7d
CC60DC7D 304A430C 3130334A-4F442E21 4F440443 .CJ0J301!.DOC.DO
CC60DC8D 42035343 3008414A-39393030 06373939 CS.BJA.00099997.
CC60DC9D 39393930 7E0C3339-304C5257 2E353438 099993.~WRL0845.
CC60DCAD 00706D74 06000000-FF488B00 002CF7FF tmp..
They might want to make sure that these tmp files are deleted properly. There have been problems like this with corrupt directory entries.
fix
06/21/2002 09:54a 405,194 FILESYS.NLM or later
in flsysft7.exe
document
| Document Title: | server hangs due to volume use count incremented and not decremented due to a bug in filesys.nlm where it gets hung up trying to generate the dos name for the os2 equivalent name. |
| Document ID: | 10073057 |
| Solution ID: | NOVL81301 |
| Creation Date: | 30Jul2002 |
| Modified Date: | 30Jul2002 |
| Novell Product Class: | NetWare |
disclaimer
The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.