Switching to mkfs.cramfs (... removing /usr/bin/mkcramfs broke our scripts, but
I fixed that) causes the creation of the smaller second stage image to fail
Running mkcramfs /tmp/instimage.dir.20103
Exceeded MAXENTRIES. Raise this value in mkcramfs.c and recompile. Exiting.
The other mkcramfs changed the size of the entry_stack dynamically
The hard coded size is a new odd change by upstream...
Fixed. Please, update to util-linux >= util-linux-2.13-0.7.pre5.
This also seems to break other things in the image -- a number of the files end
up being zero length which shouldn't be. Backing the package out fixes things...
Please, show my a way how I can reproduce it.
I've tried extract files from stage2 and created image by old version (mkcramfs)
and by new version and there is no difference in the list of files (after mount
*** Bug 171574 has been marked as a duplicate of this bug. ***
I still cannot reproduce this bug.
mkfs.cramfs from util-linux-2.13-0.7.pre5:
# mount ./minstg2.img ./mountpoint -o loop
# ./mkfs.cramfs ./mountpoint ./minstg2.img-new
# mount ./minstg2.img-new ./mountpoint-new -o loop
# cd mountpoint <-- old image
# for f in `find ./ -type f | sort`; do md5sum $f; done > ../old
# cd ../mountpoint-new <-- new image
# for f in `find ./ -type f | sort`; do md5sum $f; done > ../new
# cd ..
$ md5sum old new
It meants that the contents of files in the images is same.
Try with stage2.img instead? I still haven't gotten to looking yet, too many
other things burning :/
My previous test has been on FC4 (with FC5 util-linux). Now I do same test with
same src.rpm on FC5 machine and it seems bad... So, I'm able to reproduce this
Fixed. Please, update to util-linux-2.13-0.10.pre5.