Lines Matching refs:node

6 Separate write-intent-bitmap are used for each cluster node.
7 The bitmaps record all writes that may have been started on that node,
18 node writes to any given block at a time, so a write
25 ensure one node doesn't read from a location where another node (or the same
26 node) is writing.
35  The bm_lockres protects individual node bitmaps. They are named in the
36  form bitmap001 for node 1, bitmap002 for node and so on. When a node
38  during the lifetime the node is part of the cluster. The lock resource
40  DLM starts node count from one and bitmap slots start from zero, one is
45 Each node has to communicate with other nodes when starting or ending
53    updated, and the node must re-read the md superblock. This is performed
57    so that each node may suspend or resume the region.
65    system. The node having the token resource is allowed to
73    is used to inform the receive node that a node wants to communicate.
126  When a node fails, the DLM informs the cluster with the slot. The node
128 	- acquires the bitmap<number> lock of the failed node
130 	- reads the bitmap of the failed node
131 	- copies the set bitmap to local node
132 	- cleans the bitmap of the failed node
133 	- releases bitmap<number> lock of the failed node
134 	- initiates resync of the bitmap on the current node
138  of the areas which are suspended. Before a resync starts, the node
140  to be suspended. Each node maintains a suspend_list, which contains
142  RESYNC_START, the node adds the range to the suspend_list. Similarly,
143  when the node performing resync finishes, it send RESYNC_FINISHED
163     4. In userspace, the node searches for the disk, perhaps
172     8. If node 1 gets the lock, it sends METADATA_UPDATED after unmarking the disk