JFFS2 mounting problem

JFFS2 mounting problem

[Sanjay Kumar]

Hi All,
I am trying to mount JFFS2 and it is taking more than 5 minutes in mounting and also reading from JFFS2 is very slow.
In case I copy a single large file, mounting and reading is fast but when I keep multiple files and try to mount then this problem is coming.
Can please someone advice why this is happening.
Thanks,
Sanjay

Re: JFFS2 mounting problem

[Vipin Malik]

Check back in the list archives. This topic has been discussed quite a bit. 
Quite recently too, if I remember correctly.

Vipin


At 10:47 PM 1/8/2002 +0530, Sanjay Kumar wrote:
>Hi All,
>I am trying to mount JFFS2 and it is taking more than 5 minutes in 
>mounting and also reading from JFFS2 is very slow.
>In case I copy a single large file, mounting and reading is fast but when 
>I keep multiple files and try to mount then this problem is coming.
>Can please someone advice why this is happening.
>Thanks,
>Sanjay
>
>
>
>______________________________________________________
>Linux MTD discussion mailing list
>http://lists.infradead.org/mailman/listinfo/linux-mtd/

jffs2 mounting problem

[Sanjay Kumar]

Hi All,
I am using linux2.4.2.
I am using two AMD flash of 4MB each. Then I am relocating them such that they
are continuous.
Then I create  three partitions, first one for bootloader, second for JFFS2
root partition and the last is free to be used latter.

Then probing of the flash also shows the following information -
physmap flash device: 800000 at bf800000
Number of erase regions: 2
Primary Vendor Command Set: 0002 (AMD/Fujitsu Standard)

Now when I boot the system from 2nd jffs2 root partition I see the following info -

#cat /proc/mtd
dev:    size   erasesize  name
mtd0: 000a0000 00010000 "bootstrap and kernel"
mtd1: 00360000 00010000 "jffs2 filesystem"
mtd2: 00400000 00010000 "jffs2 2nd filesystem"

Also I have following devices created -
#ls -l
crwxr--r--   1 root     root      90,   0 Mar 27  2002 mtd0
crwxr--r--   1 root     root      90,   1 Mar 27  2002 mtd1
crwxr--r--   1 root     root      90,   2 Mar 27  2002 mtd2
crw-r--r--   1 root     root      90,   4 Jan  1 00:03 mtd4
brwxr--r--   1 root     root      31,   0 Mar 27  2002 mtdblock0
brwxr--r--   1 root     root      31,   1 Mar 27  2002 mtdblock1
brw-r--r--   1 root     root      31,   2 Jan  1 00:02 mtdblock2



Now I want the last partition to be mounted to /mnt directory.
For that first I use /dev/mtd4 for erasing the partition and 
then I use the following command to mount the last partition -

#mount -t jffs2 /dev/mtdblock2 /mnt
which starts displaying the following -
ofs 0x00200044 has already been seen. Skipping
ofs 0x00202ea8 has already been seen. Skipping
ofs 0x0020636c has already been seen. Skipping
ofs 0x0020d370 has already been seen. Skipping
ofs 0x0020f044 has already been seen. Skipping
.
.
.
ofs 0x003f4524 has already been seen. Skipping
ofs 0x003fb13c has already been seen. Skipping
ofs 0x003ff0b0 has already been seen. Skipping


When the mounting is completed I use the command "df" and I see the
used space in the partition increases rapidly to 100%.

#df
Filesystem           1k-blocks      Used Available Use% Mounted on
/dev/root                 3456      2080      1376  60% /
/dev/mtdblock2            4096      2944      1152  72% /mnt
#df
Filesystem           1k-blocks      Used Available Use% Mounted on
/dev/root                 3456      2080      1376  60% /
/dev/mtdblock2            4096      3392       704  83% /mnt
#df
Filesystem           1k-blocks      Used Available Use% Mounted on
/dev/root                 3456      2080      1376  60% /
/dev/mtdblock2            4096      3648       448  89% /mnt
#df
Filesystem           1k-blocks      Used Available Use% Mounted on
/dev/root                 3456      2080      1376  60% /
/dev/mtdblock2            4096      3968       128  97% /mnt
#busybox df
Filesystem           1k-blocks      Used Available Use% Mounted on
/dev/root                 3456      2080      1376  60% /
/dev/mtdblock2            4096      4096         0 100% /mnt

Also at last I see the following information -
#Newly-erased block contained word 0x0 at offset 0x003f0000
Newly-erased block contained word 0x9aa39aa3 at offset 0x003e0000


