mlelstv@ wrote:
> r...@sdf.org (RVP) writes:
>
> >@@ -255,7 +255,7 @@
> > echo ${bar} Populating ffs filesystem ${bar}
> > ${MAKEFS} -rx ${endian} -N ${release}/etc -t ffs \
> > -O ${ffsoffset} \
> >- -o d=4096,f=8192,b=65536 -b $((${extra}))m \
> >+ -o d=8192,f=2048,b=16384 -b $((${extra}))m \
> > -F "$tmp/selected_sets" ${image} "${release}" "${mnt}"
>
>
> Sounds like the disklabel is incorrect then. FFS requires that
> the fragment size (not so much the blocksize) is correct, but the
> scripts seem to be inconsistent.
>
> N.B. unset fsize (== 0) defaults to fsize = BLKDEV_IOSIZE (== 2048).
I doubt recent newfs(8) or bootloaders refer bsize and fsize
in disklabel.
IIRC libsa/sa/ufs.c requires large heapsize to read blocksize,
from ffs, so sometimes it fails to load on blocksize=65536 fs.
(but I'm nots sure 64KB blocksize is valied on FFS because
newfs(8) man page just says 4KB-32KB for it)
---
Izumi Tsutsui
