Details

    • Improvement
    • Resolution: Fixed
    • Minor
    • Lustre 2.6.0
    • Lustre 2.4.0, Lustre 2.5.0
    • 3
    • 3
    • 2626

    Description

      With the fixes to MGS, MDS, and OFD, there should no longer be a need to keep the fsfilt and lvfs infrastructure. Any use of that code should be considered a bug, since it means Lustre is not using the OSD API properly. Any remaining use of fsfilt_ldiskfs can be moved directly into the osd-ldiskfs module.

      Attachments

        Issue Links

          Activity

            [LU-2158] remove lvfs and fsfilt code
            pjones Peter Jones added a comment -

            Landed for 2.6

            pjones Peter Jones added a comment - Landed for 2.6

            The last patch has landed. This ticket can be closed.

            simmonsja James A Simmons added a comment - The last patch has landed. This ticket can be closed.

            Thank you. Will test.

            simmonsja James A Simmons added a comment - Thank you. Will test.

            James, I've just updated patch to resolve new conflicts.

            tappro Mikhail Pershin added a comment - James, I've just updated patch to resolve new conflicts.
            simmonsja James A Simmons added a comment - Only patch http://review.whamcloud.com/#/c/5512 is left
            simmonsja James A Simmons added a comment - Patches needed to complete this ticket are: http://review.whamcloud.com/#/c/5331 http://review.whamcloud.com/#/c/5512

            With only three months to import the OSD api it is amazing how much did make it in. I have learned if you want a major feature you have to plan on merging over several releases. From what I'm seeing a lot of new work is ready to go as soon as the flood gates for 2.5 are open which is a good thing.

            simmonsja James A Simmons added a comment - With only three months to import the OSD api it is amazing how much did make it in. I have learned if you want a major feature you have to plan on merging over several releases. From what I'm seeing a lot of new work is ready to go as soon as the flood gates for 2.5 are open which is a good thing.

            Would such a patch be accepted for 2.4.1 is the bigger question?

            While I am quite disappointed that 2.4.0 is going to be released with this unfinished, I would personally argue that the maintenance branch is not the place for this kind of code movement. So I would propose that be added to the 2.5 plan (i.e., change "Fix Version/s" to Lustre 2.5.0).

            morrone Christopher Morrone (Inactive) added a comment - Would such a patch be accepted for 2.4.1 is the bigger question? While I am quite disappointed that 2.4.0 is going to be released with this unfinished, I would personally argue that the maintenance branch is not the place for this kind of code movement. So I would propose that be added to the 2.5 plan (i.e., change "Fix Version/s" to Lustre 2.5.0).

            oh, this is MGC.. sorry for confusion

            bzzz Alex Zhuravlev added a comment - oh, this is MGC.. sorry for confusion

            The MGS backup logs still need the lvfs layer (LU-2059). Also the push_ctx and pop_ctx code in the lvfs layer is used by ptlrpc_sec.c. So the lvfs layer is still needed. As for the fsfilt layer that could be integrated into the osd-ldiskfs layer as I did in http://review.whamcloud.com/#change,5512. Have to make sure its safe for 2.4. Would such a patch be accepted for 2.4.1 is the bigger question?

            simmonsja James A Simmons added a comment - The MGS backup logs still need the lvfs layer ( LU-2059 ). Also the push_ctx and pop_ctx code in the lvfs layer is used by ptlrpc_sec.c. So the lvfs layer is still needed. As for the fsfilt layer that could be integrated into the osd-ldiskfs layer as I did in http://review.whamcloud.com/#change,5512 . Have to make sure its safe for 2.4. Would such a patch be accepted for 2.4.1 is the bigger question?

            People

              keith Keith Mannthey (Inactive)
              adilger Andreas Dilger
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: