From owner-freebsd-hackers@freebsd.org Sat Dec 1 21:23:54 2018 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CF5EE1328325 for ; Sat, 1 Dec 2018 21:23:54 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id EA1B474F1F for ; Sat, 1 Dec 2018 21:23:53 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.55.3]) by phk.freebsd.dk (Postfix) with ESMTP id 1335A1484E; Sat, 1 Dec 2018 21:23:46 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.15.2/8.15.2) with ESMTPS id wB1LNjRn012406 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Sat, 1 Dec 2018 21:23:45 GMT (envelope-from phk@critter.freebsd.dk) Received: (from phk@localhost) by critter.freebsd.dk (8.15.2/8.15.2/Submit) id wB1LNiW2012405; Sat, 1 Dec 2018 21:23:44 GMT (envelope-from phk) To: Warner Losh cc: ish@amail.plala.or.jp, "freebsd-hackers@freebsd.org" Subject: Re: How to use trim command ?,Re: How to use trim command ? In-reply-to: From: "Poul-Henning Kamp" References: <7e69211c-6ffb-6155-b17a-a845c0b3586d@grosbein.net> <20181201.093153.893601099798031027.ish@amail.plala.or.jp> <1c7139bd-258c-e7d2-2572-052da3803b3b@freebsd.org> <20181201.202332.546134930481017424.ish@amail.plala.or.jp> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <12403.1543699424.1@critter.freebsd.dk> Content-Transfer-Encoding: quoted-printable Date: Sat, 01 Dec 2018 21:23:44 +0000 Message-ID: <12404.1543699424@critter.freebsd.dk> X-Rspamd-Queue-Id: EA1B474F1F X-Spamd-Result: default: False [5.21 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; NEURAL_SPAM_SHORT(0.73)[0.731,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[freebsd.dk]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.94)[0.937,0]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[phk.freebsd.dk]; NEURAL_SPAM_LONG(0.96)[0.956,0]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[phk@phk.freebsd.dk,phk@critter.freebsd.dk]; RCVD_NO_TLS_LAST(0.10)[]; R_DKIM_NA(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:1835, ipnet:130.225.0.0/16, country:EU]; FROM_NEQ_ENVFROM(0.00)[phk@phk.freebsd.dk,phk@critter.freebsd.dk]; IP_SCORE(0.30)[asn: 1835(1.48), country: EU(0.00)] X-Rspamd-Server: mx1.freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Dec 2018 21:23:55 -0000 -------- In message , Warner Losh writes: >On Sat, Dec 1, 2018 at 4:41 AM Masachika ISHIZUKA >wrote: >> I think 'fsck_ffs -E' is not suitable for daily midnight cron job. > >FreeBSD doesn't have an equivalent of a daemon that runs and trims blocks >after a while of being idle (trimd on linux I think). Why would you run 'fsck_ffs -E' in cron anyway ? If the file-system is has TRIM enabled, it would be a no-op, unless there are bugs in the fs ? As for command name: bio_delete(8) would be my suggestion, but I'm biased= . -- = Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe = Never attribute to malice what can adequately be explained by incompetence= .