Hide Forgot
Description of problem: When creating a thin pool, its notifies you that the thin pool was created AND a volume called lvol0 - which isnt actually created Version-Release number of selected component (if applicable): lvm2-2.02.100-8.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1. Install RHEL6.5 and yum update 2. create a thin pool 3. observe the, incorrect, additional message Actual results: Thin pool is created and you are notified that a lvol0 was also created, which is wasnt Expected results: Dont tell me lvol0 was created in addition to my thin pool Additional info: [root@thin-tests ~]# lvs LV VG Attr LSize Pool Origin Data% Move Log Cpy%Sync Convert rootvol myvg -wi-ao---- 7.31g [root@thin-tests ~]# lvcreate -l 46 --type thin-pool --thinpool tp_pool myvg Logical volume "lvol0" created Logical volume "tp_pool" created [root@thin-tests ~]# lvs LV VG Attr LSize Pool Origin Data% Move Log Cpy%Sync Convert rootvol myvg -wi-ao---- 7.31g tp_pool myvg twi-a-tz-- 1.44g 0.00 [root@thin-tests ~]# rpm -q lvm2 lvm2-2.02.100-8.el6.x86_64
It is. See output of 'lvs -a'.
Created lvol0 is volume used as a 'spare' LV for a possible thin pool recovery. It's just later renamed to lvol0_pmspare and as such it is hidden volume. (lvs -a is needed) However we are considering to remove this creation message - it's not yet defined. Anyway - it's not a bug - it's rather informational noise which needs some cleaning.
Thanks for the additional information Zdenek. Personally Id agree that the message needs removing if its a hidden vol
It's not that easy to decide. Since anywhere during creation process the machine could be turned off/crash, it might happen you would end-up after reboot with a 'lvol0' volume and you would have no idea who was creating it and why it is there (thus probably reporting even bug on lvm2....) So while we are printing info about creation of lvol0 - we make a user aware there was this volume created and it's temporarily present. But we do not inform about later usage of this volume as a thin pool spare LV. Which might be another solution for this problem - to just print notice, lvol0 is used is pool metadata spare LV.
The behaviour in Fedora seems different. [root@localhost ~]# cat /etc/redhat-release Fedora release 19 (Schrödinger’s Cat) [root@localhost ~]# lvcreate --size 5G --type thin-pool --thinpool tp_pool fedora Logical volume "tp_pool" created [root@localhost ~]#
Fedora 19 uses older lvm2 version (v2.02.98) which didn't have the support for spare LV iirc.
Wow, ok then that explains it - thanks all