SOLVED ZFS pool size is not shown at SMB shares

s0mm3r

Dabbler
Joined
Jul 25, 2018
Messages
31
the solution is here: post 26

Hi
I've replaced all 2TB disks in my pool with 3TB disks (6 disks in z2)
yesterday only one of the SMB shares showed the new size (10.5TB)
today I rebooted the server cause the other two were still showing the old size
but now none of the three shares shows the new size

what could that be?

all disks are resilvered
autogrow is enabled
'zfs list poolname' shows the correct size

My system details are in my signature

thanks
regards
 
Last edited:

s0mm3r

Dabbler
Joined
Jul 25, 2018
Messages
31
bump
 

Arubial1229

Dabbler
Joined
Jul 3, 2017
Messages
22
snapshots?
 

s0mm3r

Dabbler
Joined
Jul 25, 2018
Messages
31
there is no new data since the HDD swap
and nothing was deleted, the snapshots only take GBs
 
Last edited:

Chris Moore

Hall of Famer
Joined
May 2, 2015
Messages
10,080
Did you establish any quota or limits?
 

s0mm3r

Dabbler
Joined
Jul 25, 2018
Messages
31
nope no quotas defined

but I noticed today that the size is shrinking when copying new data onto it
I've copied 380GB on a share and all of the shares on this pool decreased by that amount
before they showed somewhat like "2 TB free of 6.8 TB" and now "2 TB free of 6.4 TB"

the shares are mounted on windows 10 only
 

s0mm3r

Dabbler
Joined
Jul 25, 2018
Messages
31
I think the problem might be the dataset?
As you can see the pool 'Media' shows the new size
but the dataset underneath has almost 4TiB less
it's the only dataset on this pool
1549985618448.png
 

SweetAndLow

Sweet'NASty
Joined
Nov 6, 2013
Messages
6,421
That is because the root dataset shows raw space. The dataset under that shows usable storage. You can almost be positive their is not a problem. You just are not understanding the numbers and how they work.
 

s0mm3r

Dabbler
Joined
Jul 25, 2018
Messages
31
That is because the root dataset shows raw space. The dataset under that shows usable storage. You can almost be positive their is not a problem. You just are not understanding the numbers and how they work.
I guess you are right and I don't understand the numbers

would you mind to clarify it a bit?

it's a ZFS Z2 Pool with 6x3TB HDD
this should result in 10.494 TiB of useable space
where do I lose another 4 TiB?
4TiB is pretty massive

thanks
 

Chris Moore

Hall of Famer
Joined
May 2, 2015
Messages
10,080

SweetAndLow

Sweet'NASty
Joined
Nov 6, 2013
Messages
6,421
I guess you are right and I don't understand the numbers

would you mind to clarify it a bit?

it's a ZFS Z2 Pool with 6x3TB HDD
this should result in 10.494 TiB of useable space
where do I lose another 4 TiB?
4TiB is pretty massive

thanks
6.9+3.6= 10.5 why you think you are missing space?
 

Chris Moore

Hall of Famer
Joined
May 2, 2015
Messages
10,080
I've replaced all 2TB disks in my pool with 3TB disks (6 disks in z2)
Not to be critical, but why would you go from 2TB to 3TB? In a RAIDz2 pool of just six drives, that only gets you a very small size increase.

1549987841035.png
 

s0mm3r

Dabbler
Joined
Jul 25, 2018
Messages
31
Not to be critical, but why would you go from 2TB to 3TB?

because when I first created the pool a year ago I only had 2x3TB and 4x2TB and decided to swap the 2TB later, which I did now
 

s0mm3r

Dabbler
Joined
Jul 25, 2018
Messages
31
6.9+3.6= 10.5 why you think you are missing space?
ok, silly me didn't see that
but that still does not explain why the SMB shares are not showing the 10.5TB

when the resilver was finished one of the three shares on this dataset showed 10.5TB as total space
now all of them are below 6
1549990816705.png

and that's what I don't understand
why did it show 10.5 in the first place?
I then restarted the server because the other two where not showing the new size and reboot of the smb service didn't help

and why is the total space decreasing when adding data to them?
is that because of the snapshots?
do they eat away the total available space?

I never saw such a behavior on a windows file server (sorry but I had to say that)

thank you
 

Chris Moore

