<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://kerneltrap.org"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>KernelTrap - LogFS</title>
 <link>http://kerneltrap.org/taxonomy/term/346/0</link>
 <description></description>
 <language>en-local</language>
<item>
 <title>LogFS, A Scalable Flash Filesystem</title>
 <link>http://kerneltrap.org/Linux/LogFS_A_Scalable_Flash_Filesystem</link>
 <description>&lt;div class=&quot;taxonomy-images&quot;&gt;&lt;a href=&quot;/news/linux&quot; class=&quot;taxonomy-image-links&quot;&gt;&lt;img src=&quot;http://kerneltrap.org/files/category_pictures/K-Linux.gif&quot; alt=&quot;Linux news&quot; title=&quot;Linux news&quot;  width=&quot;75&quot; height=&quot;75&quot; /&gt;&lt;/a&gt;&lt;/div&gt;&lt;!-- google_ad_section_start --&gt;&lt;p&gt;Jörn Engel posted the &lt;a href=&quot;http://kerneltrap.org/mailarchive/linux-kernel/2008/4/3/1341944&quot;&gt;sixth version&lt;/a&gt; of patches &lt;a href=&quot;http://kerneltrap.org/mailarchive/linux-kernel/2008/4/1/1341764&quot;&gt;introducing his new LogFS filesystem&lt;/a&gt; for flash devices to the Linux kernel.  He highlighted some areas of the code that need some more work, and cc&#039;d the appropriate people for further review.  Regarding LogFS itself, he noted that one of its big advantages compared to other solutions was improved mount time and reduced memory consumption compared to other solutions, &quot;&lt;i&gt;LogFS has an on-medium tree, fairly similar to Ext2 in structure, so mount times are O(1).&lt;/i&gt;&quot;  He went on to add that flash is becoming more and more common in standard PC hardware, explaining:&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;&quot;Flash behaves significantly different to hard disks.  In order to use flash, the current standard practice is to add an emulation layer and an old-fashioned hard disk filesystem.  As can be expected, this is eating up some of the benefits flash can offer over hard disks.  In principle it is possible to achieve better performance with a flash filesystem than with the current emulated approach.  In practice our current flash filesystems are not even near that theoretical goal.  LogFS in its current state is already closer.&quot;&lt;/p&gt;&lt;/blockquote&gt;
&lt;!-- google_ad_section_end --&gt;&lt;p&gt;&lt;a href=&quot;http://kerneltrap.org/Linux/LogFS_A_Scalable_Flash_Filesystem&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://kerneltrap.org/Linux/LogFS_A_Scalable_Flash_Filesystem#comments</comments>
 <category domain="http://kerneltrap.org/filesystem">filesystem</category>
 <category domain="http://kerneltrap.org/taxonomy/term/347">flash</category>
 <category domain="http://kerneltrap.org/taxonomy/term/345">Jörn Engel</category>
 <category domain="http://kerneltrap.org/Linux">Linux</category>
 <category domain="http://kerneltrap.org/taxonomy/term/346">LogFS</category>
 <category domain="http://kerneltrap.org/news/linux">Linux news</category>
 <pubDate>Mon, 07 Apr 2008 22:13:09 +0000</pubDate>
 <dc:creator>Jeremy</dc:creator>
 <guid isPermaLink="false">15934 at http://kerneltrap.org</guid>
</item>
<item>
 <title>Comparing UBIFS And LogFS</title>
 <link>http://kerneltrap.org/Linux/Comparing_UBIFS_And_LogFS</link>
 <description>&lt;div class=&quot;taxonomy-images&quot;&gt;&lt;a href=&quot;/news/linux&quot; class=&quot;taxonomy-image-links&quot;&gt;&lt;img src=&quot;http://kerneltrap.org/files/category_pictures/K-Linux.gif&quot; alt=&quot;Linux news&quot; title=&quot;Linux news&quot;  width=&quot;75&quot; height=&quot;75&quot; /&gt;&lt;/a&gt;&lt;/div&gt;&lt;!-- google_ad_section_start --&gt;&lt;p&gt;Following the recent announcement that UBIFS is &lt;a href=&quot;http://kerneltrap.org/Linux/UBI_File_System&quot;&gt;nearly production ready&lt;/a&gt;, it was asked how UBIFS compares to LogFS.  LogFS author &lt;a href=&quot;http://kerneltrap.org/mailarchive/linux-kernel/2008/3/31/1305624&quot;&gt;Jörn Engel suggested&lt;/a&gt;, &quot;&lt;i&gt;both share similar design goals.  Biggest difference is that ubifs works on top of ubi and depends on ubi support, while logfs works on plain mtd (or block devices) and does everything itself.  Code size difference is huge.  Ubi weighs some 11kloc, ubifs some 30, logfs some 8.&lt;/i&gt;&quot;  He continued:&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;&quot;Ubi scales linearly, as it does a large scan at init time.  It is still reasonably fast, as it reads just a few bytes worth of header per block. Logfs mounts in O(1) but will currently become mindbogglingly slow when the filesystem nears 100% full and write are purely random.  Not that any other flash filesystem would perform well under these conditions - it is the known worst case scenario.&quot;&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;Artem Bityutskiy replied, &quot;&lt;i&gt;I personally refuse to compare a finished FS with handles all the crucial flash features to a non-finished FS. It just makes no sense.  LogFS was talked about back 2005 in Linux Kongress, but is not finished yet. Let&#039;s talk about it when it is production ready.&lt;/i&gt;&quot;&lt;/p&gt;