I don't know where I am doing any wrong.


Please help in solving this problem. Any kind of suggestions is welcome.

Thanks & Regards,
Sanjay




__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.yahoo.com/

Re: jffs2 mounting problem

[Robert Kaiser]

Hi,

Am Donnerstag, 4. April 2002 18:07 schrieben Sie:
> I am using two AMD flash of 4MB each. Then I am relocating them such that
> they are continuous.
> Then I create  three partitions, first one for bootloader, second for JFFS2
> root partition and the last is free to be used latter.
>
> Then probing of the flash also shows the following information -
> physmap flash device: 800000 at bf800000
> Number of erase regions: 2
> Primary Vendor Command Set: 0002 (AMD/Fujitsu Standard)
>
> Now when I boot the system from 2nd jffs2 root partition I see the
> following info -
>
> #cat /proc/mtd
> dev:    size   erasesize  name
> mtd0: 000a0000 00010000 "bootstrap and kernel"
> mtd1: 00360000 00010000 "jffs2 filesystem"
> mtd2: 00400000 00010000 "jffs2 2nd filesystem"
>
> Also I have following devices created -
> #ls -l
> crwxr--r--   1 root     root      90,   0 Mar 27  2002 mtd0
> crwxr--r--   1 root     root      90,   1 Mar 27  2002 mtd1
> crwxr--r--   1 root     root      90,   2 Mar 27  2002 mtd2
> crw-r--r--   1 root     root      90,   4 Jan  1 00:03 mtd4
> brwxr--r--   1 root     root      31,   0 Mar 27  2002 mtdblock0
> brwxr--r--   1 root     root      31,   1 Mar 27  2002 mtdblock1
> brw-r--r--   1 root     root      31,   2 Jan  1 00:02 mtdblock2
>

Have a look at the MAKEDEV script in directory "util" of the MTD directory. 
The minor numbers you chose for /dev/mtd? are, umm, unusual. I doubt you 
really want them. The MAKEDEV script would have assigned these numbers:

   mtd0: 0
   mtd1: 2
   mtd2: 4
   mtd4: 8

>
>
> Now I want the last partition to be mounted to /mnt directory.
> For that first I use /dev/mtd4 for erasing the partition and

Due to the (presumably wrong) minor numbers, /dev/mtd4 in your case 
corresponds to device mtd2 (i.e. "jffs2 2nd filesystem"), so that is
what got erased.

> then I use the following command to mount the last partition -
>
> #mount -t jffs2 /dev/mtdblock2 /mnt

The minor number for mtdblock2 is correct (i.e. it also corresponds to the 
"jffs2 2nd filesystem" partition), so this should actually work. My only 
guess is that you may have used "erase /dev/mtd4" to do the erase ? Note that 
the "erase" command by default erases only one block, "eraseall" erases an 
entire device.

>
> When the mounting is completed I use the command "df" and I see the
> used space in the partition increases rapidly to 100%.

This is normal AFAIK. After increasing to 100% as you observed, it should go 
back to some 5% or so (depends on the erase block size).

Hope this helps

Rob


----------------------------------------------------------------
Robert Kaiser                         email: rkaiser@sysgo.de
SYSGO RTS GmbH
Am Pfaffenstein 14                    phone: (49) 6136 9948-762
D-55270 Klein-Winternheim / Germany   fax:   (49) 6136 9948-10

Re: jffs2 mounting problem

[Sanjay Kumar]

Hi Robert,
Thanks for you useful sugestions.
Now I create the character device using MAKEDEV script i.e 
crwxr--r--   1 root     root      90,   0 Mar 27  2002 mtd0
crwxr--r--   1 root     root      90,   2 Mar 27  2002 mtd1
crwxr--r--   1 root     root      90,   4 Mar 27  2002 mtd2
Also I am using eraseall(eraseall /dev/mtd2)to erase the last partition completely. 
Still I see the same behaviour. 
Also the used space remains at 100% and event after long time
it doesn't decrease.

Please let me know what else I can try. I am in very urgent need to solve this problem.

