From nobody Fri Feb 16 04:08:09 2024 X-Original-To: freebsd-arm@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 4TbdhV1rV4z59b4G for ; Fri, 16 Feb 2024 04:08:26 +0000 (UTC) (envelope-from ordinarybit@proton.me) Received: from mail-40135.protonmail.ch (mail-40135.protonmail.ch [185.70.40.135]) (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 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "protonmail.com", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4TbdhT6VLxz4N2X for ; Fri, 16 Feb 2024 04:08:25 +0000 (UTC) (envelope-from ordinarybit@proton.me) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=proton.me; s=protonmail; t=1708056502; x=1708315702; bh=EmVqAlGPa7T8jVDPOVlPvy99UrHaJUkWVA4fQpxPIrE=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=e4qz2catv2Zz+PEKQqIlJxnuAd0j7PXgSd0UWL901bm029iWOwZIY64aIhf2iX+OB 2lKH75S5recEJHL4igs9JEwDK0CWb+UUHnB+Z60HGqSl6qlK/u+yfe9k6n0NY/alPd XGXy5aQS+/AKkDzynHRhuXB4eaYXW02wXCMFBYNAGyJSoB3hcWSi1qQ7miWKN4vTBN 819J4w279+7QUje/Ejw6zRRJaPLdszbA1xJh/1LjMvK9DwEOBhx+UmhpfTn19S+slR /xppig/jtTpT09qInKofQ9xUddJY7LNldeSuDU6tmHwWTkOgn+W30h8XBuyOIrT7fZ kABgPQZ8bVFNg== Date: Fri, 16 Feb 2024 04:08:09 +0000 To: Mark Millard From: Ordinary Bit Cc: "freebsd-arm@freebsd.org" Subject: Re: newfs TRIM flag device support Message-ID: In-Reply-To: <6AD380D4-9B42-4511-9E02-94EB0005D278@yahoo.com> References: <6AD380D4-9B42-4511-9E02-94EB0005D278@yahoo.com> Feedback-ID: 100108111:user:proton List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spamd-Bar: ---- X-Rspamd-Queue-Id: 4TbdhT6VLxz4N2X 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:62371, ipnet:185.70.40.0/24, country:CH] Hi! On Friday, 16 February 2024 at 11:41, Mark Millard wrot= e: > [Only replying to lists I subscribe to.] >=20 > On Feb 15, 2024, at 19:19, Ordinary Bit ordinarybit@proton.me wrote: >=20 > > I'm reading the newfs manual https://man.freebsd.org/cgi/man.cgi?newfs(= 8) to be able to know about the TRIM flag. In the manual under -t parameter= , it mentioned about "underlying device support", what exactly is this devi= ce? >=20 >=20 > 2 contrasting examples: >=20 >=20 > Example 0: Optane NVMe media (PCIe card or U.2, for example) >=20 > Optane has no need of TRIM and, so, never supports TRIM. >=20 >=20 > Example 1: microsd card media usage >=20 > A microsd card in the normal type of microsd card slot on > Small Board Computers (normally) supports TRIM. Take the > same card and put it in a USB reader/writer and use it > via USB on the same system: no TRIM is supported by > FreeBSD over USB. > So you mean to say that if I have a Rasperry Pi 3 or 4 now and then have my= FreeBSD installed in a microSD card (for example, SanDisk Extreme card) wi= th UFS/FFS filesytem in it with TRIM enabled parameter then is it going to = recognize it? How to verify? >=20 > FYI: >=20 > When the file system has TRIM enabled, FreeBSD put out a > notice if TRIM will not actually be used in the actual > context in use. > Ok, got it. How to check this as well? BR, orbit