We want to allow write clusters to be written in parallel to
multiple devices. That means we need a different Verify mechanism.
Introduce - but don't yet implement - VerifyDevNext{,2} which allows
a cluster to be verified by the next header on the same device.
Signed-off-by: NeilBrown <neilb@suse.de>
#define VerifyNext 1 /* if next head is valid, this cluster is */
#define VerifyNext2 2 /* if next 2 heads are valid, this cluster is */
#define VerifySum 3 /* maybe some sort of MIC is in _data */
+#define VerifyDevNext 4 /* If next head on this device is valud, this
+ * cluster is.
+ */
+#define VerifyDevNext2 5 /* if next 2 heads on this device are valid,
+ * this cluster is.
+ */
struct la_inode {
/* 16 bytes is constant */
/*
* roll_locate scopes out the full extent of the required roll-forward.
- * It start at the start of the last checkpoint (recorded in the stateblock)
+ * It starts at the start of the last checkpoint (recorded in the stateblock)
* and checks that the end of the checkpoint exists, and continues following
* the chain as far as valid cluster heads can be found.
* roll_locate returns 0 if proper endpoints were found,