Re: No space on jffs2 fs

Re: No space on jffs2 fs

[MQuicquaro]

Dave and Ashok,

Thanks for the help.
So in essence what you are telling me is that since the block size
of my flash part is 256K, then the smallest jffs2 file system that I
can have is 5*256K or 1.25 MB?

Is this correct?

Mike

Re: No space on jffs2 fs

[David Woodhouse]

MQuicquaro@necinfrontia.com said:
>  Thanks for the help. So in essence what you are telling me is that
> since the block size of my flash part is 256K, then the smallest jffs2
> file system that I can have is 5*256K or 1.25 MB?

That's the smallest file system you can have without actually putting any 
data on it. You need 1.25MiB _above_ the amount of space actually taken by 
the data. 

This can be reduced. I'm just being overly conservative until I can prove 
that it's safe.

--
dwmw2

Re: No space on jffs2 fs

[MQuicquaro]

> That's the smallest file system you can have without actually putting any
> data on it. You need 1.25MiB _above_ the amount of space actually taken
by
> the data.
>
> This can be reduced. I'm just being overly conservative until I can prove
> that it's safe.

Can this 5 block minimum be easily reduced by me, even if its just
temporary,
so that I can get past my initial development/testing phase?  On this
Motorola
eval. board that I am using there is only 1MB of flash which I can use
while
still keeping a separate 1MB intact which has a good debugging monitor that
is
important to me since my BDM debugging isn't totally working yet.

Thanks again for the much appreciated help.

- Mike

Re: No space on jffs2 fs

[David Woodhouse]

MQuicquaro@necinfrontia.com said:
>  Can this 5 block minimum be easily reduced by me, even if its just
> temporary, so that I can get past my initial development/testing
> phase? 

Edit fs/jffs2/nodelist.h, reduce JFFS2_RESERVED_BLOCKS_BASE to 1.

--
dwmw2

No space on jffs2 fs

[MQuicquaro]

I have a Motorola CF 5272 eval. board.
I am running uClinux 2.4 with mtd/jffs2.

I am currently using the topmost 1MB of flash
partitioned as decribed in Bernhard Kuhn's
uClinux flash device mini howto.

My root filesystem ends up in the last 256K of
flash.

I did a mkfs.jffs2 on my romfs/ directory, padding
it with 0xFFs and then loading it into my flash via
the dBUG "upuser" command.   Everything seems to work
ok except I cannot ever write to my jffs2 fs because
there is never any free space.

What could cause this?

Here is some output from my system:

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

uClinux/COLDFIRE(m5272)
COLDFIRE port done by Greg Ungerer, gerg@lineo.com
Flat model support (C) 1998,1999 Kenneth Albanowski, D. Jeff Dionne
On node 0 totalpages: 1024
zone(0): 0 pages.
zone(1): 1024 pages.
zone(2): 0 pages.
Kernel command line: CONSOLE=/dev/ttyS0,19200 root=1f09
Calibrating delay loop... 43.62 BogoMIPS
Memory available: 3020k/4096k RAM, 0k/0k ROM (562k kernel code, 303k data)
kmem_create: Forcing size word alignment - vm_area_struct
kmem_create: Forcing size word alignment - mm_struct
kmem_create: Forcing size word alignment - filp
Dentry-cache hash table entries: 512 (order: 0, 4096 bytes)
Inode-cache hash table entries: 512 (order: 0, 4096 bytes)
kmem_create: Forcing size word alignment - inode_cache
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
kmem_create: Forcing size word alignment - bdev_cache
kmem_create: Forcing size word alignment - cdev_cache
Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)
Page-cache hash table entries: 1024 (order: 0, 4096 bytes)
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
kmem_create: Forcing size word alignment - sock
Starting kswapd
kmem_create: Forcing size word alignment - file lock cache
JFFS2 version 2.1. (C) 2001 Red Hat, Inc., designed by Axis Communications
AB.
ColdFire internal UART serial driver version 1.00
ttyS0 at 0x10000100 (irq = 73) is a builtin ColdFire UART
ttyS1 at 0x10000140 (irq = 74) is a builtin ColdFire UART
kmem_create: Forcing size word alignment - blkdev_requests
block: 64 slots per queue, batch=8
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
eth0: FEC ENET Version 0.2, 00:cf:52:72:c3:01
fec: Phy @ 0x0, type 0x001378e2
physmap flash device: 200000 at ffe00000
Physically mapped flash: Found 1 x16 devices at 0x0 in 16-bit mode
 Amd/Fujitsu Extended Query Table v1.0 at 0x0040