Thanks & regards,
Sanjay
--- Robert Kaiser <rob@sysgo.de> wrote:
> Hi,
> 
> Am Donnerstag, 4. April 2002 18:07 schrieben Sie:
> > I am using two AMD flash of 4MB each. Then I am relocating them such that
> > they are continuous.
> > Then I create  three partitions, first one for bootloader, second for JFFS2
> > root partition and the last is free to be used latter.
> >
> > Then probing of the flash also shows the following information -
> > physmap flash device: 800000 at bf800000
> > Number of erase regions: 2
> > Primary Vendor Command Set: 0002 (AMD/Fujitsu Standard)
> >
> > Now when I boot the system from 2nd jffs2 root partition I see the
> > following info -
> >
> > #cat /proc/mtd
> > dev:    size   erasesize  name
> > mtd0: 000a0000 00010000 "bootstrap and kernel"
> > mtd1: 00360000 00010000 "jffs2 filesystem"
> > mtd2: 00400000 00010000 "jffs2 2nd filesystem"
> >
> > Also I have following devices created -
> > #ls -l
> > crwxr--r--   1 root     root      90,   0 Mar 27  2002 mtd0
> > crwxr--r--   1 root     root      90,   1 Mar 27  2002 mtd1
> > crwxr--r--   1 root     root      90,   2 Mar 27  2002 mtd2
> > crw-r--r--   1 root     root      90,   4 Jan  1 00:03 mtd4
> > brwxr--r--   1 root     root      31,   0 Mar 27  2002 mtdblock0
> > brwxr--r--   1 root     root      31,   1 Mar 27  2002 mtdblock1
> > brw-r--r--   1 root     root      31,   2 Jan  1 00:02 mtdblock2
> >
> 
> Have a look at the MAKEDEV script in directory "util" of the MTD directory. 
> The minor numbers you chose for /dev/mtd? are, umm, unusual. I doubt you 
> really want them. The MAKEDEV script would have assigned these numbers:
> 
>    mtd0: 0
>    mtd1: 2
>    mtd2: 4
>    mtd4: 8
> 
> >
> >
> > Now I want the last partition to be mounted to /mnt directory.
> > For that first I use /dev/mtd4 for erasing the partition and
> 
> Due to the (presumably wrong) minor numbers, /dev/mtd4 in your case 
> corresponds to device mtd2 (i.e. "jffs2 2nd filesystem"), so that is
> what got erased.
> 
> > then I use the following command to mount the last partition -
> >
> > #mount -t jffs2 /dev/mtdblock2 /mnt
> 
> The minor number for mtdblock2 is correct (i.e. it also corresponds to the 
> "jffs2 2nd filesystem" partition), so this should actually work. My only 
> guess is that you may have used "erase /dev/mtd4" to do the erase ? Note that 
> the "erase" command by default erases only one block, "eraseall" erases an 
> entire device.
> 
> >
> > When the mounting is completed I use the command "df" and I see the
> > used space in the partition increases rapidly to 100%.
> 
> This is normal AFAIK. After increasing to 100% as you observed, it should go 
> back to some 5% or so (depends on the erase block size).
> 
> Hope this helps
> 
> Rob
> 
> 
> ----------------------------------------------------------------
> Robert Kaiser                         email: rkaiser@sysgo.de
> SYSGO RTS GmbH
> Am Pfaffenstein 14                    phone: (49) 6136 9948-762
> D-55270 Klein-Winternheim / Germany   fax:   (49) 6136 9948-10


__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.yahoo.com/

Re: jffs2 mounting problem

[Sanjay Kumar]

Hi Robert,
One more intersting thing. 
Even the "df" commnad shows uses to 100%, I can copy files to this last partition.
Also copy between the two flashes(partition last to second) is extremly slow.
Also still i see all those messages.
What can be the reasons?