&lt;!-- google_ad_section_end --&gt;&lt;p&gt;&lt;a href=&quot;http://kerneltrap.org/Linux/Comparing_UBIFS_And_LogFS&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://kerneltrap.org/Linux/Comparing_UBIFS_And_LogFS#comments</comments>
 <category domain="http://kerneltrap.org/taxonomy/term/1018">Artem Bityutskiy</category>
 <category domain="http://kerneltrap.org/taxonomy/term/347">flash</category>
 <category domain="http://kerneltrap.org/taxonomy/term/345">Jörn Engel</category>
 <category domain="http://kerneltrap.org/Linux">Linux</category>
 <category domain="http://kerneltrap.org/taxonomy/term/346">LogFS</category>
 <category domain="http://kerneltrap.org/taxonomy/term/1016">UBIFS</category>
 <category domain="http://kerneltrap.org/news/linux">Linux news</category>
 <pubDate>Mon, 31 Mar 2008 15:00:26 +0000</pubDate>
 <dc:creator>Jeremy</dc:creator>
 <guid isPermaLink="false">15889 at http://kerneltrap.org</guid>
</item>
<item>
 <title>Linux:  LogFS, A New Flash Filesystem</title>
 <link>http://kerneltrap.org/node/8159</link>
 <description>&lt;div class=&quot;taxonomy-images&quot;&gt;&lt;a href=&quot;/news/linux&quot; class=&quot;taxonomy-image-links&quot;&gt;&lt;img src=&quot;http://kerneltrap.org/files/category_pictures/K-Linux.gif&quot; alt=&quot;Linux news&quot; title=&quot;Linux news&quot;  width=&quot;75&quot; height=&quot;75&quot; /&gt;&lt;/a&gt;&lt;/div&gt;&lt;!-- google_ad_section_start --&gt;&lt;p&gt;Jörn Engel announced &lt;a href=&quot;http://logfs.org/logfs/&quot;&gt;LogFS&lt;/a&gt;, &quot;&lt;i&gt;a scalable flash filesystem.&lt;/i&gt;&quot;  The project&#039;s home page notes that LogFS aims to be the successor of JFFS2, &quot;&lt;i&gt;the two main problems of JFFS2 are memory consumption and mount time. Unlike most filesystems, there is no tree structure of any sorts on the medium, so the complete medium needs to be scanned at mount time and a tree structure kept in-memory while the filesystem is mounted. With bigger devices, both mount time and memory consumption increase linearly.  JFFS2 has recently gained summary support, which helps reduce mount time by a constant factor.  Linear scalability remains.  YAFFS also appears to be better by a constant factor, yet still scales linearly.&lt;/i&gt;&quot;&lt;/p&gt;
&lt;p&gt;In contrast, Jörn compared his new LogFS, &quot;&lt;i&gt;LogFS has an on-medium tree, fairly similar to Ext2 in structure, so mount times are O(1).  In absolute terms, the OLPC system has mount times of ~3.3s for JFFS2 and ~60ms for LogFS.&lt;/i&gt;&quot;  Regarding its stability, he noted, &quot;&lt;i&gt;LogFS works and survives my testcases.  It has fairly good chances of not eating your data during regular operation.  There are still two known bugs that will eat data if the filesystem is uncleanly unmounted.  Also still missing is wear leveling.&lt;/i&gt;&quot;  Thomas Gleixner reviewed the code and offered the following summary, suggesting the code has a ways to go before it replaces JFFS2, &