SMB Share 0 bytes Available 0 bytes Used

[stadlereric]

After an upgrade to FreeNAS-11-MASTER-201710070509 from FreeNAS-11-MASTER-20170507 my SMB shares are now showing the used and available space as 0 bytes, which is causing issues for one of the applications we use here internally. I've tried re-mapping drives, and restarting the SMB service. Not sure what information would be required to troubleshoot this issue? I do see this in log.smbd

[2017/10/13 09:56:43.187116, 0] ../source3/smbd/dfree.c:124(sys_disk_free)
sys_disk_free: VFS disk_free failed. Error was : No such file or directory
[2017/10/13 09:56:45.008457, 0] ../source3/smbd/dfree.c:124(sys_disk_free)
sys_disk_free: VFS disk_free failed. Error was : No such file or directory
[2017/10/13 09:56:45.008990, 0] ../source3/smbd/dfree.c:124(sys_disk_free)
sys_disk_free: VFS disk_free failed. Error was : No such file or directory

 

[dlavigne]

Out of curiosity, why are you running nightlies instead of STABLE? Nightlies can be in a state of brokenness at any point in time.

 

[stadlereric]

wish I could remember why I went with that nightly, I built that instance of freenas around the time they announced that coral wasn't going to be continued. that may have had something to do with it.

I'll take that as good advice, and configure a new instance of freenas stable.

 

[anodos]

There were some changes to the samba vfs layer and disk_free function in 4.7. This broke zfs_space. Try removing the vfs object. I believe John recently did a PR with a fix.

 

[stadlereric]

Anodos thank you. After making that change and a restart of the SMB service I can see free and used space.

 

[anodos]

Anodos thank you. After making that change and a restart of the SMB service I can see free and used space.

On the bleeding-edge sometimes you bleed. ;-)