All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonas Dietsche <maillist@fsforth.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] jffs2 view u-boot/linux
Date: Wed, 01 Jun 2005 17:13:01 +0200	[thread overview]
Message-ID: <429DD07D.1080305@fsforth.de> (raw)
In-Reply-To: <429AFC63.2070205@fsforth.de>

Hi,

I created a 1MB partition to speed up the testing.
Maybe someone can do the same tests and tell me if he sees the same 
results...

* under linux I erased the partition with
	flash_eraseall -j /dev/mtd/2
* then I mounted it with
	mount -t jffs2 /dev/mtdblock/2 /mnt
* and created a file on the partition
	cd /mnt/
	echo test >testfile
* reboot linux
* under u-boot I did a ls and got the following (DEBUG_DIRENT and 
DEBUG_FRAGMENTS in jffs2_1pass.c are enabled)
Scanning JFFS2 FS: . done.


******The directory Entries******

testfile
         build_list: magic =  00001985
         build_list: nodetype =  0000e001
         build_list: hdr_crc =  fa3ebe78
         build_list: pino =  00000001
         build_list: version =  00000001
         build_list: ino =  00000002
         build_list: mctime =  00000074
         build_list: nsize =  00000008
         build_list: type =  00000008
         build_list: node_crc =  c489d275
         build_list: name_crc =  ddab2c44
         build_list: offset =  004f8044


******The fragment Entries******

         build_list: FLASH_OFFSET =  004f8000
         build_list: totlen =  00000044
         build_list: inode =  00000002
         build_list: version =  00000001
         build_list: isize =  00000000
         build_list: atime =  00000074
         build_list: offset =  00000000
         build_list: csize =  00000000
         build_list: dsize =  00000000
         build_list: compr =  00000000
         build_list: usercompr =  00000000
         build_list: flags =  00000000
         build_list: offset =  004f8000

         build_list: FLASH_OFFSET =  004f8074
         build_list: totlen =  00000049
         build_list: inode =  00000002
         build_list: version =  00000002
         build_list: isize =  00000005
         build_list: atime =  00000074
         build_list: offset =  00000000
         build_list: csize =  00000005
         build_list: dsize =  00000005
         build_list: compr =  00000000
         build_list: usercompr =  00000000
         build_list: flags =  00000000
         build_list: offset =  004f8074
  -rw-r--r--        5 Thu Jan 01 00:01:56 1970 testfile

* then I booted linux, mounted the jffs2 partition, deleted the file and 
rebooted
* ls in u-boot displays
Scanning JFFS2 FS: . done.


******The directory Entries******

testfile
         build_list: magic =  00001985
         build_list: nodetype =  0000e001
         build_list: hdr_crc =  fa3ebe78
         build_list: pino =  00000001
         build_list: version =  00000001
         build_list: ino =  00000002
         build_list: mctime =  00000074
         build_list: nsize =  00000008
         build_list: type =  00000008
         build_list: node_crc =  c489d275
         build_list: name_crc =  ddab2c44
         build_list: offset =  004f8044

testfile
         build_list: magic =  00001985
         build_list: nodetype =  0000e001
         build_list: hdr_crc =  fa3ebe78
         build_list: pino =  00000001
         build_list: version =  00000002
         build_list: ino =  00000000
         build_list: mctime =  00000023
         build_list: nsize =  00000008
         build_list: type =  00000000
         build_list: node_crc =  508a537f
         build_list: name_crc =  ddab2c44
         build_list: offset =  004f8200


******The fragment Entries******

         build_list: FLASH_OFFSET =  004f8000
         build_list: totlen =  00000044
         build_list: inode =  00000002
         build_list: version =  00000001
         build_list: isize =  00000000
         build_list: atime =  00000074
         build_list: offset =  00000000
         build_list: csize =  00000000
         build_list: dsize =  00000000
         build_list: compr =  00000000
         build_list: usercompr =  00000000
         build_list: flags =  00000000
         build_list: offset =  004f8000

         build_list: FLASH_OFFSET =  004f8074
         build_list: totlen =  00000049
         build_list: inode =  00000002
         build_list: version =  00000002
         build_list: isize =  00000005
         build_list: atime =  00000074
         build_list: offset =  00000000
         build_list: csize =  00000005
         build_list: dsize =  00000005
         build_list: compr =  00000000
         build_list: usercompr =  00000000
         build_list: flags =  00000000
         build_list: offset =  004f8074
  -rw-r--r--        5 Thu Jan 01 00:01:56 1970 testfile


How can I manage it that the deleted testfile isn't displayed anymore?
Is this a NAND specific problem?

Thanks.
Jonas

  parent reply	other threads:[~2005-06-01 15:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-17  8:39 [U-Boot-Users] jffs2 view u-boot/linux Jonas Dietsche
2005-05-30 11:43 ` Jonas Dietsche
2005-05-30 12:17   ` Wolfgang Denk
2005-05-30 13:08     ` Jonas Dietsche
2005-05-30 13:32       ` Wolfgang Denk
2005-05-30 14:36         ` Jonas Dietsche
2005-06-01 15:13   ` Jonas Dietsche [this message]
2005-06-01 21:01     ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2005-06-01 21:50 Dave Ellis
2005-06-03 13:01 ` Jonas Dietsche
2005-06-03 18:54   ` Dave Ellis

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=429DD07D.1080305@fsforth.de \
    --to=maillist@fsforth.de \
    --cc=u-boot@lists.denx.de \
    /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.