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

Test failure on posix test_1: ext4 is supported in read-only mode only

Details

    • Bug
    • Resolution: Fixed
    • Blocker
    • Lustre 2.4.0
    • Lustre 2.4.0
    • None
    • lustre master build #1011 SLES11 SP2 client
    • 3
    • 5434

    Description

      This issue was created by maloo for sarah <sarah@whamcloud.com>

      This issue relates to the following test suite run: https://maloo.whamcloud.com/test_sets/b1f3e694-2549-11e2-9e7c-52540035b04c.

      The sub-test test_1 failed with the following error:

      Copy POSIX test suite failed

      Hit this error on SLES11 SP2 client

      mount: warning: /usr/src/posix/ext4 seems to be mounted read-only.
      
      cp: cannot create regular file `/usr/src/posix/ext4/build-posix.exp': Read-only file system
      cp: cannot create regular file `/usr/src/posix/ext4/install-posix.exp': Read-only file system
      cp: cannot create regular file `/usr/src/posix/ext4/install.sh': Read-only file system
      cp: cannot create regular file `/usr/src/posix/ext4/lts_vsx-pcts2.0beta2.tgz': Read-only file system
      cp: cannot create regular file `/usr/src/posix/ext4/myscen.bld': Read-only file system
      cp: cannot create regular file `/usr/src/posix/ext4/myscen.exec': Read-only file system
      cp: cannot create regular file `/usr/src/posix/ext4/one-step-setup.sh': Read-only file system
      cp: cannot create regular file `/usr/src/posix/ext4/run_posix_suite.pl': Read-only file system
      cp: cannot create regular file `/usr/src/posix/ext4/tet_vsxgen_3.02.tgz': Read-only file system
       posix test_1: @@@@@@ FAIL: Copy POSIX test suite failed 
        Trace dump:
      

      Attachments

        Activity

          [LU-2274] Test failure on posix test_1: ext4 is supported in read-only mode only
          yujian Jian Yu added a comment -

          Patch was landed on master branch.

          yujian Jian Yu added a comment - Patch was landed on master branch.
          yujian Jian Yu added a comment - - edited

          Patch for master branch is in http://review.whamcloud.com/4524.

          I also created TT-952 to improve loadjenkinsbuild to install the packages required by POSIX test suite.

          With the above patch, POSIX test suite passed on SLES 11 SP2 clients against master branch, the baseline was ext3:
          https://maloo.whamcloud.com/test_sessions/7d69f330-2d93-11e2-89bf-52540035b04c

          It also passed on RHEL6 clients, the baseline was ext4:
          https://maloo.whamcloud.com/test_sessions/5d85df66-2e6f-11e2-8849-52540035b04c

          yujian Jian Yu added a comment - - edited Patch for master branch is in http://review.whamcloud.com/4524 . I also created TT-952 to improve loadjenkinsbuild to install the packages required by POSIX test suite. With the above patch, POSIX test suite passed on SLES 11 SP2 clients against master branch, the baseline was ext3: https://maloo.whamcloud.com/test_sessions/7d69f330-2d93-11e2-89bf-52540035b04c It also passed on RHEL6 clients, the baseline was ext4: https://maloo.whamcloud.com/test_sessions/5d85df66-2e6f-11e2-8849-52540035b04c
          yujian Jian Yu added a comment -

          Hi Joshua,

          Let me change the test script to use ext3 for POSIX testing on SLES11 kernels. Thanks.

          yujian Jian Yu added a comment - Hi Joshua, Let me change the test script to use ext3 for POSIX testing on SLES11 kernels. Thanks.

          How shall I (or someone else?) go about making this change? And is this the best option? I'll do whatever needs to be done, I just want to make sure there is a "signed off by" before I do.

          joshua Joshua Kugler (Inactive) added a comment - How shall I (or someone else?) go about making this change? And is this the best option? I'll do whatever needs to be done, I just want to make sure there is a "signed off by" before I do.

          We can't close this bug without actually getting the testing to run.

          One option is to patch the SLES kernel to remove this read-only restriction for ext4, though this would mean testing POSIX only on server kernels. Another, probably better, option is to change the test script to use ext3 for POSIX testing on SLES11 kernels.

          adilger Andreas Dilger added a comment - We can't close this bug without actually getting the testing to run. One option is to patch the SLES kernel to remove this read-only restriction for ext4, though this would mean testing POSIX only on server kernels. Another, probably better, option is to change the test script to use ext3 for POSIX testing on SLES11 kernels.

          OK, given adilger's comment, should I close this as "won't fix" or "not a bug," or do we want to load up the ext4 kernel module for this?

          joshua Joshua Kugler (Inactive) added a comment - OK, given adilger 's comment, should I close this as "won't fix" or "not a bug," or do we want to load up the ext4 kernel module for this?

          I can't comment for sure why SuSE does not support ext4, since it is the default for RHEL6 on the same kernel and keeping this in sync shouldn't be rocket science. Even then, I'd consider btrfs much less stable than ext4, so it makes even less sense to me what they are doing.

          It wouldn't be unreasonable to just run the SLES 11 SP2 baseline POSIX tests using ext3 instead of ext4, which is probably a lot easier going forward compared to installing this extra kernel module for each update.

          adilger Andreas Dilger added a comment - I can't comment for sure why SuSE does not support ext4, since it is the default for RHEL6 on the same kernel and keeping this in sync shouldn't be rocket science. Even then, I'd consider btrfs much less stable than ext4, so it makes even less sense to me what they are doing. It wouldn't be unreasonable to just run the SLES 11 SP2 baseline POSIX tests using ext3 instead of ext4, which is probably a lot easier going forward compared to installing this extra kernel module for each update.

          Yeah, we'll probably have to add the package to the chef recipe, or to kickstart file. This makes no sense, though. They support ext3, but not ext4? WHY?

          I will work on this Wednesday. I'll have to find a spare machine in our staging environment to test.

          joshua Joshua Kugler (Inactive) added a comment - Yeah, we'll probably have to add the package to the chef recipe, or to kickstart file. This makes no sense, though. They support ext3, but not ext4? WHY? I will work on this Wednesday. I'll have to find a spare machine in our staging environment to test.
          yujian Jian Yu added a comment -

          Hi Joshua,
          Could you please help find the ext4-writeable KMP (kernel module package) for SLES11 SP2 and make loadjenkinsbuild install it while provisioning a SLES11 SP2 Lustre client?

          After it works, please re-assign this ticket to me to verify whether posix test can be run on SLES11 SP2 client or not. Thanks.

          yujian Jian Yu added a comment - Hi Joshua, Could you please help find the ext4-writeable KMP (kernel module package) for SLES11 SP2 and make loadjenkinsbuild install it while provisioning a SLES11 SP2 Lustre client? After it works, please re-assign this ticket to me to verify whether posix test can be run on SLES11 SP2 client or not. Thanks.
          yujian Jian Yu added a comment -

          I can't even find in the stock kernel where this message is generated. Could you please post the chunk of code that is generating the ext4 is supported in read-only mode only message.

          I found these threads:
          https://forums.suse.com/archive/index.php/t-749.html
          http://www.novell.com/linux/releasenotes/x86_64/SUSE-SLES/11-SP2/#fate-311111

          To facilitate the migration of an ext4 file system to another, supported file system, the SLE 11 SP2 kernel now contains a fully supported ext4 file system module, which provides solely read-only access to the file system.
          
          If read-write access to an ext4 file system is still required, you may install the ext4-writeable KMP (kernel module package). This package is available in the online repository "SLES11-Extras" and contains a kernel module that provides read-write access to an ext4 file system. Be aware, that this kernel module is unsupported.
          
          ext4 is not supported for the installation of the SUSE Linux Enterprise operating system files
          
          With SUSE Linux Enterprise 11 SP2 we support offline migration from ext4 to the supported btrfs filesystem.
          
          yujian Jian Yu added a comment - I can't even find in the stock kernel where this message is generated. Could you please post the chunk of code that is generating the ext4 is supported in read-only mode only message. I found these threads: https://forums.suse.com/archive/index.php/t-749.html http://www.novell.com/linux/releasenotes/x86_64/SUSE-SLES/11-SP2/#fate-311111 To facilitate the migration of an ext4 file system to another, supported file system, the SLE 11 SP2 kernel now contains a fully supported ext4 file system module, which provides solely read-only access to the file system. If read-write access to an ext4 file system is still required, you may install the ext4-writeable KMP (kernel module package). This package is available in the online repository "SLES11-Extras" and contains a kernel module that provides read-write access to an ext4 file system. Be aware, that this kernel module is unsupported. ext4 is not supported for the installation of the SUSE Linux Enterprise operating system files With SUSE Linux Enterprise 11 SP2 we support offline migration from ext4 to the supported btrfs filesystem.

          People

            yujian Jian Yu
            maloo Maloo
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: