G
George Potemkin
Guest
> index check is quite slow sometimes. And sometimes it's too short-spoken. We spent 6 days on idxcheck and got the error message (14684) that does not help to localize the corruption. We need to know the dbkey of an intermediate index block with a key that reffers to dbkey mentioned in the error (dbkey 0, area 29). We don't know how many blocks are corrupted: the error 14684 is fatal and it forces a process to terminate. And idxfix seems to be unable to find this corruption. I see the only option: to run idxcheck against a copy of database started in multi-user mode but only for idxcheck and promon. When idxcheck will exit after the error 14684 we will check the most recently used index blocks in promon/R&D/6/4. Lru Chains. Are there any other possible solutions? How to fix the corrupted index block is another challenge. ;-(
Continue reading...
Continue reading...