From owner-freebsd-current@FreeBSD.ORG Sun Jun 9 04:56:27 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 514BF69A; Sun, 9 Jun 2013 04:56:27 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id EC77E1103; Sun, 9 Jun 2013 04:56:26 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.7/8.14.7) with ESMTP id r594uPhx067455; Sat, 8 Jun 2013 22:56:25 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.7/8.14.7/Submit) with ESMTP id r594uPXd067452; Sat, 8 Jun 2013 22:56:25 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Sat, 8 Jun 2013 22:56:25 -0600 (MDT) From: Warren Block To: Glen Barber Subject: Re: 10-CURRENT i386 memstick snapshots broken? In-Reply-To: <20130609005348.GG13292@glenbarber.us> Message-ID: References: <20130607205129.GA1103@jmobile.jimmy.net> <20130607212256.GG38117@glenbarber.us> <20130608173411.GD13292@glenbarber.us> <20130609.050100.598816322573845734.hrs@allbsd.org> <20130609005348.GG13292@glenbarber.us> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Sat, 08 Jun 2013 22:56:25 -0600 (MDT) Cc: jimmy.kelley@charter.net, freebsd-current@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Jun 2013 04:56:27 -0000 On Sat, 8 Jun 2013, Glen Barber wrote: > The problem is creating the gpart(8) partition scheme on the md(4) > device. > > Below follows script(1) output of what the make-memstick.sh script does: > > Script started on Sun Jun 9 00:41:08 2013 > root@snap:/snap/releng # chroot /snap/releng/10-i386-snap > root@snap:/ # cd /usr/obj/usr/src/release > root@snap:/usr/obj/usr/src/release # echo \ > '/dev/ufs/FreeBSD_Install / ufs ro,noatime 1 1' > release/etc/fstab > root@snap:/usr/obj/usr/src/release # makefs -B \ > little -o label=FreeBSD_Install test.img release > Calculated size of `test.img': 649420800 bytes, 12922 inodes > Extent size set to 8192 > test.img: 619.3MB (1268400 sectors) block size 8192, fragment size 1024 > using 12 cylinder groups of 54.40MB, 6963 blks, 1152 inodes. > super-block backups (for fsck -b #) at: > 32, 111440, 222848, 334256, 445664, 557072, 668480, 779888, > 891296, 1002704, 1114112, 1225520, > Populating `test.img' > Image `test.img' complete > root@snap:/usr/obj/usr/src/release # mdconfig -a -t vnode -f test.img > md0 > > All fine up until this point. Now the gpart(8) partition is created: > > root@snap:/usr/obj/usr/src/release # gpart create -s BSD /dev/md0 > gpart: Inappropriate ioctl for device > root@snap:/usr/obj/usr/src/release # gpart list md0 > Segmentation fault (core dumped) This might be a good time to stop using a bare bsdlabel (aka "dangerously dedicated"). MBR plus bsdlabel is not great, but more widely understood, and other operating systems will at least recognize the MBR slice. I can help with this if needed.