Operating System - OpenVMS
1753776 Members
7408 Online
108799 Solutions
New Discussion юеВ

Re: -MOUNT-F-MBRTOOSMALL,

 
SOLVED
Go to solution
Joewee
Regular Advisor

-MOUNT-F-MBRTOOSMALL,

I know there is another thread with the same name for the same problem, I need more information on this.

Both the disks are identical. Im not sure why this error is popping up.

This is on my personal alpha

$ sho sys/noproc
OpenVMS V8.3 on node JOSE 3-DEC-2010 22:01:26.27 Uptime 0 00:27:53



$ sho dev d

Device Device Error Volume Free Trans Mnt
Name Status Count Label Space Count Cnt
DSA4: Mounted 0 ALPHASYS 2.98GB 413 1
$4$DKA0: (JOSE) ShadowSetMember 0 (member of DSA4:)
$4$DKA100: (JOSE) Online 0
$4$DKA300: (JOSE) Online 0
$ mount/system/noassist dsa4: /shad=($4$DKA100:) ALPHASYS ALPHASYS
%MOUNT-I-MOUNTED, ALPHASYS mounted on _DSA4:
%MOUNT-I-SHDWMEMFAIL, _$4$DKA100: (JOSE) failed as a member of the shadow set
-MOUNT-F-MBRTOOSMALL, must be the same size or larger than logical volume size
%MOUNT-I-ISAMBR, _$4$DKA0: (JOSE) is a member of the shadow set
$


$ sho dev $4$DKA100:/full

Disk $4$DKA100: (JOSE), device type RZ29, is online, allocated, deallocate on
dismount, mounted, software write-locked, file-oriented device, shareable,
available to cluster, error logging is enabled.

Error count 0 Operations completed 67498
Owner process "SYSTEM" Owner UIC [SYSTEM]
Owner process ID 000000AD Dev Prot S:RWPL,O:RWPL,G:R,W
Reference count 2 Default buffer size 512
Total size 3.99GB Sectors per track 113
Total cylinders 3708 Tracks per cylinder 20
Logical Volume Size 3.99GB Expansion Size Limit 1023.99GB
Allocation class 4

Volume label "ALPHASYS" Relative volume number 0
Cluster size 16 Transaction count 1
Free space 3.95GB Maximum files allowed 16711679
Extend quantity 5 Mount count 1
Mount status Process Cache name "_DSA4:XQPCACHE"
Extent cache size 64 Maximum blocks in extent cache 830121
File ID cache size 64 Blocks in extent cache 0
Quota cache size 0 Maximum buffers in FCP cache 450
Volume owner UIC [SYSTEM] Vol Prot S:RWCD,O:RWCD,G:RWCD,W:RWCD

Volume Status: ODS-2, subject to mount verification, allocation inhibited
because of error on bitmap, erase on delete, file high-water marking,
write-back caching enabled.

$ sho dev dka0/full

Disk DSA4:, device type RZ29, is online, mounted, file-oriented device,
shareable, available to cluster, error logging is enabled, device supports
bitmaps (no bitmaps active).

Error count 0 Operations completed 10604
Owner process "" Owner UIC [SYSTEM]
Owner process ID 00000000 Dev Prot S:RWPL,O:RWPL,G:R,W
Reference count 194 Default buffer size 512
Total size 3.99GB Sectors per track 113
Total cylinders 3708 Tracks per cylinder 20
Logical Volume Size 3.99GB Expansion Size Limit 1023.96GB

Volume label "ALPHASYS" Relative volume number 0
Cluster size 16 Transaction count 413
Free space 2.98GB Maximum files allowed 492946
Extend quantity 5 Mount count 1
Mount status System Cache name "_DSA4:XQPCACHE"
Extent cache size 64 Maximum blocks in extent cache 625108
File ID cache size 64 Blocks in extent cache 625040
Quota cache size 0 Maximum buffers in FCP cache 450
Volume owner UIC [1,1] Vol Prot S:RWCD,O:RWCD,G:RWCD,W:RWCD

Volume Status: ODS-5, subject to mount verification, protected subsystems
enabled, file high-water marking, write-through caching enabled, hard
links enabled.

Disk $4$DKA0:, device type RZ29, is online, member of shadow set DSA4:, error
logging is enabled.

Error count 0 Shadow member operation count 7549
Allocation class 4
11 REPLIES 11
Heinz W Genhart
Honored Contributor

Re: -MOUNT-F-MBRTOOSMALL,

Hi Joewee

DKA0 and DKA100 are not initialized the same way.
DKA100: Maximum files allowed 16711679
DKA0: Maximum files allowed 492946

Try to initialize DKA100 the same way as DKA0 is.

INIT(/nohigh) /LIMIT/OWNER=SYSTEM/SIZE=exactly-same-size-in-blocks-as-dka0 DKA100

Then try to add DKA100 into the shadow-set DSA4:

