All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Karev <lineum@mail.ru>
To: linux-mtd@lists.infradead.org
Subject: jffs2 and nand mtd
Date: Thu, 11 Aug 2005 11:31:21 +0400	[thread overview]
Message-ID: <42FAFEC9.1090306@mail.ru> (raw)

Hello

While we mount empty jffs2 and then copying  files it's ok, after 
remount/reboot. the files have zero gaps ~2kb at some (stable?) 
locations, and filesytem is broken that way.
install procedure following:

#flash_eraseall -j /dev/mtd0
#mount -t jffs2 /dev/mtdblock0 /mnt
#cp ...
    at this stage files looks ok.
#umount
#mount
    zero gaps appear in data on flash and lot of debug info with some 
Eeps, sometimes kernel panic.


Also we try to use mkfs.jffs2, same result.

#mkfs.jffs2 -e 0x4000 -l -n ....     or #mkfs.jffs2 -e 0x4000 -p -l -n 
.... with different variations.

#flash_eraseall -j /dev/mtd0
#nandwrite -j /dev/mtd0 root_fs.jffs2
#mount ...
#umount ...
#mount ...
... usually have debug output, sometimes kernel panic.

Hardware:
ST VEGA PC.
General SW BIOS with extension.
SAMSUNG NAND K9F2808U0C. ports: 0x300 data, 0x301 cmd; erase block 16Kb 
according documentation. no ecc 16Mb

Software:
Our NAND driver implementation, derived from edb7312.c
2 partition
Linux kernel 2.4.29 with patch from mtd c vs.

             reply	other threads:[~2005-08-11  7:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-11  7:31 Alex Karev [this message]
2005-08-11  7:39 ` jffs2 and nand mtd Artem B. Bityuckiy
2005-08-11  8:07   ` Alex Karev
2005-08-11  8:29     ` Artem B. Bityuckiy
2005-08-11  8:32       ` Artem B. Bityuckiy
2005-08-11  8:35       ` Thomas Gleixner
2005-08-11  9:58         ` Alex Karev
2005-08-11  9:42       ` Martin Egholm Nielsen
2005-08-11 14:42         ` Gianluca
2005-08-11 15:20           ` Thomas Gleixner
2005-08-11  8:33 ` David Woodhouse

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42FAFEC9.1090306@mail.ru \
    --to=lineum@mail.ru \
    --cc=linux-mtd@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.