storage bitmap on RVN 1 does not cover the entire device

[Andrea Arthur]

Does anyone what causes this error and is it possible to fix it (without initing the drive)? This data disk was built on VMS 5.5-2 and the analyze/repair was done from a VMS 7.2 box. Thanks

[Ken Robinson]

Is this a volume set?

What was the exact error message?

Ken

[Ian Miller.]

I have seen that error on CDs there has not been any problem using them. It may be due to improved checking in VMS V7.2 (with the extended bitmap changes).

[Garry Fruth · Accepted solution]

I'm not sure if this helps. But from HELP/MESSAGE/WORD=INIT STORAGE on VMS7.3-2:

SHORTBITMAP, storage bitmap on RVN 'n' does not cover the entire device

Facility: ANALDISK, Analyze/Disk_Structure Utility

Explanation: The storage bitmap file, [000000]BITMAP.SYS;1, on the
specified relative volume is too small for the device size and volume cluster factor. This is an informational message. The volume is usable by the file system. However, only the space described by the storage bitmap is available for file allocation.

User Action: None. However, do not mount this volume on OpenVMS Version 7.1 or earlier systems; doing so could cause the system to crash.

[Garry Fruth]

Was the volume somehow enlarged? Perhaps it is an EVA disk that was made larger?

If so, A SET VOLUME/SIZE might clear up the informational message from ANALYZE/DISK; but if you are still using V5.5-2 I'm not sure if it will continue to be usable from that system.

From SHOW DEVICE/FULL, compare the TOTAL BLOCKS with the LOGICAL VOLUME SIZE. If the logical size is smaller than the total blocks, then SET VOLUME/SIZE would give you more space to play with; you may have to do a SET VOLUME/LIMIT first.

[John Gillings]

>If so, A SET VOLUME/SIZE might clear up

V7.3-2 and higher only.

Andrea, as the HELP/MESSAGE output posted by Garry says, the only real issue is there is some disk space that you can't access.

If you want to fix it, I'd recommend an IMAGE backup from the affected disk to a new one of equivalent or larger size. To avoid any potential problems:

$ INIT newdisk
$ MOUNT/FOREIGN newdisk
$ BACKUP/IMAGE/NOINIT olddisk: newdisk:

Do this on the OLDEST version that you wish to use this disk from.