The Question is:
Is there any tool which does allow to recalculate which file is using which
LBN. Given the fact that DECevent does report "bad" blocks as LBN it would be
nice to check, which file does contain that lbn. This might help to classify
the severity of any impact on production very easy.
The Answer is :
First, perform a full BACKUP/IMAGE and archive the contents of this
disk. When you restore the contents, you will receive marked-bad
(FORCEDERROR) warnings from BACKUP for files with forced errors; on
the files where the contents are uncertain. (The write to the LBN
will also trigger the bad block recovery processing.)
The DFU tool on the OpenVMS Freeware can do this (DFU SEARCH/LBN=lbn),
as can the FINDFILE tool from the DECUS archives.
Also consider the following commands:
BACKUP/PHYSICAL/LOG ddcu: NLA0:nosuchfile.bck/SAVE