Date: Sun, 1 Mar 2020 10:55:30 -0300 From: Mario Olofo <mario.olofo@gmail.com> To: Daniel Kalchev <daniel@digsys.bg> Cc: Theron <theron.tarigo@gmail.com>, Pete Wright <pete@nomadlogic.org>, FreeBSD Stable <freebsd-stable@freebsd.org> Subject: Re: Running FreeBSD on M.2 SSD Message-ID: <CAP4Gn9CcbogfMM5y3L-PoNaa%2BrB5rpg=12xOB60k1S7swk%2Bd8A@mail.gmail.com> In-Reply-To: <29C7C315-99F2-46CE-A269-341FBDFE117E@digsys.bg> References: <CAP4Gn9CPtsrSTia%2BsSyT7yRiSHGfO0qJGPGrqR7sOSth7dsiwg@mail.gmail.com> <29C7C315-99F2-46CE-A269-341FBDFE117E@digsys.bg>
next in thread | previous in thread | raw e-mail | index | archive | help
Yes, I installed with TRIM on and used the system with it on, but now I expanded the partition, reinstalled and rebuild the kernel with the quirk of broken TRIM to be safe but it appears to not be needed as far as I can tell. Will continue to work on the wifi driver now that the filesystem is stable =3D) Thank you all! <3 Mario Em dom., 1 de mar. de 2020 =C3=A0s 03:24, Daniel Kalchev <daniel@digsys.bg> escreveu: > Is TRIM still on? > > I understand the quirks patch indicates the drive has some trouble with 4= K > aligned writes. If memory serves it I also indicated broken TRIM so to be > safe you need both. > > Daniel > > > > On 29 Feb 2020, at 2:46, Mario Olofo <mario.olofo@gmail.com> wrote: > > > > =EF=BB=BFHello guys, a little update that let me more confused > > > > I reinstalled the FreeBSD with 4k pages using the sysctl > > vfs.zfs.min_auto_ashift =3D 12 and no errors after a lot of stress I pu= t on > > it. > > One thing that I noticed is that with the pool as 4k, the disk fill up > very > > fast, recompiling the kernel used my 8GB space and didn't even complete= d. > > But now I don't know if the 4k is the correct answer or if this just > delays > > the problem as the pages are bigger. > > > > Mario > > > >> Em sex., 28 de fev. de 2020 =C3=A0s 13:18, Mario Olofo < > mario.olofo@gmail.com> > >> escreveu: > >> > >> Yes, tried 4k quirk but not on install because don't know how to, I di= d > a > >> clean install then patch and rebuild the kernel, but > >> the volume was already configured for 512bytes, I think I would need t= o > >> 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 d= e > >>>> recupera=C3=A7=C3=A3o > >>>> /dev/sdb2 1024000 1228799 204800 100M Sistema EFI > >>>> /dev/sdb3 1228800 1261567 32768 16M Microsoft reservad= o > >>>> /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 thin= k > >>> 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 > >>> that > >>>> 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 > >>> > >> > > _______________________________________________ > > freebsd-stable@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.or= g > " > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAP4Gn9CcbogfMM5y3L-PoNaa%2BrB5rpg=12xOB60k1S7swk%2Bd8A>