gmane.linux.file-systems.yaffs

Building Yaffs2 as a module for Raspbian Wheezy

Darragh Merrick — 2013-05-10T16:19:36

Hi,
     I'm working on a MSc Dissertation for Android forensics and I am
currently trying to extract a YAFFS2 image of the filesystem (mtd0 - mtd6)
from an Android device, load the image into Nandsim with nandwrite and
mount as a filesystem. I have successfully built a Vagrant -Virtualbox VM
with YAFFS2 module as per the video on the www.yaffs.net website.
1. I extract the mtd images from the device with Nandsim

2. Set up the mtdblock and Nandsim
   sudo modprobe mtdblock
   sudo modprobe nandsim first_id_byte=0x20 second_id_byte=0x71
cache_file=/tmp/nandsim.bin
   sudo modprobe yaffs2multi

   cat /proc/mtd
    dev:   size        erasesize       name mtd0:
         10000000 00004000 "NAND simulator partition 0"

3. Write the image into the mtdblock
   nandwrite -r -a /dev/mtdblock0  /media/yaffs/mtd3.img

4. Mount the image as a Yaffs2
    sudo mount -t yaffs2 /dev/mtdblock0 /mnt/yaffs2/

5. When I browse to /mnt/yaffs2/ there is only a folder 'lost & Found'

I get no errors during the mount or nandwrite?

New Yaffs driver model

Charles Manning — 2013-05-09T21:40:45

Hello All

It has been a long time coming, but Yaffs now has a new driver model.

The old drivers had to know all about tags and the twists in packing them.

The new driver model refactors all that. Tags handling has been pulled into a 
new layer (yaffs_tags_marshall.c) and the drivers just deal with transferring 
bytes to/from flash, erasing, and other low-level stuff.

These changes make it far easier to integrate Yaffs. There is no need to learn 
all those Yaffs-isms, 

Along with the new driver model, Yaffs Direct Interface (the RTOS/portable 
version of Yaffs) also has some new example drivers. These new drivers are 
real drivers that work with back-end flash simulators and should work with 
real hardware with only slight tweaks. That also makes it a lot easier to get 
Yaffs up and running on a new platform. There are example drivers for regular 
NAND, CFI-style NOR and Intel M18 ( a whacky NOR architecture that is part 
SLC and part MLC).


Regards

Charles

Re: Building yaffs2 as a module for Ubuntu 12.10 fails.

wingstrife — 2013-04-26T15:10:39

Hi yaffs-request 

Do you configure the mtd device driver in kernel config？
----- Receiving the following content ----- 

----------------------------------------------------------------------

Message: 1
Date: Thu, 10 Jan 2013 12:04:48 +0100
From: Jarl Friis <jarl< at >softace.dk>
To: yaffs< at >lists.aleph1.co.uk
Subject: [Yaffs] Building yaffs2 as a module for Ubuntu 12.10 fails.
Message-ID:
  <CAOjsGA1hZLDo8WoBUV4VCs1bfQy9gWMHDAKAsJSHywqBPdh68A< at >mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

This is what I have done:

git clone git://kernel.ubuntu.com/ubuntu/ubuntu-quantal.git
git clone git://www.aleph1.co.uk/yaffs2
cd ubuntu-quantal
git checkout -b 3.5.0-21.32-yaffs2 Ubuntu-3.5.0-21.32
cd ../yaffs2
./patch-ker.sh c m ../ubuntu-quantal/
cd ../ubuntu-quantal

Ensured that kernel configuration is OK, i.e. yaffs2 is configured as module

then `make`

At the end it spits out:
  CC [M] fs/yaffs2/yaffs_vfs.o
fs/yaffs2/yaffs_vfs.c:438:2: warning: initialization from incompat

Re: open erase blocks

Charles Manning — 2013-04-25T21:37:37

I am sorry I mislead you slightly. The checkpoint is written to different 
blocks.

I did once consider the idea of separating the object headers from the file 
data into different "streams" but this didn't seem to give any significant 
benefits and was not really worth doing.

What benefits can you see in using different blocks for  object headers and 
data?

On Friday 26 April 2013 09:22:15 Zavi wrote:
wrote:

Re: open erase blocks

Zavi — 2013-04-25T21:22:15

Is this a necessity? wouldn't it be better to have several "open"
blocks, used for various needs? say one for storing inodes and
checkpoints, another for storing data? maybe this is a bad example,
but I'm sute it's possible to think of a better one.

