Another thought --

LSM is a pig for changing permissions after a reboot.
I have a note to use chmod -hR and chown -fR
and somtimes have put these in startup scripts.

F. Fernandez wrote
> Sent: 26 January 2004 15:27
> To: informix-list@iiug.org
> Subject: 9.21.FC6 - problems started with LSM installation in alpha
> tru64 5.1
>
>
> Hi all!
>
> A customer with an Alpha running Tru64 Unix 5.1
> installed new and larger disks mirrored with LSM
> (don't ask me why).

To be able to use more than 14GB on a disk ?

>
> Preliminary tests run ok but when users started to
> work this morning the JDBC sessions started to die
> with "System or internal error" and "Attempt to
> connect to database server (dbserver) failed".
> Also, sessions in dbaccess running complex queries
> frequently abort with error "25580 - System error
> occurred in network function".
>
> IDS logs show no problem. IBM/Informix support
> says can't find any problem.
>
> It's probably an OS problem derived from the
> activation of LSM but HP support is nothing like
> IBM/Informix's.
>
> Has anyone had a similar problem?

In my experience of LSM, there is NO difference between LSM, SAN and directly configured disks under Tru64. The only slight wrinkle
might be on the permission of the underlying chunks, which normally link back to /dev/rvol/rootdg.

I cannot think of any reason why this would affect only JDBC unless the permissions of the java/jdbc files have changed.

I think it unlikely LSM is the problem. We use LSM on many of our dev servers and there has not been any network issues. It is a
storage system that works reasonably well.

Colin Bull
c.bull@videonetworks.com

sending to informix-list