Thanks,
Sanjay 
--- Robert Kaiser <rob@sysgo.de> wrote:
> Hi,
> 
> Am Donnerstag, 4. April 2002 18:07 schrieben Sie:
> > I am using two AMD flash of 4MB each. Then I am relocating them such that
> > they are continuous.
> > Then I create  three partitions, first one for bootloader, second for JFFS2
> > root partition and the last is free to be used latter.
> >
> > Then probing of the flash also shows the following information -
> > physmap flash device: 800000 at bf800000
> > Number of erase regions: 2
> > Primary Vendor Command Set: 0002 (AMD/Fujitsu Standard)
> >
> > Now when I boot the system from 2nd jffs2 root partition I see the
> > following info -
> >
> > #cat /proc/mtd
> > dev:    size   erasesize  name
> > mtd0: 000a0000 00010000 "bootstrap and kernel"
> > mtd1: 00360000 00010000 "jffs2 filesystem"
> > mtd2: 00400000 00010000 "jffs2 2nd filesystem"
> >
> > Also I have following devices created -
> > #ls -l
> > crwxr--r--   1 root     root      90,   0 Mar 27  2002 mtd0
> > crwxr--r--   1 root     root      90,   1 Mar 27  2002 mtd1
> > crwxr--r--   1 root     root      90,   2 Mar 27  2002 mtd2
> > crw-r--r--   1 root     root      90,   4 Jan  1 00:03 mtd4
> > brwxr--r--   1 root     root      31,   0 Mar 27  2002 mtdblock0
> > brwxr--r--   1 root     root      31,   1 Mar 27  2002 mtdblock1
> > brw-r--r--   1 root     root      31,   2 Jan  1 00:02 mtdblock2
> >
> 
> Have a look at the MAKEDEV script in directory "util" of the MTD directory. 
> The minor numbers you chose for /dev/mtd? are, umm, unusual. I doubt you 
> really want them. The MAKEDEV script would have assigned these numbers:
> 
>    mtd0: 0
>    mtd1: 2
>    mtd2: 4
>    mtd4: 8
> 
> >
> >
> > Now I want the last partition to be mounted to /mnt directory.
> > For that first I use /dev/mtd4 for erasing the partition and
> 
> Due to the (presumably wrong) minor numbers, /dev/mtd4 in your case 
> corresponds to device mtd2 (i.e. "jffs2 2nd filesystem"), so that is
> what got erased.
> 
> > then I use the following command to mount the last partition -
> >
> > #mount -t jffs2 /dev/mtdblock2 /mnt
> 
> The minor number for mtdblock2 is correct (i.e. it also corresponds to the 
> "jffs2 2nd filesystem" partition), so this should actually work. My only 
> guess is that you may have used "erase /dev/mtd4" to do the erase ? Note that 
> the "erase" command by default erases only one block, "eraseall" erases an 
> entire device.
> 
> >
> > When the mounting is completed I use the command "df" and I see the
> > used space in the partition increases rapidly to 100%.
> 
> This is normal AFAIK. After increasing to 100% as you observed, it should go 
> back to some 5% or so (depends on the erase block size).
> 
> Hope this helps
> 
> Rob
> 
> 
> ----------------------------------------------------------------
> Robert Kaiser                         email: rkaiser@sysgo.de
> SYSGO RTS GmbH
> Am Pfaffenstein 14                    phone: (49) 6136 9948-762
> D-55270 Klein-Winternheim / Germany   fax:   (49) 6136 9948-10


__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.yahoo.com/

RE: jffs2 mounting problem

[ajcurtis84]

How old is your distribution? We had this problem with the HHL 2.0 source.

-----Original Message-----
From: linux-mtd-admin@lists.infradead.org
[mailto:linux-mtd-admin@lists.infradead.org]On Behalf Of Sanjay Kumar
Sent: Thursday, April 04, 2002 1:24 PM
To: rkaiser@sysgo.de
Cc: linux-mtd@lists.infradead.org
Subject: Re: jffs2 mounting problem


Hi Robert,
One more intersting thing.
Even the "df" commnad shows uses to 100%, I can copy files to this last
partition.
Also copy between the two flashes(partition last to second) is extremly
slow.
Also still i see all those messages.
What can be the reasons?

