Zdenek Kabelac 79ea81b8a8 thin: restore transaction_id handling ...

Revert back to already existing behavior which has been slightly
modified by a900d150e4658a5d72c39acdd4fefd069b8f00b8.

At the end however it seem to be equal to change TID right with first
metadata write.

Existing code missed handling for 'unused' thin-pool which would
require to also check empty message list for TID==0.

So with the fix we now again preserve 'active' thin-pool volume
when first thin volume is created - this property was lost and caused
problems in cluster, where the lock was hold, but volume was no longer
active on the node.

Another missing part was the proper support for already increased,
but unfinished TID change.

So going back here with existing logic -

TID is increased with first MDA update.

Code allows start with either same TID or (TID-1).

If there are messages, TID must be lower by 1 for sending,
otherwise messages were already posted.

2015-08-17 11:25:03 +02:00

..

.exported_symbols

Initial code layout for thin provisioning target

2011-08-24 08:27:49 +00:00

Makefile.in

Initial code layout for thin provisioning target

2011-08-24 08:27:49 +00:00

thin.c

thin: restore transaction_id handling

2015-08-17 11:25:03 +02:00