Hello list,

Recently, we're exercising our container environment which uses lvm to manage thin LVs, meanwhile we found a very strange error to activate the thin LV:

“Aborting.  LV mythinpool_tmeta is now incomplete and '--activationmode partial' was not specified.\n: exit status 5: unknown"

centos 7.6
# lvm version
  LVM version:     2.02.180(2)-RHEL7 (2018-07-20)
  Library version: 1.02.149-RHEL7 (2018-07-20)
  Driver version:  4.35.0

It has appeared several times, but can not be reproduced easily by simple steps, and it only errors at that moment, after it happens everything seems OK but only that activation failed.

Looking at the code a bit. At first, I suspect the PV may disappear for some reason, but the VG sits on only one PV, the setup is simple, the environment is only for testing purposes, it seems unlikely the PV has problem at that moment and I don't see any problem message with the disk.

```
2513         /* FIXME Avoid repeating identical stat in dm_tree_node_add_target_area */
2514 for (s = start_area; s < areas; s++) {
2515 if ((seg_type(seg, s) == AREA_PV &&
2516 (!seg_pvseg(seg, s) || !seg_pv(seg, s) || !seg_dev(seg, s) ||
2517 !(name = dev_name(seg_dev(seg, s))) || !*name ||
2518 stat(name, &info) < 0 || !S_ISBLK(info.st_mode))) ||
2519 (seg_type(seg, s) == AREA_LV && !seg_lv(seg, s))) {
2520 if (!seg->lv->vg->cmd->partial_activation) {
2521 if (!seg->lv->vg->cmd->degraded_activation ||
2522 !lv_is_raid_type(seg->lv)) {
2523 log_error("Aborting. LV %s is now incomplete "
2524 "and '--activationmode partial' was not specified.",
2525 display_lvname(seg->lv));
2526 return 0;
```
So, does anyone see the same problem? Or any hints to hunt the root cause? Any suggestion would be welcome!

Regards,
Eric