number of CFI chips: 1
0: offset=0x0,size=0x4000,blocks=1
1: offset=0x4000,size=0x2000,blocks=2
2: offset=0x8000,size=0x38000,blocks=1
3: offset=0x40000,size=0x40000,blocks=7
Creating 10 MTD partitions on "Physically mapped flash":
0x00000000-0x00004000 : "boot (16K)"
mtd: Giving out device 0 to boot (16K)
0x00080000-0x00100000 : "kernel (512K)"
mtd: Giving out device 1 to kernel (512K)
0x00100000-0x00200000 : "rootfs (1024K)"
mtd: Giving out device 2 to rootfs (1024K)
0x00004000-0x00006000 : "spare (8K)"
mtd: Giving out device 3 to spare (8K)
0x00006000-0x00008000 : "spare (8K)"
mtd: Giving out device 4 to spare (8K)
0x00040000-0x00080000 : "spare (256K)"
mtd: Giving out device 5 to spare (256K)
0x00000000-0x00200000 : "complete (2048K)"
mtd: Giving out device 6 to complete (2048K)
0x00100000-0x00140000 : "boot J13 (256K)"
mtd: Giving out device 7 to boot J13 (256K)
0x00140000-0x001c0000 : "kernel J13 (512K)"
mtd: Giving out device 8 to kernel J13 (512K)
0x001c0000-0x00200000 : "rootfs J13 (256K)"
mtd: Giving out device 9 to rootfs J13 (256K)
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
kmem_create: Forcing size word alignment - ip_dst_cache
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 512 bind 512)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
VFS: Mounted root (jffs2 filesystem) readonly.
Freeing unused kernel memory: 20k freed
Shell invoked to run file: /etc/rc
Command: hostname uClinux-coldfire
Command: /bin/expand /etc/ramfs.img /dev/ram0
Command: mount -t proc proc /proc
Command: mount -t ext2 /dev/ram0 /var
Command: mkdir /var/tmp
Command: mkdir /var/log
Command: mkdir /var/run
Command: mkdir /var/lock
Command: ifconfig lo 127.0.0.1
Command: route add -net 127.0.0.0 lo
SIOCADDRT: Invalid argument
pid 14: failed 1792
Command: dhcpcd -p -a eth0 &
[15]
Command: cat /etc/motd
Welcome to
          ____ _  _
         /  __| ||_|
    _   _| |  | | _ ____  _   _  _  _
   | | | | |  | || |  _ \| | | |\ \/ /
   | |_| | |__| || | | | | |_| |/    \
   |  ___\____|_||_|_| |_|\____|\_/\_/
   | |
   |_|

For further information check:
http://www.uclinux.org/

Execution Finished, Exiting

Sash command shell (version 1.1.1)
/> eth0: config: auto-negotiation on, 100FDX, 100HDX, 10FDX, 10HDX.

/> mount
/dev/root on / type jffs2 (ro)
proc on /proc type proc (rw)
/dev/ram0 on /var type ext2 (rw)
/> mount -orw,remount /
/> mount
/dev/root on / type jffs2 (rw)
proc on /proc type proc (rw)
/dev/ram0 on /var type ext2 (rw)
/> df /
Total Kbytes: 256
Free  Kbytes: 0
Total  nodes: 0
Free   nodes: 0
/> touch fubar
fubar: No space left on device
/>

Re: No space on jffs2 fs

[David Woodhouse]

MQuicquaro@necinfrontia.com said:
> I did a mkfs.jffs2 on my romfs/ directory, padding it with 0xFFs and
> then loading it into my flash via the dBUG "upuser" command.
> Everything seems to work ok except I cannot ever write to my jffs2 fs
> because there is never any free space. 

> Kernel command line: CONSOLE=/dev/ttyS0,19200 root=1f09
> 0x001c0000-0x00200000 : "rootfs J13 (256K)"
> mtd: Giving out device 9 to rootfs J13 (256K)

Your root filesystem is only 256KiB, and that appears to match the erase 
size - you have only one erase block in your root filesystem. JFFS2 
currently needs five spare blocks, although it could get away with fewer if 
I wasn't so cautious about reducing that number.

--
dwmw2