Storage configuration/expansion

[mgreeny]

Hi All,

Would someone be able to briefly explain the image attached please?

I have four 500GB drives in a RAID-Z2 format, which should give me around 1TB usable storage. I want to expand NEWiSCSI which is being used in VMware as a 400GB datastore.

My issue is, when I attempt to extend NEWiSCSI I get an error saying that I should not use 80% of my available space for my zol, however I've only used 40%, I can't even give it 1 GB more.

Really confused by this!

Thanks

 

[SweetAndLow]

Hardware, version of FreeNAS and disk layout?

Sent from my Nexus 5X using Tapatalk

 

[mgreeny]

Hardware, version of freenas and disk layout?

Sent from my Nexus 5X using Tapatalk

Hi, thanks for your reply. i've got a Dell T20, 14GB Ram, Intel Pentium CPU G3220 @ 3.00GHz 4x500GB disks in Raid-Z2 layout. Version FreeNAS-9.10.1-U4

Thanks

 

[dlavigne]

Were you able to figure this out?

 

[mgreeny]

Hi,

Not yet, the screenshot doesn't tally with what i expect to be available. I should be able to allocate the entire storage to my iscsi pool but no luck.

Thanks

 

[darkwarrior]

Hi,

from a general point of view you should not expect to be able to use ALL your pool space, especially for zVols. ZFS is COW filesystem after all.
When you are reaching 90% or more hell breaks loose, many kitten die and some saw even pigs fly
It's not without reason, that the general recommendation is to stay under 50% used on your pool, in this kind of usage scenario.

That being said, you should technically still be able to resize that zVol (even if it's not recommended...).
But there is something that is puzzling me:
IIRC usually zVols appear just under the root dataset, Pool1 in your case.
But on your screenshot you have a child dataset NEWiSCSI.
Are you sure you are not using file extents ?
Or maybe you have configured a quota on that dataset ?

 

[mgreeny]

Hi,

from a general point of view you should not expect to be able to use ALL your pool space, especially for zVols. ZFS is COW filesystem after all.
When you are reaching 90% or more hell breaks loose, many kitten die and some saw even pigs fly
It's not without reason, that the general recommendation is to stay under 50% used on your pool, in this kind of usage scenario.

That being said, you should technically still be able to resize that zVol (even if it's not recommended...).
But there is something that is puzzling me:
IIRC usually zVols appear just under the root dataset, Pool1 in your case.
But on your screenshot you have a child dataset NEWiSCSI.
Are you sure you are not using file extents ?
Or maybe you have configured a quota on that dataset ?

Hi, thanks for getting back to me and so sorry for the delayed reply!

Looking at iSCSI it says i'm using Device Extents, not File extents.

Quota for the Pool1 dataset (and child datasets) are set to 0 which must mean no quota set.

Freenas is fully up to date, and has had a recent scrub. Not sure where to go from here?

Looking at this I wonder if i've created a zVOL within a Dataset within a Dataset and should be creating a zVOL within a Dataset (just one)...

 

[darkwarrior]

Hi, thanks for getting back to me and so sorry for the delayed reply!

Looking at iSCSI it says i'm using Device Extents, not File extents.

Quota for the Pool1 dataset (and child datasets) are set to 0 which must mean no quota set.

FreeNAS is fully up to date, and has had a recent scrub. Not sure where to go from here?

Looking at this I wonder if i've created a zVOL within a Dataset within a Dataset and should be creating a zVOL within a Dataset (just one)...

Hi there,
it looks like you have been tinkering with the zfs command line, because when using the webinterface all zVols are created at the root of your pool ;)
Maybe you wanna start there and create a new zvol and see if you can increase the size afterwards, like you tried to do :)

 

[mgreeny]

Hi,

OK so this is a strange but it's fixed at least. Thanks Darkwarrior for your help. When I was resizing the zVOL I was originally putting 500G (and getting that error message). However, when I tried putting 500GiB it worked!

When I originally created the zVOL I just used the G, not the GiB notation.

Bug perhaps?

 

[mgreeny]

Looks like it
https://bugs.pcbsd.org/issues/11587

 

[pirateghost]

Hi there,
it looks like you have been tinkering with the zfs command line, because when using the webinterface all zVols are created at the root of your pool ;)
Maybe you wanna start there and create a new zvol and see if you can increase the size afterwards, like you tried to do :)

You can create zvols wherever you like...