Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-30949

Calculate, allocate, or warn in relation to size of pool-level metadata and space allocated for it

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • stratisd
    • None
    • Handle Pool-level Metadata Expansion
    • Hide
      • An adequate reporting mechanism to alert users when the ratio of the metadata size to the size of the metadata region crosses a threshold.
      • An adequate means of choosing a metadata size dynamically when new devices are written so that the resulting metadata can be written to the new devices.
      • An adequate way of selecting metadata size when creating a pool.
      Show
      An adequate reporting mechanism to alert users when the ratio of the metadata size to the size of the metadata region crosses a threshold. An adequate means of choosing a metadata size dynamically when new devices are written so that the resulting metadata can be written to the new devices. An adequate way of selecting metadata size when creating a pool.
    • FutureFeature
    • sst_logical_storage
    • ssg_platform_storage
    • False
    • Hide

      None

      Show
      None

      stratisd stores its pool-level metadata in a region of bounded size. Each copy of the metadata+ its header must not require more than 254 KiB. In general, only a very large pool will require more space for metadata than 254 KiB. But, in the case that the pool-level metadata can not be written, the pool will be in an inconsistent situation that it can not easily remedy. This proposes a number of tasks to address this problem.

            amulhern@redhat.com the Mulhern
            amulhern@redhat.com the Mulhern
            stratis-team stratis-team
            storage-qe storage-qe
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: