Extremely useful rundown. You wouldn't believe how hard it is to find straightforward and good documentation on TrueNAS. I appreciate the video and help! Consider my donation as a small portion of savings I have now that I don't need to pay google or otherwise for cloud storage!
Thank you very much! Could not figure out where I was going wrong with my TrueNAS NFS config. Slowly reviewing what I had based off of your tutorial did the trick!
It seems a lot more difficult than it needs to be to configure Just read that v2 came out in 1989 which is when I was programming mainframe computers so I guess it's not surprising Even though it's still going with v4.2 released in 2016 it still feels old school Mind you it's faster than SMB so I still plan on using it
Thank you for making the most in-depth tutorial on TrueNAS and the NFS protocol. Your explanations of all aspects of sharing a dataset are clear and concise. I have benefitted greatly from the information in the video.
Thank you for a clear and logical description of sequnce of actions in your video. I found it very informational and will use it to learn about NFS share setup in Truenas. Much appreciated.
This is a very good presentation. I've used it many times as I add new configurations and advance file sharing on my self hosted systems. Thank you for your excellent work!
Hi David, just discovered a few of your videos. Such great content! That deserve a better microphone, hopefully you'll be able to figure that out the easy way ;) You have a new member! Cheers!
Thanks for the feedback and good to know the video was useful I don't like the search engine at all Once on you searched for something and got a list of videos about that topic Now you just get a few video suggestions and the rest have nothing whatsoever to do with what you're looking for It needs a serious overhaul
I don't really see me using it anymore so there are no plans at the moment for an iSCSI video It makes a lot of sense for companies But iSCSI uses block storage whereas NFS uses file storage For me, the performance tradeoff for VMs isn't noticeable on bare metal servers and it makes backups and recovery easier The NAS can see all of the files in an NFS share but sees nothing in an iSCSI share So I prefer to let the NAS just back itself up and then if anything goes wrong with a VM I can restore an individual file much easier
Such a informative video david. helped me clear many doubts. however, i have a question and was hoping you could give your two bits... i have a linux server running alma linux. i also have another server acting as network storage running truenas. I want to have my linux server users home directories in the truenas server. i have freeipa running in the linux server for identity management. i have also added the same ipa server as an ldap directory service in truenas. in truenas i have shared a "home" dataset as an nfs share. am thinking of mounting this share in the home mountpoint of the linux machine. since truenas "knows" the users through the ipa directory service i dont think there will be any permission issues. what do you think?
first of all: thank you second: I just set up TrueNAS and I also have Proxmox (different machines). I am still testing everything but it seems, that many services or applications (under linux) have some issues when you offer to the OS the storage from TrueNAS as samba - permissions or access - I am not sure. The moment I start using NFS from TrueNAS to VMs on Proxmox, I have much less issues. I am not yet done with testing and speed as well but it looks promising. Question is: should I i.e. dedicate 10TB nfs from TrueNAS to Proxmox and then, offer space from this storage to each VM under Proxmox, or, should I rather create as many nfs storage datasets on TrueNAS as many VMs want and then, mount them DIRECTLY from TrueNAS to the VMs? If that makes sense...
I prefer to keep things simple Create an NFS dataset and share that in TrueNAS Use that to create an NFS storage in Proxmox to store your VMs, containers, etc When you create a disk for a VM, make sure to select the NFS storage At a later date you can always add more disks and even increase disk capacity if you like by just updating the VM configuration However, if the VM needs access to sensitive data, then you should create an NFS or SMB share with the proper authentication and IP restrictions The VM should then be configured to attach to that share but from within its own OS
@@TechTutorialsDavidMcKone thank you for your post brother. The only problem I see with giving big pool to Proxmox and then to share it/create FS on it per VM means: in case s...t happens, I don't have DIRECT access to the files (from TrueNAS) - because Proxmox will create there the disk images only - and this is what I am afraid of - not having direct access to files from TrueNAS. Other aspects are ok: thin provision on Proxmox, possibility of over provisioning etc - all these are ok. Plus: samba has credentials - I don't see NFS having the same so even if I share to one IP only, still it does NOT require authentication (NFS), right?
@@zyghom If you want direct access to the files than connecting to a share from within the VM is the way to go The default NFS setup doesn't offer much in the way of user authentication, although for some reason I thought it did TrueNAS by default uses SYS but I've noticed it does offer Kerberos Personally I've just used Samba/SMB for data shares as I have Windows computers as well as Linux ones Windows does have an NFS client but even though Linux computers get much better transfer rates with NFS, I think it's too much hassle to this set up
@@TechTutorialsDavidMcKone ha, so my case is a bit different: amongst maybe 10 computers we have 0 windows (thx god). But, on serious matter: some applications have issues while data is on SMB - once I moved to NFS the problem disappeared (it was something to do with sqlite that stores data in file - no idea what exactly but once it was on SMB share it had conflicts but on ext4 or nfs it was ok). I tried also iscsi but I cannot see any difference at all in the speed or so
@@TechTutorialsDavidMcKone Thanks for replying. This is what I think should be one of the leading tech channels on YT. Perfect teaching, production etc... Thanks so much and keep it up sir!
What is the purpose of creating a user with a secure password if there is no encryption and authentication and anyone on the specified network can connect to the share?
If a system needs authentication True it may not be encrypted but obviously it doesn't care In which case you layer the network to restrict access If you can't connect to something, you can't login to it
If all my disks are nvme drives then would it help to add a Log VDEV of nvme as well? I'm guessing it wouldn't help unless my backend disks are slower than my Log VDEV disks correct?
It depends on where the bottleneck is If the network isn't high speed and so the data input doesn't overwhelm writes to disk, then things won't go any faster by adding a log I ran a basic test with some cheap NVMs and the throughput was getting me close to the limits of a 10Gb NIC But given how little storage they had, the cost implications and the shorter lifetime expectancy I stuck with mechanical drives and added a separate log as otherwise the 10Gb NIC would have been wasted
@@TechTutorialsDavidMcKone assuming no network bottleneck, and using same NVME type drives, is there any benefit to using Log VDEV if the backend data VDEV are already on the same fast NVME drives? I'm guess there's no need for the Log VDEV but please correct me if I'm wrong.
A domain name is used to basically name your network and allow users and computers to connect to mostly servers using a name rather than an IP address For example, whenever you want to connect to a public facing computer owned by Google you'll use their domain of google For private networks, the domain name can be more or less whatever you like really, but you have to make sure there isn't a clash with anything used in public For this lab I opted for a name of templab as it's for temporary lab use DNS names are defined from right to left You start with the TLD or top level domain, which for Google is .com To avoid conflict, I opted for .lan as the last time I checked it isn't being used in public You then add your domain to derive the domain name For Google we get google.com For my lab it's templab.lan And it's that overall domain name that needs to be unique So even if someone has registered templab.com on the public Internet, it's different to my private domain name of templab.lan Once you have a domain name, each computer requires a unique hostname as that hostname is added to the domain name to derive the FDQN or fully qualified domain name So I could have computers called www.templab.lan, ns1.templab.lan, etc As an aside, what users don't normally see is the root domain, which is . So if I want to set up my own DNS server the domain name would actually be templab.lan. Hope that helps
@TechTutorialsDavidMcKone amazing thankyou sir 🙏 very well exsplaned I appreciate it alot . I've been battling a two server (truenas , Ubuntu) plex set up woth docker running the arr software for about 6 weeks now. I was able to actually get the nfs connected by following your video but run into issues woth docker being able to read and write to the nfs so the battle continues
Extremely useful rundown. You wouldn't believe how hard it is to find straightforward and good documentation on TrueNAS. I appreciate the video and help!
Consider my donation as a small portion of savings I have now that I don't need to pay google or otherwise for cloud storage!
Thank you very much
And good to know the video was helpful
Thank you very much! Could not figure out where I was going wrong with my TrueNAS NFS config. Slowly reviewing what I had based off of your tutorial did the trick!
It seems a lot more difficult than it needs to be to configure
Just read that v2 came out in 1989 which is when I was programming mainframe computers so I guess it's not surprising
Even though it's still going with v4.2 released in 2016 it still feels old school
Mind you it's faster than SMB so I still plan on using it
Thank you for making the most in-depth tutorial on TrueNAS and the NFS protocol. Your explanations of all aspects of sharing a dataset are clear and concise. I have benefitted greatly from the information in the video.
Thanks for the feedback and good to know the video was helpful
Thank you for a clear and logical description of sequnce of actions in your video. I found it very informational and will use it to learn about NFS share setup in Truenas. Much appreciated.
Thanks for the feedback, really appreciate it
And good to know the video was helpful
This is a very good presentation. I've used it many times as I add new configurations and advance file sharing on my self hosted systems. Thank you for your excellent work!
Thanks for the feedback and good to hear the video was helpful
Thank you! Very useful!
Good to know the video was useful
Hi David, just discovered a few of your videos. Such great content! That deserve a better microphone, hopefully you'll be able to figure that out the easy way ;) You have a new member! Cheers!
Wow that is bad. I don't know what happened there as I didn't notice it during the editing and the mic is normally fine
Thanks!
Thank you very much
great video, just found your channel and subscribed! why can't your channel come up in my youtube suggestions rather than all the crap.
Thanks for the feedback and good to know the video was useful
I don't like the search engine at all
Once on you searched for something and got a list of videos about that topic
Now you just get a few video suggestions and the rest have nothing whatsoever to do with what you're looking for
It needs a serious overhaul
@@TechTutorialsDavidMcKone yes truely. at least I found a channel to go through and watch videos for a few hours !
David, did you ever do a video setting up the storage as iSCSI? Thanks and great video.
I don't really see me using it anymore so there are no plans at the moment for an iSCSI video
It makes a lot of sense for companies
But iSCSI uses block storage whereas NFS uses file storage
For me, the performance tradeoff for VMs isn't noticeable on bare metal servers and it makes backups and recovery easier
The NAS can see all of the files in an NFS share but sees nothing in an iSCSI share
So I prefer to let the NAS just back itself up and then if anything goes wrong with a VM I can restore an individual file much easier
Such a informative video david. helped me clear many doubts. however, i have a question and was hoping you could give your two bits...
i have a linux server running alma linux. i also have another server acting as network storage running truenas. I want to have my linux server users home directories in the truenas server. i have freeipa running in the linux server for identity management. i have also added the same ipa server as an ldap directory service in truenas. in truenas i have shared a "home" dataset as an nfs share. am thinking of mounting this share in the home mountpoint of the linux machine. since truenas "knows" the users through the ipa directory service i dont think there will be any permission issues. what do you think?
I've only used NFS shares for server storage and not as home folders
So I'm not sure what your outcome would be
first of all: thank you
second: I just set up TrueNAS and I also have Proxmox (different machines). I am still testing everything but it seems, that many services or applications (under linux) have some issues when you offer to the OS the storage from TrueNAS as samba - permissions or access - I am not sure. The moment I start using NFS from TrueNAS to VMs on Proxmox, I have much less issues. I am not yet done with testing and speed as well but it looks promising.
Question is: should I i.e. dedicate 10TB nfs from TrueNAS to Proxmox and then, offer space from this storage to each VM under Proxmox, or, should I rather create as many nfs storage datasets on TrueNAS as many VMs want and then, mount them DIRECTLY from TrueNAS to the VMs? If that makes sense...
I prefer to keep things simple
Create an NFS dataset and share that in TrueNAS
Use that to create an NFS storage in Proxmox to store your VMs, containers, etc
When you create a disk for a VM, make sure to select the NFS storage
At a later date you can always add more disks and even increase disk capacity if you like by just updating the VM configuration
However, if the VM needs access to sensitive data, then you should create an NFS or SMB share with the proper authentication and IP restrictions
The VM should then be configured to attach to that share but from within its own OS
@@TechTutorialsDavidMcKone thank you for your post brother. The only problem I see with giving big pool to Proxmox and then to share it/create FS on it per VM means: in case s...t happens, I don't have DIRECT access to the files (from TrueNAS) - because Proxmox will create there the disk images only - and this is what I am afraid of - not having direct access to files from TrueNAS. Other aspects are ok: thin provision on Proxmox, possibility of over provisioning etc - all these are ok. Plus: samba has credentials - I don't see NFS having the same so even if I share to one IP only, still it does NOT require authentication (NFS), right?
@@zyghom If you want direct access to the files than connecting to a share from within the VM is the way to go
The default NFS setup doesn't offer much in the way of user authentication, although for some reason I thought it did
TrueNAS by default uses SYS but I've noticed it does offer Kerberos
Personally I've just used Samba/SMB for data shares as I have Windows computers as well as Linux ones
Windows does have an NFS client but even though Linux computers get much better transfer rates with NFS, I think it's too much hassle to this set up
@@TechTutorialsDavidMcKone ha, so my case is a bit different: amongst maybe 10 computers we have 0 windows (thx god). But, on serious matter: some applications have issues while data is on SMB - once I moved to NFS the problem disappeared (it was something to do with sqlite that stores data in file - no idea what exactly but once it was on SMB share it had conflicts but on ext4 or nfs it was ok). I tried also iscsi but I cannot see any difference at all in the speed or so
Wow.
Glad to hear you found the video helpful
@@TechTutorialsDavidMcKone Thanks for replying. This is what I think should be one of the leading tech channels on YT. Perfect teaching, production etc... Thanks so much and keep it up sir!
What is the purpose of creating a user with a secure password if there is no encryption and authentication and anyone on the specified network can connect to the share?
If a system needs authentication
True it may not be encrypted but obviously it doesn't care
In which case you layer the network to restrict access
If you can't connect to something, you can't login to it
If all my disks are nvme drives then would it help to add a Log VDEV of nvme as well? I'm guessing it wouldn't help unless my backend disks are slower than my Log VDEV disks correct?
It depends on where the bottleneck is
If the network isn't high speed and so the data input doesn't overwhelm writes to disk, then things won't go any faster by adding a log
I ran a basic test with some cheap NVMs and the throughput was getting me close to the limits of a 10Gb NIC
But given how little storage they had, the cost implications and the shorter lifetime expectancy I stuck with mechanical drives and added a separate log as otherwise the 10Gb NIC would have been wasted
@@TechTutorialsDavidMcKone assuming no network bottleneck, and using same NVME type drives, is there any benefit to using Log VDEV if the backend data VDEV are already on the same fast NVME drives? I'm guess there's no need for the Log VDEV but please correct me if I'm wrong.
@@DavidLee-n9r I don't think so as I found as the write speed is already very high
@@TechTutorialsDavidMcKone thank you. I'm new to this and want to confirm
can someone break down the domain part from me please?
I'm a bit of a noob but trying to lean
A domain name is used to basically name your network and allow users and computers to connect to mostly servers using a name rather than an IP address
For example, whenever you want to connect to a public facing computer owned by Google you'll use their domain of google
For private networks, the domain name can be more or less whatever you like really, but you have to make sure there isn't a clash with anything used in public
For this lab I opted for a name of templab as it's for temporary lab use
DNS names are defined from right to left
You start with the TLD or top level domain, which for Google is .com
To avoid conflict, I opted for .lan as the last time I checked it isn't being used in public
You then add your domain to derive the domain name
For Google we get google.com
For my lab it's templab.lan
And it's that overall domain name that needs to be unique
So even if someone has registered templab.com on the public Internet, it's different to my private domain name of templab.lan
Once you have a domain name, each computer requires a unique hostname as that hostname is added to the domain name to derive the FDQN or fully qualified domain name
So I could have computers called www.templab.lan, ns1.templab.lan, etc
As an aside, what users don't normally see is the root domain, which is .
So if I want to set up my own DNS server the domain name would actually be templab.lan.
Hope that helps
@TechTutorialsDavidMcKone amazing thankyou sir 🙏 very well exsplaned I appreciate it alot .
I've been battling a two server (truenas , Ubuntu) plex set up woth docker running the arr software for about 6 weeks now. I was able to actually get the nfs connected by following your video but run into issues woth docker being able to read and write to the nfs so the battle continues