Date: Sat, 01 Dec 2018 22:40:42 +0000 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: RW <rwmaillists@googlemail.com>, RW via freebsd-hackers <freebsd-hackers@freebsd.org> Subject: Re: How to use trim command ?,Re: How to use trim command ? Message-ID: <1177.1543704042@critter.freebsd.dk> In-Reply-To: <20181201222424.0ae8abfd@gumby.homeunix.com> 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> <20181201222424.0ae8abfd@gumby.homeunix.com>
next in thread | previous in thread | raw e-mail | index | archive | help
-------- In message <20181201222424.0ae8abfd@gumby.homeunix.com>, RW via freebsd-ha= ckers writes: >On Sat, 01 Dec 2018 21:23:44 +0000 >> 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. I suspect people would have reached that conclusion back when various shady outfits started selling camera-grade FAL devices in 2.5" form-factor. My advice would be to avoid any device where that pattern is observed, because that means there is too few write buffers and paths. -- = 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= .
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1177.1543704042>