Best BSD filesystem for ssd reddit / BSD ---------------------------------------------------------------------- renshencha · 2019-01-10 00:39 So I'm quite new to BSD and thinking about installing some flavor of it on a laptop with an SSD. Which file system should I use? ---------------------------------------------------------------------- gjs278 · 2019-01-10 00:47 well it depends which one you pick. if you picked dragonflybsd, you'd be using hammer2. if you picked freebsd, you'd be using zfs. the others, probably some form of ufs. ---------------------------------------------------------------------- 7YdszFAv · 2019-01-10 02:36 You need to pick a BSD first. ---------------------------------------------------------------------- 3MuchCaffeine5Me · 2019-01-10 02:36 Theoretically, you'll get the most drive life out of a non-journaling filesystem, at the expense data corruption on unexpected power outages. ---------------------------------------------------------------------- BumpitySnook · 2019-01-10 03:21 All the filesystems work fine on SSDs; pick a filesystem on its merits for your use. As others have said, choice of BSD will govern options. ---------------------------------------------------------------------- Darth_Ender_Ro · 2019-01-10 06:35 Zfs ---------------------------------------------------------------------- shabty · 2019-01-10 09:38 I am surprised no one has mentioned HAMMER2. It is the only BSD filesystem designed from the ground up to be especially performant with today's solid state disks. Extreme performance is possible using NVMEs in particular with DragonFlyBSDs custom driver. ​ [https://gitweb.dragonflybsd.org/dragonfly.git/commitdiff/04b8e8398279 26484acf1fe15b10ba9401e83885](https://gitweb.dragonflybsd.org/dragonfl y.git/commitdiff/04b8e839827926484acf1fe15b10ba9401e83885) [https://gitweb.dragonflybsd.org/dragonfly.git/commitdiff/049f03b76415 d7669e26b8272f00b6b4c9b22d59](https://gitweb.dragonflybsd.org/dragonfl y.git/commitdiff/049f03b76415d7669e26b8272f00b6b4c9b22d59) [https://gitweb.dragonflybsd.org/dragonfly.git/commitdiff/9942a85186eb 01e7d377406f3f6c91aba66a35ac](https://gitweb.dragonflybsd.org/dragonfl y.git/commitdiff/9942a85186eb01e7d377406f3f6c91aba66a35ac) [http://apollo.backplane.com/DFlyMisc/nvme\_randread.txt](http://apoll o.backplane.com/DFlyMisc/nvme_randread.txt) ---------------------------------------------------------------------- Xenepa · 2019-01-10 09:50 That is really stupid misconception right now. There is no drive life to be worried about. Write endurance tests were made, worst case drive failed after ~1 PB written to it. If you write 50 GB a day, it will take **54 YEARS** to reach that number. If you're unlucky. It's far more likely you lose data on non-journaled FS within those 54 years. ---------------------------------------------------------------------- crest_ · 2019-01-10 11:53 Some of my servers write 50GB/s per minute. ---------------------------------------------------------------------- FUZxxl · 2019-01-10 12:06 All of them should do just fine. ---------------------------------------------------------------------- raevnos · 2019-01-10 12:15 It was mentioned in one of the first comments... ---------------------------------------------------------------------- RonaldoNazario · 2019-01-10 12:52 Obvious per second per minute joke aside.... To a single drive? Nonstop? I’m not sure many SSDs could even ingest ~800MB/s... ---------------------------------------------------------------------- crest_ · 2019-01-10 13:10 To a ZFS pool. The pools consists of four Optane 905P ZIL devices (two way mirrors) and 44 mirrored disks (two way mirrors) as well as a hot spare disk. Each ZIL device can sustain at least 800MB/s with <0.2ms latency. The system is a NFSv3 server so it has to deal with lots of sync writes. ---------------------------------------------------------------------- RonaldoNazario · 2019-01-10 15:21 That makes sense but you were responding to someone talking about write rate and endurance of a single drive. ---------------------------------------------------------------------- marmulak · 2019-01-10 17:29 I'm not like an expert on this topic, but I would likely have chosen UFS2 with soft update and journaling disabled. (I normally use FreeBSD.) ZFS and HAMMER might be overkill for what you may be using it for. ---------------------------------------------------------------------- marmulak · 2019-01-10 17:29 > at the expense data corruption on unexpected power outages. Soft updates. ---------------------------------------------------------------------- rhavenn · 2019-01-10 18:29 ...which has nothing to do with running a single disk on a laptop. I doubt a laptop could even handle that much I/O on its pci lanes. ---------------------------------------------------------------------- qci · 2019-01-10 19:49 I would choose filesystems that support TRIM. ---------------------------------------------------------------------- fupjack · 2019-01-11 22:06 In BSDland, there are no bad filesystem choices. ---------------------------------------------------------------------- alaindevos · 2019-01-18 02:49 Why disable soft updates. Why disable journaling ---------------------------------------------------------------------- marmulak · 2019-01-18 07:24 I think I worded that wrong... I wanted to say [with soft updates] and [journaling disabled], because soft updates are awesome and supposedly journaling is not always desirable on a solid state drive, but I read some of the other comments and they seem to suggest that SSD's can handle journaling well now.