Date: Sat, 21 Oct 2000 19:42:13 +0900 From: Makoto MATSUSHITA <matusita@jp.FreeBSD.org> To: current@FreeBSD.ORG Subject: Re: current.freebsd.org problems? Message-ID: <20001021194213T.matusita@jp.FreeBSD.org> In-Reply-To: <20001021191803H.matusita@jp.FreeBSD.org> References: <20001020181137T.matusita@jp.FreeBSD.org> <200010210809.e9L89sk93221@zibbi.icomtek.csir.co.za> <20001021191803H.matusita@jp.FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
matusita> When I backout this change, the problem seems disappeared...
This is sample shell script to reproduce recent kernel hungup:
#!/bin/sh
dd of=/tmp/image if=/dev/zero count=1440 bs=1k
awk 'BEGIN {printf "%c%c", 85, 170}' | \
dd of=/tmp/image obs=1 seek=510 conv=notrunc
vnconfig -s labels -c /dev/rvn0 /tmp/image
disklabel -Brw /dev/rvn0 fd1440
newfs -i 80000 -T fd1440 -o space /dev/rvn0c
mount /dev/vn0c /mnt
cp /etc/rc /mnt
umount /mnt
vnconfig -u /dev/rvn0
exit 0
If you are running recent (at least Sep/30/2000) -current kernel, and
your newfs(8) is newer mkfs.c (rev 1.30) it will hungup as soon as
cp(1) is invoked.
-- -
Makoto `MAR' MATSUSHITA
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001021194213T.matusita>