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

mounting lustre oops on older kernels

Details

    • Bug
    • Resolution: Duplicate
    • Minor
    • None
    • Lustre 2.1.2
    • None
    • sles10sp4
    • 3
    • 6362

    Description

      in lustre 2.1 and up, the lustre_fill_super() was changed to expect the anonymous pointer to be of the type struct lustre_mount_data2. however, the ifdef for lustre_get_sb() for kernels < 2.6.18 was not updated. the attached patch seems to fix things but you might run into trouble when nfs exporting from these old kernels since lmd_mnt cannot be filled in for these older kernels.

      Attachments

        Issue Links

          Activity

            [LU-1646] mounting lustre oops on older kernels

            Also besides patch http://review.whamcloud.com/#change,3661 from LU-812 you will need LU-1718 for NFS export which has the patch at http://review.whamcloud.com/#change,3840.

            simmonsja James A Simmons added a comment - Also besides patch http://review.whamcloud.com/#change,3661 from LU-812 you will need LU-1718 for NFS export which has the patch at http://review.whamcloud.com/#change,3840 .
            bogl Bob Glossman (Inactive) added a comment - back port to b2_1 http://review.whamcloud.com/#change,3661

            since you cant even mount lustre on really old kernels, i dont think anyone is using the nfs export feature. so this seems fine to me.

            chas3 chas williams - CONTRACTOR added a comment - since you cant even mount lustre on really old kernels, i dont think anyone is using the nfs export feature. so this seems fine to me.

            chas,
            Is it OK if we disable NFS export in 2.1.x for really old kernels? Can you possibly work around that restriction by using 1.8.x with such old kernels, at least until we have a fix from LU-1718 available?

            bogl Bob Glossman (Inactive) added a comment - chas, Is it OK if we disable NFS export in 2.1.x for really old kernels? Can you possibly work around that restriction by using 1.8.x with such old kernels, at least until we have a fix from LU-1718 available?

            if we proceed with a back port we will also need LU-1718 back ported to reenable NFS export

            bogl Bob Glossman (Inactive) added a comment - if we proceed with a back port we will also need LU-1718 back ported to reenable NFS export

            The change in http://review.whamcloud.com/#change,1951 can be back ported, but with side effects. LU-1718 mentioned by James in the previous comment tracks the disable of reexport of lustre fs to NFS due to this change. Doing the back port would disable reexport to NFS for old kernels just as it is for 3.0+ kernels. This would remain true until a fix for LU-1718 is completed and back ported.

            bogl Bob Glossman (Inactive) added a comment - The change in http://review.whamcloud.com/#change,1951 can be back ported, but with side effects. LU-1718 mentioned by James in the previous comment tracks the disable of reexport of lustre fs to NFS due to this change. Doing the back port would disable reexport to NFS for old kernels just as it is for 3.0+ kernels. This would remain true until a fix for LU-1718 is completed and back ported.

            More than that patch would need to be back ported. See LU-1718 as well.

            simmonsja James A Simmons added a comment - More than that patch would need to be back ported. See LU-1718 as well.
            pjones Peter Jones added a comment -

            Bob

            Could you please look into this change and see whether it would be practical to backport it to b2_1?

            Thanks

            Peter

            pjones Peter Jones added a comment - Bob Could you please look into this change and see whether it would be practical to backport it to b2_1? Thanks Peter

            this was fixed via LU-812 in commit 2eba197319886c4f2903fd937aebe69eea35290e. do i need to do anything for this to get backported to the 2.1 and 2.2 releases?

            chas3 chas williams - CONTRACTOR added a comment - this was fixed via LU-812 in commit 2eba197319886c4f2903fd937aebe69eea35290e. do i need to do anything for this to get backported to the 2.1 and 2.2 releases?
            pjones Peter Jones added a comment -

            Hi Chas

            SLES10 is not officially supported for 2.1.x (see http://wiki.whamcloud.com/display/PUB/Lustre+Support+Matrix). There is some interest in adding this support. If you would like to get your patch landed into the Lustre tree could you please upload it into gerrit so that it can be tested and reviewed? Details on how to do this are on the Whamcloud wiki

            Thanks

            Peter

            pjones Peter Jones added a comment - Hi Chas SLES10 is not officially supported for 2.1.x (see http://wiki.whamcloud.com/display/PUB/Lustre+Support+Matrix ). There is some interest in adding this support. If you would like to get your patch landed into the Lustre tree could you please upload it into gerrit so that it can be tested and reviewed? Details on how to do this are on the Whamcloud wiki Thanks Peter

            2.1 for the foreseeable future.

            chas chas@cmf.nrl.navy.mil added a comment - 2.1 for the foreseeable future.

            People

              bogl Bob Glossman (Inactive)
              chas chas@cmf.nrl.navy.mil
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: