Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 28 Feb 2020 13:18:02 -0300
From:      Mario Olofo <mario.olofo@gmail.com>
To:        Theron <theron.tarigo@gmail.com>
Cc:        Pete Wright <pete@nomadlogic.org>, FreeBSD Stable <freebsd-stable@freebsd.org>
Subject:   Re: Running FreeBSD on M.2 SSD
Message-ID:  <CAP4Gn9BqATHXyEbVDKvwQ_YcyUevAYoCt=PjdY5RpzWzyEVt5g@mail.gmail.com>
In-Reply-To: <ac300578-126c-3f9a-082d-d4c560c09879@gmail.com>
References:  <CAP4Gn9DbdzSMbj=xn3E4TMRWzs-WY%2Bun2Rzd9Dt3PUeDL%2BYtpA@mail.gmail.com> <20200224144602.GA64065@phouka1.phouka.net> <CAP4Gn9DYui-x_wsDN3TUMd7cDPB%2BTSfRX3TL5DAa=8a1=eRGxQ@mail.gmail.com> <437a5eae-03c8-737d-48bf-39e2e9163d6d@nomadlogic.org> <CAP4Gn9Cy1w=ftw5QrdCFhWOQ_TaOOK=Wj2NGDC6R81fGPPAB6w@mail.gmail.com> <81ef514d-2575-e9e2-136b-dc79d1c62d74@nomadlogic.org> <CAP4Gn9AqK0BEmWhJ%2BqPqHcqN__GYf6tyonW6dwnvRqf-a2_www@mail.gmail.com> <5127f890-3e97-4982-1e09-3f9e53ecf6aa@nomadlogic.org> <CAP4Gn9CVRmWuo4VNOikEoyfRcVurjEMPj63DWjMY1ezrAgt_EQ@mail.gmail.com> <ac300578-126c-3f9a-082d-d4c560c09879@gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Yes, tried 4k quirk but not on install because don't know how to, I did a
clean install then patch and rebuild the kernel, but
the volume was already configured for 512bytes, I think I would need to
create manually the volume, but don't remember how to anymore xD
But I'll search some tutorials and try. From what I saw, the patch
suggested on bugzilla got merged into the stable branch, so the quirk will
be
detected to use 4k in the installer in a near future.

Mario

Em sex., 28 de fev. de 2020 =C3=A0s 12:52, Theron <theron.tarigo@gmail.com>
escreveu:

> On 2020-02-28 09:14, Mario Olofo wrote:
> > Thanks!
> >
> > The only thing that I didn't checked was the questions of Theron, about
> > misaligned data.
> > The layout of the disk is as follows:
> >
> > Disco /dev/sdb: 447,1 GiB, 480113590272 bytes, 937721856 setores
> > Unidades: setor de 1 * 512 =3D 512 bytes
> > Tamanho de setor (l=C3=B3gico/f=C3=ADsico): 512 bytes / 512 bytes
> > Tamanho E/S (m=C3=ADnimo/=C3=B3timo): 512 bytes / 512 bytes
> > Tipo de r=C3=B3tulo do disco: gpt
> > Identificador do disco: D1725E60-D734-4461-90F8-E9EB2376A65A
> >
> > Dispositivo    In=C3=ADcio       Fim   Setores Tamanho Tipo
> > /dev/sdb1        2048   1023999   1021952    499M Windows ambiente de
> > recupera=C3=A7=C3=A3o
> > /dev/sdb2     1024000   1228799    204800    100M Sistema EFI
> > /dev/sdb3     1228800   1261567     32768     16M Microsoft reservado
> > /dev/sdb4     1261568 532482047 531220480  253,3G Microsoft dados b=C3=
=A1sico
> > /dev/sdb5   532482048 549257215  16775168      8G FreeBSD ZFS
> > /dev/sdb6   549257216 937719807 388462592  185,2G Linux sistema de
> arquivos
> >
> > The zfsroot was configured automatically by the installer, so I think
> that
> > it align the volume automaticaly right?
> >
> > Mario
>
> Yes, I don't see any potential alignment issue here.  I would wonder if
> this drive is misrepresenting its physical sector size, deceiving ZFS
> and the SATA driver into making small writes that the drive does not
> actually support, but it looks like you may have already tried the
> relevant workaround:
>
> On 2020-02-27 23:44, Mario Olofo wrote:
> > Maybe the problem really is a combination of factors, for the person th=
at
> > filed a bug on bugzilla the fix was setting the quirks 4k and
> broken_trim,
> > but for me the real block size is 512bytes and only setting the flag
> > broken_trim didn't help...
> >
> > Mario
> Did you try 4k quirk ?
>
> Theron
>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAP4Gn9BqATHXyEbVDKvwQ_YcyUevAYoCt=PjdY5RpzWzyEVt5g>