Date: Sat, 1 Dec 2018 22:24:24 +0000 From: RW <rwmaillists@googlemail.com> 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> <CANCZdfqsVo_mk4TqJy8pmp%2BDQvDSg-cgwxM03%2BxgT5_Y%2BVKvnA@mail.gmail.com> <12404.1543699424@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20181201222424.0ae8abfd>