OCFS2 Mainline Regression Test

Introduction

Regression test for Mainline is expected to be carried out when 'merge_window' of each stable mainline version gets activated, in other words, it should be right after rc1 mainline kernel get released. For ocfs2, we're going to mainly test the fixups and new features from Joel's 'merge_window' branch as a whole, the testing itself should be sophisticated and comprehensive enough to cover all features to expose potential issues. One of our main goals is to guarantee the sanity of FS for sure after each rc1 mainline kernel get released, especially, needs to catch regression bugs after bigfix and new features get pushed when testing FS comprehensively(codes/fixes from sub-features may conflict with each other), on the other hand, it's also a good place to watch how OCFS2 would be affected given that VFS gets significant changes.

The testing itself also should be automatic enough to perform the same task in a given time, it needs to yield delicate logfiles with few interventions from human hands.

Test Automation

Currently, it's not a bad choice of taking singe_run.sh as candidate for automatic testing launcher, as in, its framework allows a easy addup for new testcase, also we're happy with the logfiles it shows.

Testcases Involved

Following list almost covers all of the existing testcases from ocfs2-test.git:

1.Single-node

    -----fs-----
    create_and_open
    directaio
    fill_verify_holes
    renamewriterace
    aiostress
    filesizelimits
    mmaptruncate
    buildkernel
    splice
    sendfile
    mmap
    reserve_space
    inline_data
    xattr_test
    reflink_test
    ---tools---
    mkfs-test
    tunefs-test
    backup_super_test
 

2.Multi-nodes

    
To-be-added...

 

Single-node Testing Status

Multi-nodes Testing Status

FFSB Benchmark/Perf Testing