From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 9B7CC15ACFB for ; Tue, 18 Apr 2023 21:25:28 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 87A67E0899; Tue, 18 Apr 2023 21:25:24 +0000 (UTC) Received: from mail-lj1-x232.google.com (mail-lj1-x232.google.com [IPv6:2a00:1450:4864:20::232]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 4095EE0874 for ; Tue, 18 Apr 2023 21:25:24 +0000 (UTC) Received: by mail-lj1-x232.google.com with SMTP id r9so18240044ljp.9 for ; Tue, 18 Apr 2023 14:25:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1681853122; x=1684445122; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=Zb+J1WYPNA//ctRRW5S6ddWpw1u4OwdBWiYrrzDnQHM=; b=cHlbg/pYPWg4NSIu4tWJcSP4Cuvyf7SfX4Avp0m3hRcvlZqcXU+YAcb2xUJ7oMh3aq ZkIzoK9caze6TN4TbeKJkJTlnXgurn2XLE8DtqqKHYLbFFv4+CYwBaahV1wmluse8qHX NoDyQ9Aja22iOfWA2ZJEvY8wnstrKLGszvHJQJBl6AOns345uSWamkkXckfXT3PpbvBV cHEVR4yopvhbytdqpjBl4opV0qWc4PTEiwRHNb/7BYC3dGa0rC41QSoDwBzVKt2mQfd7 ZzBXLltmv19Ud9uiL3FGag1KqPVU7O/AnMvbV/bs4pMB/NgSv+LcPU0Kam1OZAVlUG4v F0Sw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1681853122; x=1684445122; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=Zb+J1WYPNA//ctRRW5S6ddWpw1u4OwdBWiYrrzDnQHM=; b=SxVdM9RN+QUvhygDUE4zSguESJgvylZkDdGGAqI1pMLDTF6rJ4PpZksoCcp5evsb36 qprNMsecBDCoesjYDuRf7PQs5cwsNC+dHzO1XYtXxnl1ZJBJf791A6INqJ2B1KaOD4qT 2S6ALvInA9aq6e84GzbTUD+sGq4/xYeNw1qzfS0mwEBTgXSJ5qc10ExhjVpEHS17lR1H RwwnBZTja+SKZfuBJNDYuCKLwYaPBTPeN51ke/wAd+OW3MQa5xepyD2fQzxUUJ4ylGLM rv82L4rxqPETRkjoWx4je7qLIRaNJ9zKsEaAqaTtaqHlUNWWgGbxaIubzEpy707InMjh lXQQ== X-Gm-Message-State: AAQBX9f0K+QO4KQ1zn0w+vBOlam8xBt64HFGPqUEToem6fQ2ZlJYALG5 cfbEZePUZbdOMNfILpnttHQAdMpJOolvV48hnulilaVSiVY= X-Google-Smtp-Source: AKy350akcPC9qw6ctNLOomAdRfAUtfXWTET4pr0SuMiiMfNQSspjsrNgxuuIJ23n8L7rVW03wZUAdJtf7E/kKH0E+jY= X-Received: by 2002:a2e:8050:0:b0:2a5:f6f2:1ff4 with SMTP id p16-20020a2e8050000000b002a5f6f21ff4mr1281392ljg.10.1681853122392; Tue, 18 Apr 2023 14:25:22 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 References: <3a8a143d-38f0-b7ea-4aa1-10c0b3a2a1e0@gmail.com> <50d5c2a3-76cc-39bc-290a-c6d3d9e0d7c4@gmail.com> <660b8812-817b-8c2b-ccd0-63b002be9888@gmail.com> <21dff871-ba5d-963d-900a-26e38a955414@gmail.com> In-Reply-To: <21dff871-ba5d-963d-900a-26e38a955414@gmail.com> From: Mark Knecht Date: Tue, 18 Apr 2023 14:25:11 -0700 Message-ID: Subject: Re: [gentoo-user] Re: Finally got a SSD drive to put my OS on To: gentoo-user@lists.gentoo.org Content-Type: multipart/alternative; boundary="000000000000ecb78d05f9a2f11d" X-Archives-Salt: 2b7af60f-cd74-4eb2-a220-e3bddab3eb73 X-Archives-Hash: 0521a1da0e096945f4f640d42c89deca --000000000000ecb78d05f9a2f11d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Apr 18, 2023 at 2:15=E2=80=AFPM Dale wrote: > > Mark Knecht wrote: > > > > On Tue, Apr 18, 2023 at 1:02=E2=80=AFPM Dale wrote= : > > > > > Someone mentioned 16K block size. > > > I mentioned it but I'm NOT suggesting it. > > It would be the -b option if you were to do it for ext4. > > I'm using the default block size (4k) on all my SSDs and M.2's and > as I've said a couple of time, I'm going to blast past the 5 year > warranty time long before I write too many terabytes. > > Keep it simple. > > - Mark > > One reason I ask, some info I found claimed it isn't even supported. It actually spits out a error message and doesn't create the file system. I wasn't sure if that info was outdated or what so I thought I'd ask. I think I'll skip that part. Just let it do its thing. > > Dale I'd start with something like mkfs.ext4 -b 16384 /dev/sdX and see where it leads. It's *possible* that the SSD might fight back, sending the OS a response that says it doesn't want to do that. It could also be a partition alignment issue, although if you started your partition at the default starting address I'd doubt that one. Anyway, I just wanted to be clear that I'm not worried about write amplification based on my system data. Cheers, Mark --000000000000ecb78d05f9a2f11d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Tue, Apr 18, 2023 at 2:15=E2=80=AFPM Dale <<= a href=3D"mailto:rdalek1967@gmail.com">rdalek1967@gmail.com> wrote:<= br>>
> Mark Knecht wrote:
>
>
>
> On Tue, = Apr 18, 2023 at 1:02=E2=80=AFPM Dale <rdalek1967@gmail.com> wrote:
> <SNIP>
> >=
> > Someone mentioned 16K block size.
> <SNIP>
>= ;
> I mentioned it but I'm NOT suggesting it.
>
> It = would be the -b option if you were to do it for ext4.
>
> I'= ;m using the default block size (4k) on all my SSDs and M.2's and
&g= t; as I've said a couple of time, I'm going to blast past the 5 yea= r
> warranty time long before I write too many terabytes.
>
= > Keep it simple.
>
> - Mark
>
> One reason I a= sk, some info I found claimed it isn't even supported.=C2=A0 It actuall= y spits out a error message and doesn't create the file system.=C2=A0 I= wasn't sure if that info was outdated or what so I thought I'd ask= .=C2=A0 I think I'll skip that part.=C2=A0 Just let it do its thing. >
> Dale
<SNIP>

I'd start with someth= ing like

mkfs.ext4 -b 16384 /dev/sdX

and see whe= re it leads. It's *possible* that the SSD might fight=C2=A0
b= ack, sending the OS a response that says it doesn't want to=C2=A0
=
do that.

It could also be a partition alignme= nt issue, although if you
started your partition at the default s= tarting address I'd doubt=C2=A0
that one.

Anyway, I just wanted to be clear that I'm not worried about
write amplification based on my system data.

Cheers,
Mark
--000000000000ecb78d05f9a2f11d--