From dfc9db7b2060dbc077bf2b49ada4389402c9f3ef Mon Sep 17 00:00:00 2001 From: obrien Date: Fri, 9 Mar 2001 01:03:15 +0000 Subject: newfs with `-m 1' This is needed even with `-o space' as the kernel decides to be "helpful" and not really do space optimization. Looking at src/sys/ufs/ffs/ffs_alloc.c we see why: if (fs->fs_minfree <= 5 || fs->fs_cstotal.cs_nffree > (off_t)fs->fs_dsize * fs->fs_minfree / (2 * 100)) break; log(LOG_NOTICE, "%s: optimization changed from SPACE to TIME\n" I have picked `1' vs. `0' just incase some code somewhere has the assumption the %free can never be `0'. Helped with understanding why -m 1 made a different: imp --- release/scripts/doFS.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'release') diff --git a/release/scripts/doFS.sh b/release/scripts/doFS.sh index 14a0ff0..0acd734 100644 --- a/release/scripts/doFS.sh +++ b/release/scripts/doFS.sh @@ -47,7 +47,7 @@ do fi fi disklabel -Brw /dev/${MDDEVICE} ${FSLABEL} - newfs -i ${FSINODE} -T ${FSLABEL} -o space /dev/${MDDEVICE}c + newfs -i ${FSINODE} -T ${FSLABEL} -o space -m 1 /dev/${MDDEVICE}c tunefs -m 0 /dev/${MDDEVICE}c mount /dev/${MDDEVICE}c ${MNT} -- cgit v1.1