LogFS - Revision history

Tim Bird at 19:21, 12 October 2012

2012-10-12T19:21:33Z

Tim Bird at 18:54, 12 October 2012

2012-10-12T18:54:59Z

Tim Bird at 18:49, 12 October 2012

2012-10-12T18:49:49Z

Tim Bird: Created page with "*[http://logfs.org/logfs/ logfs] - LogFS is a scalable flash filesystem. It is aimed to replace JFFS2 for most uses, but focuses more on the large devices. Matt Mackall writes (..."

2012-10-12T18:37:22Z

Created page with "*[http://logfs.org/logfs/ logfs] - LogFS is a scalable flash filesystem. It is aimed to replace JFFS2 for most uses, but focuses more on the large devices. Matt Mackall writes (..."

New page

*[http://logfs.org/logfs/ logfs] - LogFS is a scalable flash filesystem. It is aimed to replace
JFFS2 for most uses, but focuses more on the large devices.

Matt Mackall writes (in July of 2007):

LogFS is a filesystem designed to support large volumes on FLASH. It
uses a simple copy-on-write update process to ensure consistency (the
"log" in the name is a historical artifact). It's easily the most
modern and scalable open-source FLASH filesystem available for Linux
and it's well on its way to being accepted in the mainline tree.

Scott Preece writes:

The big win for LogFS (in my limited knowledge of it) is that it stores
its tree structure in the media, rather than building it in memory at
mount time. This significantly reduces both startup time and memory
consumption. This becomes more important as the size of the flash device
increases. Read more in LWN (http://lwn.net/Articles/234441) and
linux.com (http://www.linux.com/articles/114295).

Some newer flash memory, like MLC (multi-level cell), are not well supported.

LogFS now has its own mailing list: see http://logfs.org/cgi-bin/mailman/listinfo/logfs

@@ Line 16: / Line 16: @@
 It appears to be less-used than other flash filesystems, and in some testing
 was not robust enough to complete testing.
 == Resources ==

@@ Line 1: / Line 1: @@
-LogFS was a raw flash filesystem, intended to replace JFFS2, with a focus
+LogFS is a raw flash filesystem, intended to replace JFFS2, with a focus
 on scalability.
@@ Line 10: / Line 10: @@
   and it's well on its way to being accepted in the mainline tree.
-It was originally written by Joern Engel, but has recently (as of October, 2012) been
+It was originally written by Joern Engel, but has recently (up to October, 2012) been
 maintained by Prasad Joshi.
-It appears to be less-used than other flash filesystems.
+LogFS was mainlined in kernel version 2.6.34 (in November 2009).
 == Resources ==

@@ Line 1: / Line 1: @@
-*[http://logfs.org/logfs/ logfs] - LogFS is a scalable flash filesystem. It is aimed to replace
+LogFS was a raw flash filesystem, intended to replace JFFS2, with a focus
-JFFS2 for most uses, but focuses more on the large devices.
+on scalability.
-Matt Mackall writes (in July of 2007):
+In July of 2007, Matt Mackall wrote:
   LogFS is a filesystem designed to support large volumes on FLASH. It
@@ Line 10: / Line 10: @@
   and it's well on its way to being accepted in the mainline tree.
-Scott Preece writes:
+It was originally written by Joern Engel, but has recently (as of October, 2012) been
   The big win for LogFS (in my limited knowledge of it) is that it stores
@@ Line 16: / Line 29: @@
   mount time. This significantly reduces both startup time and memory
   consumption. This becomes more important as the size of the flash device
-  increases. Read more in LWN (http://lwn.net/Articles/234441) and
+  increases.
- linux.com (http://www.linux.com/articles/114295).
 Some newer flash memory, like MLC (multi-level cell), are not well supported.