Ginkgo & Kauri: organisation of filesystems

System configuration

Currently ginkgo has three hard disk systems: kauri also has three hard disk systems: Check the appended tables for detailed partitioning information.

/ncc/ttpro hierarchy

In the contect of TestTraffic project, the /ncc/ttpro (tt production) hierarchy is most important. The following table lists the purpose of the various subtrees.

/ncc/ttpro /bin    scripts and executables supporting TT production
  /config    configuration files
  /include    include files for general use
  /lib    program libraries for ROOT and analysis software
  /cron    scripts run by cron
  /data /plots/    output directory for daily plots; currently maps to publish area on Filer.
    /processed/ year/month/day   storage of processed data (PCBK files)
    /raw/ year/month/day   storage of incoming raw data
    /root/ year/month/day   storage of final data (ROOT files)
    /sql    storage of MySQL database files
    tapes/    online tape database: which tape holds which files
  /sbin    supporting programs, not to be called directly by users
  /spool    spooling space, short term storage area
  /src    working area for code development (regularly checked in to CVS)
  /tmp    temporary files, scratch area
  /SETUP    source trees and other stuff related to testbox installation

The colors in the left side of this table indicate the distribution of /ncc/ttpro over different filesystems:

Backup policy

The backup policy agreed upon with OPS is to have only partitions used by the OS and the nccfs* filesystems included in the backup scheme (daily incremental, weekly or biweekly full backup); the ttfs* filesystems are responsibility of TestTraffic operators.

With the exception of raw_data and processed_data storage, there is no need for backup of complete external filesystems: these hold root_data which is saved on tape immediately after creation and can also easily be recreated from processed data files. raw_data are saved to tape upon arrival, but it is good to have two copies of it: if one tape is damaged, we still have the second. Full backups of raw- and processed data should be done at least once a month.

Ginkgo disk partitioning

disk / partition size (kbytes) Mount point
/dev/dsk/c0t0d0s0 57567 /
/dev/dsk/c0t0d0s3 577286 /usr
/dev/dsk/c0t0d0s4 192423 /var
/dev/dsk/c0t0d0s5 2052750 /opt
/dev/dsk/c0t0d0s6 2668822 /export/nccfs6
/dev/dsk/c0t0d0s7 2776150 /export/nccfs7
/dev/dsk/c2t3d0s0 6452806 /export/ttfs1
/dev/dsk/c2t3d0s1 6452806 /export/ttfs2
/dev/dsk/c2t3d0s3 6452806 /export/ttfs3
/dev/dsk/c2t3d0s4 6452806 /export/ttfs4
/dev/dsk/c2t3d0s5 6452806 /export/ttfs5
/dev/dsk/c2t3d0s6 6452806 /export/ttfs6
/dev/dsk/c2t3d0s7 6474926 /export/ttfs7
/dev/dsk/c1t4d0s0 6452806 /export/ttfs8
/dev/dsk/c1t4d0s1 6452806 /export/ttfs9
/dev/dsk/c1t4d0s3 6452806 /export/ttfs10
/dev/dsk/c1t4d0s4 6452806 /export/ttfs11
/dev/dsk/c1t4d0s5 6452806 /export/ttfs12
/dev/dsk/c1t4d0s6 6452806 /export/ttfs13
/dev/dsk/c1t4d0s7 6474926 /export/ttfs14

Kauri disk partitioning

disk / partition size (kbytes) Mount point
/dev/dsk/c0t0d0s0 57567 /
/dev/dsk/c0t0d0s3 577286 /usr
/dev/dsk/c0t0d0s4 192423 /var
/dev/dsk/c0t0d0s5 2052750 /opt
/dev/dsk/c0t0d0s6 6013278 /export/nccfs4
/dev/dsk/c0t1d0s3 5804406 /export/ttfs15
/dev/dsk/c0t1d0s4 5804406 /export/ttfs16
/dev/dsk/c0t1d0s5 5804406 /export/ttfs17
/dev/dsk/c1t3d0s0 13321532 /export/ttfs18
/dev/dsk/c1t3d0s1 13321532 /export/ttfs19
/dev/dsk/c1t3d0s4 13321532 /export/ttfs20
/dev/dsk/c1t3d0s5 13321532 /export/ttfs21
/dev/dsk/c1t3d0s6 13321532 /export/ttfs22
/dev/dsk/c1t3d0s7 3975730 /export/ttfs23

$Id: ginkgo-filesystems.html,v 1.2 2001/11/23 14:44:47 wilhelm Exp $