- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- MOUNT-F-MBRTOOSMALL
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-14-2009 10:28 AM
тАО05-14-2009 10:28 AM
MOUNT-F-MBRTOOSMALL
$ MOUNT/NOMOUNT_VERIFICATION/NOASSIST/SYSTEM DSA1: /SHADOW=($1$DKB100:, $1$DKD100:) User_1 User_1
%MOUNT-I-MOUNTED, USER_1 mounted on _DSA1:
%MOUNT-I-ISAMBR, _$1$DKB100: (GRED28) is a member of the shadow set
%MOUNT-I-SHDWMEMFAIL, _$1$DKD100: (GRED28) failed as a member of the shadow set
-MOUNT-F-MBRTOOSMALL, must be the same size or larger than logical volume size
Any help would be appreciated!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-14-2009 10:55 AM
тАО05-14-2009 10:55 AM
Re: MOUNT-F-MBRTOOSMALL
Is the box current on ECO kits for OpenVMS Alpha V8.3?
What are the SCSI controllers involved here, and what other gear here is (also) in allocation class 1 in the cluster?
Also look to replace the RZ28 drives; replacement SCSI disk widgets here are cheap, are newer, and also have larger capacities.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-14-2009 10:59 AM
тАО05-14-2009 10:59 AM
Re: MOUNT-F-MBRTOOSMALL
can you post up a sh dev/full for the disks involved here.
hth
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-14-2009 11:06 AM
тАО05-14-2009 11:06 AM
Re: MOUNT-F-MBRTOOSMALL
Apologies for asking the obvious, but what are the two rz28 drives physical block sizes for DKD & DKB?
There were different flavors of 2GB disks that DEC used for RZ28x-xx and not all were the same exact size.
hth,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-14-2009 11:26 AM
тАО05-14-2009 11:26 AM
Re: MOUNT-F-MBRTOOSMALL
--
Why don't you want mount verification?
There are very few reasons why you'd ever want to do that.
-- Rob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-14-2009 11:37 AM
тАО05-14-2009 11:37 AM
Re: MOUNT-F-MBRTOOSMALL
As others have stated (and it is why we're all asking for the block size via SHOW DEVICE /FULL or otherwise), the block count is a key here.
Similarly, depending on the particular SCSI controllers here, there can be size differences presented up to the OpenVMS host; some RAID controllers can present "non-transportable" (with metadata) and "transportable" (without metadata) disk configurations.
For comparison purposes, current single-spindle disks are now available with 1 and 1.5 and 2 terabyte capacities. OpenVMS can address that first of these, but the second and third are beyond the 31-bit addressing limits of the current ODS-2 and ODS-5 file systems.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-14-2009 12:15 PM
тАО05-14-2009 12:15 PM
Re: MOUNT-F-MBRTOOSMALL
_IF_ DSA1 has not yet been modified, _THEN_ this situation can be overcome by
- DISMOUNT DSA1
- MOUNT /SYSTEM DSA1: /shadow=$1$DKD100 [...] ! ONLY the member that reportedly was the smaller
- MOUNT DSA1: /SHAD=$1$DKB100: ! add the larger mem ber
The cost: lost of all modifications since the upgrade and the time of a full copy.
... if this was the system disk, then things are somewhat more complicated; the dismount involves shutdown and the boot should be from the second member.
hth
Proost.
Have one on me.
jpe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-15-2009 08:30 AM
тАО05-15-2009 08:30 AM
Re: MOUNT-F-MBRTOOSMALL
All block/buffer sizes are 512.
- Since these are virtual RZ28's I simply created new RZ28 (2GB) virtuals for DKD*.
- Then Windows file copied those to DKD* to DKC*
- Standalone boot -> backup/image the original DKB* to new DKC*
- Renamed the DKC* virtual containers to DKB*.
- Reboot with mount/shadow ... worked fine.