Re: zpool asize problem on 11.0

2017-01-12 Thread Steven Hartland
On 12/01/2017 22:57, Stefan Bethke wrote: Am 12.01.2017 um 23:29 schrieb Stefan Bethke : I’ve just created two pools on a freshly partitioned disk, using 11.0 amd64, and the shift appears to be 9: # zpool status -v host pool: host state: ONLINE status: One or more devices are configured to u

Re: zpool asize problem on 11.0

2017-01-12 Thread Stefan Bethke
> Am 12.01.2017 um 23:29 schrieb Stefan Bethke : > > I’ve just created two pools on a freshly partitioned disk, using 11.0 amd64, > and the shift appears to be 9: > > # zpool status -v host > pool: host > state: ONLINE > status: One or more devices are configured to use a non-native block size

zpool asize problem on 11.0

2017-01-12 Thread Stefan Bethke
I’ve just created two pools on a freshly partitioned disk, using 11.0 amd64, and the shift appears to be 9: # zpool status -v host pool: host state: ONLINE status: One or more devices are configured to use a non-native block size. Expect reduced performance. action: Replace affected de

Re: Can't boot on ZFS -- /boot/zfsloader not found

2017-01-12 Thread Steven Hartland
On 12/01/2017 21:12, Jeremie Le Hen wrote: Hey Steven, (Please cc: me on reply) On Thu, Jan 12, 2017 at 1:32 AM, Steven Hartlan The reason I'd recommend 512k for boot is to provide room for expansion moving forward, as repartitioning to upgrade is a scary / hard thing to do. Remember it wasn't

Re: Can't boot on ZFS -- /boot/zfsloader not found

2017-01-12 Thread Jeremie Le Hen
Hey Steven, (Please cc: me on reply) On Thu, Jan 12, 2017 at 1:32 AM, Steven Hartlan > The reason I'd recommend 512k for boot is to provide room for expansion > moving forward, as repartitioning to upgrade is a scary / hard thing to do. > Remember it wasn't long ago when it was well under 64k and

Re: NFS and amd on older FreeBSD

2017-01-12 Thread Holger Kipp
Dear Karl, > On 12 Jan 2017, at 20:29, Karl Young wrote: > > Daniel Braniss(da...@cs.huji.ac.il)@2017.01.12 10:25:03 +0200: >> >>> On 12 Jan 2017, at 9:49 AM, Daniel Braniss wrote: >>> >>> On 12 Jan 2017, at 1:47 AM, Karl Young wrote: I inherited a lab that has a few hundred

Re: NFS and amd on older FreeBSD

2017-01-12 Thread Karl Young
Daniel Braniss(da...@cs.huji.ac.il)@2017.01.12 10:25:03 +0200: > > > On 12 Jan 2017, at 9:49 AM, Daniel Braniss wrote: > > > > > >> On 12 Jan 2017, at 1:47 AM, Karl Young wrote: > >> > >> I inherited a lab that has a few hundred hosts running FreeBSD 7.2. > >> These hosts run test scripts tha

Re: NFS and amd on older FreeBSD

2017-01-12 Thread Karl Young
Thanks Greg One correction. The new server is FreeBSD 9.2, not 9.3. Replies below Greg Byshenk(free...@byshenk.net)@2017.01.12 08:58:16 +0100: > On Wed, Jan 11, 2017 at 03:47:37PM -0800, Karl Young wrote: > > I inherited a lab that has a few hundred hosts running FreeBSD 7.2. > > These hosts ru

Re: NFS and amd on older FreeBSD

2017-01-12 Thread Daniel Braniss
> On 12 Jan 2017, at 9:49 AM, Daniel Braniss wrote: > > >> On 12 Jan 2017, at 1:47 AM, Karl Young wrote: >> >> I inherited a lab that has a few hundred hosts running FreeBSD 7.2. >> These hosts run test scripts that access files that are stored on >> FreeBSD 6.3 host. The 6.3 host exports a

Re: NFS and amd on older FreeBSD

2017-01-12 Thread Greg Byshenk
On Wed, Jan 11, 2017 at 03:47:37PM -0800, Karl Young wrote: > I inherited a lab that has a few hundred hosts running FreeBSD 7.2. > These hosts run test scripts that access files that are stored on > FreeBSD 6.3 host. The 6.3 host exports a /data directory with NFS > > [...] > > $ showmount -e 9