Clustered MD RAID1
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest24 patches 14 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/24 | md-cluster: Design DocumentationDocumentation/ | +178 | 3 replies | |
| 2/24 | Add number of nodes to bitmap structure for clusteringdrivers/ | +3 | 2 replies | |
| 3/24 | Create a separate module for clustering supportdrivers/ drivers/ drivers/ | +47 | 0 replies | |
| 4/24 | DLM lock and unlock functionsdrivers/ | +104 | 0 replies | |
| 5/24 | Introduce md_cluster_operations to handle cluster functionsdrivers/ drivers/ drivers/ +1 more | +91 | 0 replies | |
| 6/24 | Introduce md_cluster_infodrivers/ drivers/ drivers/ | +74 | 0 replies | |
| 7/24 | Return MD_SB_CLUSTERED if mddev is clustereddrivers/ include/ | +4 | 0 replies | |
| 8/24 | Add node recovery callbacksdrivers/ drivers/ drivers/ +3 more | +64 | 0 replies | |
| 9/24 | Use separate bitmaps for each nodes in the clusterdrivers/ drivers/ drivers/ +1 more | +64 | 0 replies | |
| 10/24 | Lock bitmap while joining the clusterdrivers/ | +16 | 0 replies | |
| 11/24 | Gather on-going resync information of other nodesdrivers/ drivers/ drivers/ | +119 | 0 replies | |
| 12/24 | bitmap_create returns bitmap pointerdrivers/ drivers/ drivers/ | +50 | 0 replies | |
| 13/24 | Copy set bits from another slotdrivers/ drivers/ | +78 | 0 replies | |
| 14/24 | Initiate recovery on node failuredrivers/ | +59 | 0 replies | |
| 15/24 | Perform resync for cluster node failuredrivers/ | +11 | 0 replies | |
| 16/24 | Communication Framework: Receivingdrivers/ | +101 | 0 replies | |
| 17/24 | Communication Framework: Sending functionsdrivers/ | +84 | 0 replies | |
| 18/24 | metadata_update sends message to other nodesdrivers/ drivers/ drivers/ | +106 | 0 replies | |
| 19/24 | Reload superblock if METADATA_UPDATED is receiveddrivers/ drivers/ drivers/ | +23 | 0 replies | |
| 20/24 | Send RESYNCING while performing resync start/stopdrivers/ drivers/ drivers/ | +35 | 0 replies | |
| 21/24 | Resync start/Finish actionsdrivers/ | +46 | 0 replies | |
| 22/24 | Suspend writes in RAID1 if within rangedrivers/ drivers/ drivers/ +1 more | +31 | 0 replies | |
| 23/24 | Read from the first device when an area is resyncingdrivers/ | +7 | 0 replies | |
| 24/24 | Add new disk to clustered arraydrivers/ drivers/ drivers/ +4 more | +171 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 00/24] Clustered MD RAID1
Hello,
This is an attempt to make MD-RAID cluster-aware. The advantage of redundancy can help highly available systems to improve uptime. Currently, the implementation is limited to RAID1 but with further work (and some positive feedback), we could extend this to other compatible RAID scenarios.
The design document (first patch) is pretty descriptive of how the md has been made cluster-aware and how DLM is used to safeguard data and communication.
This work requires some patches to the mdadm tool [1]
A quick howto:
1. With your corosync/pacemaker based cluster running execute:
# mdadm --create md0 --bitmap=clustered --raid-devices=2 --level=mirror --assume-clean /dev/sda /dev/sdb
2. On other nodes, issue:
# mdadm --assemble md0 /dev/sda /dev/sdb
References:
[1] mdadm tool changes: https://github.com/goldwynr/mdadm branch:cluster-md
[2] Patches against stable 3.14: https://github.com/goldwynr/linux branch: cluster-md-devel
Regards,
Signature · 1 line
Goldwyn