Extend Vol1 not taking space from vol2

[kolpesandeep]

Hello,
I have free NAS 11. Intially I have create Vol1 of 20 TB , after that I have extended the existing vol1 by adding 27 TB vol2.
It shows me th volume extended and size is 45 TB , however when I tried to upload data my volume is getting hung and saying no space available.
I have checked datastore 1 is getting out of space . It is not taking space from datastore 2
Not able to understand how the extended volume is working.
Created VM FREE NAS 11.1 on esxi 6.5
datastore1 20 TB
datastore2 27 TB

please find the attached screenshot for details.
please help me to resolve this issue.

 

[danb35]

There's a great deal wrong here, not least that you're running a five-year-old version of FreeNAS; more than that, that you're running it as a VM; and yet more than that, you're feeding it virtual disks for storage. What's the output of zpool status and zpool list?

 

[kolpesandeep]

Hello Danb,
Thanks for your response.yes I have installed this set up five years ago. Last year I have updated the disk space and created datastore2. Which is 27 TB and extended exsiting Vol1 successfully.
Fre NAS shell it shows me 45 TB for Vol1 please find the attached out put and more details.

 

[kolpesandeep]

Hello @danb35 ,
Please find the attached screenshot for details.
Need help to resolve this issue

 

[danb35]

There is no screenshot attached to your last post, and the one before that didn't give the information I asked for. But your setup is so wrong in so many ways that I don't think I'm going to be able to help you further.

 

[HoneyBadger]

Best I can make of this is that you've somehow mounted "vol2" inside of "vol1" (did you do this manually through a command line?) rather than extending the pool. But you've reached a point where this is not a situation that can be easily salvaged, if at all possible.

I would suggest that if you haven't already extended the pool onto that 27TB secondary disk, you don't do it. You may be need to use those disks as a holding area for your data in order to rescue it and make it available elsewhere.

What's the output of zpool status and zpool list?

Please connect to your FreeNAS machine over SSH and post this output using the "CODE" tags in the forum, so we can see if this can be salvaged.

Code:

Using CODE tags will result in better formatted text, such as this.

 

[kolpesandeep]

Best I can make of this is that you've somehow mounted "vol2" inside of "vol1" (did you do this manually through a command line?) rather than extending the pool. But you've reached a point where this is not a situation that can be easily salvaged, if at all possible.

I would suggest that if you haven't already extended the pool onto that 27TB secondary disk, you don't do it. You may be need to use those disks as a holding area for your data in order to rescue it and make it available elsewhere.



Please connect to your FreeNAS machine over SSH and post this output using the "CODE" tags in the forum, so we can see if this can be salvaged.

Code:

Using CODE tags will result in better formatted text, such as this.

 

[kolpesandeep]

There is no screenshot attached to your last post, and the one before that didn't give the information I asked for. But your setup is so wrong in so many ways that I don't think I'm going to be able to help you further.

Hello @danb35
Please find attached screenshot for zpool status and zpool list

 

[kolpesandeep]

Hello @danb35
Please find attached screenshot for zpool status and zpool list

I have extended Vol1 successfully, however it is showing disk full error in vmware.

 

[HoneyBadger]

Warning: You have painted yourself into a very small and perilous corner with the use of vDisks on a RAID controller. Proceed with extreme caution.

Hello @danb35
Please find attached screenshot for zpool status and zpool list

According to this screenshot, you have a stripe pool (no ZFS redundancy) which will not give ZFS any capability to correct errors it detects. On the plus side, you could theoretically still remove a device and use the other one as a holding space to rebuild - and you should rebuild, because this configuration is pathologically bad for your data's health. While it is possible to run TrueNAS in a virtual environment, there are quite a few guidelines and precautions outlined, which unfortunately don't seem to have been followed here.

Yes, You Can (Still) Virtualize TrueNAS

TrueNAS is a powerful storage virtualization software solution that helps businesses virtualize data. Get started today with TrueNAS.

www.truenas.com

You will need to know how your existing drives are connected, and whether or not you would be able to add a PCIe HBA (Host Bus Adapter) to your current system, as well as isolate all of the drives making up the "datastore2" storage from what I assume is a RAID controller. This may or may not be possible, depending on your system/storage backplane. If it is a whitebox tower build without hotswap, it may be more plausible, as you can directly connect the "datastore2" drives to the new HBA.

I have extended Vol1 successfully, however it is showing disk full error in vmware.

That's a VMware level error in that it is attempting to write to the VMDK, but cannot do so because the underlying VMFS volume is out of space. Did you create the main disk as a thin VMDK? If not, do you have other VMs sharing this datastore, have it configured as a log/scratch datastore, or any other things that would have consumed space (snapshots?)

You may be able to recover a small amount of space from "datastore1" by powering off the FreeNAS VM, reserving all of its memory (which eliminates the 16GB .vswap file on the datastore) and then powering it on again. If you are able to do this, you should likely remove the "vol2" disk (as it is presumably almost completely empty) and use its space to begin bootstrapping either a supported and healthy hardware configuration either on the existing hardware (using a PCIe-passthrough HBA) or on a separate bare-metal system.