Hi, > So do you get 'partial' error on thin-pool activation on your physical server ? Yes, the VG of the thin pool only has one simple physical disk, at beginning, I also suspected the disk may disconnect at that moment. But, I start to think maybe it is caused by some reason hidden in the interaction between lvm and dm driver in kernel. It can not be reproduced easily, but happens randomly for several times. The behavior model of lvm abstracted from the upper service is like: there are many (64) control flow in parallel, in each one it loops to randomly create/activate/delete thin LVs. The error happened two place: 1. activate the thin LV: _lv_activate -> _tree_action -> dev_manager_activate -> _add_new_lv_to_dtree -> add_areas_line -> striped_add_target_line on **metadata LV**, I don't what .add_target_line() does for? 2. fail to suspend the origin LV when created. I'm trying to reproduce it in a simple way, will report once succeed :-) Thanks very much! Eric _______________________________________________ linux-lvm mailing list linux-lvm@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
