Hello,

I installed the 3.1.0.8 version, as Norbert told, and now we are able to start
the dsmrecalld and dsmmonitord deamons, but when we try to add HSM to a FS we
get these messages:

04/14/00   09:07:53 ANS9529W dsmmonitord: cannot obtain handle of file system
state file
04/14/00   09:07:56 ANS9512E dsmhsm: cannot set DM attributes on session 19 for
file handle = 000000000239ffff 000000190000ff00 0000000000000000
000001ff40ff00ff token = 0. Reason : Invalid argument
04/14/00   09:07:56 ANS9529W dsmhsm: cannot obtain handle of file system state
file
04/14/00   09:07:57 ANS9848W Cannot activate file system /prueba_HSM.
04/14/00   09:08:03 ANS9529W dsmmonitord: cannot obtain handle of file system
state file
04/14/00   09:08:13 ANS9529W dsmmonitord: cannot obtain handle of file system
state file
04/14/00   09:08:23 ANS9529W dsmmonitord: cannot obtain handle of file system
state file
04/14/00   09:08:32 ANS9512E dsmhsm: cannot set DM attributes on session 19 for
file handle = 000000000239ffff 000000180000ff00 0000000000000000
000001ff40ff00ff token = 0. Reason : Invalid argument
04/14/00   09:08:32 ANS9529W dsmhsm: cannot obtain handle of file system state
file
04/14/00   09:08:32 ANS9529W dsmhsm: cannot obtain handle of file system state
file
04/14/00   09:08:33 ANS9848W Cannot activate file system
/home/intra/prd/dat/fich_rtr.
04/14/00   09:08:33 ANS9529W dsmmonitord: cannot obtain handle of file system
state file
04/14/00   09:08:33 ANS9529W dsmmonitord: cannot obtain handle of file system
state file
04/14/00   09:08:43 ANS9529W dsmmonitord: cannot obtain handle of file system
state file
04/14/00   09:08:43 ANS9529W dsmmonitord: cannot obtain handle of file system
state file
04/14/00   09:08:53 ANS9529W dsmmonitord: cannot obtain handle of file system
state file
04/14/00   09:08:53 ANS9529W dsmmonitord: cannot obtain handle of file system
state file

and in the system messages there are two lines at the same time:

Apr 14 09:07:56 fintra unix: ADSM HSM XOPEN DSM API Kernel Extension
dmiAttrStateChange bogus len 1040
Apr 14 09:07:56 fintra /sbin/cvcd-(HOSTNAME:fintra): lost data output
Apr 14 09:08:32 fintra unix: ADSM HSM XOPEN DSM API Kernel Extension
dmiAttrStateChange bogus len 1040

Any idea?

Thank you
Pilar Prieto






Norbert Conrad <Norbert.Conrad AT hrz.uni-giessen DOT de> con fecha 13/04/2000 
19:52:46

Hello,

it seems ADSM client 3.1.0.7 does not support Veritas 3.3.2 . This can be
concluded from the README files:

-----------------------------------------------------------------
3.1.0.7 README:
3.1.0.7 README:

   HSM requires the following software in order to run:

       Sun Solaris 2.6
       Veritas file system (VxFS 3.2.4 or 3.2.5)

------------------------------------------------------------------
3.1.0.8 README:
3.1.0.8 README:

   HSM requires the following software in order to run:

       Sun Solaris 2.6     (Solaris 7 is not supported)
       Veritas file system (VxFS 3.2.4-3.2.6, or 3.3.2;
                                    VxFS 3.3.1 is not supported)

 o 2 different packages of the Solaris 2.6/7 client are supplied:
   sunadsm.pkg contains all components and supports Veritas file system
   version 3.2.4 - 3.2.6 .
   sunadsm.pkg.33 contains all components and supports Veritas file system
   version 3.3.2 .

--------------------------------------------------------------------
Kind regards,
Kind regards,

Norbert.

--
Norbert Conrad                             phone: ++49 641 9913021
Norbert Conrad                             phone: ++49 641 9913021
Hochschulrechenzentrum                     email: conrad AT hrz.uni-giessen DOT 
de
Heinrich-Buff-Ring 44
35392 Giessen
Germany

                   Leave others their otherness

______________________________________________________________________________

Asunto:   Re: Problem with dsmrecalld (HSM)


> Hello,
>
> we are installing , well, trying to, HSM in a Solaris 2.6 server, Veritas
3.3.2,
> ADSM client 3.1.0.7. When we try to start the dsmrecalld deamon we are getting
> the following message:
>
> 04/13/00   16:13:40 ANS9500W dsmrecalld: cannot disposition the mount event.
> Reason: Bad address
> 04/13/00   16:13:40 ANS9510E dsmrecalld: cannot get event messages from
session
> 4,
> expected max message-length = 1024, returned message-length = -268437048.
> Reason : Resource temporarily unavailable
>
> Any idea on what's happening?
>
> Thank you and regards
> Pilar Prieto
>