From owner-freebsd-sysinstall@FreeBSD.ORG Sat Nov 22 00:03:45 2014 Return-Path: Delivered-To: freebsd-sysinstall@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1025C749; Sat, 22 Nov 2014 00:03:45 +0000 (UTC) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id AFD3DF9E; Sat, 22 Nov 2014 00:03:44 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.9/8.14.9) with ESMTP id sAM03g75053115 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 21 Nov 2014 17:03:42 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.9/8.14.9/Submit) with ESMTP id sAM03gLp053112; Fri, 21 Nov 2014 17:03:42 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Fri, 21 Nov 2014 17:03:42 -0700 (MST) From: Warren Block To: Nathan Whitehorn Subject: Re: Dangerously dedicated mode with FreeBSD 10.1 In-Reply-To: <546FC5C8.7020303@freebsd.org> Message-ID: References: <546F6D79.9060909@freebsd.org> <546FBEC0.500@freebsd.org> <546FC5C8.7020303@freebsd.org> User-Agent: Alpine 2.11 (BSF 23 2013-08-11) 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]); Fri, 21 Nov 2014 17:03:42 -0700 (MST) Cc: Rostislav Krasny , freebsd-sysinstall@freebsd.org X-BeenThere: freebsd-sysinstall@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Sysinstall Work List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Nov 2014 00:03:45 -0000 On Fri, 21 Nov 2014, Nathan Whitehorn wrote: >> This might be an "Advanced Format" thing, where the drive uses 4K sectors >> but reports that it uses 512-byte sectors. The forum thread shows that it >> does not align to 4K on SSDs. My SSDs also report 4K stripesize but only >> 512 byte sectoresize. >> > > Sure, but the installer aligns to the reported "stripe size". For AF disks > like your SSD, the kernel reports the right thing in the stripe size. > > Where in the forum thread does it show an issue? The only thing I see is some > gpart output from a 10K spinning SAS disk, which almost certainly has > 512-byte physical sectors. Hmm, I thought that was still about an SSD. I sent a followup asking for the block size of the drive. I set out to test this on a machine with an SSD, but can't get an install image to work from my PXE setup (it can't find the install disk label), and have no easily-accessible DVD drives or empty memory sticks right now. It seems like it should be easier than this. Anyway, for now let's say it works.