Howto share a TrueNAS ramdisk? Network speed comparision

[flashdrive]

Hello,

how would I create an 8 GByte large ram disk in TrueNAS and share this via SMB?

 

[sretalla]

mkdir /mnt/RamDisk && mdmfs -M -S -o async -s 8192m md10 /mnt/RamDisk && chown root:wheel /mnt/RamDisk/ && chmod 0775 /mnt/RamDisk

Then configure your share using /mnt/RamDisk as the location.

 

[flashdrive]

mkdir /mnt/RamDisk && mdmfs -M -S -o async -s 8192m md10 /mnt/RamDisk && chown root:wheel /mnt/RamDisk/ && chmod 0775 /mnt/RamDisk

Then configure your share using /mnt/RamDisk as the location.

Hello @sretalla

thank you - I would never have guessed this command

 

[flashdrive]

Error "The path must reside within a volume mount point"

Workaround

shell

ln -s /mnt/pool/ramdisk /mnt/ramdisk

Reddit - The heart of the internet

www.reddit.com

FreeNAS: Share an arbitrary path via SMB

By default, FreeNAS/TrueNAS won't let you share a folder that's not part of its managed volumes, giving the error " The path must reside wi...

jb-weblog.blogspot.com

 

[Joel Golden]

The symbolic link does not show up in the NFS share GUI under TrueNAS-12.0-U7.

 

[anodos]

Code:

        if data['path']:
            await self.validate_path_field(data, schema_name, verrors, bypass=bypass)

            """
            When path is not a clustervolname, legacy behavior is to make all path components
            so skip this step here. This is a very rough check is to prevent users from sharing
            unsupported filesystems over SMB as behavior with our default VFS options in such
            a situation is undefined.
            """
            if not data['cluster_volname'] and os.path.exists(data['path']):
                fstype = (await self.middleware.call('filesystem.statfs', data['path']))['fstype']
                if fstype != 'zfs':
                    verrors.add(f'{schema_name}.path', f'{fstype}: path is not a ZFS dataset')

We do not support sharing non-ZFS volumes over SMB.

 

[anodos]

Any time you work around our middleware validation, you run risk of a future update breaking your workaround. Just FYI. We've been gradually adding more calls to realpath to resolve symlinks to avoid exposure of unexpected parts of filesystems over our file-sharing protocols.