archive mirror
 help / color / mirror / Atom feed
From: David Teigland <>
To: Sherpa Sherpa <>
Subject: Re: [linux-lvm] what is the IOPS behavior when partitions of single disk(raid5 backend) are used in an LVM?
Date: Thu, 11 Oct 2018 09:25:50 -0500	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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.

  reply	other threads:[~2018-10-11 14:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-11  3:08 [linux-lvm] what is the IOPS behavior when partitions of single disk(raid5 backend) are used in an LVM? Sherpa Sherpa
2018-10-11 14:25 ` David Teigland [this message]
2018-10-11 14:31   ` Emmanuel Gelati
2018-10-12 12:02     ` Heinz Mauelshagen
2018-10-12 15:46       ` Sherpa Sherpa
2018-10-15 14:48         ` Heinz Mauelshagen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).