When reloading a volume with the same name as a mounted volume rldr_check_pvol_ and rldr_input_ report inappropriate messages

[Eric Swenson]

If you boot a system with a d451 RPV, and reload an rpv to a 3381 io drive, you see the following messages:

1512.9  RCP: Mounted copy of Storage System volume rpv on dska_00a for user I/O.
1512.9  RCP: Mounted IO volume  on dska_00b for user I/O.
1512.9  RCP: Mounted IO volume  on dska_00c for user I/O.
rldr_check_pvol_: Reload may overflow volume
rldr_check_pvol_: Disk label requires 27006 records; Volog label requires 29950 records on pv rpv
rldr_check_pvol_: Reload may overflow vtoc
rldr_check_pvol_: Disk label requires 13505 vtoce; Volog label requires 14974 vtoce on pv rpv

reload_volume: Initialized physical volume rpv does not match online logical image. Do you wish to proceed   M-> [auto-input] yes

These are not really appropriate messages. Of course the rpv-to-be-reloaded does not (necessarily) match the rpv that is mounted. But we shouldn't be comparing these two.

The reload works perfectly fine, but the messages are wrong. Also, a little later in the reload, you see:

rldr_input_: Please get the following input volumes
:  V01
reload_volume: Begin reload of volume rpv  at 1512.9
Mounting tape V01 for reading
1512.9  RCP: Attached tapa_01 for Initializer.SysDaemon.z
1512.9  RCP: Note (tapa_01) - V01,sys
1512.9  RCP: Using Reel V01 on tapa_01 for Initializer.SysDaemon.z
Mounted Multics volume "V01" (recorded at 800 BPI), on device tapa_01
rldr_input_: Warning - new disk type for rpv
1513.2  RCP: Detached tapa_01 from Initializer.SysDaemon.z
rldr_input_: reloaded from input volume V01 112 records of 28 directories and 3323 records of 251 segments on pv rpv
reload_volume: End reload of volume rpv at 1513.2
reload_volume: Reloaded on volume rpv 112 records of 28 directories and  3323 records of 251 segments and 0 null vtoces

The message: "rldr_input_: Warning - new disk type for rpv" is also not correct. We don't really care that the foreign system rpv is not of the same disk type as the system on which we're performing the reload.

These messages should be suppressed when the reload is done to volumes that were init_vol'ed with "-copy". Not sure if that information is around by the time the reload happens though.