All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: Ryan Norwood <ryan.p.norwood@gmail.com>
Cc: vdo-devel@redhat.com, dm-devel@redhat.com
Subject: Re: max_sectors_kb limitations with VDO and dm-thin
Date: Wed, 24 Apr 2019 17:27:51 -0400	[thread overview]
Message-ID: <20190424212751.GC14367@redhat.com> (raw)
In-Reply-To: <CAFTvtQnALzibyS3jKisXRb+XGe8dopQfkj33=gtJAjd2+XymYQ@mail.gmail.com>


On Wed, Apr 24 2019 at 10:46am -0400,
Ryan Norwood <ryan.p.norwood@gmail.com> wrote:

>    On Wed, Apr 24, 2019 at 9:08 AM Ryan Norwood <[1]ryan.p.norwood@gmail.com>
>    wrote:
> 
>      Thank you for your help.
>      You are correct, it appears that the problem occurs when there is a RAID
>      5 or RAID 50 volume beneath VDO.
>      NAME      KNAME    RA   SIZE ALIGNMENT  MIN-IO  OPT-IO PHY-SEC LOG-SEC
>      RQ-SIZE SCHED    WSAME
>      sdh
>       sdh     128 977.5G         0     512       0     512     512     128
>      deadline    0B
>      +-sed6
>      dm-6    128 977.5G         0     512       0     512     512     128
>               0B
>        +-md127
>       md127 12288   5.7T         0 1048576 6291456     512     512     128
>               0B
>          +-vdo_data
>      dm-17   128   5.7T         0 1048576 6291456     512     512     128
>               0B
>            +-vdo
>       dm-18   128  57.3T         0    4096    4096    4096    4096     128
>               0B
>      /sys/block/md126/queue/max_hw_sectors_kb:2147483647
>      /sys/block/md126/queue/max_integrity_segments:0
>      /sys/block/md126/queue/max_sectors_kb:512
>      /sys/block/md126/queue/max_segments:64
>      /sys/block/md126/queue/max_segment_size:4096
>      /sys/block/dm-17/queue/max_hw_sectors_kb:512
>      /sys/block/dm-17/queue/max_integrity_segments:0
>      /sys/block/dm-17/queue/max_sectors_kb:512
>      /sys/block/dm-17/queue/max_segments:64
>      /sys/block/dm-17/queue/max_segment_size:4096
>      /sys/block/dm-18/queue/max_hw_sectors_kb:4
>      /sys/block/dm-18/queue/max_integrity_segments:0
>      /sys/block/dm-18/queue/max_sectors_kb:4
>      /sys/block/dm-18/queue/max_segments:64
>      /sys/block/dm-18/queue/max_segment_size:4096
>      NAME      KNAME    RA   SIZE ALIGNMENT  MIN-IO  OPT-IO PHY-SEC LOG-SEC
>      RQ-SIZE SCHED    WSAME
>      sdq       sdq     128 977.5G         0     512       0     512     512
>         128 deadline    0B
>      +-sed15   dm-15   128 977.5G         0     512       0     512     512
>         128             0B
>        +-vdo   dm-16   128  57.3T         0    4096    4096    4096    4096
>         128             0B
>      /sys/block/sdq/queue/max_hw_sectors_kb:256
>      /sys/block/sdq/queue/max_integrity_segments:0
>      /sys/block/sdq/queue/max_sectors_kb:256
>      /sys/block/sdq/queue/max_segments:64
>      /sys/block/sdq/queue/max_segment_size:65536
>      /sys/block/dm-15/queue/max_hw_sectors_kb:256
>      /sys/block/dm-15/queue/max_integrity_segments:0
>      /sys/block/dm-15/queue/max_sectors_kb:256
>      /sys/block/dm-15/queue/max_segments:64
>      /sys/block/dm-15/queue/max_segment_size:4096
>      /sys/block/dm-16/queue/max_hw_sectors_kb:256
>      /sys/block/dm-16/queue/max_integrity_segments:0
>      /sys/block/dm-16/queue/max_sectors_kb:256
>      /sys/block/dm-16/queue/max_segments:64
>      /sys/block/dm-16/queue/max_segment_size:4096

[please don't top-post]

The above examples are hard to parse due to premature line wrapping.

Would appreciate seeing the IO stack in terms of:
dmsetup ls --tree -o blkdevname
dmsetup table

Feel free to trucate the output of both commands to just show one entire
example of the IO stack in question.

thanks,
Mike

  reply	other threads:[~2019-04-24 21:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-19 14:40 max_sectors_kb limitations with VDO and dm-thin Ryan Norwood
2019-04-23 10:11 ` Zdenek Kabelac
2019-04-23 17:02   ` Ryan Norwood
     [not found]     ` <CAMeeMh-v+xpn2YDizFQg4cKHZgC=aCdJwLfAMeGLGT1gB1ZURw@mail.gmail.com>
     [not found]       ` <CAFTvtQnLDU_MKzse5t4xc_CVWENsZtwQQSTAFyj-45tPg5STZQ@mail.gmail.com>
2019-04-24 14:46         ` Ryan Norwood
2019-04-24 21:27           ` Mike Snitzer [this message]
2019-04-24 22:22             ` Mike Snitzer
2019-04-25 11:58               ` Ryan Norwood
2019-04-25 18:11                 ` [Vdo-devel] " Gionatan Danti
2019-04-25 18:26                   ` Ryan Norwood
2019-04-24 19:45 ` Mike Snitzer
2019-04-24 21:18   ` Mike Snitzer

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=20190424212751.GC14367@redhat.com \
    --to=snitzer@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=ryan.p.norwood@gmail.com \
    --cc=vdo-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.