Dne 12. 04. 19 v 17:03 Eric Ren napsal(a):
Hi,
Although the /dev/dm-26 is visible, but the device seems not ready in kernel.
Sorry, it's not:
[root@iZuf6dbyd7ede51sykedamZ ~]# dmsetup info /dev/dm-26
Device dm-26 not found
Command failed.
[root@iZuf6dbyd7ede51sykedamZ ~]# dmsetup info /dev/dm-25
Name: vg0-21
State: ACTIVE
Read Ahead: 256
Tables present: LIVE
Open count: 0
Event number: 0
Major, minor: 252, 25
Number of targets: 1
UUID: LVM-PIFRRbKrhSqE5j6Q8jfk1qJJ1TNFPUI2SzDoe3z1azKH6HAOPsleizy3LozEMJus
[root@iZuf6dbyd7ede51sykedamZ ~]# dmsetup status | grep vg0-22
vg0-22: 0 20971520 thin 274432 20971519
[root@iZuf6dbyd7ede51sykedamZ ~]# dmsetup info vg0-22
Name: vg0-22
State: ACTIVE
Read Ahead: 256
Tables present: LIVE
Open count: 0
Event number: 0
Major, minor: 252, 26
Number of targets: 1
UUID: LVM-PIFRRbKrhSqE5j6Q8jfk1qJJ1TNFPUI2YMnwPdLNF3JggAzXGwaFujcPePyOAeqd
Hi
Hmm would it be possible that associated thin pool would be in some erroneous
condition - i.e. out-of-space - or processing some resize ?
This likely could result into some significant processing delay ?
Since you are using very ancient lvm2 (2.02.130) we have heavily improved
logic for such pools over the time...
Zdenek
_______________________________________________
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/
