[Info-vax] BACKUP issues wrong informational message
Phillip Helbig---undress to reply
helbig at astro.multiCLOTHESvax.de
Thu Feb 17 17:47:23 EST 2011
In article
<baff8638-6389-4e2b-b173-bbc020abf1a6 at i39g2000prd.googlegroups.com>,
abrsvc <dansabrservices at yahoo.com> writes:
> On Feb 17, 3:21 pm, hel... at astro.multiCLOTHESvax.de (Phillip Helbig---
> undress to reply) wrote:
> > $ back/image/noinit/log $110$dkb300: $110$dkb400:
> > %BACKUP-I-LOGNOTPRES, logical volume size of volume $110$DKB400: not preserved
> > %BACKUP-I-LIMITNOTPRES, expansion size limit of volume $110$DKB400: not preserve
> > Despite the message above, both the logical volume size and the
> > expansion size limit ARE preserved. (I noticed this after doing a
> > similar copy a few days ago.)
I just checked; they were NOT preserved. I was pretty sure they were on
the previous copy.
> I would have expected the messages to appear, BUT... they should have
> referenced DKB300. I seem to recall informational messages stating
> that the input volume specs were not preserved. Here the output
> device was listed not the input device. Subtle but distinct
> difference.
The input volume was write-locked, so they can't change. The point is
that the LIMIT on the output volume was overwritten, even though I said
/NOINIT. The cluster size was not. Fortunately, there is SET VOL/LIM
which can correct this.
If I copy from A to B and A overwrites B then, as the message says, it
is indeed B which is not preserved.
More information about the Info-vax
mailing list