Lines Matching full:node
12 Separate write-intent-bitmaps are used for each cluster node.
13 The bitmaps record all writes that may have been started on that node,
24 one node writes to any given block at a time, so a write request will
31 one node doesn't read from a location where another node (or the same
32 node) is writing.
43 The bm_lockres protects individual node bitmaps. They are named in
44 the form bitmap000 for node 1, bitmap001 for node 2 and so on. When a
45 node joins the cluster, it acquires the lock in PW mode and it stays
46 so during the lifetime the node is part of the cluster. The lock
48 subsystem. Since DLM starts node count from one and bitmap slots
52 The LVB of the bitmap lock for a particular node records the range
53 of sectors that are being re-synced by that node. No other
54 node may write to those sectors. This is used when a new nodes
60 Each node has to communicate with other nodes when starting or ending
88 been updated, and the node must re-read the md superblock. This is
95 ended so that each node may suspend or resume the region. Each
97 sending node is about to resync. This overrides any previous
98 notification from that node: only one ranged can be resynced at a
99 time per-node.
121 If a node is stopped locally but the bitmap
122 isn't clean, then another node is informed to take the ownership of
134 system. The node having the token resource is allowed to
146 is used to inform the receiving node that a node wants to
213 4.1 Node Failure
216 When a node fails, the DLM informs the cluster with the slot
217 number. The node starts a cluster recovery thread. The cluster
220 - acquires the bitmap<number> lock of the failed node
222 - reads the bitmap of the failed node
223 - copies the set bitmap to local node
224 - cleans the bitmap of the failed node
225 - releases bitmap<number> lock of the failed node
226 - initiates resync of the bitmap on the current node
230 Which means when one node is resyncing it blocks all
235 of the areas which are suspended. Before a resync starts, the node
237 be suspended. Each node maintains a suspend_list, which contains the
239 the node adds the range to the suspend_list. Similarly, when the node
251 routine. When a node detects a device failure it does not allow
261 1. Node 1 issues mdadm --manage /dev/mdX --add /dev/sdYY which issues
263 2. Node 1 sends a NEWDISK message with uuid and slot number
266 4. In userspace, the node searches for the disk, perhaps
274 7. Node 1 attempts EX lock on "no-new-dev"
275 8. If node 1 gets the lock, it sends METADATA_UPDATED after
320 allows some other node to take over.
336 Firstly, it will check if any node is currently resyncing
341 Secondly, while node recovery is happening it reports that
344 a node failure.
374 These are called when change bitmap to none. If a node plans