From owner-freebsd-stable@freebsd.org Sat Feb 29 04:54:26 2020 Return-Path: Delivered-To: freebsd-stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 8684B2556C9 for ; Sat, 29 Feb 2020 04:54:26 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ultimatedns.net", Issuer "Let's Encrypt Authority X3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 48TvFs1NdXz4PZm for ; Sat, 29 Feb 2020 04:54:24 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (localhost [IPv6:0:0:0:0:0:0:0:1]) by udns.ultimatedns.net (8.15.2/8.15.2) with ESMTPS id 01T4sdKI049924 (version=TLSv1.2 cipher=DHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Fri, 28 Feb 2020 20:54:45 -0800 (PST) (envelope-from bsd-lists@BSDforge.com) X-Mailer: Cypht MIME-Version: 1.0 In-Reply-To: From: Chris Reply-To: bsd-lists@BSDforge.com To: Subject: Re: Running FreeBSD on M.2 SSD Date: Fri, 28 Feb 2020 20:54:45 -0800 Message-Id: <10e3153ee81dcd7919079cd0bfc16656@udns.ultimatedns.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 48TvFs1NdXz4PZm X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of bsd-lists@BSDforge.com has no SPF policy when checking 24.113.41.81) smtp.mailfrom=bsd-lists@BSDforge.com X-Spamd-Result: default: False [-1.04 / 15.00]; ARC_NA(0.00)[]; HAS_REPLYTO(0.00)[bsd-lists@BSDforge.com]; XM_UA_NO_VERSION(0.01)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; IP_SCORE(-0.29)[ip: (-0.53), ipnet: 24.113.0.0/16(-0.26), asn: 11404(-0.60), country: US(-0.05)]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-0.999,0]; DMARC_NA(0.00)[BSDforge.com]; REPLYTO_ADDR_EQ_FROM(0.00)[]; NEURAL_HAM_MEDIUM(-0.66)[-0.663,0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:11404, ipnet:24.113.0.0/16, country:US]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Feb 2020 04:54:26 -0000 On Fri, 28 Feb 2020 21:44:45 -0300 Mario Olofo mario=2Eolofo@gmail=2Ecom said > Hello guys, a little update that let me more confused >=20 > I reinstalled the FreeBSD with 4k pages using the sysctl > vfs=2Ezfs=2Emin_auto_ashift =3D 12 and no errors after a lot of stress I put = on > it=2E > One thing that I noticed is that with the pool as 4k, the disk fill up ve= ry > fast, recompiling the kernel used my 8GB space and didn't even completed=2E > But now I don't know if the 4k is the correct answer or if this just dela= ys > the problem as the pages are bigger=2E The TLDR of 4k vs 512 largely has to do with the size of the files going onto your medium=2E Many files of a smaller size fit better on a 512 boundary= =2E Whereas larger mp3s or archives fair better on a 4k boundary=2E BTW these are called SECTOR sizes=2E Not pages=2E :) 4k blocks typically read faster, than th= e 512 blocks (sectors)=2E Because more data can be consumed in one read/write=2E So really, your going to have to decide how best to "tune" your disk to bes= t suite it's intended use=2E Many small files=2E Or big files, and storage=2E HTH --Chris FreeBSD 14=2E0-FUTURE #0=2E000 cray256 >=20 > Mario >=20 > Em sex=2E, 28 de fev=2E de 2020 =C3=A0s 13:18, Mario Olofo > escreveu: >=20 > > 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=2E From what I saw, the patch > > suggested on bugzilla got merged into the stable branch, so the quirk w= ill > > be > > detected to use 4k in the installer in a near future=2E > > > > Mario > > > > Em sex=2E, 28 de fev=2E de 2020 =C3=A0s 12:52, Theron > > escreveu: > > > >> On 2020-02-28 09:14, Mario Olofo wrote: > >> > Thanks! > >> > > >> > The only thing that I didn't checked was the questions of Theron, ab= out > >> > misaligned data=2E > >> > 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=2E I would wonder i= f > >> 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=2E=2E=2E > >> > > >> > Mario > >> Did you try 4k quirk ? > >> > >> Theron > >> > > > _______________________________________________ > freebsd-stable@freebsd=2Eorg mailing list > https://lists=2Efreebsd=2Eorg/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd=2Eorg"