Wrong Diagnose Result

[F. Kneubuehl]

Hi 

 

One of my customers reported, that if he run a diagnosis (built in function
of our software) it reports the following errors:

 

.....> VolumeOnFile: C:\_DMXPData\DMXP_DB.ind

"FILE:
..\..\sources\VKernel\FBL\prot\LowLevel\Volume\VolumeOnFile\prot_SegmentMap\
Tree\FBL_Node_RBTree.cpp FUNCTION: fbl::RBTree_Node::get_Left LINE: 204"
SegmentMap is corrupted - "Embedded file's tree corrupted: 0 node found"

"FILE:
..\..\sources\VKernel\FBL\prot\LowLevel\Volume\VolumeOnFile\prot_SegmentMap\
Tree\FBL_Node_RBTree.cpp FUNCTION: fbl::RBTree_Node::get_Left LINE: 204"
SegmentMap is corrupted - "Embedded file's tree corrupted: 0 node found"

"FILE:
..\..\sources\VKernel\FBL\prot\LowLevel\Volume\VolumeOnFile\prot_SegmentMap\
Tree\FBL_Node_RBTree.cpp FUNCTION: fbl::RBTree_Node::get_Left LINE: 204"
SegmentMap is corrupted - "Embedded file's tree corrupted: 0 node found"

"FILE:
..\..\sources\VKernel\FBL\prot\LowLevel\Volume\VolumeOnFile\prot_SegmentMap\
Tree\FBL_Node_RBTree.cpp FUNCTION: fbl::RBTree_Node::get_Left LINE: 204"
SegmentMap is corrupted - "Embedded file's tree corrupted: 0 node found"

 

After restart of the app the error is gone. Rebuilding the index doesn't
change this behavior.

 

Is it possible, that some data are still in memory and the DIAGNOSE-function
doesn't took this into account? Or do I have to close and reopen the DB
before diagnosis? Or would even help a FLUSH?

 

Thanks for help

Fabian Kneubuehl

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macserve.net/pipermail/valentina/attachments/20101214/e599c429/attachment.htm>