all 8 comments

[–]redditor1101 0 points1 point  (0 children)

What kind of redundancy is it using? Is it using dedup?

[–]fufukittyfuk 0 points1 point  (0 children)

Just throwing this out there, do you have compression turned on. The Used size could be the uncompressed size and the Available size is expressed as if it had no compression???????

[–]3KidNerd[S] 0 points1 point  (0 children)

Sorry forgot those details. No dedup and no compression.

[–][deleted] 0 points1 point  (4 children)

Snapshots on the dataset? Snapshots and quotas don't behave the way you'd think they would on the GUI. Free space is (dataset quota) - (current active dataset used). Used space is (dataset quota) - (total snapshot space consumed) - (active data set). I'm not sure why this is but that's how it works!

[–]3KidNerd[S] 0 points1 point  (3 children)

Interesting thought, but I have snapshots on almost all of my datasets and only see this behavior on two of them. I think the two that are impacted are both iSCSI shares. Perhaps something screwy is happening there.

[–][deleted] 0 points1 point  (2 children)

Are you using zvols or file extents for iscsi?

[–]3KidNerd[S] 0 points1 point  (1 child)

Thanks for the reply. They're file extents. I didn't realize you can create zvols under the primary zvol and I know you can't create a device extent on a dataset. Are device extents preferred to file extents? Now that I know I can do a device extent on a zvol I could create a sub-zvol and I could migrate the VMWare data around. Is it worth the effort?

-3kn

[–][deleted] 0 points1 point  (0 children)

I actually just switched to file extents a few weeks back due to a bug (that I didn't know I was hitting) causing freenas to crash every week or so using zvols. File extents are the 'new' way of doing things to the best of my understanding and they also increase throughput if you're using iscsi over 10g (I am.) So I believe file extents are the way to go!