Bit of a necro post, but I'm finally getting back around to NFS review for RHCSA. nfsstat -s tells me I'm using version 4.

@scottalanmiller Sounds solid. The speed difference is dramatic. Thanks.

rpcbind services is not required for NFSv4 https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/deploying_different_types_of_servers/exporting-nfs-shares_deploying-different-types-of-servers

@Emad-R said in Linux NFS SSD caching: AID 10 on Linux File Server machine, how can I speed up this NFS storage by an intelligent cache, for example I wish to add another 250 GB SSD to act as cache, how will tha Yeah the RAID 10 is on HDD, due to cost effectiveness. Will check LVM since its baked in.

@phlipelder said in Use Hyper-V to replicate Linux vm file share: @scottalanmiller said in Use Hyper-V to replicate Linux vm file share: @phlipelder said in Use Hyper-V to replicate Linux vm file share: Hyper-V Replica would work in this situation with a few caveats. There is a 15 second limit on replication cycles. If the VMs are running database/active services this could be a problem. That would be handled earlier in the process by the backup job. If the backup is good, the replication won't cause an issue. If the backup is bad, the replication can't fix it, of course, but will replicate the bad backup. But the only place that this can be addressed is in the backup step, the replication is of backup files, so not at a point in the process where it matters. "Garbage in garbage out" never seems to go away. It's been the bane of our existence since the switch to image/block based backups. :S File backups suffered from this, too. Databases are just hard to back up.

@fateknollogee said in NFS Server...what to build??: @scottalanmiller said in NFS Server...what to build??: @fateknollogee said in NFS Server...what to build??: @scottalanmiller said in NFS Server...what to build??: @fateknollogee said in NFS Server...what to build??: HW is simple: 2x SSD for o/s 4 - xx SSD for NFS shares Why would you have drives for the OS? This both breaks standard storage practices AND assumes a physical install which is a 'no no'. Why would you assume a physical install ? I'm installing the hypervisor (in this case FC28) on a Raid1 array of 2x SSDs Because you stated a dedicated array for the OS, not for the hypervisor. I'm only going by what you wrote. If you wanted dedicated for the OS, you'd need it whether you had a hypervisor or not. Understood. Next time, will be more specific Since that's a lot of money to spend just for a hypervisor that isn't used, it seems much more rational to use it for an OS than a hypervisor. It's not that there is truly zero value to a dedicated HV array, but it is nearly zero. SSDs, even cheap consumer ones, aren't free. But the value is so low, they'd basically have to be.

Maybe problem with noowners mount option? https://www.barryodonovan.com/2012/12/12/apple-os-x-as-an-nfs-server-with-linux-clients

@poorizad said in Storing Elastix 2 Call Recordings on NFS NAS Share: @scottalanmiller hi again....i guess the nfs drive is unmount from the server, because no file record on Nas after the 2016/07/28.....nothing changed on settings.....but a few server shutdown for hardware maintenance.....how can i fix it again ? Try the mount command again. It might mount right up. If the NFS server has restarted, it would disconnect.

Bug found, scheduled for release in 4.15 https://xen-orchestra.com/forum/topic/159/nfs-connection-issue/46

No, there is nothing like that. The filesystem is just not there. It would warn you, though, so you would know not to be trying to save to something that doesn't exist.

It is not uncommon to only have servers approved to access the storage listed. So many shops will go in and add a server one by one to enable access. If your servers almost never change, this works pretty well and is extremely secure. You can do this in the firewall too, for even more security. But if you are using DevOps and creating and destroying VMs regularly you will want to automate this in some fashion.

@DustinB3403 said: Did you not have somewhere to jump off of? XS/XO/XOA is all great, but seriously the thread count is stupid. The knowledge is lost in all the noise.

@scottalanmiller said: @brianlittlejohn said: @scottalanmiller said: @anonymous said: @DustinB3403 Thanks for your help! NFS is case sententive, it is mounted now! Everything outside of the Windows and DOS worlds is case sensitive. SMB, NFS, URLs, file names, passwords, usernames, everything. Thats what bugs me about Linux ... I hate case sensitive things. I'm the opposite, I can't stand that DOS can't tell two characters apart and has "close enough" syntax so that people become sloppy and begin to lose the concept of congruency. I remember dealing with a bunch of students and getting them to understand things like "This", "this" and "t h I s" were not congruent was a real problem. Windows teachers users that exact doesn't mean exact, not always. I think that is why I like cisco's ios software... i don't have to type the full command... just enough to distinguish it from the other commands available.... I see the benefits of case sensitive, it just will take me a bit to get used to using it as I learn Linux.

@scottalanmiller You should also include cloud-init https://cloudinit.readthedocs.org/en/latest/

@DustinB3403 said: Damn you NFS-Common!! That was it. All working! Good to hear!

