On Mon, Nov 05, 2007 at 05:00:06PM +0000, Christopher Key wrote: > The problem is, I'm sure, is essentially identical to that described in, > > http://www.mail-archive.com/[EMAIL PROTECTED]/msg21675.html > > namely that the entry for the memory filesystem, /tmp, in /etc/fstab is > confusing fsck. My /etc/fstab looks like, > > # cat /etc/fstab > # Device Mountpoint FStype Options Dump > Pass# > /dev/ad8s1b none swap sw 0 0 > /dev/ad8s1a / ufs rw 1 1 > md /tmp mfs rw,-s64m > 2 2 > /dev/ad8s1f /usr ufs rw 2 2 > /dev/ad8s1e /var ufs rw 2 2 > /dev/ad8s1d /var/tmp ufs rw 3 3 > /dev/mirror/gm0s1d /svn ufs rw 2 2 > /dev/mirror/gm0s2d /data ufs rw 2 2 > /dev/mirror/gm0s3d /music ufs rw 2 2 > > I can get the system to boot quite happily by carrying on into single > user mode and exiting, but I still get the same behaviour next reboot. > > Does anyone have any suggestions?
mount_mfs(8), in the EXAMPLES section, says this: Create and mount a 32 megabyte swap-backed file system on /tmp: mdmfs -s 32m md /tmp The same file system created as an entry in /etc/fstab: md /tmp mfs rw,-s32m 2 0 Try setting the passno field (the last one) to 0, and see how that works. Dan -- Daniel Bye _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \
Description: PGP signature