linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Heinz Mauelshagen <heinzm@redhat.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] what is the IOPS behavior when partitions of single disk(raid5 backend) are used in an LVM?
Date: Fri, 12 Oct 2018 14:02:22 +0200	[thread overview]
Message-ID: <581cfd57-aca0-70f5-b715-f05357e4bbad@redhat.com> (raw)
In-Reply-To: <CAE7pJ3DZn9H5BXSuTo=uuFfVZQYxYymvzaAN21hCfhA+=AWO5w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2482 bytes --]

On 10/11/18 4:31 PM, Emmanuel Gelati wrote:
> If you use sdb only for data, you don't have need to use partition on 
> the disk.

Though that's true, keeping 1 partition per disk for each LVM PV adds 
additional
'visibility' by tools like fdisk/[cs]fdisk, parted etc. showing the 
partition type to be 'Liinux LVM'.

Using the whole disk, blkid or lsblk will provide that information still,
e.g. 'blkid --match-token TYPE=LVM2_member'.

Heinz

>
> Il giorno gio 11 ott 2018 alle ore 16:26 David Teigland 
> <teigland@redhat.com <mailto:teigland@redhat.com>> ha scritto:
>
>     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.
>
>     _______________________________________________
>     linux-lvm mailing list
>     linux-lvm@redhat.com <mailto:linux-lvm@redhat.com>
>     https://www.redhat.com/mailman/listinfo/linux-lvm
>     read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>
>
>
> -- 
>   .~.
>   /V\
>  //  \\
> /(   )\
> ^`~'^
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/


[-- Attachment #2: Type: text/html, Size: 4675 bytes --]

  reply	other threads:[~2018-10-12 12:02 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
2018-10-11 14:31   ` Emmanuel Gelati
2018-10-12 12:02     ` Heinz Mauelshagen [this message]
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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=581cfd57-aca0-70f5-b715-f05357e4bbad@redhat.com \
    --to=heinzm@redhat.com \
    --cc=linux-lvm@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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).