Uploaded image for project: 'CPE Infrastructure'
  1. CPE Infrastructure
  2. CPE-2638

Can we take the rest of the storinator space for Copr backups?

XMLWordPrintable

    • False
    • None
    • False
    • Testable

      https://pagure.io/fedora-infrastructure/issue/12280

      Hello team, we do Copr Backend backups (built results) onto storinator.

      We backup weekly, and do rsnapshot increments (we keep ~1 month delta). Copr Backend currently consumes ~30T of storage, and the monthly delta is expected to be ~10T => which means we're going to eat 40T more on storinator (+ space for one more increment ~2.5T is needed, for the one "in progress" - till one of the old increments gets removed).

      The 4th increment is in progress right now (runs for 3 days already), next week we are going to rotate for the first time. Current status:

      ```
      df -h /srv/nfs/copr-be
      /dev/mapper/VG_nfs-copr--be 48T 41T 7.1T 86% /srv/nfs/copr-be
      ```

      I think we are going to fit for the next week increment, but It would be nice to add few more TBs to stay "calm" and not panic.

      ```

      1. vgs
        VG #PV #LV #SN Attr VSize VFree
        VG_nfs 1 4 0 wz-n 100.05t <16.41t
        ```

      Would it be OK to consume say 6TB more from the volume group now, and perhaps count with the rest of the remaining space for the future?

              Unassigned Unassigned
              rh-ee-mkonecny Michal Konecny
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: