From owner-freebsd-bugs@freebsd.org  Sat Aug 13 13:55:04 2016
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 65E6ABB85C6
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Sat, 13 Aug 2016 13:55:04 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 551E811F0
 for <freebsd-bugs@FreeBSD.org>; Sat, 13 Aug 2016 13:55:04 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u7DDt3JE039132
 for <freebsd-bugs@FreeBSD.org>; Sat, 13 Aug 2016 13:55:04 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 211361] suggested boot partition size is too small, bsdinstall
 creates unaligned partitions
Date: Sat, 13 Aug 2016 13:55:04 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: misc
X-Bugzilla-Version: 11.0-STABLE
X-Bugzilla-Keywords: patch, performance
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: des@FreeBSD.org
X-Bugzilla-Status: Open
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: mfc-stable11?
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-211361-8-M2U3xmeysz@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-211361-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-211361-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Aug 2016 13:55:04 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211361

--- Comment #21 from Dag-Erling Sm=C3=83=C2=B8rgrav <des@FreeBSD.org> ---
I don't want the 4k alignment to be a system policy, I want it to be an
installer policy.  And as I've mentioned repeatedly, we get the stripe size
wrong most of the time.  The only cases I know of in which we get it right =
are
a) directly connected AF SATA drives for which we have a quirk entry and b)
when using our own software RAID drivers.  None of the HW RAID controllers =
I've
encountered report a stripe size, and since they hide the identities of the
drives, we can't even apply quirks to individual drives.  Hypervisors (I've
tried VirtualBox, KVM and VMWare) don't report a stripe size either, even f=
or
paravirtualized storage.

--=20
You are receiving this mail because:
You are the assignee for the bug.=