If there is no reason to use highwater marking I would recommand to disable higwater marking on DSA4, with SET VOLUME/NOHIGH DSA4.

Regards

Geni
Volker Halle
Honored Contributor

Re: -MOUNT-F-MBRTOOSMALL,

Joewee,

could you please repeat the SHOW DEV/FULL commands after setting $ SET PROC/UNIT=BLOCKS ?

Interestingly, the other ITRC article also seems to have happened on an Alpha emulator (PersonalAlpha ?).

Volker.
Joewee
Regular Advisor

Re: -MOUNT-F-MBRTOOSMALL,

Hi Geni,

I can do that.

I will give this option a try and I will let you know the out come.


Hi Volker,

Please find the output below.


$ sho dev dka0/full

Disk DSA4:, device type RZ29, is online, mounted, file-oriented device,
shareable, available to cluster, error logging is enabled, device supports
bitmaps (no bitmaps active).

Error count 0 Operations completed 11198
Owner process "" Owner UIC [SYSTEM]
Owner process ID 00000000 Dev Prot S:RWPL,O:RWPL,G:R,W
Reference count 194 Default buffer size 512
Total blocks 8380080 Sectors per track 113
Total cylinders 3708 Tracks per cylinder 20
Logical Volume Size 8380080 Expansion Size Limit 2147418112

Volume label "ALPHASYS" Relative volume number 0
Cluster size 16 Transaction count 413
Free blocks 6251088 Maximum files allowed 492946
Extend quantity 5 Mount count 1
Mount status System Cache name "_DSA4:XQPCACHE"
Extent cache size 64 Maximum blocks in extent cache 625108
File ID cache size 64 Blocks in extent cache 624992
Quota cache size 0 Maximum buffers in FCP cache 450
Volume owner UIC [1,1] Vol Prot S:RWCD,O:RWCD,G:RWCD,W:RWCD

Volume Status: ODS-5, subject to mount verification, protected subsystems
enabled, file high-water marking, write-through caching enabled, hard
links enabled.

Disk $4$DKA0:, device type RZ29, is online, member of shadow set DSA4:, error
logging is enabled.

Error count 0 Shadow member operation count 8089
Allocation class 4

$ sho dev dka100/full

Disk $4$DKA100: (JOSE), device type RZ29, is online, file-oriented device,
shareable, available to cluster, error logging is enabled.

Error count 0 Operations completed 67504
Owner process "" Owner UIC [SYSTEM]
Owner process ID 00000000 Dev Prot S:RWPL,O:RWPL,G:R,W
Reference count 0 Default buffer size 512
Total blocks 8380080 Sectors per track 113
Total cylinders 3708 Tracks per cylinder 20
Allocation class 4

$ mount/over=id dka100
%MOUNT-W-VOLSHDWMEM, mounting a shadow set member volume; volume write locked
%MOUNT-I-MOUNTED, ALPHASYS mounted on _$4$DKA100: (JOSE)
$ sho dev dka100/full

Disk $4$DKA100: (JOSE), device type RZ29, is online, allocated, deallocate on
dismount, mounted, software write-locked, file-oriented device, shareable,
available to cluster, error logging is enabled.

Error count 0 Operations completed 67583
Owner process "SYSTEM" Owner UIC [SYSTEM]
Owner process ID 000000AD Dev Prot S:RWPL,O:RWPL,G:R,W
Reference count 2 Default buffer size 512
Total blocks 8380080 Sectors per track 113
Total cylinders 3708 Tracks per cylinder 20
Logical Volume Size 8380080 Expansion Size Limit 2147475456
Allocation class 4

Volume label "ALPHASYS" Relative volume number 0
Cluster size 16 Transaction count 1
Free blocks 8301216 Maximum files allowed 16711679
Extend quantity 5 Mount count 1
Mount status Process Cache name "_DSA4:XQPCACHE"
Extent cache size 64 Maximum blocks in extent cache 830121
File ID cache size 64 Blocks in extent cache 0
Quota cache size 0 Maximum buffers in FCP cache 450
Volume owner UIC [SYSTEM] Vol Prot S:RWCD,O:RWCD,G:RWCD,W:RWCD

Volume Status: ODS-2, subject to mount verification, allocation inhibited
because of error on bitmap, erase on delete, file high-water marking,
write-back caching enabled.

$
Joewee
Regular Advisor

Re: -MOUNT-F-MBRTOOSMALL,

Geni,

Its not working..

