Filesystem layout for install

Clovertech Forums Read Only Archives Cloverleaf Operating Systems Filesystem layout for install

  • Creator
    Topic
  • #48678
    Joshua Snyder
    Participant

      I’ve been tasked with building a new server which will support the Cloverleaf 5.1 Integrator application and I’m looking for suggestions for a proper filesystem layout.  I’ve been browsing the install guide for both 5.1 and 5.4 and they give examples that seem to be a bit contradictory.  At one point, they’ll show /opt/quovadx as an installation directory, but then they make note that the install script for HP-UX will try to create an lvhci mount point to /integrator.  Then later, the docs make mention of FPATH being set to /integrator/kshlib and ‘setroot’ being issued /quovadx/qdx5.1/integrator.  Maybe it’s just my lack of previous exposure to the product, but, I could use some clarification as to how everybody lays out their filesystems.  

      Also, what do you do for working directories for the output data files?  Our current environment is a bit of a mess and I’ve been asked to better define the filesystem structure for the new server.

    Viewing 1 reply thread
    • Author
      Replies
      • #59372
        Chris Brossette
        Participant

          Joshua,

          I had the same dilemna on one of our last upgrades, many of the directories that grow were actually under the /qdx logical volume structure and should have been created outside.  So for what it is worth, here is what we did…..

          Basically the /qdx logical volume contains the Cloverleaf system, Netconfigs, tclprocs, xlates, etc…..any files that are processed and kept in the Cloverleaf system are retained in their own separate logical volumes and structure.  Any scripts (tcl, ksh, etc) are outside of the /qdx directory structure supplied by Quovadx so they will not be overwritten in future upgrades and the structure allows us to add additional versions….

          /dev/fslv00      13107200   9679488   27%    29152     2% /qdx

          /dev/fslv01        786432    182168   77%     3813     9% /qdx/charges

          /dev/fslv02       3932160   3931232    1%        4     1% /qdx/hpf

          /dev/fslv03        262144    258404    2%       29     1% /qdx/notif

          /dev/lv11        78643200  20376464   75%    46540     2% /qdx/cycle_saves

          # ls -al /qdx

          total 24

          drwxrwxrwx   9 root     system          256 Jan 26 2006  .

          drwxr-xr-x  20 root     system         4096 Aug 01 12:28 ..

          drwxr-xr-x   6 hci      staff           256 Jan 26 2006  charges

          drwxr-xr-x   7 hci      staff          4096 Apr 11 11:28 cycle_saves

          drwxr-xr-x   3 hci      staff           256 Jan 22 2006  hpf

          drwxrwxr-x   9 hci      staff          4096 Dec 21 2005  local

          drwxr-xr-x   2 hci      staff           256 Jan 22 2006  lost+found

          drwxr-xr-x   6 hci      staff           256 Jan 26 2006  notif

          drwxr-xr-x   3 hci      staff           256 Jan 26 2006  qdx5.3

          # ls -al /qdx/cycle_saves

          total 69752

          drwxrwxr-x   9 hci      staff           512 Apr 11 11:25 .

          drwsrwsr-x  14 hci      staff           512 Jul 07 12:57 ..

          drwxrwxr-x   2 hci      staff           512 Nov 03 2005  env_tar

          drwxrwxr-x   2 hci      staff           512 Oct 31 2005  medq

          drwxr-x—   3 root     system          512 Oct 03 2005  portal

          drwxr-xr-x 205 hci      staff          5120 Aug 01 23:30 qlive1

          drwxr-xr-x 205 hci      staff          5120 Aug 01 23:40 qlive2

          drwxrwxr-x   2 hci      staff           512 Oct 11 2005  qtest1

          drwxrwxr-x   2 hci      staff           512 Oct 11 2005  qtest2

          # ls -al /qdx/charges

          total 48

          drwxr-sr-x   6 hci      staff           512 Feb 21 14:46 .

          drwsrwsr-x  14 hci      staff           512 Jul 07 12:57 ..

          drwxrwsr-x   2 hci      staff          4096 Aug 02 10:00 log

          drwxrwsr-x  13 hci      staff           512 Feb 08 12:56 qdev

          drwxrwxr-x  14 hci      staff           512 Feb 14 12:17 qlive

          drwxrwxr-x  15 hci      staff          1024 Jun 06 10:08 qtest

          # ls -al /qdx/charges/qlive

          total 312

          drwxrwxr-x  14 hci      staff           512 Feb 14 12:17 .

          drwxr-sr-x   6 hci      staff           512 Feb 21 14:46 ..

          drwxrwxrwx   2 hci      staff           512 Mar 07 10:37 a4

          drwxrwxr-x   2 hci      staff         17920 Jun 06 14:42 accu

          drwxrwxr-x   3 hci      staff         11264 Aug 02 10:00 apollonew

          drwxrwxr-x   2 hci      staff           512 Mar 19 2004  cath

          drwxrwxr-x   2 hci      staff         45056 Aug 01 22:23 lab

          drwxrwxr-x   2 hci      staff          7168 Aug 01 14:05 mems

          drwxrwxr-x   2 hci      staff         25600 Aug 01 22:30 muse

          drwxrwxr-x   2 hci      staff          7168 Aug 01 10:51 perse

          drwxrwxr-x   2 hci      staff          1024 Mar 06 07:45 pg_rehab

          drwxrwxr-x   2 hci      staff          4096 Aug 01 19:00 redoc_bhs

          drwxrwxr-x   2 hci      staff           512 Jul 08 2005  redoc_mps

          drwxrwxr-x   2 hci      staff          7168 Mar 29 18:00 rehab

          #

          I hope the screen prints give you an idea of how we have our structure.  We have fine-tuned it over the last couple of upgrades.  If you have questions, please let me know

          Chris Brossette

          MS Baptist Health Systems

          cbrossette@mbhs.org

          601.968.1462

        • #59373
          Joshua Snyder
          Participant

            Thanks a lot Chris.  That’s exactly what I was looking for.

            ~ Josh

        Viewing 1 reply thread
        • The forum ‘Operating Systems’ is closed to new topics and replies.