From owner-freebsd-sysinstall@FreeBSD.ORG Fri Nov 21 23:00:59 2014 Return-Path: Delivered-To: freebsd-sysinstall@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0BC5F214; Fri, 21 Nov 2014 23:00:59 +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 AA011A3A; Fri, 21 Nov 2014 23:00:58 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.9/8.14.9) with ESMTP id sALN0ubl037042 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 21 Nov 2014 16:00:56 -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 sALN0ulh037038; Fri, 21 Nov 2014 16:00:56 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Fri, 21 Nov 2014 16:00:56 -0700 (MST) From: Warren Block To: Nathan Whitehorn Subject: Re: Dangerously dedicated mode with FreeBSD 10.1 In-Reply-To: <546FBEC0.500@freebsd.org> Message-ID: References: <546F6D79.9060909@freebsd.org> <546FBEC0.500@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 16:00:57 -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: Fri, 21 Nov 2014 23:00:59 -0000 On Fri, 21 Nov 2014, Nathan Whitehorn wrote: >>> This has never been true. It does 4K alignment on disks with 4K physical >>> sectors (no matter what the logical sector size is). If you have disks >>> with larger sectors or preferred boundaries (e.g. a striped RAID), it will >>> also align to that. >> >> I know that it did not automatically do that alignment originally, which >> was why I entered PR 161720: >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=161720 >> >> After that, I thought it was fixed, and now this appears to be a >> regression: >> http://forums.freebsd.org/threads/does-bsdinstall-in-10-1-properly-partition-ssds.48993/ >> > > It has done this since initially committed to the tree before 9.0. If you > have a drive with 512 byte physical sectors, it will use 512 byte alignment. > If you have a 4K drive, it will use 4K alignment. Is there anywhere in those > threads where it misaligns a partition? Most of the discussion just seems to > be that it does use 512 byte alignment sometimes, which isn't an issue if you > have 512 byte sectors. 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.