Red HatThis forum is for the discussion of Red Hat Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I want to know why lsblk showing me LVM pool i haven't create any pool, but i noticed after installing veritas infoscale on RHEL 7.3, i'm getting below screen with rhel-pool00_tmeta and rhel-pool00_tdata.
i removed all installed application from rhel 7.3 but still i am able to see below output.
I suppose that the LVM structures created by Infoscale (if that is the origin of your pool) remain even after you remove Infoscale. An application that removes all user data when getting uninstalled would not survive in the market.
For better readability, format code as code (see below for instructions).
Last edited by berndbausch; 12-26-2018 at 10:12 PM.
[root@RHEL_INFOSCALE ~]# lvdisplay
--- Logical volume ---
LV Name pool00
VG Name rhel
LV UUID 6L2Xhs-gAg2-H1w4-LP7I-2fHD-Dan6-CRnOS9
LV Write Access read/write
LV Creation host, time localhost.localdomain, 2018-12-05 11:46:04 +0530
LV Pool metadata pool00_tmeta
LV Pool data pool00_tdata
LV Status available
# open 2
LV Size 279.40 GiB
Allocated pool data 4.81%
Allocated metadata 2.63%
Current LE 71526
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 8192
Block device 253:2
--- Logical volume ---
LV Path /dev/rhel/root
LV Name root
VG Name rhel
LV UUID rEg8GX-Xx6q-Cdsh-rAtD-Fi3s-Z2eA-i90ilD
LV Write Access read/write
LV Creation host, time localhost.localdomain, 2018-12-05 11:46:05 +0530
LV Pool name pool00
LV Status available
# open 1
LV Size 279.40 GiB
Mapped size 4.81%
Current LE 71526
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 8192
Block device 253:3
--- Logical volume ---
LV Path /dev/rhel/swap
LV Name swap
VG Name rhel
LV UUID YSPuKe-5fUk-etk3-ybAg-jxUR-Ejig-XFkhF0
LV Write Access read/write
LV Creation host, time localhost.localdomain, 2018-12-05 11:46:34 +0530
LV Status available
# open 2
LV Size 4.66 GiB
Current LE 1192
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 8192
Block device 253:4
I don't understand why someone running RHEL who is "RHCE Certified" wouldn't contact RedHat for support...
That said, the question is not at all clear. What is the specific problem?
Hi scasey,
Let me tell you one thing i am not familiar with storage pool,
this is my UAT server where i was testing veritas infoscale which is used for HA and Storage foundation,there is no issue but i want to know why LVM pool created over there without configuration when i'm going to remove this pool its removed completely after reboot its again appearing in lsblk output. for more info please check my lsblk output and post.
[root@RHEL_INFOSCALE ~]# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 500G 0 disk
├─sda1 8:1 0 953M 0 part /boot
└─sda2 8:2 0 300.1G 0 part
├─rhel-pool00_tmeta 253:0 0 72M 0 lvm
│ └─rhel-pool00-tpool 253:2 0 279.4G 0 lvm
│ ├─rhel-root 253:3 0 279.4G 0 lvm /
│ └─rhel-pool00 253:5 0 279.4G 0 lvm
├─rhel-pool00_tdata 253:1 0 279.4G 0 lvm
│ └─rhel-pool00-tpool 253:2 0 279.4G 0 lvm
│ ├─rhel-root 253:3 0 279.4G 0 lvm /
│ └─rhel-pool00 253:5 0 279.4G 0 lvm
└─rhel-swap 253:4 0 4.7G 0 lvm [SWAP]
sr0 11:0 1 1024M 0 rom
[root@RHEL_INFOSCALE ~]# lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
pool00 rhel twi-aotz-- 279.40g 4.81 2.63
root rhel Vwi-aotz-- 279.40g pool00 4.81
swap rhel -wi-ao---- 4.66g
[root@RHEL_INFOSCALE ~]# lvdisplay
--- Logical volume ---
LV Name pool00
VG Name rhel
LV UUID 6L2Xhs-gAg2-H1w4-LP7I-2fHD-Dan6-CRnOS9
LV Write Access read/write
LV Creation host, time localhost.localdomain, 2018-12-05 11:46:04 +0530
LV Pool metadata pool00_tmeta
LV Pool data pool00_tdata
LV Status available
# open 2
LV Size 279.40 GiB
Allocated pool data 4.81%
Allocated metadata 2.63%
Current LE 71526
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 8192
Block device 253:2
--- Logical volume ---
LV Path /dev/rhel/root
LV Name root
VG Name rhel
LV UUID rEg8GX-Xx6q-Cdsh-rAtD-Fi3s-Z2eA-i90ilD
LV Write Access read/write
LV Creation host, time localhost.localdomain, 2018-12-05 11:46:05 +0530
LV Pool name pool00
LV Status available
# open 1
LV Size 279.40 GiB
Mapped size 4.81%
Current LE 71526
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 8192
Block device 253:3
--- Logical volume ---
LV Path /dev/rhel/swap
LV Name swap
VG Name rhel
LV UUID YSPuKe-5fUk-etk3-ybAg-jxUR-Ejig-XFkhF0
LV Write Access read/write
LV Creation host, time localhost.localdomain, 2018-12-05 11:46:34 +0530
LV Status available
# open 2
LV Size 4.66 GiB
Current LE 1192
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 8192
Block device 253:4
[root@RHEL_INFOSCALE ~]#
Regards,
Pravin Goud
RHCE Certified
Last edited by Pravingoud89; 12-27-2018 at 01:46 AM.
[root@RHEL_INFOSCALE ~]# lvdisplay
--- Logical volume ---
LV Name pool00
VG Name rhel
LV UUID 6L2Xhs-gAg2-H1w4-LP7I-2fHD-Dan6-CRnOS9
LV Write Access read/write
LV Creation host, time localhost.localdomain, 2018-12-05 11:46:04 +0530
LV Pool metadata pool00_tmeta
LV Pool data pool00_tdata
LV Status available
# open 2
LV Size 279.40 GiB
Allocated pool data 4.81%
Allocated metadata 2.63%
Current LE 71526
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 8192
Block device 253:2
--- Logical volume ---
LV Path /dev/rhel/root
LV Name root
VG Name rhel
LV UUID rEg8GX-Xx6q-Cdsh-rAtD-Fi3s-Z2eA-i90ilD
LV Write Access read/write
LV Creation host, time localhost.localdomain, 2018-12-05 11:46:05 +0530
LV Pool name pool00
LV Status available
# open 1
LV Size 279.40 GiB
Mapped size 4.81%
Current LE 71526
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 8192
Block device 253:3
--- Logical volume ---
LV Path /dev/rhel/swap
LV Name swap
VG Name rhel
LV UUID YSPuKe-5fUk-etk3-ybAg-jxUR-Ejig-XFkhF0
LV Write Access read/write
LV Creation host, time localhost.localdomain, 2018-12-05 11:46:34 +0530
LV Status available
# open 2
LV Size 4.66 GiB
Current LE 1192
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 8192
Block device 253:4
[root@RHEL_INFOSCALE ~]# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 500G 0 disk
├─sda1 8:1 0 953M 0 part /boot
└─sda2 8:2 0 300.1G 0 part
├─rhel-pool00_tmeta 253:0 0 72M 0 lvm
│ └─rhel-pool00-tpool 253:2 0 279.4G 0 lvm
│ ├─rhel-root 253:3 0 279.4G 0 lvm /
│ └─rhel-pool00 253:5 0 279.4G 0 lvm
├─rhel-pool00_tdata 253:1 0 279.4G 0 lvm
│ └─rhel-pool00-tpool 253:2 0 279.4G 0 lvm
│ ├─rhel-root 253:3 0 279.4G 0 lvm /
│ └─rhel-pool00 253:5 0 279.4G 0 lvm
└─rhel-swap 253:4 0 4.7G 0 lvm [SWAP]
sr0 11:0 1 1024M 0 rom
[root@RHEL_INFOSCALE ~]# lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
pool00 rhel twi-aotz-- 279.40g 4.81 2.63
root rhel Vwi-aotz-- 279.40g pool00 4.81
swap rhel -wi-ao---- 4.66g
[root@RHEL_INFOSCALE ~]# lvdisplay
--- Logical volume ---
LV Name pool00
VG Name rhel
LV UUID 6L2Xhs-gAg2-H1w4-LP7I-2fHD-Dan6-CRnOS9
LV Write Access read/write
LV Creation host, time localhost.localdomain, 2018-12-05 11:46:04 +0530
LV Pool metadata pool00_tmeta
LV Pool data pool00_tdata
LV Status available
# open 2
LV Size 279.40 GiB
Allocated pool data 4.81%
Allocated metadata 2.63%
Current LE 71526
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 8192
Block device 253:2
--- Logical volume ---
LV Path /dev/rhel/root
LV Name root
VG Name rhel
LV UUID rEg8GX-Xx6q-Cdsh-rAtD-Fi3s-Z2eA-i90ilD
LV Write Access read/write
LV Creation host, time localhost.localdomain, 2018-12-05 11:46:05 +0530
LV Pool name pool00
LV Status available
# open 1
LV Size 279.40 GiB
Mapped size 4.81%
Current LE 71526
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 8192
Block device 253:3
--- Logical volume ---
LV Path /dev/rhel/swap
LV Name swap
VG Name rhel
LV UUID YSPuKe-5fUk-etk3-ybAg-jxUR-Ejig-XFkhF0
LV Write Access read/write
LV Creation host, time localhost.localdomain, 2018-12-05 11:46:34 +0530
LV Status available
# open 2
LV Size 4.66 GiB
Current LE 1192
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 8192
Block device 253:4[/B]
[root@RHEL_INFOSCALE ~]#
Please stop with the huge red text; you need to post things in CODE tags, to make them readable, as you were explicitly told. And scasey has a very good point: why would someone who claims to be 'RHCE Certified', using Red Hat Enterprise, need help with such things? Further, you're using Veritas products with RHEL...both are commercial, PAY FOR products, and as such, you can contact either Veritas or Red Hat support...why haven't you done so???
Please don't say "this is UAT server, we have no support since we're just testing"...that doesn't fly. If you're testing products for purchase, companies will fall over themselves to make sure things are working for the test. Getting support is FAR easier for pre-purchase testing than it is later in production, typically.
Quote:
Originally Posted by Pravingoud89
there is no issue but i want to know why LVM pool created over there without configuration when i'm going to remove this pool its removed completely after reboot its again appearing in lsblk output.
So there is no issue/problem, and you want to know why things are working like they are? Great...have you then read the documentation, which explains all of this??? Or, again, contacted Veritas support who can explain it to you??
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.