Thanks,
Sanjay
--- Robert Kaiser <rob@sysgo.de> wrote:
> Hi,
>
> Am Donnerstag, 4. April 2002 18:07 schrieben Sie:
> > I am using two AMD flash of 4MB each. Then I am relocating them such
that
> > they are continuous.
> > Then I create  three partitions, first one for bootloader, second for
JFFS2
> > root partition and the last is free to be used latter.
> >
> > Then probing of the flash also shows the following information -
> > physmap flash device: 800000 at bf800000
> > Number of erase regions: 2
> > Primary Vendor Command Set: 0002 (AMD/Fujitsu Standard)
> >
> > Now when I boot the system from 2nd jffs2 root partition I see the
> > following info -
> >
> > #cat /proc/mtd
> > dev:    size   erasesize  name
> > mtd0: 000a0000 00010000 "bootstrap and kernel"
> > mtd1: 00360000 00010000 "jffs2 filesystem"
> > mtd2: 00400000 00010000 "jffs2 2nd filesystem"
> >
> > Also I have following devices created -
> > #ls -l
> > crwxr--r--   1 root     root      90,   0 Mar 27  2002 mtd0
> > crwxr--r--   1 root     root      90,   1 Mar 27  2002 mtd1
> > crwxr--r--   1 root     root      90,   2 Mar 27  2002 mtd2
> > crw-r--r--   1 root     root      90,   4 Jan  1 00:03 mtd4
> > brwxr--r--   1 root     root      31,   0 Mar 27  2002 mtdblock0
> > brwxr--r--   1 root     root      31,   1 Mar 27  2002 mtdblock1
> > brw-r--r--   1 root     root      31,   2 Jan  1 00:02 mtdblock2
> >
>
> Have a look at the MAKEDEV script in directory "util" of the MTD
directory.
> The minor numbers you chose for /dev/mtd? are, umm, unusual. I doubt you
> really want them. The MAKEDEV script would have assigned these numbers:
>
>    mtd0: 0
>    mtd1: 2
>    mtd2: 4
>    mtd4: 8
>
> >
> >
> > Now I want the last partition to be mounted to /mnt directory.
> > For that first I use /dev/mtd4 for erasing the partition and
>
> Due to the (presumably wrong) minor numbers, /dev/mtd4 in your case
> corresponds to device mtd2 (i.e. "jffs2 2nd filesystem"), so that is
> what got erased.
>
> > then I use the following command to mount the last partition -
> >
> > #mount -t jffs2 /dev/mtdblock2 /mnt
>
> The minor number for mtdblock2 is correct (i.e. it also corresponds to the
> "jffs2 2nd filesystem" partition), so this should actually work. My only
> guess is that you may have used "erase /dev/mtd4" to do the erase ? Note
that
> the "erase" command by default erases only one block, "eraseall" erases an
> entire device.
>
> >
> > When the mounting is completed I use the command "df" and I see the
> > used space in the partition increases rapidly to 100%.
>
> This is normal AFAIK. After increasing to 100% as you observed, it should
go
> back to some 5% or so (depends on the erase block size).
>
> Hope this helps
>
> Rob
>
>
> ----------------------------------------------------------------
> Robert Kaiser                         email: rkaiser@sysgo.de
> SYSGO RTS GmbH
> Am Pfaffenstein 14                    phone: (49) 6136 9948-762
> D-55270 Klein-Winternheim / Germany   fax:   (49) 6136 9948-10


__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.yahoo.com/

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

use "nandwrite" instead of "cp"?

[??]

  dear all,
  thanks for your help,
 
 now i try to:
 
1> eraseall /dev/mtd1
2> cp test.img /dev/mtdblock1 
     (should i use "nandwrite" instead of "cp" here?)
3> mount -t jffs2 /dev/mtdblock1 /mnt
 
 then it still report many "magic bitmask not found"
  do i missing something?
  
  thanks in advanced!:)
  
  best regards,
  kevin
 
>  ----following message
> > log------------------------------------------------------
> > jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00298014:
> > 0xa3dc in
> > stead
> > jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00298018:
> > 0xccfe in
> > stead
> > jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0029801c:
> > 0xd1b5 in
> > stead
> > jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00298020:
> > 0xf8fd in
> > stead
> > jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00298024:
> > 0xb452 in
> > stead
> > Further such events for this erase block will not be printed
> > nand_read_ecc: Failed ECC read, page 0x00007fc0
> > nand_read_ecc: Failed ECC read, page 0x00007fc0
> > nand_read_ecc: Failed ECC read, page 0x00007fc1
> > nand_read_ecc: Failed ECC read, page 0x00007fc1
> > nand_read_ecc: Failed ECC read, page 0x00007fc2
> > nand_read_ecc: Failed ECC read, page 0x00007fc2
> > nand_read_ecc: Failed ECC read, page 0x00007fc3
> > nand_read_ecc: Failed ECC read, page 0x00007fc3
> > jffs2_scan_empty(): Read 0x1000 bytes at 0x00df8000 returned -5
> > mount: wrong fs type, bad option, bad superblock on /dev/mtdblock1,
> >        or too many mounted file systems
> > 
> > 
> > ______________________________________________________
> > Linux MTD discussion mailing list
> > http://lists.infradead.org/mailman/listinfo/linux-mtd/
> 

jffs2 mounting problem

[??]

   dear all,
   thanks for your help,

  now i try to:

 1> eraseall /dev/mtd1
 2> cp test.img /dev/mtdblock1

      test.img is created from:
     mkfs.jffs2 -r rootfs_jffs2 -e 16K -l -o test.img
     nand device is TC58128FT (16MBytes Nand flash)
      (should i use "nandwrite" instead of "cp" here?)

 3> mount -t jffs2 /dev/mtdblock1 /mnt

  then it still report many "magic bitmask not found"
   do i missing something?
   or is it caused by bad-block/ecc-error?

   thanks in advanced!:)

   best regards,
   kevin