On Fri, Apr 26, 2013 at 12:11 AM, Charles Manning <cdhmanning< at >gmail.com> wrote:

Re: open erase blocks

Charles Manning — 2013-04-25T21:11:26

Yes

Yaffs2 is log structured which means it writes as a sequential log. That means 
it only writes sequentially to one block at a time. When that block is full 
it finds another block to write to.

The blocks that are written are not necessarily sequential, but writes within 
a block are.

Yaffs2 will generally fill a block before moving to another block, but there 
are some exceptions:
* If there is an error.
* On every remount it starts with a new block.

open erase blocks

Zavi — 2013-04-24T13:28:40

I've been reading on MLC flash lately, and saw that erase blocks must
be written sequentially. Does this mean that YAFFS2 manages a single
MLC chip so that there is only one "open" erase block used for writing
in every point in time? and only when it is filled can data be written
to an other erase block?

I have a strange problem ,have two file named "log" in one dir

Chenjie (K — 2013-03-04T09:06:57

the kernel is 2.6.34.9 ，and the yaffs2 version is 2012.12.12
when I use yaffs2

 ls
c00200434 obj->obj_id = 304 ,obj->short_name == pm
c00200434 obj->obj_id = 302 ,obj->short_name == per
c00200434 obj->obj_id = 299 ,obj->short_name == alm
c00200434 obj->obj_id = 289 ,obj->short_name == odu26
c00200434 obj->obj_id = 544 ,obj->short_name == odu25
c00200434 obj->obj_id = 543 ,obj->short_name == odu24
c00200434 obj->obj_id = 542 ,obj->short_name == odu23
c00200434 obj->obj_id = 541 ,obj->short_name == odu22
c00200434 obj->obj_id = 540 ,obj->short_name == odu21
c00200434 obj->obj_id = 536 ,obj->short_name == post
c00200434 obj->obj_id = 535 ,obj->short_name == errpick
c00200434 obj->obj_id = 534 ,obj->short_name == rp
c00200434 obj->obj_id = 533 ,obj->short_name == license
c00200434 obj->obj_id = 532 ,obj->short_name == patch
c00200434 obj->obj_id = 531 ,obj->short_name == sm
c00200434 obj->obj_id = 530 ,obj->short_name == mml
c00200434 obj->obj_id = 529 ,obj->short_name == pkg
c00200434 ob

I have a strange problem ,have two file named "log" in one dir

Chenjie (K — 2013-03-04T07:34:40

 ls
c00200434 obj->obj_id = 304 ,obj->short_name == pm
c00200434 obj->obj_id = 302 ,obj->short_name == per
c00200434 obj->obj_id = 299 ,obj->short_name == alm
c00200434 obj->obj_id = 289 ,obj->short_name == odu26
c00200434 obj->obj_id = 544 ,obj->short_name == odu25
c00200434 obj->obj_id = 543 ,obj->short_name == odu24
c00200434 obj->obj_id = 542 ,obj->short_name == odu23
c00200434 obj->obj_id = 541 ,obj->short_name == odu22
c00200434 obj->obj_id = 540 ,obj->short_name == odu21
c00200434 obj->obj_id = 536 ,obj->short_name == post
c00200434 obj->obj_id = 535 ,obj->short_name == errpick
c00200434 obj->obj_id = 534 ,obj->short_name == rp
c00200434 obj->obj_id = 533 ,obj->short_name == license
c00200434 obj->obj_id = 532 ,obj->short_name == patch
c00200434 obj->obj_id = 531 ,obj->short_name == sm
c00200434 obj->obj_id = 530 ,obj->short_name == mml
c00200434 obj->obj_id = 529 ,obj->short_name == pkg
c00200434 obj->obj_id = 528 ,obj->short_name == web
c00200434 obj->obj_id = 527 ,obj->short_name

[PATCH 2/2] mkyaffs2image: add support for inband tags anduser-defined page geometries

Angus CLARK — 2013-02-26T14:41:13

Signed-off-by: Angus Clark <angus.clark< at >st.com>
---
 utils/mkyaffs2image.c |  154 +++++++++++++++++++++++++++++++++++++-----------
 1 files changed, 118 insertions(+), 36 deletions(-)

diff --git a/utils/mkyaffs2image.c b/utils/mkyaffs2image.c
index b46f285..ddebcb6 100644
--- a/utils/mkyaffs2image.c
+++ b/utils/mkyaffs2image.c
< at >< at > -29,6 +29,7 < at >< at >
 #include <dirent.h>
 #include <string.h>
 #include <unistd.h>
+#include <getopt.h>
 #include <errno.h>
 #include <assert.h>
 #include "yaffs_ecc.h"
< at >< at > -40,12 +41,15 < at >< at > unsigned yaffs_trace_mask=0;
 
 #define MAX_OBJECTS 10000
 
-// Adjust these to match your NAND LAYOUT:
-#define chunkSize 2048
-#define spareSize 64
-#define pagesPerBlock 64
-
+#define inbandSize 16
 
+int pageSize = 2048;
+int spareSize = 64;
+int blockSize = 0x20000;
+int chunkSize;
+int pagesPerBlock;
+int inband_tags = 0;
+int no_pad = 0;
 
 typedef struct
 {
< at >< at > -207,14 +211,21 < at >< at > static int write_chunk(u8 *data, u32 id, u32 chunk_id, u32 n_bytes)
 
 nPages++;
 
-memset(&pt, 0, sizeof(pt));
-

[PATCH 1/2] yaffs linux: update yaffs_get_mtd_device() coderefactoring

Angus CLARK — 2013-02-26T14:41:12

Commit 78ce897e5d894acf9866ca504086961d7ac604aa "yaffs linux: Rationalise and
fix compilation for Linux 3.4 and 3.5" moved some of the MTD initialisation
checks from yaffs_vfs_multi.c:yaffs_internal_read_super() to a new function
yaffs_mtdif_multi.c:yaffs_get_mtd_device().  However, this function is not
actually called, with yaffs_internal_read_super() still using get_mtd_device().
As a result, the intialisation checks are no longer active.  Furthermore, the
new unused function, yaffs_get_mtd_device() calls itself recusively with no
termination condition; I suspect get_mtd_device() should be used here.

This patch updates the code to what I believe was probably originally intended
as part of the code refactoring.

Signed-off-by: Angus Clark <angus.clark< at >st.com>
---
 yaffs_mtdif_multi.c |    7 +++++--
 yaffs_vfs_multi.c   |    2 +-
 2 files changed, 6 insertions(+), 3 deletions(-)

diff --git a/yaffs_mtdif_multi.c b/yaffs_mtdif_multi.c
index 265dd78..5ea4673 100644
--- a/yaffs_mtdif_multi.c
+++ b/yaffs_mtdif_

Re: adding bad blocks back into a yaffs2 filesystem

Charles Manning — 2013-02-20T01:06:31


There are varied speed options:
Fastest: Use checkpointing
Next fastest: Scan using block summaries
Slowest: Scan without chunk summaries

A scan with summaries is generally only a touch slower than checkpointing but 
is very dependent on the hardware etc.

From something I posted 16th May 2011:
"On the weekend I set up an Overo board  (equivalent to a slower Beagleboard) 
with yaffs to get a datapoint for the block summary speed up. Flash speed was 
quite slow due to a slow mtd implementation.

I filled almost 250Mbytes with 1MB files and observed the following mount 
times:

Mount with full scan using no checkpoint or block summary info: 8.67 seconds
Mount with block summary: 1.02 seconds
Mount with checkpoint: 0.17 seconds"

Re: adding bad blocks back into a yaffs2 filesystem

Steven Hein — 2013-02-19T18:34:09

Thanks Charles!   Checkpointing was the issue.
If I mount with "no-checkpoint-read" after the erase, then my
FS is intact.

Other than longer mount times, is there any other down side to
using no-checkpoint-read?  Would you expect the non-checkpointed
mount delay to be significant for a 256MiB filesystem on a 2K block
NAND device (size 512MiB)?

Thanks, Steve

Re: adding bad blocks back into a yaffs2 filesystem

Charles Manning — 2013-02-18T22:34:43

Adding erased blocks to a yaffs partition should not cause any problems so 
long as you mount without the scheckpoint, thus forcing a rescan to find the 
erased blocks.

I suspect your procedure might not be working properly. Sometimes drivers will 
not erase a bad block.

Try changing the order:
unmount,
unmark then erase bad blocks.
check that the block really is erased
remount.

Re: Is it possible to format a USB as YAFFS2?

Peter Barada — 2013-02-17T03:58:48

USB memory sticks poperate with a IDE full block-managed flash 
underneath them that includes remapping of bad blocks and wear levelling.

YAFFS is built to deal with _raw_ NAND, including access to the per-page 
OOB (out of band) area that holds the meta-data for YAFFS, and is 
completely hidden/inaccessible on a USB memory stick.

it is inappropriate to try to format a USB memory stick as a YAFFS 
filesystem.  It isn't worth it when an EXT journaling filesystem is more 
than adequate on such a block device....

Is it possible to format a USB as YAFFS2?

S. K. — 2013-02-16T12:21:55

Hello!



Usually we can format a USB with "mkfs" command. this command can use to format a USB as ext2, ext3 , ... .
I think there is something similar for YAFFS like 'mkfs.yaffs2'. My guess is true and there is such a file but this executable file only convert a directory to image!

I can not understand why it is useful for formatt a USB!?

Is it possible to format a USB as YAFFS2 with that file? If not, What is the way to do that?

as I mentioned before, I searched a lot even in the YAFFS website But nothing found. It is a good time to explain about it for me and anyone with the same problem.



Thanks. _______________________________________________
yaffs mailing list
yaffs< at >lists.aleph1.co.uk
http://lists.aleph1.co.uk/cgi-bin/mailman/listinfo/yaffs

format a usb with yaffs2

S. K. — 2013-02-16T06:21:38


Hello!



I am going to format a 4GB SP USB with YAFFS2.

Can everyone help me please what i have to do?

I searched a lot to understanding how to do that but nothing found. Would you explain it step by step if it possible?



Thanks._______________________________________________
yaffs mailing list
yaffs< at >lists.aleph1.co.uk
http://lists.aleph1.co.uk/cgi-bin/mailman/listinfo/yaffs

adding bad blocks back into a yaffs2 filesystem

Steven Hein — 2013-02-15T22:30:43

I've had a situation where NAND blocks are being marked bad
invalidly due to a HW/driver issue, and I am trying to recover them.

I've patched the MTD code to allow bad block erase, and I've
the scrounged together a MEMSETGOODBLOCK ioctl patch to
allow bad blocks to be unmarked in the BBT.    All of this is working:
I can erase bad blocks (and verify that data and OOB are all 0xff's),
and I can unmark the blocks bad in the BBT.

When I have a YAFFS2 filesystem that has bad blocks, I use this
sequence to attempt to recover the blocks:

(1) unmount the filesystem
(2) erase the bad blocks
(3) unmark the blocks bad
(4) mount the filesystem

After this sequence, I have found that I have files in the
filesystem that are corrupted or missing, but they were
correct before I started the sequence.


Is this a valid sequence to use?   Are there other steps that I need?
Are there inherent issues with re-adding erased blocks back into
a yaffs2 filesystem?

Thanks, Steve

Re: single kernel variant compilation broken

Charles Manning — 2013-02-10T23:23:30

The  single version glue code has not yet been been brought up to date.

single kernel variant compilation broken

Yury — 2013-02-04T10:32:46

Hello,

Commit
6c0b1f629b813db703ceac9e35822380d7f73f1f
breaks kernel compilation.

put_super_fn removed from yaffs_linux_context, but it is still used in
yaffs_vfs_single.c

Thx,
Yury

Kernel panic - not syncing: No init found ARM linux 3.6.6

Gigin Jose — 2013-01-30T10:37:03



----- Forwarded Message -----
From: Gigin Jose <gigin_jose< at >yahoo.co.in>
To: Laurie van Someren <laurie< at >aleph1.co.uk> 
Sent: Wednesday, 30 January 2013 3:35 PM
Subject: Re: [Yaffs] Kernel panic - not syncing: No init found ARM linux 3.6.6
 

Dear Laurie, 

I am trying to put the YAFFS , with patch for linux 3.6.(http://www.gnu.org/licenses/gpl-2.0.html) into the linux 3.6.6 version. The compilation happens fine, but shows kernel panic error once put on board. 
The same YAFFS patch, with the same file system image works fine for linux 2.6.21 version. 


Here are the relevant serial port debug outputs from both the versions of linux

Linux 2.6.21
[    1.170000] S3C NAND Driver, (c) 2007 Samsung Electronics
[    1.175000] S3C NAND Driver is using hardware ECC.
[    1.175000] NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit)
[    1.180000] Creating 3 MTD partitions on "NAND 128MiB 3,3V 8-bit":
[    1.185000] 0x00000000-0x00040000 : "Bootloader"
[    1.195000] 0x0