[LU-2274] Test failure on posix test_1: ext4 is supported in read-only mode only

• Type: Bug
• Resolution: Fixed
• Priority: Blocker
• Fix Version/s: Lustre 2.4.0
• Affects Version/s: Lustre 2.4.0
• Environment: lustre master build #1011 SLES11 SP2 client
• Severity: 3
• Assignee: Jian Yu
• Reporter: Maloo

Description

This issue was created by maloo for sarah <[e-mail]>

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:

Comments

[Jian Yu]

Patch was landed on master branch.

[Jian Yu]

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

[Jian Yu]

Hi Joshua,

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

[Joshua Kugler (Inactive)]

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.

[Andreas Dilger]

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.

[Joshua Kugler (Inactive)]

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?

[Andreas Dilger]

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.