Actions
Bug #12172
closedtasks.cephfs.test_auto_repair.TestMDSAutoRepair fails
Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:
0%
Source:
other
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
Labels (FS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Updated by Zheng Yan almost 9 years ago
Updated by Zheng Yan almost 9 years ago
- Status changed from 12 to Fix Under Review
Updated by John Spray almost 9 years ago
- Status changed from Fix Under Review to Resolved
commit 510b238e2c9cbf02bfccf269a5786315e0606603 Merge: 1a847dc 835ad8b Author: John Spray <jcspray@gmail.com> Date: Mon Jun 29 11:30:23 2015 +0100 Merge pull request #473 from ceph/wip-12172 Wip 12172 Reviewed-by: John Spray <john.spray@redhat.com> commit 835ad8b8f3038290846c612b66f3bffcc5755338 Author: Yan, Zheng <zyan@redhat.com> Date: Mon Jun 29 17:37:23 2015 +0800 cephfs/test_auto_repair.py: flush journal after umount When client capabilities get released, MDS may update corresponding inodes' client writable range and mark those inodes dirty. The auto repair test expects MDS to trim inodes from its cache, but MDS can't trim dirty inodes. So we should flush journal after umount. Fixes: #12172 Signed-off-by: Yan, Zheng <zyan@redhat.com>
Actions