Talk:JFFS2

Computing Low‑importance

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles
Low	This article has been rated as Low-importance on the project's importance scale.

VfD Result[edit]

This article was nominated for deletion on June 4, 2005; the consensus was keep. For discussion, please see Wikipedia:Votes for deletion/JFFS2.

Truncation and holes[edit]

According to http://sources.redhat.com/jffs2/jffs2-html/node3.html#SECTION00037000000000000000 truncation and holes are supported. Is this correct?

You're right: the hole itself appears to be logged as a special kind of node. My mistake, and thank you for pointing that out. —Ghakko 14:39, 22 July 2005 (UTC)[reply]

Negative compression rates[edit]

Mostly with too small data size (headers take space) and precompressed data (zip, mp3). I think that's a known issue with all compression methods, and doesn't actually qualify as a "Disadvantage of jffs2". More like an optimization note. - Tazpa 19:24, 3 September 2007 (UTC)[reply]

NAND access . . .[edit]

On NAND access, having direct Sequential I/O support in the filesystem isn't necessary for using it, but it removes additional software layers.

Namely to access a NAND device using memory mapping (such as if you have to access by a software block device), you need to add an additional software layer to transfer the serial I/O through RAM buffers to create a virtual layer of memory mappability. This slows down access, and makes it much more difficult to access features of the flash chip. This is particularly troublesome on microprocessors that don't have routine call based virtual memory features in their MMU subsystem to map memory sector addresses to program routines.

Is there a way to rephrase the article to better describe this limitation of using memory-mapping dependent file systems running on NAND devices. I think using the word "directly" might fit, but it might somehow get misinterpreted. — Preceding unsigned comment added by RuediiX (talk • contribs) 01:36, 28 October 2012 (UTC)[reply]

External links modified[edit]

Hello fellow Wikipedians,

I have just modified one external link on JFFS2. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

Added archive https://web.archive.org/web/20140307004309/http://www.micron.com/~/media/Documents/Products/Software%20Article/SWNL_jffs2_profile.pdf to http://www.micron.com/~/media/Documents/Products/Software%20Article/SWNL_jffs2_profile.pdf

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 18 January 2022).

If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot (Report bug) 02:36, 2 January 2018 (UTC)[reply]