From owner-freebsd-bugs@freebsd.org Thu Sep 17 19:21:33 2015 Return-Path: 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 BC6ED9CECD0 for ; Thu, 17 Sep 2015 19:21:33 +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 8DE531F3F for ; Thu, 17 Sep 2015 19:21:33 +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 t8HJLXEh072222 for ; Thu, 17 Sep 2015 19:21:33 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 203180] bsdinstall 4K sector option could/should be persisted in /boot/loader.conf Date: Thu, 17 Sep 2015 19:21:33 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: 10.2-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: oliver@openbrackets.net X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit 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.20 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 19:21:33 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203180 Bug ID: 203180 Summary: bsdinstall 4K sector option could/should be persisted in /boot/loader.conf Product: Base System Version: 10.2-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: misc Assignee: freebsd-bugs@FreeBSD.org Reporter: oliver@openbrackets.net I wouldn't really classify this as a "bug", but really an improvement to the bsdinstall "experimental" zfs on root feature => sane defaults. If you choose "4K Sectors" during a zfs-on-root install in 10.2 RELEASE bsdinstall correctly sets vfs.zfs.min_auto_ashift=12 and creates the initial zroot pool vdev using 4K minimum sector size. In my case this was a 2-disk mirror. Further vdevs which are created, in my case with this command, adding a second mirror to the zroot pool: zpool add zroot mirror ada2 ada3 This results in the following sector sizes: root@zfsroot:~ # zdb -l /dev/ada0p3 | grep ashift ashift: 12 root@zfsroot:~ # zdb -l /dev/ada1p3 | grep ashift ashift: 12 root@zfsroot:~ # zdb -l /dev/ada2 | grep ashift ashift: 9 root@zfsroot:~ # zdb -l /dev/ada3 | grep ashift ashift: 9 ie, fine (following the installer option) on initial vdev, and back to the OS default for the next vdev. Knowing this I could easily set the sysctl before adding the mirror. My humble suggestion is that this might be a nice-to-have "sane default" set by bsdinstall. Given the sysadmin has chosen 4K sectors for the initial it is "reasonable" (?) to assume that this is a modern'ish machine and 4K sectors are better for the hardware or desired for other reasons. Further, future vdevs created are probably subject to the same context. Could bsdinstall just add the sysctl setting for 4K settings to /boot/loader.conf if that option is chose during install? After the initial reboot, the sysadmin would then naturally create vdevs of the same sector size as chosen at bootup or can change the setting back to 512b (ashift=9). It might be worth communicating this loader.conf adjustment to the sysadmin at an appropriate point. -- You are receiving this mail because: You are the assignee for the bug.