<div dir="ltr">If you use sdb only for data, you don't have need to use partition on the disk.<br></div><br><div class="gmail_quote"><div dir="ltr">Il giorno gio 11 ott 2018 alle ore 16:26 David Teigland <<a href="mailto:teigland@redhat.com">teigland@redhat.com</a>> ha scritto:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Thu, Oct 11, 2018 at 08:53:07AM +0545, Sherpa Sherpa wrote:<br>
> I have LVM(backed by hardware RAID5) with logical volume and a volume group<br>
> named "dbstore-lv" and "dbstore-vg" which have sdb1 sdb2 sdb3 created from<br>
> same sdb disk.<br>
<br>
> sdb 8:16 0 19.7T 0 disk<br>
> ├─sdb1 8:17 0 7.7T 0 part<br>
> │ └─dbstore-lv (dm-1) 252:1 0 9.4T 0 lvm /var/db/st01<br>
> ├─sdb2 8:18 0 1.7T 0 part<br>
> │ └─dbstore-lv (dm-1) 252:1 0 9.4T 0 lvm /var/db/st01<br>
> └─sdb3 8:19 0 10.3T 0 part<br>
> └─archive--archivedbstore--lv (dm-0) 252:0 0 10.3T 0 lvm<br>
<br>
> I am assuming this is due to disk seek problem as the same disk partitions<br>
> are used for same LVM or may be its due to saturation of the disks<br>
<br>
You shouldn't add different partitions as different PVs. If it's too late<br>
to fix, it might help to create new LV that uses only one of the<br>
partitions, e.g. lvcreate -n lv -L size vg /dev/sdb2, and then copy your<br>
current LV to the new one.<br>
<br>
_______________________________________________<br>
linux-lvm mailing list<br>
<a href="mailto:linux-lvm@redhat.com" target="_blank">linux-lvm@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/linux-lvm" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/linux-lvm</a><br>
read the LVM HOW-TO at <a href="http://tldp.org/HOWTO/LVM-HOWTO/" rel="noreferrer" target="_blank">http://tldp.org/HOWTO/LVM-HOWTO/</a></blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"> .~.<br> /V\<br> // \\<br>/( )\<br>^`~'^</div>