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

utils: lfs setstripe to specify OSTs

Details

    • New Feature
    • Resolution: Fixed
    • Critical
    • Lustre 2.7.0
    • None
    • 3
    • 12785

    Description

      #5: Sparse OST indicies
      #6: Setstripe for specified OSTs.

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. LU-5170 lfs usability

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

          Bug - A problem which impairs or prevents the functions of the product. LU-5878 lfs migrate sends file to stdout

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

          Improvement - An improvement or enhancement to an existing feature or task. LU-9392 lfs migrate -o and lfs setstripe -o should pick OST from ost_list

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

          Improvement - An improvement or enhancement to an existing feature or task. LU-8417 setstripe -o does not work on directories

          • Major - Major loss of function.
          • Resolved
          is related to

          Bug - A problem which impairs or prevents the functions of the product. LU-3840 llapi_layout API design discussion

          • Major - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. LU-6135 improved support for selecting specific OSTs for files

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

          Activity

            [LU-4665] utils: lfs setstripe to specify OSTs
            adilger Andreas Dilger added a comment -

            Have moved the other patches over to LU-6135.

            adilger Andreas Dilger added a comment - Have moved the other patches over to LU-6135 .
            adilger Andreas Dilger added a comment -

            I opened LU-6135 for the follow-on patches.

            adilger Andreas Dilger added a comment - I opened LU-6135 for the follow-on patches.
            jay Jinshan Xiong (Inactive) added a comment -

            Do we need a new ticket # for http://review.whamcloud.com/#/c/12275?

            jay Jinshan Xiong (Inactive) added a comment - Do we need a new ticket # for http://review.whamcloud.com/#/c/12275?
            emoly.liu Emoly Liu added a comment -

            Andreas, sure.

            emoly.liu Emoly Liu added a comment - Andreas, sure.
            adilger Andreas Dilger added a comment -

            Emoly, could you please refresh the 12663 patch according to the review comments, and add a test case for this to the llapi_layout_ test program.

            adilger Andreas Dilger added a comment - Emoly, could you please refresh the 12663 patch according to the review comments, and add a test case for this to the llapi_layout_ test program.
            adilger Andreas Dilger added a comment -

            I've pushed http://review.whamcloud.com/12663 but it is a best-effort patch for now. It doesn't have a test case yet, and has had no testing at all.

            adilger Andreas Dilger added a comment - I've pushed http://review.whamcloud.com/12663 but it is a best-effort patch for now. It doesn't have a test case yet, and has had no testing at all.
            simmonsja James A Simmons added a comment -

            No. The llapi_layout api is not mature enough to be used. I tried using it as a back end but it just broke lots of test.

            simmonsja James A Simmons added a comment - No. The llapi_layout api is not mature enough to be used. I tried using it as a back end but it just broke lots of test.
            adilger Andreas Dilger added a comment -

            Is it possible to access this functionality via the new llapi_layout_* API added in LU-3840? It doesn't seem like it looking at the code. I've got a partially completed patch to add this, will link it here when I push the patch.

            adilger Andreas Dilger added a comment - Is it possible to access this functionality via the new llapi_layout_* API added in LU-3840 ? It doesn't seem like it looking at the code. I've got a partially completed patch to add this, will link it here when I push the patch.
            green Oleg Drokin added a comment -

            Ah, I also noticed that the current patch returns error if ldo_def_stripe_offset is not in the list of OSTs, but failed to consider that -1 should mean "use something that makes sense". This too needs to be addressed. Esp. in light of the previous comment

            green Oleg Drokin added a comment - Ah, I also noticed that the current patch returns error if ldo_def_stripe_offset is not in the list of OSTs, but failed to consider that -1 should mean "use something that makes sense". This too needs to be addressed. Esp. in light of the previous comment
            green Oleg Drokin added a comment -

            This feature totally needs a way to specify ost_count in addition to OST list that way we do not force user to do their own load balancing.
            Say I have a set of 100 OSTs that are local enough for my set of nodes, but I only need a striping of 4...
            We seriously should consider adding this as a follow on patch.

            green Oleg Drokin added a comment - This feature totally needs a way to specify ost_count in addition to OST list that way we do not force user to do their own load balancing. Say I have a set of 100 OSTs that are local enough for my set of nodes, but I only need a striping of 4... We seriously should consider adding this as a follow on patch.

            People

              emoly.liu Emoly Liu
              jay Jinshan Xiong (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              21 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: