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

DoM component inherited from parent/ROOT does not honor lod.*.dom_stripesize limit

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • Minor
    • None
    • None
    • None
    • 3
    • 9223372036854775807

    Description

      It appears that if lod.*.dom_stripesize is set on the MDT, then it prevents setting new explicit/default layouts on files/directories via "lfs setstripe", but it does not affect the inheritance of DoM components from parent/ROOT default layouts. The following commands show this:

      $ lfs setstripe -E 1M -L mdt -E eof -c 1 /mnt/testfs
      $ lctl set_param lod.*.dom_stripesize=64K
      $ touch /mnt/testfs/dom
      $ lfs getstripe /mnt/testfs/dom
      

      The dom file is created with a 1MB DoM component instead of a 64KB DoM component.

      I wonder if it makes sense to use the new "lod.*.dom_stripesize_max_kb" parameter to control the maximum amount of space for DoM components as they are created, while the older "lod.*.dom_stripesize" parameter would control what the maximum DoM component size can be specified by "lfs setstripe"? Alternately, we could just consider this existing behavior as a bug and change new files to be limited to "dom_stripesize" regardless of where the parameter came from.

      Attachments

        Issue Links

          Activity

            People

              tappro Mikhail Pershin
              adilger Andreas Dilger
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: