Jonathan Earl Brassow e5b9338ada Fix bug in cmirror that caused incorrect status info to print on some nodes. ... Looking at the code in cmirrord/local.c, we can see the various different request types handled in different ways. Some information that is non-changing does not need to go around the cluster and can be short-circuited. For example, once the cluster mirror is in-sync, it is pointless to continue sending that query around the cluster. We can save network bandwidth and reply directly back to the kernel. When it comes to status information, there are two types 'TABLE' and 'INFO'. The 'TABLE' information never changes and belongs to the group of requests that can be safely short-circuited. The 'STATUS' information can change - and will change if a device fails. Thus it cannot be short-circuited, but this is exactly what was found. The 'STATUS' information request was being short-circuited and therefore never reporting the failure condition to anyone other than the "server" that experienced it directly.		2012-04-26 17:30:49 +00:00
..
clvmd	Update singlenode locking	2012-04-24 12:16:40 +00:00
cmirrord	Fix bug in cmirror that caused incorrect status info to print on some nodes.	2012-04-26 17:30:49 +00:00
dmeventd	Synchronize with self-destruction of dmeventd	2012-04-24 12:25:12 +00:00
lvmetad	Add fixmes	2012-03-23 10:34:51 +00:00
Makefile.in	Reflect new file locations, include file updates etc.	2012-02-28 18:35:04 +00:00