Linked by Amjith Ramanujam on Fri 1st Aug 2008 15:32 UTC, submitted by Daniel Sieger
Today, support for metadata journaling has been added to NetBSD's implementation of the Berkeley Fast File System (FFS), eliminating the need for lengthy file system checks after a crash or power failure. Support for converting existing file systems to use the new journaling capabilities is provided as well. See the official announcement
for all the details.
Thread beginning with comment 325298
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Member since:2005-07-24
My understanding has been that soft-updates was a fairly complex feature to implement. More so than journaling. It may very well be that the maintenance overhead outweighed any possible technical advantages it may have had. The BSDs have always been a bit out in right field, in my opinion, on this issue.
Member since:2008-08-01
Member since:2005-07-24
The default is neither logging nor softdep. The NetBSD installer sysinst will let you enable one or the other, or you can enable it after the fact by editing /etc/fstab.
There should be a default. Quivering in limbo is not proper installer behavior.
Edited 2008-08-02 02:17 UTC
Member since:
2005-07-06
The whole debate of soft updates vs journaling, and the bragging of BSD dudes about soft updates being superior, is now enlightened with a whole new light.
Of course, I applaud NetBSD and Wasibi for offering this, and it's a Good Thing that the user can /choose/ between soft updates and journaling.
But what will be the default? Journaling or soft updates? And if it will be journaling, are the fs devs who advised journaling still to be taken serious?