Re: [U2] Determine bad block in universe hash file

[Glenn Herbert]

The number given by the blink error will always be in "primary" space 
(unless something major is broken); it always is a number that identifies 
the beginning of a group.   The only thing you need to know is the 
separation size of the file and the file header size (in separation units).

If it's a dynamic file, then the header is either 2048 or 4096 and matches 
the separation size. It's a little trickier for regular hashed file:

-  if the separation is odd, then the header size will be 512 bytes
-  if the separation is a multiple of 4, the header size will be 2048 bytes
-  all other even separation values, the header size will be 1024 bytes
So it's basic math:  (Group_Addr - Header_Size) / Separation will give you 
the group number, i.e (0x14E7800 - 0x800) / 0x800 = 0x29CE , or 
10702  (this assumes a header size of 2048 bytes and a separation of 4 
(also 2048 bytes)).

At 03:37 PM 3/30/2005, you wrote:
I got the following message-
Computed blink of 0xFF6800 does not match expected blink of 0xAAA5800
Detected within group starting at address 0x14E7800
The  module of the file is 8581 so the group starting address must be in
an overflow record. I'm trying to use "uvfixfile" to trace the blocks to
maybe fix the problem, but it has to have a starting group number within
the primary group. I ascii dumped that section of the starting at
0x14E7800 and found what looked like a key. I then used the "hash"
command under uvfixfile to determine the starting group number. I then
did a "trace", but no errors occurred.
How can I associate the overflow block to a primary block based on the
address given above?
Thanks in advance...
-- Rod Hills
-------
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit 
<http://listserver.u2ug.org/>http://listserver.u2ug.org/
-------
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/