mtd/fs/jffs3 JFFS3design.tex,1.1,1.2

Artem Bityuckiy dedekind at
Sat Jan 22 09:04:46 EST 2005

Update of /home/cvs/mtd/fs/jffs3
In directory

Modified Files:
Log Message:
Few updates.

Index: JFFS3design.tex
RCS file: /home/cvs/mtd/fs/jffs3/JFFS3design.tex,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- JFFS3design.tex	21 Jan 2005 20:15:06 -0000	1.1
+++ JFFS3design.tex	22 Jan 2005 14:04:43 -0000	1.2
@@ -31,7 +31,7 @@
 TODO: insert GNU's one
@@ -40,7 +40,7 @@
-\large \textbf{Term}
+\large \textbf{Abbrev.}
 \large \textbf{Definition}
@@ -73,6 +73,16 @@
 \large \textbf{Definition}
+\raggedright \emph{Block, Sector} 
+The minimal flash erasable unit. \\[4pt]
+\raggedright \emph{Eblock}
+JFFS3 may treat several sectors as one eblock. Thus, the minimal
+erasable flash unit from the JFFS3's viewpoint is eblock which consists
+of one or more flash blocks. \\[4pt]
 \raggedright \emph{Node} 
 Basic JFFS3 data structure - anything which JFFS3 stores on flash is
@@ -148,6 +158,17 @@
+\subsubsection*{JFFS2 correspondence}
+JFFS2 uses checksums to detect errors caused by unclean reboots (unclean
+reboot may happen any time and partially written nodes may
+appear on the flash). JFFS2 treats any checksum error as an error caused by
+unclean reboots and have no general ability to distinguish between
+checksum errors due to physical flash corruptiona and due to unclean
+In general, in JFFS3 checksum is not intended to detect errors cased by unclean
+reboots. There is another mechanism exists for this purpose. 
 \subsection{Checksum modes}
 Two JFFS3 working modes are defined:

More information about the linux-mtd-cvs mailing list