Hall of Famer
Joined
May 2, 2015
Messages
10,080
and why is the total space decreasing when adding data to them?
The free space is decreasing.
I think that what you need to do is go to a terminal window on the NAS and look at the output of the zpool list command.
Should look something like this:
Code:
root@Emily-NAS:~/scripts # zpool list

NAME           SIZE  ALLOC   FREE  EXPANDSZ   FRAG    CAP  DEDUP  HEALTH  ALTROOT
Backup        21.8T  16.4T  5.34T         -     0%    75%  1.00x  ONLINE  /mnt
Emily         43.5T  16.6T  26.9T         -     0%    38%  1.00x  ONLINE  /mnt
Irene         43.5T  17.1T  26.4T         -     0%    39%  1.00x  ONLINE  /mnt
freenas-boot  37.2G  10.4G  26.9G         -      -    27%  1.00x  ONLINE  -

That will show you the total size, how much is used and how much is free as well as how fragmented it is and what percentage of the total capacity is used. Pretty useful, I think.
 

s0mm3r

Dabbler
Joined
Jul 25, 2018
Messages
31
The free space is decreasing.
I meant the total size of the SMB shares, of course the free space decreases
but every time I copy new data on the shares the total size decreases as well
you know, this part:
1549994917108.png

I've just copied 45GB to one share on that dataset
and the total space of all shares decreased:
1549996081738.png

of course the free space decreased too
but the free space is always the same size on all shares, no differences there

zpool list:
this looks correct I'd say
Code:
root@freenas:/ # zpool list Media
NAME    SIZE  ALLOC   FREE  EXPANDSZ   FRAG    CAP  DEDUP  HEALTH  ALTROOT
Media  16.3T  10.4T  5.89T         -     1%    63%  1.00x  ONLINE  /mnt
root@freenas:/ #


again: my problem is not the pool, it's the shares
why are the shares not showing the actual total space of the dataset?
can this be configured somehow?
is there a flag that can be set?
did I misconfigure something in the smb settings?
1549995617836.png

1549995590260.png


or maybe at the share itself?

1549995694189.png

1549995717030.png


the other two shares have this objects:

1549996390831.png


this is the snapshot space on that dataset for those three shares:
Code:
root@freenas:/ # zfs list -r -o space,refer,written -t all Media/Filme | head -2
NAME                               AVAIL   USED  USEDSNAP  USEDDS  USEDREFRESERV  USEDCHILD  REFER  WRITTEN
Media/Filme                        3.54T  2.11T     16.0G   2.09T              0          0  2.09T    5.31M
root@freenas:/ # zfs list -r -o space,refer,written -t all Media/Serien | head -2
NAME                                AVAIL   USED  USEDSNAP  USEDDS  USEDREFRESERV  USEDCHILD  REFER  WRITTEN
Media/Serien                        3.54T  2.26T      127G   2.13T              0          0  2.13T    44.8G
root@freenas:/ # zfs list -r -o space,refer,written -t all Media/Spiele | head -2
NAME                                AVAIL   USED  USEDSNAP  USEDDS  USEDREFRESERV  USEDCHILD  REFER  WRITTEN
Media/Spiele                        3.54T  1.76T     2.06M   1.76T              0          0  1.76T     352K
root@freenas:/ #


thank you
 
Last edited:

Chris Moore

Hall of Famer
Joined
May 2, 2015
Messages
10,080
but the free space is always the same size on all shares, no differences there
If all of these shares are mapped to different directories in the same FreeNAS dataset, the info for the dataset is going to be the same for all the shares. You would need to create separate datasets for FreeNAS to report the space separately.
Would you show the output of df -h?
 

Arubial1229

Dabbler
Joined
Jul 3, 2017
Messages
22
This is normal behavior when you have multiple datasets. Mine do the same thing. The total size of the mapped drives will decrease as data is written to them.

Edit: nevermind, after checking your screenshot, I noticed you said it's the only dataset in the pool
 

s0mm3r

Dabbler
Joined
Jul 25, 2018
Messages
31
Thanks for your help so far but can somebody answer this?
why are the shares not showing the actual total space of the dataset?
can this be configured somehow?
 
Joined
Jul 3, 2015
Messages
926
I may be missing this completely so if so please ignore but I add the below line to my SMB Global Auxiliary parameters to address reported size differences.

allocation roundup size = 4096
 
Top