This issue was created by maloo for Bob Glossman <bob.glossman@intel.com>

This issue relates to the following test suite run: http://maloo.whamcloud.com/test_sets/0c9e055a-e0f8-11e3-9a8d-52540035b04c.

Have been seeing this fairly frequently lately on test runs for a lot of different patch, so high confidence it's not due to patches being tested.

Some instances both before and after test 76 was renamed 76a.

The sub-test test_76a failed with the following error:

max_dirty_mb is not saved after remount

Info required for matching: conf-sanity 76a