Hi!
Finnix 89.0 and 89.2 fails to boot on one of our servers here in 64-bit mode (x86-64).
When failing, it has the interesting error message:
"tmpfs: Bad value '-16587919k' for mount option 'size'"
The server in question is beefy, it has 16 detected cores and 32GB ram.
I tracked the failure down to this, in /isolinux/minirt:
--- tmp4/sbin/init 2006-10-17 10:10:05.000000000 +0200
+++ tmp5/sbin/init 2007-09-05 13:58:43.000000000 +0200
@@ -173,14 +173,20 @@
# New in Kernel 2.4.x: tmpfs with variable ramdisk size.
# We check for available memory anyway and limit the ramdisks
# to a reasonable size.
-FOUNDMEM="$(awk '/MemTotal/{print $2}' /proc/meminfo)"
-TOTALMEM="$(awk 'BEGIN{m=0};/MemFree|Cached/{m+=$2};END{print m}' /proc/meminfo)"
-# Never use more than 80% of the RAM available at this point
-RAMSIZE=$(expr $TOTALMEM \* 80 / 100)
-echo "${WHITE}[${BLUE}*${WHITE}]${NORMAL} Total memory: ${WHITE}${FOUNDMEM}k${NORMAL}, shared ramdisk: ${WHITE}${RAMSIZE}k${NORMAL}"
+#
+# // knan+finnix@linpro.no, 2007-09-05
+# // commented out the size calculations - unneeded in 2.6, and breaks on 32GB RAM servers
+# //
+# // FOUNDMEM="$(awk '/MemTotal/{print $2}' /proc/meminfo)"
+# // TOTALMEM="$(awk 'BEGIN{m=0};/MemFree|Cached/{m+=$2};END{print m}' /proc/meminfo)"
+# // Never use more than 80% of the RAM available at this point
+# // RAMSIZE=$(expr $TOTALMEM \* 80 / 100)
+# // echo "${WHITE}[${BLUE}*${WHITE}]${NORMAL} Total memory: ${WHITE}${FOUNDMEM}k${NORMAL}, shared ramdisk: ${WHITE}${RAMSIZE}k${NORMAL}"
echo -n "${WHITE}[${BLUE}*${WHITE}]${NORMAL} Setting up ramdisk... "
-mount -n -t tmpfs -o "size=${RAMSIZE}k" none /ramdisk
-mount -n -t tmpfs -o "size=${RAMSIZE}k" none /etc
+# // mount -n -t tmpfs -o "size=${RAMSIZE}k" none /ramdisk
+# // mount -n -t tmpfs -o "size=${RAMSIZE}k" none /etc
+mount -n -t tmpfs none /ramdisk
+mount -n -t tmpfs none /etc
for i in UNIONFS FINNIX cdrom dev initrd mnt proc selinux sys tmp tmp/UNIONFS tmp/FINNIX busybin; do
mkdir /ramdisk/$i
done(Hopefully bbpress doesn't mangle the patch too badly.)
Please consider including this patch or doing something similar in your next release. It's not as if the calculation is actually needed these days.