"No space left on device" - rootfs image build error

[sjremya]

Hi all

I am using SUSE LINUX Distributor.

I have downloaded a roof filesystem source and trying to create a compressed image using mkimage which is installed in my Suse linux host machine.

I could create the image, using the following script
/*************************



RD_DIR=$1
RD_FILE=$2

RD_TEMP_FILE=$RD_FILE"_temp"
RD_TEMP_DIR=$RD_FILE"_mount"

GZ_FILE=$RD_TEMP_FILE".gz"
mkdir $RD_TEMP_DIR
dd if=/dev/zero of=$RD_TEMP_FILE bs=1024k count=20
/sbin/mke2fs -F -m0 $RD_TEMP_FILE
/sbin/tune2fs -c 0 $RD_TEMP_FILE
mount $RD_TEMP_FILE $RD_TEMP_DIR -o loop
cp -r -d $RD_DIR/* $RD_TEMP_DIR
umount $RD_TEMP_DIR
gzip $RD_TEMP_FILE

mkimage -A arm -T ramdisk -C gzip -n "Ramdisk" -d $GZ_FILE $RD_FILE


******************************/

I am getting this following log, with an error "no space left on device" Please help me out to solve.



20+0 records in
20+0 records out
20971520 bytes (21 MB) copied, 0.0443623 s, 473 MB/s
mke2fs 1.39 (29-May-2006)
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
5136 inodes, 20480 blocks
0 blocks (0.00%) reserved for the super user
First data block=1
Maximum filesystem blocks=20971520
3 block groups
8192 blocks per group, 8192 fragments per group
1712 inodes per group
Superblock backups stored on blocks:
8193

Writing inode tables: done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 20 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
tune2fs 1.39 (29-May-2006)
Setting maximal mount count to -1
cp: writing `rfs_image_v.4_mount/bin/cp': No space left on device
cp: writing `rfs_image_v.4_mount/bin/echo': No space left on device
cp: writing `rfs_image_v.4_mount/bin/vi': No space left on device
cp: writing `rfs_image_v.4_mount/bin/chgrp': No space left on device
cp: writing `rfs_image_v.4_mount/bin/dmesg': No space left on device
cp: writing `rfs_image_v.4_mount/bin/mount': No space left on device
cp: writing `rfs_image_v.4_mount/bin/netstat': No space left on device
cp: writing `rfs_image_v.4_mount/bin/uname': No space left on device
cp: writing `rfs_image_v.4_mount/bin/pwd': No space left on device
cp: writing `rfs_image_v.4_mount/bin/hostname': No space left on device
cp: writing `rfs_image_v.4_mount/bin/rm': No space left on device
cp: writing `rfs_image_v.4_mount/bin/false': No space left on device
cp: writing `rfs_image_v.4_mount/bin/cpio': No space left on device
cp: writing `rfs_image_v.4_mount/bin/su': No space left on device
cp: writing `rfs_image_v.4_mount/bin/touch': No space left on device
cp: cannot create directory `rfs_image_v.4_mount/srv': No space left on device
cp: cannot create directory `rfs_image_v.4_mount/sys': No space left on device
cp: cannot create directory `rfs_image_v.4_mount/tmp': No space left on device
cp: cannot create directory `rfs_image_v.4_mount/tsrpm': No space left on device
cp: cannot create directory `rfs_image_v.4_mount/usr': No space left on device
cp: cannot create directory `rfs_image_v.4_mount/var': No space left on device
Image Name: Ramdisk
Created: Thu Aug 26 17:20:57 2010
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 10893713 Bytes = 10638.39 kB = 10.39 MB
Load Address: 0x00000000
Entry Point: 0x00000000
===================

[gogalthorp]

How much space did you allocate to root and how much is available? Temp files are normally created in /tmp directory which is normally on the root partition.

[sjremya]

@ gogalthorp :

Thanks for the reply.

I will make my problem more clear .

This root FS is for ARM architecture, not for a general PC. So for cross compile purpose, I am using Suse host machine.

With mkimage tool, I have created an RFS image from an RFS source of size 174MB. The Image I got has a size of 10 MB approximately. I have used the mentioned script file, to make use of mkimage tool

But it is throwing me an error while doing cp, " No space left on device". So I have come to one colclusion that the 10MB is not the actual size of the image.


cp: writing `rfs_image_v.4_mount/bin/cp': No space left on device


Please give me advice ..

Regards
SJR

[sjremya]

@ gogalthorp :

Thanks for the reply.

I will make my problem more clear .

This root FS is for ARM architecture, not for a general PC. So for cross compile purpose, I am using Suse host machine.

With mkimage tool, I have created an RFS image from an RFS source of size 174MB. The Image I got has a size of 10 MB approximately. I have used the mentioned script file, to make use of mkimage tool

But it is throwing me an error while doing cp, " No space left on device". So I have come to one colclusion that the 10MB is not the actual size of the image.


cp: writing `rfs_image_v.4_mount/bin/cp': No space left on device


Please give me advice ..

Regards
SJR

thanks for the reply....

My RFS source is of size of 174 MB.

I have modifies "dd if=/dev/zero of=$RD_TEMP_FILE bs=1024k count=20" with count=180 , so space problem during copying got solved.

Is it the correct way to solve this issue.?

Please help me out

Regards
SJR

[gogalthorp]

dd is a raw copy method.

If it works it is correct