It could also be that you've run out of file system inodes. That's something that bit me on a recent project.
To find out, run "stat -f /" Regards, Jeremy Wood On Thu, Sep 13, 2012 at 8:01 AM, Peter Barada <[email protected]>wrote: > On 09/13/2012 10:48 AM, CB wrote: > > Hello! > > > > Today I ran into an odd problem. > > To avoid flashing my whole rootfs all over again on every try of my > tool, I > > wanted to install the generated RPM on the target. I fixed the paths > with --root > > and --prefix. Also the tmp-dir was set to point to the rootfs (ext2 > partition on > > a SD card). But 'rpm' fails during unpacking with "no space left on > device" > > despite 'df' shows 40MB of free space (rootfs is 100MB total). > > The rootfs image on the host machine is generated correctly containing > my tool. > > So the RPM file seems to be correct. > > Any suggestions on how to track down the problem? > You could try to strace the rpm command on the target to see where it > opens files for writing. It may be that RPM needs some temp files - do > you have a small ramfs mounted on /tmp? > > > > -- > Peter Barada > [email protected] > > > _______________________________________________ > LTIB home page: http://ltib.org > > Ltib mailing list > [email protected] > https://lists.nongnu.org/mailman/listinfo/ltib > -- - - - - - - - - - - - Jeremy Wood Ensemble Designs [email protected] www.ensembledesigns.com
_______________________________________________ LTIB home page: http://ltib.org Ltib mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/ltib