> >  ----following message
> > > log------------------------------------------------------
> > > jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00298014:
> > > 0xa3dc in
> > > stead
> > > jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00298018:
> > > 0xccfe in
> > > stead
> > > jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0029801c:
> > > 0xd1b5 in
> > > stead
> > > jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00298020:
> > > 0xf8fd in
> > > stead
> > > jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00298024:
> > > 0xb452 in
> > > stead
> > > Further such events for this erase block will not be printed
> > > nand_read_ecc: Failed ECC read, page 0x00007fc0
> > > nand_read_ecc: Failed ECC read, page 0x00007fc0
> > > nand_read_ecc: Failed ECC read, page 0x00007fc1
> > > nand_read_ecc: Failed ECC read, page 0x00007fc1
> > > nand_read_ecc: Failed ECC read, page 0x00007fc2
> > > nand_read_ecc: Failed ECC read, page 0x00007fc2
> > > nand_read_ecc: Failed ECC read, page 0x00007fc3
> > > nand_read_ecc: Failed ECC read, page 0x00007fc3
> > > jffs2_scan_empty(): Read 0x1000 bytes at 0x00df8000 returned -5
> > > mount: wrong fs type, bad option, bad superblock on /dev/mtdblock1,
> > >        or too many mounted file systems
----- following eraseall log -------------------------------
Erasing 16 Kibyte @ dc4000 -- 98 % complete.MTD_ioctl
Erasing 16 Kibyte @ dc8000 -- 98 % complete.MTD_ioctl
Erasing 16 Kibyte @ dcc000 -- 98 % complete.MTD_ioctl
Erasing 16 Kibyte @ dd0000 -- 98 % complete.MTD_ioctl
Erasing 16 Kibyte @ dd4000 -- 98 % complete.MTD_ioctl
Erasing 16 Kibyte @ dd8000 -- 98 % complete.MTD_ioctl
Erasing 16 Kibyte @ ddc000 -- 98 % complete.MTD_ioctl
Erasing 16 Kibyte @ de0000 -- 99 % complete.MTD_ioctl
Erasing 16 Kibyte @ de4000 -- 99 % complete.MTD_ioctl
Erasing 16 Kibyte @ de8000 -- 99 % complete.MTD_ioctl
Erasing 16 Kibyte @ dec000 -- 99 % complete.MTD_ioctl
Erasing 16 Kibyte @ df0000 -- 99 % complete.MTD_ioctl
Erasing 16 Kibyte @ df4000 -- 99 % complete.MTD_ioctl
Erasing 16 Kibyte @ df8000 -- 99 % complete.MTD_ioctl
nand_erase: attempt to erase a bad block at page 0x00007fc0

./eraseall: /dev/mtd1: MTD Erase failure: Input/output error
Erasing 16 Kibyte @ dfc000 -- 99 % complete.MTD_ioctl
nand_erase: attempt to erase a bad block at page 0x00007fe0

./eraseall: /dev/mtd1: MTD Erase failure: Input/output error
Erased 14336 Kibyte @ 0 -- 100% complete.
MTD_close
-----------------------end of log ----------------------------

JFFS2 mounting problem

[Amit Sharma]

Hi  all

I am working on JFFS2 MTD driver on NAND device

I try to copy file to JFFs2 partition before mounting my device to mnt
partition but after mounting i do not find any file in my mount
directory.

Can any one help me why i donot find any file in mount directory after
mounting when device have file.

mkfs.jffs2 -d /home/jffs2stuff -o /tmp/jffs2.image
cat /tmp/jffs2.image >/dev/mtdblock/0
mount -t jffs2 /dev/mtdblock/0 /mnt/
ls
--------No file available--------

but i am able to create file after mounting in jffs2 partition.

Regards
AK

Re: JFFS2 mounting problem

[Thomas Gleixner]

On Thu, 2005-07-28 at 16:57 +0900, Amit Sharma wrote:
> mkfs.jffs2 -d /home/jffs2stuff -o /tmp/jffs2.image

Yoe have to set the correct options for your FLASH.

mkfs.jffs2 -e ERASEBLOCKSIZE -p NANDPAGESIZE -n -d ... -o ...

> cat /tmp/jffs2.image >/dev/mtdblock/0

Use nandwrite for that. Read
http://linux-mtd.infradead.org/faq/nand.html

> mount -t jffs2 /dev/mtdblock/0 /mnt/

tglx