Shawn,
In your virtual volume devclass definition you might try to set a
maxsize equal to that of the real storage behind it. This should
prevent stacking.
Neil Strand
Storage Engineer - Legg Mason
Baltimore, MD.
(410) 580-7491
Whatever you can do or believe you can, begin it.
Boldness has genius, power and magic.
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Shawn Drew
Sent: Thursday, August 13, 2009 11:52 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Virtual Volume assistance
We started using Virtual Volumes earlier this year for some new branch
locations with no local, long-term storage.
As it works, multiple virtual volumes will get stacked into one "real"
sequential volume.
The problem is that periodically, a reclamation process will require two
volumes that happen to be stacked together. On the destination side,
it
cancels one of the mounts with a "being preempted by higher priority
operation", then the whole reclamation fails and the first volume is
marked "read-only"
As I write this an idea come to the fore. Perhaps I should be using the
RECLAIMSTGpool feature. Does anyone else have this problem? Is
RECLAIMSTGpool the standard workaround?
Regards,
Shawn
________________________________________________
Shawn Drew
This message and any attachments (the "message") is intended solely for
the addressees and is confidential. If you receive this message in
error, please delete it and immediately notify the sender. Any use not
in accord with its purpose, any dissemination or disclosure, either
whole or partial, is prohibited except formal approval. The internet can
not guarantee the integrity of this message. BNP PARIBAS (and its
subsidiaries) shall (will) not therefore be liable for the message if
modified. Please note that certain functions and services for BNP
Paribas may be performed by BNP Paribas RCC, Inc.
IMPORTANT: E-mail sent through the Internet is not secure. Legg Mason
therefore recommends that you do not send any confidential or sensitive
information to us via electronic mail, including social security numbers,
account numbers, or personal identification numbers. Delivery, and or timely
delivery of Internet mail is not guaranteed. Legg Mason therefore recommends
that you do not send time sensitive
or action-oriented messages to us via electronic mail.
This message is intended for the addressee only and may contain privileged or
confidential information. Unless you are the intended recipient, you may not
use, copy or disclose to anyone any information contained in this message. If
you have received this message in error, please notify the author by replying
to this message and then kindly delete the message. Thank you.
|
