From owner-freebsd-hackers@freebsd.org Sat Dec 1 22:24:31 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 900891329EBA for ; Sat, 1 Dec 2018 22:24:31 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: from mail-wm1-x32d.google.com (mail-wm1-x32d.google.com [IPv6:2a00:1450:4864:20::32d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E6903770EC for ; Sat, 1 Dec 2018 22:24:29 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: by mail-wm1-x32d.google.com with SMTP id y1so2260427wmi.3 for ; Sat, 01 Dec 2018 14:24:29 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=Zv05fszc1bOSJehQd7Raa1LwS4DzKqQbyY7EKR08faU=; b=K5s+4QsaqoGNrT+p6YQ4Ae4APc160ZvHgiHlzr2WmEeXTZHK+w+nAqNL6P+O/ZHSd9 ySwoR+d7FWGjZmo2MQ9iB+/7ficLm+mZasemRvMwjPXynnj1YuFxmL1+Ih4QHqbFPwnC Z2BpL7ro9Np4JeM2TasXZ337LD1BFZzDjza8k0pOjf3ZTbfW6L78HdwtLwm4NqyBiHQp i3ttpfJLic8P2pMPXy3r4x7bZcK6Tdez2v3Nbr69PFSvSmRepvcpgGhr3soMrPquzqot 8CFJ7URYuogrX4KTLgEQmya4bmxXw/a+vu+C6Hi6SdbHH3gYiDIInhyN/Ue1UqUI1TqZ St/w== X-Gm-Message-State: AA+aEWYJoJFGZpzIDY3A7GmwBazcUnkQ73nqQKn3UTSdl36eaUQ8SCvt mTDeN5aPQvs75hkeM8uLapfSLuopQJw= X-Google-Smtp-Source: AFSGD/WEvF9R9SQ86mU3pjY7HhvTSSql5sjjrubY1MM3Nl0F18GFSD7WmuNfqGnGu1zz34w1TdZxzg== X-Received: by 2002:a1c:e90d:: with SMTP id q13mr3497713wmc.106.1543703068561; Sat, 01 Dec 2018 14:24:28 -0800 (PST) Received: from gumby.homeunix.com ([2.121.229.87]) by smtp.gmail.com with ESMTPSA id t70sm2612964wmd.36.2018.12.01.14.24.27 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sat, 01 Dec 2018 14:24:27 -0800 (PST) Date: Sat, 1 Dec 2018 22:24:24 +0000 From: RW To: freebsd-hackers@freebsd.org Subject: Re: How to use trim command ?,Re: How to use trim command ? Message-ID: <20181201222424.0ae8abfd@gumby.homeunix.com> In-Reply-To: <12404.1543699424@critter.freebsd.dk> 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> <12404.1543699424@critter.freebsd.dk> X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; amd64-portbld-freebsd11.1) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: E6903770EC X-Spamd-Result: default: False [-3.34 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; FREEMAIL_FROM(0.00)[googlemail.com]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[googlemail.com:+]; DMARC_POLICY_ALLOW(-0.50)[googlemail.com,quarantine]; MX_GOOD(-0.01)[alt3.gmail-smtp-in.l.google.com,alt4.gmail-smtp-in.l.google.com,gmail-smtp-in.l.google.com,alt2.gmail-smtp-in.l.google.com,alt1.gmail-smtp-in.l.google.com]; NEURAL_HAM_SHORT(-0.77)[-0.769,0]; RECEIVED_SPAMHAUS_PBL(0.00)[87.229.121.2.zen.spamhaus.org : 127.0.0.10]; IP_SCORE(-0.56)[ipnet: 2a00:1450::/32(-1.42), asn: 15169(-1.30), country: US(-0.09)]; SUBJECT_ENDS_QUESTION(1.00)[]; FREEMAIL_ENVFROM(0.00)[googlemail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; FROM_EQ_ENVFROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[googlemail.com]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; RCVD_TLS_LAST(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[d.2.3.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0] 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 22:24:31 -0000 On Sat, 01 Dec 2018 21:23:44 +0000 Poul-Henning Kamp wrote: > 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 ? There's a school of thought that trimming in real-time, after file deletion, slows down I/O on the device. Some people advocate turning-off trim support in the file-system and trimming all the unused space in one go from cron when the system is likely to be idle. I don't know whether there's any truth in it. It sounds unlikely with modern drives.