Journaled Soft-Updates, Dr. Kirk McKusick, BSDCan 2010 reddit / BSD ---------------------------------------------------------------------- [deleted] · 2012-02-20 15:58 [deleted] ---------------------------------------------------------------------- [deleted] · 2012-02-21 08:40 [deleted] ---------------------------------------------------------------------- [deleted] · 2012-02-21 08:45 [deleted] ---------------------------------------------------------------------- [deleted] · 2012-02-21 08:53 McKusick is of course the real deal. He designed the original BSD FFS filesystem (in around 1979). That FS has really stood the test of time as the design is still the basis of the current FreeBSD UFS2 filesystem, which he's still engaged with developing. I had the pleasure of having lunch with him at a BSD conference a few years back and can report that he's also a very nice guy. There were a couple of comments that he made in this talk which I didn't quite get though. One was about the suitability of ZFS vs UFS for use with Flash SSD drives. He seemed to say that copy-on-write systems like ZFS are inherently better behaved on Flash SSDs because they don't depend on rewriting the same hotspot blocks (such as superblocks) many times -- an operation which would be expected to cause failure on a Flash SSD as it has a physical limit on the number of times a block can be rewritten. Most SSDs now have an indirection between physical blocks and logical blocks in order to allow a [wear- leveling](http://en.wikipedia.org/wiki/Wear_leveling) algorithm to execute on the controller which prevents the same blocks from being rewritten too frequently. I would think this would cancel the copy-on- write benefit and make UFS just as suitable for use on those types of device. He didn't seem to be aware of that. The other odd comment was in answer to a question about the suitability of journaled softupdate filesystems for use with a database, to which he replied that putting a database on top of a filesystem didn't make much sense. That seems an odd position to take. Of course one can see that for maximum performance it is better to give the DB a raw disk to manage, but I don't think that's a common configuration. Typically its more convenient and flexible to put the DB cluster somewhere on an existing filesystem. It must surely be the case that the number of installations where the DB accesses the disk through the FS greatly outnumbers those where the DB gets a dedicated volume. A more relevant answer to that question would then seem to be that the benefits for a DB server of journaling softupdates are the same as for any server -- i.e. you get a quick return to full performance after a crash.