Re: Custom partition layout corrupts install ? +MFS question
Sylvain Saboua <[email protected]>
| Newsgroups | gmane.os.openbsd.misc |
|---|---|
| Message-ID | <[email protected]> |
On 2026-08-12 17:30, Brian Conway wrote: >> One thing that might be causing disturbances is that I want >> to put /var and /tmp on MFS, because it is said that constant >> effort put on an SSD disk might corrupt it faster. This is >> actually a question in its own right that I should ask as well: >> Is it a better practice with today's system and materials to >> put /var, /tmp and maybe others on virtual memory instead of >> disk ? Especially for a server that might run 24/7 ? > > I can't speak to the errors you're getting (because I don't think you > included them?), That's right, I haven't included the errors since this would have required me to film my screen and upload a video. (And even with that, I didn't run into the same errors once I re-installed with the default partitionning anyway). From my (somewhat) extensive research I believe the failure is actually due to an oversized root partition, that apparently corrupts the heap memory of the bootloader. I'll try a custom layout again formatting a < 8GB root partition. > but given that the SSD you're using is a Samsung SSD 870 and not > something generic/noname/garbage, I would not put the effort into > moving paritions onto mfs in an attempt to protect disk writes. And I > say that as someone that enjoys slinging around mfs mounts. Really, even for a 24/7 server ? I might do that then, as it reduces the hassle. -- Sylvain Saboua looking for a PDP-11