$ init/limit/owner=system/size=8380080 dka100 ALPHASYS
%INIT-I-DEFCLUSTER, value for /CLUSTER defaulted to 16
$ mount/system/noassist dsa4: /shad=($4$DKA100:) ALPHASYS ALPHASYS
%MOUNT-I-MOUNTED, ALPHASYS mounted on _DSA4:
%MOUNT-I-SHDWMEMFAIL, _$4$DKA100: (JOSE) failed as a member of the shadow set
-MOUNT-F-MBRTOOSMALL, must be the same size or larger than logical volume size
%MOUNT-I-ISAMBR, _$4$DKA0: (JOSE) is a member of the shadow set
$ SET VOLUME/NOHIGH DSA4
$ mount/system/noassist dsa4: /shad=($4$DKA100:) ALPHASYS ALPHASYS
%MOUNT-I-MOUNTED, ALPHASYS mounted on _DSA4:
%MOUNT-I-SHDWMEMFAIL, _$4$DKA100: (JOSE) failed as a member of the shadow set
-MOUNT-F-MBRTOOSMALL, must be the same size or larger than logical volume size
%MOUNT-I-ISAMBR, _$4$DKA0: (JOSE) is a member of the shadow set
$
Volker Halle
Honored Contributor

Re: -MOUNT-F-MBRTOOSMALL,

Joewee,

the total no. of blocks and logical volume size are identical for both drives (8380080 blocks). But - for whatever reason - the Expansion size limit is different.

I'd suggest that you just do a plain INIT $4$DKA100: SCRATCH and try again. The device will be overwritten by the shadowcopy anyway.

Volker.
Joewee
Regular Advisor

Re: -MOUNT-F-MBRTOOSMALL,

Volker,

Please find the output below.

$ init dka100
_Label: ALPHASYS
$ init $4$DKA100:
_Label: ALPHASYS
$ mount/system/noassist dsa4: /shad=($4$DKA100:) ALPHASYS ALPHASYS
%MOUNT-I-MOUNTED, ALPHASYS mounted on _DSA4:
%MOUNT-I-SHDWMEMFAIL, _$4$DKA100: (JOSE) failed as a member of the shadow set
-MOUNT-F-MBRTOOSMALL, must be the same size or larger than logical volume size
%MOUNT-I-ISAMBR, _$4$DKA0: (JOSE) is a member of the shadow set
$ mount/over=id dka100
%MOUNT-I-MOUNTED, ALPHASYS mounted on _$4$DKA100: (JOSE)
$ sho dev dka100/full

Disk $4$DKA100: (JOSE), device type RZ29, is online, allocated, deallocate on
dismount, mounted, file-oriented device, shareable, available to cluster,
error logging is enabled.

Error count 0 Operations completed 69220
Owner process "SYSTEM" Owner UIC [SYSTEM]
Owner process ID 000000AD Dev Prot S:RWPL,O:RWPL,G:R,W
Reference count 2 Default buffer size 512
Total blocks 8380080 Sectors per track 113
Total cylinders 3708 Tracks per cylinder 20
Logical Volume Size 8380080 Expansion Size Limit 9371648
Allocation class 4

Volume label "ALPHASYS" Relative volume number 0
Cluster size 16 Transaction count 1
Free blocks 8379760 Maximum files allowed 246472
Extend quantity 5 Mount count 1
Mount status Process Cache name "_DSA4:XQPCACHE"
Extent cache size 64 Maximum blocks in extent cache 837976
File ID cache size 64 Blocks in extent cache 0
Quota cache size 0 Maximum buffers in FCP cache 450
Volume owner UIC [SYSTEM] Vol Prot S:RWCD,O:RWCD,G:RWCD,W:RWCD

Volume Status: ODS-2, subject to mount verification, file high-water marking,
write-back caching enabled.

$
Volker Halle
Honored Contributor

Re: -MOUNT-F-MBRTOOSMALL,

Joewee,

what about $ INIT/LIMIT $4$DKA100: SCRATCH

If you look at the size of the .vdisk container files on your host operating system (Windows), what sizes are shown for the 2 .vdisk files ?

Volker.
Joewee
Regular Advisor

Re: -MOUNT-F-MBRTOOSMALL,

Volker,

On windows.

DKA100 - 3.99 GB (4,290,600,960 bytes)
DKA0 - 3.99 GB (4,290,600,960 bytes)

One more thing is, I have created the container file for DKA0 with the FreeAXP emulator, and the container file for DKA100 with Personal Alpha. I'm going to create another container file with FreeAXP and check. Very slimmest of chances are there still im gonna give a try.

Output:

$ INIT/LIMIT $4$DKA100: SCRATCH
%INIT-I-DEFCLUSTER, value for /CLUSTER defaulted to 16
$ mount/system/noassist dsa4: /shad=($4$DKA100:) ALPHASYS ALPHASYS
%MOUNT-I-MOUNTED, ALPHASYS mounted on _DSA4:
%MOUNT-I-SHDWMEMFAIL, _$4$DKA100: (JOSE) failed as a member of the shadow set
-MOUNT-F-MBRTOOSMALL, must be the same size or larger than logical volume size
%MOUNT-I-ISAMBR, _$4$DKA0: (JOSE) is a member of the shadow set
$
Volker Halle
Honored Contributor
Solution

Re: -MOUNT-F-MBRTOOSMALL,

Joewee,

and does the same error also happen when running under FreeAXP instead of PersonalAlpha ?

Volker.