-
Type: Task
-
Status: Done (View Workflow)
-
Priority: Normal
-
Resolution: Done
-
Component/s: None
-
Labels:
-
Story Points:1
-
Sprint:SM1PD-2019 C
Currently /data is a new ZFS filesystem, with the server side named /proddata because that was the name on the old server.
We probably want a slightly different structure, for clarity, efficiency, and maintainability. I suggest that we keep mounting data products under /data, but have several ZFS filesystems mounted under that. In particular:
- /data/mcs/ (in use; old data needs to be copied over to the new server.)
- /data/sps/ (currently named /data/pfs at LAM/JHU. Keeping that would be easier. )
- /data/agcc/
- /data/drp/
The raw data filesystems (mcs,sps,agcc) should have compression turned off (we use FITS compression), but any others should have the default compression on. The server filesystem names should be the same as the exported mountpoints.
All should be group pfs. /data/sps must be user pfs-data and chmod 02755; the rest should be user pfs and 02775. [ /data/
{mcs,agcc}should also be user=pfs-data, 02755, but that needs to be a separate ticket. ].
Any other sub-directories we come up with should be their own ZFS filesystems (/data/logs, etc.)
Comments? Especially: arnaud.lefur fmadec chyan rhl philip Yoshida, Hiroshige
- relates to
-
INSTRM-895 Document Subaru /data structure
- Done
-
PIPE2D-571 Ingest into a common data repo
- Done
-
INSTRM-831 Re-layer /data usage for MCS and SPS.
- Done