1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
|
/*
Copyright (c) 2014 Red Hat, Inc. <http://www.redhat.com>
This file is part of GlusterFS.
This file is licensed to you under your choice of the GNU Lesser
General Public License, version 3 or any later version (LGPLv3 or
later), or the GNU General Public License, version 2 (GPLv2), in all
cases as published by the Free Software Foundation.
*/
#ifndef _AFR_MESSAGES_H_
#define _AFR_MESSAGES_H_
#ifndef _CONFIG_H
#define _CONFIG_H
#include "config.h"
#endif
#include "glfs-message-id.h"
/*! \file afr-messages.h
* \brief AFR log-message IDs and their descriptions.
*/
/* NOTE: Rules for message additions
* 1) Each instance of a message is _better_ left with a unique message ID, even
* if the message format is the same. Reasoning is that, if the message
* format needs to change in one instance, the other instances are not
* impacted or the new change does not change the ID of the instance being
* modified.
* 2) Addition of a message,
* - Should increment the GLFS_NUM_MESSAGES
* - Append to the list of messages defined, towards the end
* - Retain macro naming as glfs_msg_X (for redability across developers)
* NOTE: Rules for message format modifications
* 3) Check acorss the code if the message ID macro in question is reused
* anywhere. If reused then then the modifications should ensure correctness
* everywhere, or needs a new message ID as (1) above was not adhered to. If
* not used anywhere, proceed with the required modification.
* NOTE: Rules for message deletion
* 4) Check (3) and if used anywhere else, then cannot be deleted. If not used
* anywhere, then can be deleted, but will leave a hole by design, as
* addition rules specify modification to the end of the list and not filling
* holes.
*/
#define GLFS_COMP_BASE_AFR GLFS_MSGID_COMP_AFR
#define GLFS_NUM_MESSAGES 9
#define GLFS_MSGID_END (GLFS_COMP_BASE_AFR + GLFS_NUM_MESSAGES + 1)
#define glfs_msg_start_x GLFS_COMP_BASE_AFR, "Invalid: Start of messages"
/*!
* @messageid 108001
* @diagnosis Client quorum is not met due to which file modification
* operations are disallowed.
* @recommendedaction Some brick processes are down/ not visible from the
* client. Ensure that the bricks are up/ network traffic is not blocked.
*/
#define AFR_MSG_QUORUM_FAIL (GLFS_COMP_BASE_AFR + 1)
/*!
* @messageid 108002
* @diagnosis The bricks that were down are now up and quorum is restored.
* @recommendedaction Possibly check why the bricks went down to begin with.
*/
#define AFR_MSG_QUORUM_MET (GLFS_COMP_BASE_AFR + 2)
/*!
* @messageid 108003
* @diagnosis Client quorum-type was set to auto due to which the quorum-count
* option is no longer valid.
* @recommendedaction None.
*/
#define AFR_MSG_QUORUM_OVERRIDE (GLFS_COMP_BASE_AFR + 3)
/*!
* @messageid 108004
* @diagnosis Replication sub volume witnessed a connection notification
* from a brick which does not belong to it's replica set.
* @recommendedaction None. This is a safety check in code.
*/
#define AFR_MSG_INVALID_CHILD_UP (GLFS_COMP_BASE_AFR + 4)
/*!
* @messageid 108005
* @diagnosis A brick that was down earlier has come back up.
* @recommendedaction Possibly check why the brick went down to begin with.
*/
#define AFR_MSG_SUBVOL_UP (GLFS_COMP_BASE_AFR + 5)
/*!
* @messageid 108006
* @diagnosis All bricks of a replica set are down. Data residing in that
* replica cannot be accessed until one of the bricks come back up.
* @recommendedaction Ensure that the bricks are up.
*/
#define AFR_MSG_ALL_SUBVOLS_DOWN (GLFS_COMP_BASE_AFR + 6)
/*!
* @messageid 108007
* @diagnosis Entry unlocks failed on a brick.
* @recommendedaction Error number in the log should give the reason why it
* failed. Also observe brick logs for more information.
*/
#define AFR_MSG_ENTRY_UNLOCK_FAIL (GLFS_COMP_BASE_AFR + 7)
/*!
* @messageid 108008
* @diagnosis There is an inconsistency in the file's data/metadata/gfid
* amongst the bricks of a replica set.
* @recommendedaction Resolve the split brain by clearing the AFR changelog
* attributes from the appropriate brick and trigger self-heal.
*/
#define AFR_MSG_SPLIT_BRAIN (GLFS_COMP_BASE_AFR + 8)
/*!
* @messageid 108009
* @diagnosis open/opendir failed on a brick.
* @recommendedaction Error number in the log should give the reason why it
* failed. Also observe brick logs for more information.
*/
#define AFR_MSG_OPEN_FAIL (GLFS_COMP_BASE_AFR + 9)
#define glfs_msg_end_x GLFS_MSGID_END, "Invalid: End of messages"
#endif /* !_AFR_MESSAGES_H_ */
|
