<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8"> <META NAME="GENERATOR" CONTENT="GtkHTML/3.32.2"> </HEAD> <BODY> As others have pointed out, setting autoexpand=on on the pool is the key to making use of any new space allocated to your drive. As a test, I created a 30GB drive and created a new pool. I then expanded that drive to 50GB. The size of the pool didn't change until I turned on autoexpand on the pool. This was done in a VM and not with a iscsi target lun but the principle should apply the same. <PRE> <A HREF="mailto:root@omnios1">root@omnios1</A>:~# zpool create tank0 /dev/rdsk/c1t2d0 <A HREF="mailto:root@omnios1">root@omnios1</A>:~# zpool list NAME SIZE ALLOC FREE EXPANDSZ CAP DEDUP HEALTH ALTROOT rpool 15.9G 2.51G 13.4G - 15% 1.00x ONLINE - tank0 29.8G 156K 29.7G - 0% 1.00x ONLINE - <A HREF="mailto:root@omnios1">root@omnios1</A>:~# zpool get autoexpand tank0 NAME PROPERTY VALUE SOURCE tank0 autoexpand off default <A HREF="mailto:root@omnios1">root@omnios1</A>:~# prtvtoc /dev/rdsk/c1t2d0s0 * /dev/rdsk/c1t2d0s0 partition map * * Dimensions: * 512 bytes/sector * 62914560 sectors * 62914493 accessible sectors * * Flags: * 1: unmountable * 10: read-only * * Unallocated space: * First Sector Last * Sector Count Sector * 34 222 255 * * First Sector Last * Partition Tag Flags Sector Count Sector Mount Directory 0 4 00 256 62897887 62898142 8 11 00 62898143 16384 62914526 </PRE> --- Expanded /dev/rdsk/c1t2d0 to 50GB --- <PRE> <A HREF="mailto:root@omnios1">root@omnios1</A>:~# zpool list NAME SIZE ALLOC FREE EXPANDSZ CAP DEDUP HEALTH ALTROOT rpool 15.9G 2.51G 13.4G - 15% 1.00x ONLINE - tank0 29.8G 130K 29.7G 20G 0% 1.00x ONLINE - <A HREF="mailto:root@omnios1">root@omnios1</A>:~# zpool get autoexpand tank0 NAME PROPERTY VALUE SOURCE tank0 autoexpand off default <A HREF="mailto:root@omnios1">root@omnios1</A>:~# zpool set autoexpand=on tank0 <A HREF="mailto:root@omnios1">root@omnios1</A>:~# zpool list NAME SIZE ALLOC FREE EXPANDSZ CAP DEDUP HEALTH ALTROOT rpool 15.9G 2.51G 13.4G - 15% 1.00x ONLINE - tank0 49.8G 200K 49.7G - 0% 1.00x ONLINE - <A HREF="mailto:root@omnios1">root@omnios1</A>:~# prtvtoc /dev/rdsk/c1t2d0 * /dev/rdsk/c1t2d0 partition map * * Dimensions: * 512 bytes/sector * 104857600 sectors * 104857533 accessible sectors * * Flags: * 1: unmountable * 10: read-only * * Unallocated space: * First Sector Last * Sector Count Sector * 34 222 255 * * First Sector Last * Partition Tag Flags Sector Count Sector Mount Directory 0 4 00 256 104840927 104841182 8 11 00 104841183 16384 104857566 </PRE> <TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%"> <TR> <TD> -- Scott LeFevre </TD> </TR> </TABLE> On Thu, 2014-02-27 at 09:54 +0000, Svavar Örn Eysteinsson wrote: <BLOCKQUOTE TYPE=CITE> Hello List. </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> I'm experimenting with ZFS on a iSCSI target. </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> Currently I have a OmniOS server which is a iSCSI initiator to a iSCSI target </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> located out on the public internet from my hosting provider. </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> As for now the iSCSI target is about 300GB which I have managed to connect </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> and created a ZFS pool on the target. </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> Now for the questions, what would the scenario be if I asked my provider </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> to extend (grow) the iSCSI target, and how will my ZFS OmniOS box see </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> the new size ? Do I need any to scrub the pool, or how to I grow my pool </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> to the new size provided by my hosting provider ? </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> As before, now I have a 300GB ZFS pool on the iSCSI target. </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> Which I have mounted and everything seems to work fine. </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> Later the iSCSI target will be grown to 500GB. Are there anything </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> special work that needs to be done regarding growing the ZFS datapool from 300GB to 500GB. </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> (those extra 200GB) ? </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> Thanks in advance people. </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> Best regards, </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> Svavar O - Reykjavik - Iceland </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> <PRE> _______________________________________________ OmniOS-discuss mailing list <A HREF="mailto:OmniOS-discuss@lists.omniti.com">OmniOS-discuss@lists.omniti.com</A> <A HREF="http://lists.omniti.com/mailman/listinfo/omnios-discuss">http://lists.omniti.com/mailman/listinfo/omnios-discuss</A> </PRE> </BLOCKQUOTE> </BODY> </HTML>