Mapped network drive capacity is shrinking

[nMad]

I have the following pool and datasets:

And I have setup a CIFS share which is mounted to the 'data' dataset:

I mapped this share to a network drive in Windows 8.1:

When I copy files to the /data/videos dataset the available capacity of the mapped network drive is shrinking. It is now 9.71 TB instead of the initial 10.5 TB. However it should say "9.71 TB of 10.5 TB available", ZFSguru 10.1 shows this correctly.

Is there a way to avoid this without creating a share for each dataset? I want all of my data in one mapped network drive.

Code:

[root@nas ~]# zpool list                                                                                                        
NAME           SIZE  ALLOC   FREE  EXPANDSZ   FRAG    CAP  DEDUP  HEALTH  ALTROOT                                               
freenas-boot  14.5G   963M  13.6G         -      -     6%  1.00x  ONLINE  -                                                     
tank          16.2T  1.20T  15.0T         -     3%     7%  1.00x  ONLINE  /mnt 

Code:

[root@nas ~]# zfs  list                                                                                                         
NAME                                                   USED  AVAIL  REFER  MOUNTPOINT                                           
freenas-boot                                           962M  13.1G    31K  none                                                 
freenas-boot/ROOT                                      954M  13.1G    31K  none                                                 
freenas-boot/ROOT/FreeNAS-9.3-STABLE-201502162250      954M  13.1G   933M  /                                                    
freenas-boot/ROOT/Initial-Install                        1K  13.1G   932M  legacy                                               
freenas-boot/ROOT/default                               45K  13.1G   933M  legacy                                               
freenas-boot/grub                                     7.82M  13.1G  7.78M  legacy                                               
tank                                                   806G  9.70T   192K  /mnt/tank                                            
tank/.system                                          5.14M  9.70T  3.03M  legacy                                               
tank/.system/cores                                     192K  9.70T   192K  legacy                                               
tank/.system/rrd-5a1e22f5286d453ca9fcfb104651ce47      192K  9.70T   192K  legacy                                               
tank/.system/samba4                                    735K  9.70T   735K  legacy                                               
tank/.system/syslog-5a1e22f5286d453ca9fcfb104651ce47  1.02M  9.70T  1.02M  legacy                                               
tank/data                                              806G  9.70T   192K  /mnt/tank/data                                       
tank/data/videos                                       806G  9.70T   806G  /mnt/tank/data/videos   

 

[cyberjock]

There really isn't a "good" solution that I'm aware of. The problem is that each dataset (and the pool itself) are independent file systems. What you give to one you take away from the rest. I'm not aware of any way to make this work properly, hacky or otherwise. I'll ask a dev. If you don't hear back from me before the end of the weekend ask for me to respond in this thread.

 

[cyberjock]

Talked to a dev. He's gonna fix this...

https://bugs.freenas.org/issues/8134

 

[nMad]

Thanks cyberjock, that's really great! :)

Will this fix be a part of an upcoming update which I can install via the web GUI?

 

[gpsguy]

Yes

 

[cyberjock]

Yes. Please don't hold our feet to the fire if it takes more than a week. We're about to roll out TrueNAS 9.3, so that's taking up a lot of the developer's time. But I have no doubt it will be fixed. Just need John to have time to do it. ;)

 

[nMad]

I just installed the latest update and the reported size is correct now, thanks a lot!

 

[cyberjock]

You are welcome! Thanks for asking about it. It's been something that has been discussed before, but at the time it wasn't fixable. Now it was (and relatively easily), so we fixed it.

It never hurts to ask about fixing something. ;)