As the book "OpenBSD Mastery Filesystems", Michael W Lucas, 2023 reads at the side cover:
“Many users assume that their advanced filesystem is better than UFS because they have so many features—snapshots, checksums, compression, sophisticated caching algorithms, and so on—while all UFS has ever done is muck about putting data on disk. But, conversely, UFS users believe their filesystem is better for exactly the same reasons.” —Hitchhikers Guide to OpenBSD And go on chapter 0: " OpenBSD includes many standard tools for disk management. Its Unix File System has been continuously used for decades and is both robust and well–understood. While it lacks features found in newer filesystems like ZFS and btrfs, the OpenBSD developers have never been seriously interested in file system features. A file system should put data on disk. That data should be safely stored and reliably read. That’s it. Error checking? Deduplication? No. The operating system has other tools for ensuring data integrity and compactness." on Chapt 1: " While many Unix-like operating systems dump everything onto the disk and hope things work out, OpenBSD uses a meticulous partitioning scheme to improve confidentiality, integrity, and availability. Additionally, OpenBSD’s multi–architecture design demands abstraction layers between the storage hardware and the user–visible file system. Taking a little time to understand these two systems and how they interact will greatly simplify your work as a system administrator." I am the type of guy that likes to hold the pages to read them, that is why i quote the book, but you could also look at the internet or in the papers https://www.openbsd.org/events.html, https://www.openbsd.org/papers/eurobsdcon2022-krw-blockstobooting.pdf i suggest you to read and investigate to understand the difference in the approach from: a) giving lots of choices you will never use or are poorly maintained or b) place the one that could be audited and maintained. Personally I have grown to see and love that from OpenBSD, the same happens in filesystems, as well as in bluetooth, docker, wine, and all the stuff that some could dessire at one point just because you are used to, but if you want to use OpenBSD, you should be ready to learn and enjoy the tools available, i think is similar to the people that install some Linux distro and just want to work with MS Office and Photoshop, use libreoffice and Gimp or don´t waste time, go back to Windows and be happy! I hope it helps you to clarify your concern. Manuel El mar, 5 sept 2023 a las 8:12, John Holland (<johnbholl...@icloud.com>) escribió: > I just had a kernel panic when reloading a firefox tab pointed at > facebook. After restarting, all the filesystems had errors but /home was > particularly bad and caused the boot to stop and prompt if I wanted to > enter a root shell. > > > I eventually got fsck to mark the /home filesystem clean but it found > >4000 lost files that it moved to lost&found. I am not so experienced > with this, running "file" on a few of them shows that they may be intact > files but they have numeric names now. > > > I've really been enjoying OpenBSD but I think it could really use a > journaled filesystem. I believe I have the correct options in fstab for > the best results: > > 1f08fbc2b303f0ef.k /home ffs rw,softdep,noatime,nodev,nosuid 1 2 > > > I was just thinking how much I was enjoying OpenBSD compared to some > others when this happened. > > > OpenZFS? License issues? Hammer? Anything? > > -- Lic. Manuel Solís Vázquez
