Date: Wed, 1 Jun 2011 12:10:17 +0100 From: krad <kraduk@gmail.com> To: Daniel Kalchev <daniel@digsys.bg> Cc: freebsd-fs@freebsd.org Subject: Re: ZFS on 4K drives - Expanding zpool and adding spares (gnop method) Message-ID: <BANLkTikoT76J1C5mh6VzXrZJWB44Eo9%2B_w@mail.gmail.com> In-Reply-To: <4DE5F7A8.6020300@digsys.bg> References: <4DE5D7B1.5040902@decayingorbits.com> <20110601101924.11334wftbjfrvor0@webmail.leidinger.net> <4DE5F7A8.6020300@digsys.bg>
next in thread | previous in thread | raw e-mail | index | archive | help
On 1 June 2011 09:26, Daniel Kalchev <daniel@digsys.bg> wrote: > > > On 01.06.11 11:19, Alexander Leidinger wrote: > >> >> The 4k-sector part results in a pool specific config setting. I would >> expect that if you add additional drives (no matter if 4k or not), that the >> pool will continue to use 4k sectors. So I would expect that you do not need >> gnop to expend an existing pool, but I have not tested/verified this. >> >> >> The ashift property is per-vdev, so you have to use gnop for each new > vdev you add to the zpool. You also do not need to create gnop devices for > all new drives -- the vdev will use the largest sector size of any member to > calculate it's ashift value. > > For example, creating the pool > > gnop create -S 4096 disk0 > zpool create test mirror disk0.nop disk1 > zpool export test > gnop destroy disk0.nop > zpool import test > > adding another vdev > > gnop create -S 4096 disk2 > zpool add test mirror disk2.nop disk3 > zpool export test > gnop destroy disk2.nop > zpool import test > > Daniel > > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > i concur always use the gnop trick for new devices and you will be ok. Also make sure the gpt layout is 4k aligned
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BANLkTikoT76J1C5mh6VzXrZJWB44Eo9%2B_w>