On Sat 28 Jul 2018 at 15:23:48 (-0700), Rick Thomas wrote:
>
> On Jul 28, 2018, at 1:28 PM, Henrique de Moraes Holschuh
> wrote:
>
> > On Sat, 28 Jul 2018, David Wright wrote:
> >> On Sat 28 Jul 2018 at 10:57:45 (-0300), Henrique de Moraes Holschuh wrote:
> >>> On Sat, 28 Jul 2018, Rick Thomas
On Jul 28, 2018, at 1:28 PM, Henrique de Moraes Holschuh
wrote:
> On Sat, 28 Jul 2018, David Wright wrote:
>> On Sat 28 Jul 2018 at 10:57:45 (-0300), Henrique de Moraes Holschuh wrote:
>>> On Sat, 28 Jul 2018, Rick Thomas wrote:
> rbthomas@small:~$ lsblk -t
> NAME ALIGNMENT
On Sat, 28 Jul 2018, David Wright wrote:
> On Sat 28 Jul 2018 at 10:57:45 (-0300), Henrique de Moraes Holschuh wrote:
> > On Sat, 28 Jul 2018, Rick Thomas wrote:
> > > > rbthomas@small:~$ lsblk -t
> > > > NAME ALIGNMENT MIN-IO OPT-IO PHY-SEC LOG-SEC ROTA SCHED
> > > > RQ-SIZE
On Sat 28 Jul 2018 at 10:57:45 (-0300), Henrique de Moraes Holschuh wrote:
> On Sat, 28 Jul 2018, Rick Thomas wrote:
> > > rbthomas@small:~$ lsblk -t
> > > NAME ALIGNMENT MIN-IO OPT-IO PHY-SEC LOG-SEC ROTA SCHED
> > > RQ-SIZE RA WSAME
> > > sda0 4096
On Sat, 28 Jul 2018, Rick Thomas wrote:
> > rbthomas@small:~$ lsblk -t
> > NAME ALIGNMENT MIN-IO OPT-IO PHY-SEC LOG-SEC ROTA SCHED
> > RQ-SIZE RA WSAME
> > sda0 4096 335539204096 5121 mq-deadline
> >60 1280B
> > `-sda1
groups of four, each group with a different “start” value and corresponding
>>> minor device)
>>>
>>>> Jul 24 03:40:08 small kernel: device-mapper: table: 254:1: adding target
>>>> device sda1 caused an alignment inconsistency: physical_block_size=4096
; device)
>>
>>> Jul 24 03:40:08 small kernel: device-mapper: table: 254:1: adding target
>>> device sda1 caused an alignment inconsistency: physical_block_size=4096,
>>> logical_block_size=512, alignment_offset=0, start=33553920
>>
>> Can anyon
pper: table: 254:1: adding target
> > device sda1 caused an alignment inconsistency: physical_block_size=4096,
> > logical_block_size=512, alignment_offset=0, start=33553920
>
> Can anyone tell me what it means and what I should do about it?
That's the same message a
Alignment ensures optimal use of your drive, sometimes software gets this wrong
and compensates by using a larger cache, check
cat /sys/block/sd?/queue/optimal_io_size
to correct that you have to re format (likely both the GPT/LVM layers) look
into --dataalignment and --dataalignmentoffset
When booting, I get 12 error messages similar to the following (three groups of
four, each group with a different “start” value and corresponding minor device)
> Jul 24 03:40:08 small kernel: device-mapper: table: 254:1: adding target
> device sda1 caused an alignment inconsi
10 matches
Mail list logo
