I seem to have two problems with the new Solaris 2.6 client...

Client version 3, release 1, level 0.5
pkg name, IP21383.pkg for Solaris 2.6


1.  The package does not install properly on a new ADSM client system.

    This is because the /etc/adsm directory does not already exist.

    I believe the following code in the 'postinstall' script is
    causing the problem.  It only checks for /etc/adsm/SpaceMan
    And then tries to make all these sub directores and check the file.
    Then it fails on systems that ADSM client has never been installed
    on because /etc/adsm doesn't exist.. (there wasn't a check for that)

>#if the client is installed without HSM the file
>#/etc/adsm/SpaceMan/config/dsmmigfstab is needed
>#if it does not exist, it has to be created
>if [ -d /etc/adsm/SpaceMan ]
>then
> if [ -d /etc/adsm/SpaceMan/config ]
> then
>  if [ ! -f /etc/adsm/SpaceMan/config/dsmmigfstab ]
>  then
>   touch /etc/adsm/SpaceMan/config/dsmmigfstab
> else
>   echo " "
>  fi
> else
>  mkdir /etc/adsm/SpaceMan/config
>  touch /etc/adsm/SpaceMan/config/dsmmigfstab
> fi
>else
> mkdir /etc/adsm/SpaceMan
> cd /etc/adsm/SpaceMan
> mkdir config
> cd /etc/adsm/SpaceMan/config
> touch dsmmigfstab
>fi

I am not an expert script writer but, why not change this whole check
into alot less lines.

if [ ! -f /etc/adsm/SpaceMan/config/dsmmigfstab ]
  then
    mkdir -p /etc/adsm/SpaceMan/config
    touch /etc/adsm/SpaceMan/config/dsmmigfstab
  else
   echo " "
fi


2.  My ADSM client is backing up certain mounted directories
    that it shouldn't be!!!!

    It is backing up mounted directories that are
    exported from and mounted on the machine I am backing up...

    They are directories mounted with 'lofs'...

    lofs  = loop back virtual file system.  So the server
            doesn't use NFS to mount a directory exported from
            itself, and it also allows you to mount things in
            different places that are already mounted (instead of
            using soft links)

example...

ufs file system:

/dev/dsk/c1t0d0s7    4123342 2605571 1476538    64%    /export/home3

lofs file system:

/export/home3/mwg    4123342 2605571 1476538    64%    /home/mwg

So, on this machine, /export/home3 is getting backed up, and also
/home/mwg is getting backed up, as a separate file system!

This is the exact opposite of a bug I was encountering on revision 0.4
of the client, where /export/home3/mwg WASN'T getting backed up because
/home/mwg was being lofs mounted....  It appears that Some sort of basic
logic in the client software must be messed up, or someone doesn't know
about lofs....

I dont have any special 'AUTOMOUNT /home' statements in any options
files. So why is /home/mwg getting backed up as a filesystem?  I believe
because some confusion exists as to what should be in the
"DOMAIN ALL-LOCAL' default...

I would treat lofs mounted file systems just as I would NFS ones and
not back them up unless specificaly told to.

Anyone have any suggestions for me?  Or am I way off in these problems
and somthing else may be the cause?

--
Matthew Glanville
Matthew Glanville
mwg AT kodak DOT com
(716) 477-9371