Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

HBMM %SYSTEM-F-SHADFEATNOMNT,

 
Benjamin Levy
Frequent Advisor

HBMM %SYSTEM-F-SHADFEATNOMNT,

Hello

On a VMS V7.3-2 Alpha cluster, the SYPAGSWPFILES.COM contains
Set Shadow/Enable=HBMM Sys$Sysdevice:
after a complete cluster shutdown, the first node to reboot executes this command and gives:

%SYSTEM-F-SHADFEATNOMNT, device not mounted on system that supports requested Shadowing feature

HELP/MESSAGE does not seem to know about this error. Any ideas?

No obvious actual adverse impact on the system, other than the error message.

Thank you
11 REPLIES 11
Steven Schweda
Honored Contributor

Re: HBMM %SYSTEM-F-SHADFEATNOMNT,

I know nothing, but around here:

alp $ help /mess SHADFEATNOMNT

SHADFEATNOMNT, device not mounted on system that supports requested
shadowing feature

Facility: SET, SET Command and SET Utility

Explanation: You tried to enable an enhanced shadowing feature on the
specified shadow set, but the shadow set is mounted on at
least one system in the cluster that does not support that
feature.

User Action: Dismount the shadow set on the system that does not support
the requested enhanced shadowing feature; then try the
operation again.


alp $ write sys$output "''f$getsyi( "version")' ''f$getsyi( "arch_name")'"
V8.3 Alpha


What's mounted where?
SHOW DEVICE D
Robert Brooks_1
Honored Contributor

Re: HBMM %SYSTEM-F-SHADFEATNOMNT,

We'll need a bit more detail, like what is the policy that's in use. Is there a default policy defined for the cluster? If so, are you sure that it's defined before this attempt at using HBMM?


-- Rob
Benjamin Levy
Frequent Advisor

Re: HBMM %SYSTEM-F-SHADFEATNOMNT,

The command immediately proceeding the attempt to enable HBMM on the system disk is:

$ Set Shadow/Name=Default -
/Policy=HBMM=((MASTER_LIST=(*)),RESET_THRESHOLD=50000)


I think this may be due to the 2nd node booting into the cluster being not very far behind the 1st node. Possibly the 2nd node is far along enough in the boot for the shadow driver to count it as a node, but not far enough for the shadow driver to enable HBMM on that other node??
Robert Brooks_1
Honored Contributor

Re: HBMM %SYSTEM-F-SHADFEATNOMNT,

Possibly the 2nd node is far along enough in the boot for the shadow driver to count it as a node, but not far enough for the shadow driver to enable HBMM on that other node??

--
That's a possibility, although I'll need to think about this a bit. The SHADOW_SERVER process is required for ANY shadow set to be mounted, even if HBMM isn't used. Thus, it's hard to imagine (but not impossible) a window where enough of the system was running to allow the mounting of the shadowed system disk
on the 2nd node, but yet not enough to have
gone through the locking protocol to allow it to run any of the enhanced features (HBMM or dissimilar device shadowing).

-- Rob
Benjamin Levy
Frequent Advisor

Re: HBMM %SYSTEM-F-SHADFEATNOMNT,

OK - looked back a little more closely. Have seen the issue twice in the last month. In both cases the first node was starting to boot, and in SYPAGSWPFILES.COM. The second node had not yet started to boot - was still at >>> prompt. The second node did start to boot a little later - before the first node had finished booting - but well after the suspicious shadow driver message.