From nobody Fri Dec 08 14:13:07 2023 X-Original-To: freebsd-fs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SmtQn4hhsz542kr for ; Fri, 8 Dec 2023 14:13:21 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ej1-x631.google.com (mail-ej1-x631.google.com [IPv6:2a00:1450:4864:20::631]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SmtQn0yRSz4Z1Q for ; Fri, 8 Dec 2023 14:13:21 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ej1-x631.google.com with SMTP id a640c23a62f3a-a196f84d217so254946366b.3 for ; Fri, 08 Dec 2023 06:13:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1702044799; x=1702649599; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=/RSC1kl9eTA8hPITJXV+FPANxbc2f4NoV/yRJ/3ama0=; b=GGSejR4iT/3WqhjELpHHyyw9W2EvQ3aQnnohDOcjzf/bbPPrL9zeiEsJkSywqkAtLu cxI3oG+/jk0GJ/MQwx2b2UG/ZoA5aCjhXpYBxWLScF9ZyK9mPgFMhjUnwM6NZ4J/UZ+3 Kqvk3NVetelEyo1VhuypiIut2mnRlxpz0XJCtvrzjrnj6gBipqGKd9zl42wXO1+F26na 4FgCb63NVVCpyW9zujUPx5fozXDk7njQWXrAgyaDxa/A1p2unPYmKHqQErAdBXv1rhML 1QYN9460iu4N6+JHEzQn2Z8D9KVIThI3L7MZvSLf20gf9/G1Bt1ntcdozX7SnzpOHLso epIQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1702044799; x=1702649599; h=cc: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=/RSC1kl9eTA8hPITJXV+FPANxbc2f4NoV/yRJ/3ama0=; b=s1RZp6t+p8hWFjjp6gBTGIopkw//71s473h/6hhFo391P4JvNjBp4bfOt0k2EYKGUy p248DhdTB+NwKl7/3vqz4h5KXSxu3ZeSfhSY2qBO9P41DzfgCZ7ISd81v3JkRnLFO1zz 9ih/CohttsEA5KcqwI3uXvYTa1tItwCn3DIlLLbQoiGt4ILW51I8RzapQiF8mF7sQ4fu MD0XnpIFuJ/OAzHE4eddxbvGmB4/vSY/wf45RWp4Cvc05wfbELFzoYzSI0/dXaE2NE4R DrpHJurtKw62wPiALl4ko2CXXE26jvvNnpEwIOxc+w4GyTSMMxzXaAsF2Pu6klAUWCW5 PsUQ== X-Gm-Message-State: AOJu0Yzn4PH1qSjgaOGPnIDrN3gvn3w6jEu++WKwPGQjNnGtHIawmM+A uJqLnNjCAM5x/VBbpLkTLd1IcBUNcWuj2rUa8dZFKA== X-Google-Smtp-Source: AGHT+IFei6SZ4OHcP/jqV7AhGTJM1VccCvt5onwfIzSK6QREEgGLL6zJghOuvcd3X/vFceoXDjU7pb1ijOxhuvCS2zQ= X-Received: by 2002:a17:907:cb28:b0:a19:a1ba:8cd8 with SMTP id um40-20020a170907cb2800b00a19a1ba8cd8mr18563ejc.118.1702044799234; Fri, 08 Dec 2023 06:13:19 -0800 (PST) List-Id: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@freebsd.org MIME-Version: 1.0 References: <2959153.slGk94SIus@ravel> In-Reply-To: <2959153.slGk94SIus@ravel> From: Warner Losh Date: Fri, 8 Dec 2023 07:13:07 -0700 Message-ID: Subject: Re: periodic trim for ufs2 ssds To: Olivier Certner Cc: FreeBSD FS Content-Type: multipart/alternative; boundary="000000000000a68690060c002fa2" X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Spamd-Bar: ---- X-Rspamd-Queue-Id: 4SmtQn0yRSz4Z1Q --000000000000a68690060c002fa2 Content-Type: text/plain; charset="UTF-8" On Fri, Dec 8, 2023, 4:03 AM Olivier Certner wrote: > Hi, > > Did you consider trying 'fsck_ffs -B -E' on a toy system? From a glance > at the code, these flags are not exclusive and should do what you expect. > I wouldn't expect that to work... If that works, then you also have the option of not turning on trim on the > FS and instead periodically doing it at once, like you can do on ZFS. > I'd go the other way. I'd turn trim on for UFS and monitor the system under load. Newer drives I've evaluated have much better pathological behavior than the drives of a few years ago... there's a lot of left over fud about how it's always terrible... Warner Regards. > > -- > Olivier Certner > > > > --000000000000a68690060c002fa2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Fri, Dec 8, 2023, 4:03 AM Olivier Certner <olivier.freebsd@free.fr> wrote= :
Hi,

Did you consider trying 'fsck_ffs -B -E' on a toy system?=C2=A0 Fro= m a glance at the code, these flags are not exclusive and should do what yo= u expect.


I wouldn't expect that to work...=

If that works, then you also have the option of not turning on trim on the = FS and instead periodically doing it at once, like you can do on ZFS.

I'= d go the other way. I'd turn trim on for UFS and monitor the system und= er load. Newer drives I've evaluated have much better pathological beha= vior than the drives of a few years ago... there's a lot of left over f= ud about how it's always terrible...

<= div dir=3D"auto">Warner

=
Regards.

--
Olivier Certner



--000000000000a68690060c002fa2--