[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20 empty blocks, 0k free



We have linux booting on the the Shannon (http://TuxScreen.net) phone.
This is a StrongARM box with 4M flash:

They contain 4 MB BootableFlash on two Am29LV160DB-120EC chips:

SA1100 flash: probing 32-bit flash bus
SA1100 flash: Found 2 x16 devices at 0x0 in 32-bit mode
 Amd/Fujitsu Extended Query Table v1.0 at 0x0040
number of CFI chips: 1
0: offset=0x0,size=0x8000,blocks=1
1: offset=0x8000,size=0x4000,blocks=2
2: offset=0x10000,size=0x10000,blocks=1
3: offset=0x20000,size=0x20000,blocks=31
Using static partition definition
Creating 3 MTD partitions on "SA1100 flash":
0x00000000-0x00020000 : "BLOB boot loader"
0x00020000-0x00100000 : "kernel"
0x00100000-0x00400000 : "initrd"

I erased the initrd partition by writing 0xff to it as blob does not yet
have erase code. And copied in sample_img-01.jffs2 from
ftp://ftp.arm.linux.org.uk/pub/armlinux/people/nico/ just to get
started.

On bootup 20 blocks are seen as empty:

NetWinder Floating Point Emulator V0.95 (c) 1998-1999 Rebel.com
jffs2_scan_empty(): Empty block at 0x0000fffc ends at 0x00010000 (with
0xe0021985)! Marking dirty
jffs2_scan_empty(): Empty block at 0x0002fffc ends at 0x00030000 (with
0xe0021985)! Marking dirty
jffs2_scan_empty(): Empty block at 0x0004ffbc ends at 0x00050000 (with
0xe0021985)! Marking dirty
jffs2_scan_empty(): Empty block at 0x0006ffdc ends at 0x00070000 (with
0xe0021985)! Marking dirty
jffs2_scan_empty(): Empty block at 0x0008fffc ends at 0x00090000 (with
0xe0021985)! Marking dirty
jffs2_scan_empty(): Empty block at 0x000afffc ends at 0x000b0000 (with
0xe0021985)! Marking dirty
jffs2_scan_empty(): Empty block at 0x000cfffc ends at 0x000d0000 (with
0xe0021985)! Marking dirty
jffs2_scan_empty(): Empty block at 0x000efffc ends at 0x000f0000 (with
0xe0021985)! Marking dirty
jffs2_scan_empty(): Empty block at 0x0010fffc ends at 0x00110000 (with
0xe0021985)! Marking dirty
jffs2_scan_empty(): Empty block at 0x0012fffc ends at 0x00130000 (with
0xe0021985)! Marking dirty
jffs2_scan_empty(): Empty block at 0x0014fffc ends at 0x00150000 (with
0xe0021985)! Marking dirty
jffs2_scan_empty(): Empty block at 0x0016fffc ends at 0x00170000 (with
0xe0021985)! Marking dirty
jffs2_scan_empty(): Empty block at 0x0018fffc ends at 0x00190000 (with
0xe0021985)! Marking dirty
jffs2_scan_empty(): Empty block at 0x001afffc ends at 0x001b0000 (with
0xe0021985)! Marking dirty
jffs2_scan_empty(): Empty block at 0x001cfffc ends at 0x001d0000 (with
0xe0021985)! Marking dirty
jffs2_scan_empty(): Empty block at 0x001efffc ends at 0x001f0000 (with
0xe0021985)! Marking dirty
jffs2_scan_empty(): Empty block at 0x0020fff8 ends at 0x00210000 (with
0xe0021985)! Marking dirty
jffs2_scan_empty(): Empty block at 0x0022fffc ends at 0x00230000 (with
0xe0021985)! Marking dirty
jffs2_scan_empty(): Empty block at 0x0024fffc ends at 0x00250000 (with
0xe0021985)! Marking dirty
jffs2_scan_empty(): Empty block at 0x0026fffc ends at 0x00270000 (with
0xe0021985)! Marking dirty
VFS: Mounted root (jffs2 filesystem) readonly.

but root still shows 0k free:

[root@Linux /root]$cat /proc/mounts     
/dev/root / jffs2 rw 0 0
proc /proc proc rw 0 0
[root@Linux /root]$df
Filesystem           1k-blocks      Used Available Use% Mounted on
/dev/root                 3072      3072         0 100% /

there is a GC task running:

[root@Linux /root]$ps
  PID TTY         TIME CMD
    1   0,0   00:00:07 init
    2   0,0   00:00:00 keventd
    3   0,0   00:00:00 kswapd
    4   0,0   00:00:00 kreclaimd
    5   0,0   00:00:00 bdflush
    6   0,0   00:00:00 kupdated
    7   0,0   00:00:00 mtdblockd
    8   0,0   00:00:00 jffs2_gcd_mtd2
   38   0,0   00:00:00 syslogd
   55   0,0   00:00:00 inetd
   75 204,5   00:00:00 bash
  123 204,5   00:00:00 ps

but a kill -CONT 8 does not seem to affect it.

Thoughts?
-- 
Tim Riker - http://rikers.org/ - short SIGs! <g>
All I need to know I could have learned in Kindergarten
... if I'd just been paying attention.

To unsubscribe from this list: send the line "unsubscribe jffs-dev" in
the body of a message to majordomo@xxxxxxx.com