From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Thu, 11 Oct 2018 09:25:50 -0500 From: David Teigland Message-ID: <20181011142550.GA15437@redhat.com> References: MIME-Version: 1.0 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Subject: Re: [linux-lvm] what is the IOPS behavior when partitions of single disk(raid5 backend) are used in an LVM? Reply-To: LVM general discussion and development List-Id: LVM general discussion and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , List-Id: Content-Type: text/plain; charset="utf-8" To: Sherpa Sherpa Cc: linux-lvm@redhat.com On Thu, Oct 11, 2018 at 08:53:07AM +0545, Sherpa Sherpa wrote: > I have LVM(backed by hardware RAID5) with logical volume and a volume group > named "dbstore-lv" and "dbstore-vg" which have sdb1 sdb2 sdb3 created from > same sdb disk. > sdb 8:16 0 19.7T 0 disk > ├─sdb1 8:17 0 7.7T 0 part > │ └─dbstore-lv (dm-1) 252:1 0 9.4T 0 lvm /var/db/st01 > ├─sdb2 8:18 0 1.7T 0 part > │ └─dbstore-lv (dm-1) 252:1 0 9.4T 0 lvm /var/db/st01 > └─sdb3 8:19 0 10.3T 0 part > └─archive--archivedbstore--lv (dm-0) 252:0 0 10.3T 0 lvm > I am assuming this is due to disk seek problem as the same disk partitions > are used for same LVM or may be its due to saturation of the disks You shouldn't add different partitions as different PVs. If it's too late to fix, it might help to create new LV that uses only one of the partitions, e.g. lvcreate -n lv -L size vg /dev/sdb2, and then copy your current LV to the new one.