@Dashrender Okay let's retake a clean example: one VM in a SR, with one 4GB VDI: # lvscan inactive '/dev/VG_XenStorage-e27c48de-509f-3fec-d627-7f348062ab1a/MGT' [4.00 MiB] inherit inactive '/dev/VG_XenStorage-e27c48de-509f-3fec-d627-7f348062ab1a/VHD-770ceeac-e97e-4e05-b9c5-892b97b9d16e' [4.02 GiB] inherit After first snapshot: # lvscan inactive '/dev/VG_XenStorage-e27c48de-509f-3fec-d627-7f348062ab1a/MGT' [4.00 MiB] inherit inactive '/dev/VG_XenStorage-e27c48de-509f-3fec-d627-7f348062ab1a/VHD-38e2156f-da74-4edb-ac83-56fda54cfe55' [1.75 GiB] inherit inactive '/dev/VG_XenStorage-e27c48de-509f-3fec-d627-7f348062ab1a/VHD-770ceeac-e97e-4e05-b9c5-892b97b9d16e' [4.02 GiB] inherit inactive '/dev/VG_XenStorage-e27c48de-509f-3fec-d627-7f348062ab1a/VHD-f18856a5-039b-4d84-bf6c-a259d0f49a9e' [8.00 MiB] inherit After second snapshot: # lvscan inactive '/dev/VG_XenStorage-e27c48de-509f-3fec-d627-7f348062ab1a/MGT' [4.00 MiB] inherit inactive '/dev/VG_XenStorage-e27c48de-509f-3fec-d627-7f348062ab1a/VHD-38e2156f-da74-4edb-ac83-56fda54cfe55' [1.75 GiB] inherit inactive '/dev/VG_XenStorage-e27c48de-509f-3fec-d627-7f348062ab1a/VHD-f18856a5-039b-4d84-bf6c-a259d0f49a9e' [8.00 MiB] inherit inactive '/dev/VG_XenStorage-e27c48de-509f-3fec-d627-7f348062ab1a/VHD-770ceeac-e97e-4e05-b9c5-892b97b9d16e' [4.02 GiB] inherit inactive '/dev/VG_XenStorage-e27c48de-509f-3fec-d627-7f348062ab1a/VHD-68408f33-5a69-4b3b-afdd-a2cfabcad9ba' [8.00 MiB] inherit As you can see, we got a second 8 MiB logical volume, nothing more (base parent and active VDI doesn't change). Let's remove the latest snapshot: # lvscan inactive '/dev/VG_XenStorage-e27c48de-509f-3fec-d627-7f348062ab1a/MGT' [4.00 MiB] inherit inactive '/dev/VG_XenStorage-e27c48de-509f-3fec-d627-7f348062ab1a/VHD-38e2156f-da74-4edb-ac83-56fda54cfe55' [1.75 GiB] inherit inactive '/dev/VG_XenStorage-e27c48de-509f-3fec-d627-7f348062ab1a/VHD-f18856a5-039b-4d84-bf6c-a259d0f49a9e' [8.00 MiB] inherit inactive '/dev/VG_XenStorage-e27c48de-509f-3fec-d627-7f348062ab1a/VHD-770ceeac-e97e-4e05-b9c5-892b97b9d16e' [4.02 GiB] inherit It removes the previously created volume, as expected. Now, let's remove the initial snapshot. Durin few seconds, we'll have this: lvscan inactive '/dev/VG_XenStorage-e27c48de-509f-3fec-d627-7f348062ab1a/MGT' [4.00 MiB] inherit inactive '/dev/VG_XenStorage-e27c48de-509f-3fec-d627-7f348062ab1a/VHD-38e2156f-da74-4edb-ac83-56fda54cfe55' [1.75 GiB] inherit inactive '/dev/VG_XenStorage-e27c48de-509f-3fec-d627-7f348062ab1a/VHD-770ceeac-e97e-4e05-b9c5-892b97b9d16e' [8.00 MiB] inherit inactive '/dev/VG_XenStorage-e27c48de-509f-3fec-d627-7f348062ab1a/leaf_770ceeac-e97e-4e05-b9c5-892b97b9d16e_38e2156f-da74-4edb-ac83-56fda54cfe55' [4.00 MiB] inherit But it will be automatically "garbage collected" when the system will see than the chain doesn't have any snapshot in it (after few seconds in this case): # lvscan inactive '/dev/VG_XenStorage-e27c48de-509f-3fec-d627-7f348062ab1a/MGT' [4.00 MiB] inherit inactive '/dev/VG_XenStorage-e27c48de-509f-3fec-d627-7f348062ab1a/VHD-770ceeac-e97e-4e05-b9c5-892b97b9d16e' [4.02 GiB] inherit We are back to the initial situation.

@scottalanmiller said: Where DNS != DNS That was CONFUSING I knew exactly what @scottalanmiller issue was when I read his post.. I updated my post for clarity.

@Dashrender said: On the Windows side we have the free version of Unitrends and Veeam for VMs, but I'm not sure of one for bare metal. Those can become coupled if you share accounts. So it is not a panacea.

I thought that screen looked familiar, lol.

OpenLDAP is what the average Linux shop is going to turn to when looking to implement an "AD like" authentication mechanism when no Windows is involved.

OK.