Uploaded image for project: 'Lustre'
  1. Lustre
  2. LU-20600

osp: cannot tell when object precreation stopped or resumed on an OST

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • None
    • None
    • 3
    • 9223372036854775807

      An MDS stops precreating objects on an OST when the free space reported by that OST drops below osp..reserved_mb_low, or its free inode count drops below osp..reserved_ino_low, and resumes only once the corresponding *_high watermark is crossed back.

      Both transitions are only reported at CDEBUG(D_INFO) level, so in practice an administrator cannot see them.  osp.*.prealloc_status reports the current state alone: polling it tells neither when a transition happened,
      nor which free space or free inode value triggered it, nor which watermark that value was compared against.  Once the OST has recovered, there is no way to tell that it was ever out of space, or for how long.

      Raising the two edges to console warnings was considered first, but it does not scale – a setup with hundreds or thousands of OSTs would flood the logs in corner cases, so it would have to be optional at the very least.

      What is needed is a way to see, per OST, when precreation last stopped and resumed and what values caused it, without adding anything to the logs.

            xyang Xiao Yang
            xyang Xiao Yang
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: