Actions
Bug #4894
closedmds: standby shut itself down due to not having any data
Status:
Resolved
Priority:
High
Assignee:
-
Category:
-
Target version:
-
% Done:
0%
Source:
Development
Tags:
Backport:
Regression:
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
MDS
Labels (FS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
2013-05-02 02:38:31.094956 7f0496fce700 1 mds.0.2 rejoin_done 2013-05-02 02:38:31.094958 7f0496fce700 10 mds.0.cache show_subtrees - no subtrees 2013-05-02 02:38:31.094963 7f0496fce700 7 mds.0.cache show_cache 2013-05-02 02:38:31.094965 7f0496fce700 7 mds.0.cache unlinked [inode 1 [...2,head] / auth v1 snaprealm=0x2f07000 f(v0 1=0+1) n(v0 1=0+1) (iversion lock) 0x2f14860] 2013-05-02 02:38:31.094971 7f0496fce700 7 mds.0.cache unlinked [inode 100 [...2,head] ~mds0/ auth v1 snaprealm=0x2f076c0 f(v0 11=1+10) n(v0 11=1+10) (iversion lock) 0x2f14000] 2013-05-02 02:38:31.094978 7f0496fce700 1 mds.0.2 empty cache, no subtrees, leaving cluster 2013-05-02 02:38:31.094979 7f0496fce700 3 mds.0.2 request_state down:stopped 2013-05-02 02:38:31.094981 7f0496fce700 10 mds.0.2 beacon_send down:stopped seq 13 (currently up:rejoin)
I'm in the process of pulling logs into /a/teuthology-2013-05-02_01:00:52-fs-next-testing-basic/5452, but they are sadly going to be incomplete — I have the standby, the OSDs (dunno what's on them), and the monitor logs, but the active MDS log is totally empty.
Actions