SOLVED Please Help! Problem with growing file extent

[Gregorio Silveira]

Hi,

I needed to grow a file that is in use on my VMWare 1.8T to 2.3T.

Performed procedures:

File Extent Based LUN:

1) Before growing the file extent based LUN, make sure all que initiators are disconnected. Stop the iSCSI service in Control Services.
2) Then, go to Services → iSCSI → File → View File Extents Extents to determine the path of the file extent to grow. Open Shell to grow the extent. This example grows / mnt / volume1 / data by 2G:
truncate -s + 500g / mnt / zfspool / vmware18TB
3) Go back to Services → iSCSI → File → View File Extents Extents and click the Edit button for the file extent. Set the size to the 0 this causes the iSCSI target to use the existing size of the file.
4) You can now start the iSCSI service and allow initiators to connect.

I did not add 500GB and reading the "man truncate" I decided to run: truncate -s + 500G /mnt/zfspool/vmware18TB

I run -s +500g and +500G :(

The amendment was:

1979657800908800
1980194671820800

When I remounted this LUN for VMWare it showed me the 1.8TB again.

Where is my mistake?

Thanks a lot.

 

[dlavigne]

You still have to tell VMFS about the increased size. Refer to the vmware docs for instructions on how to do that.

 

[jgreco]

In the C client, Home->Inventory->Hosts/Clusters, select ${host}, Configuration, Hardware->Storage, Datastores, select ${datastore}, Datastore Details-> Properties (righthand top of region), popup window->Volume Properties->Increase

 

[Gregorio Silveira]

Why can I use only 2TB on this filesystem?

Something is wrong.

The area added using truncate was not added to the file, from what I understand.

 

[Gregorio Silveira]

After truncate should be a 2.3TB file, and is to:
[root @ Segnas] ~ # ls -lrt / mnt / zfspool / vmware18TB
-rw-r - r-- 1 root wheel 1980194671820800 Dec 19 12:19 / mnt / zfs pool / vmware 18TB
1980194671820800 bytes
terabytes 1800.9765625

 

[jgreco]

There's something you need to twiddle IIRC to enable > 2TB LUN support. Versions of ESXi prior to 5mumble only supported 2TB.

http://blogs.vmware.com/vsphere/2011/07/new-vsphere-50-storage-features-part-1-vmfs-5.html

 

[cyberjock]

Also note that if you are doing iSCSI for FreeNAS, you should stick to zvols because the performance can be massively faster than file-based. ;)

 

[Gregorio Silveira]

thanks brothers!

everything is working as it should!

 

[jgreco]

It's always nice to hear a positive report back. Thanks.