Uploaded image for project: 'Lustre'
  1. Lustre
  2. LU-10176 Data-on-MDT phase II
  3. LU-10808

DoM: component end should align with dom_stripesize

Details

    • Technical task
    • Resolution: Fixed
    • Minor
    • Lustre 2.12.0
    • Lustre 2.11.0
    • 9223372036854775807

    Description

      If the DoM component extent_end is set larger than the MDT dom_stripesize (via lfs setstripe -Eextent_end -L mdt ) then this currently generates an error.  Since users do not have any easy way to determine the dom_stripesize on the MDT, and it may in fact be different on a per-MDT basis (e.g. if MDT0000 sets dom_stripesize=0 because it was formatted before DoM, or it is adjusted automatically by the MDS when the MDT is nearly full).  This complicates DoM usage for users (imagine a striped directory that has different DoM size limits for the MDTs it is striped over).

      The MDS should automatically adjust the component extent_end to match the MDT dom_stripesize, and if dom_stripesize=0 then the DoM component should be removed.

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. LU-10786 sanity-flr test_45: Create /mnt/lustre/d45.sanity-flr/f45.sanity-flr failed

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. LU-10917 If setstripe for DoM file fails, less/no information is given

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. LU-11608 DoM2: inherited DoM component size is not limited

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          New Feature - A new feature of the product, which has yet to be developed. LU-10070 PFL self-extending file layout

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved
          is related to

          Bug - A problem which impairs or prevents the functions of the product. LU-10465 increase default stripe size to 4MB

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved
          mentioned in

          Page Loading...

          Activity

            [LU-10808] DoM: component end should align with dom_stripesize
            adilger Andreas Dilger made changes -
            Link New: This issue is related to EX-513 [ EX-513 ]
            adilger Andreas Dilger made changes -
            Link New: This issue is related to LU-10786 [ LU-10786 ]
            jamesanunez James Nunez (Inactive) made changes -
            Remote Link New: This issue links to "Page (Whamcloud Community Wiki)" [ 23570 ]
            adilger Andreas Dilger made changes -
            Link New: This issue is related to LU-11608 [ LU-11608 ]
            pjones Peter Jones made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: In Progress [ 3 ] New: Resolved [ 5 ]
            tappro Mikhail Pershin made changes -
            Status Original: Open [ 1 ] New: In Progress [ 3 ]
            rdeshmukh_ddn Rahul Deshmukh (Inactive) made changes -
            Comment [ >The MDS should automatically adjust the component {{extent_end}} to match the MDT {{dom_stripesize}}, and > if {{dom_stripesize=0}} then the DoM component should be removed. ]
            adilger Andreas Dilger made changes -
            Link New: This issue is related to LU-10917 [ LU-10917 ]
            adilger Andreas Dilger made changes -
            Description Original: If the DoM component \{{extent_end}} is set larger than the MDT \{{dom_stripesize}} via \{{lfs setstripe -Eextent_end -L mdt}) then this currently generates an error.  Since users do not have any easy way to determine the {{dom_stripesize}} on the MDT, and it may in fact be different on a per-MDT basis (e.g. if MDT0000 sets {{dom_stripesize=0}} because it was formatted before DoM, or it is adjusted automatically by the MDS when the MDT is nearly full).  This complicates DoM usage for users (imagine a striped directory that has different DoM size limits for the MDTs it is striped over).

            The MDS should automatically adjust the component {{extent_end}} to match the MDT {{dom_stripesize}}, and if {{dom_stripesize=0}} then the DoM component should be removed.             		New: If the DoM component {{extent_end}} is set larger than the MDT {{dom_stripesize}} (via {{lfs setstripe \-Eextent\_end \-L mdt}} ) then this currently generates an error.  Since users do not have any easy way to determine the {{dom_stripesize}} on the MDT, and it may in fact be different on a per-MDT basis (e.g. if MDT0000 sets {{dom_stripesize=0}} because it was formatted before DoM, or it is adjusted automatically by the MDS when the MDT is nearly full).  This complicates DoM usage for users (imagine a striped directory that has different DoM size limits for the MDTs it is striped over).

            The MDS should automatically adjust the component {{extent_end}} to match the MDT {{dom_stripesize}}, and if {{dom_stripesize=0}} then the DoM component should be removed.
            tappro Mikhail Pershin made changes -
            Assignee Original: WC Triage [ wc-triage ] New: Mikhail Pershin [ tappro ]

            People

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

              Dates

                Created:
                Updated:
                Resolved: