1588739 : Maxwell storage

Created: 2026-03-31T10:53:30Z - current status: open

**

Anonymized Summary:

A user is experiencing storage limitations on the Maxwell cluster while working with beamline-related data that is not directly tied to an official beamtime. The data is used for preparation, commissioning, or upgrade processes and requires image processing and analysis, which is currently handled on local office/lab computers. The user is inquiring about: 1. Policies for handling such intermediate/non-beamtime data on Maxwell. 2. Possibility of mounting additional DESY storage to offload this data.

Suggested Solution/Next Steps:

  1. Storage Options for Non-Beamtime Data:

  2. DUST (/data/dust):

    • Fast and suitable for temporary or reproducible data (e.g., intermediate analysis files).
    • No security guarantees (data may be purged without notice).
    • Policy note: Explicitly intended for temporary use; not for long-term storage.
    • Source: Maxwell Storage Documentation

  3. dCache (/pnfs/desy.de/):

    • Recommended for long-term storage of larger datasets.
    • Requires coordination with <osm.service@desy.de> if the user’s group lacks allocated space.
    • Source: Maxwell Storage Documentation

  4. Group-Specific GPFS (e.g., GPFS-FS for PETRA III/FLASH):

    • If the data is beamline-adjacent, check with the ASAP3 team (it-asap3@desy.de) for access to GPFS-FS.
    • Source: Storage Overview

  5. Policy Clarification:

  6. Temporary data (e.g., commissioning/upgrade files) should not reside on Maxwell’s home directories (/home, 30GB limit) or scratch space (/scratch, subject to deletion).

  7. Long-term storage requires migration to dCache or a group-owned GPFS (contact <maxwell.service@desy.de> for details).

  8. **Action Items for the