Skip to Content
File Systems Expertise

NFS for Modern Infrastructure

Network File System The quiet workhorse of Linux file sharing, simple, fast, and still going strong after four decades.

Reach out for NFS support
NFS
Where it Fits Where it Fits

Linux and Unix-based environments where multiple systems need access to shared storage over a network. A staple in virtualized infrastructure, development environments, and anywhere that centralized file access is needed without the overhead of a full storage platform.

Strengths Strengths

NFS is lightweight, widely supported, and deeply integrated into the Linux ecosystem. It requires minimal setup to get shared storage accessible across multiple systems, and performs well for workloads that don't demand the complexity of a distributed filesystem.

Watchouts Watchouts

NFS shifts a lot of trust to the network. In its older versions especially, security controls are limited and access is largely governed by IP address rather than user identity. Running NFS outside of a trusted, well-segmented network requires careful consideration.

See Other File Systems

Key Capabilities

What NFS Brings to the Table

Simple, Low-Overhead File Sharing

Simple, Low-Overhead File Sharing

Export directories from a Linux server and mount them on any client with minimal configuration and no additional software required.

Native Integration with Linux Storage Platforms

Native Integration with Linux Storage Platforms

NFS is a first-class citizen in Proxmox, TrueNAS, and most Linux-based NAS platforms, making it the natural choice for shared storage in those ecosystems.

NFSv4 Security and Authentication

NFSv4 Security and Authentication

Modern NFS supports Kerberos-based authentication and encrypted connections, addressing the trust limitations of older versions in environments that require it.

High-Performance Tuning Options

High-Performance Tuning Options

Mount options and server-side export settings give administrators granular control over read/write behavior, caching, and connection handling for performance-sensitive workloads.

Compatibility

Fit Check By Use Case

Strong Fit

Shared Storage in Virtualized Environments

NFS is a supported and widely used shared storage protocol for both Proxmox and VMware, enabling live migration and shared disk access across hypervisor hosts without a dedicated SAN. Examples: Proxmox clusters, VMware datastores, shared VM disk storage

Strong Fit

Centralized Home Directories and Development Environments

Mounting user home directories or shared development folders over NFS is a straightforward way to give multiple systems access to the same files without duplicating data. Examples: Linux workstation environments, developer file shares, CI/CD artifact storage

Conditional Fit

Cross-Platform Environments Including Windows Clients

NFS can be configured for Windows access, but it's not a natural fit. Windows has supported an NFS client for some time, but the experience is less seamless than SMB. Mixed environments often run both protocols side by side. Prerequisites: Windows NFS client configuration, clear use case justification, consider SMB as an alternative

Conditional Fit

High-Performance Database or Application Storage

NFS can support demanding workloads, but only with careful tuning and a fast, low-latency network. Using NFS for database storage without understanding the async/sync tradeoffs and network requirements is a common source of performance problems. Prerequisites: NFSv4, dedicated network path, thorough performance testing

Poor Fit

Internet-Facing or Untrusted Network Environments

NFS is designed for trusted networks. Exposing NFS shares across untrusted network segments, even with NFSv4 and Kerberos, introduces risk that purpose-built file transfer protocols handle more safely. Examples: Public-facing file access, cross-internet file sharing, multi-tenant cloud environments

Poor Fit

Environments Requiring Windows-Native File Sharing

For environments built around Windows clients and Active Directory, SMB is the right tool. NFS works in these environments but requires additional configuration and delivers a less integrated experience than CIFS/SMB natively provides. Examples: Windows-first office environments, Active Directory-integrated file shares

Our Practice

How Crafty Penguins Works with NFS

NFS comes up regularly in our infrastructure work, most often as part of a broader storage or virtualization engagement rather than as a standalone project. In Proxmox environments, we frequently use NFS to connect ZFS-backed storage to hypervisor clusters, giving virtual machines access to shared storage without the complexity of a dedicated SAN. In those contexts, getting NFS configured correctly, the right version, the right mount options, the right network path, has a direct impact on VM performance and reliability. We also help clients who have NFS shares that have grown organically over time without much governance. That typically means auditing what's exported, tightening access controls, and in some cases migrating older NFSv3 configurations to NFSv4 to bring security and performance up to a reasonable standard. It's unglamorous work, but storage that quietly misbehaves causes a lot of downstream problems.

How Crafty Penguins Works with NFS
Client Success

Don't Just Take Our Word For It

Andrew Yates
Columbia University Irving Medical Center
Crafty Penguins helped us set up a customized and small-scale HPC using existing resources in our research lab at Columbia University. The cluster has been running beautifully for several years now and throughout that time, Crafty Penguin’s support has been superb:  responsive, reliable, creative, friendly, no-nonsense. They’ve been indispensable for keeping us productive. I can’t recommend them highly enough.
Andrew Yates
Professor, Columbia University Irving Medical Center
Clint Bounds
Plan to Eat
Crafty Penguins also developed a robust deployment process with seamless rollback capabilities, while DigitalOcean provides a dependable infrastructure backbone. In over two years since the migration, Plan to Eat has not experienced a single major outage, a marked improvement over previous AWS operations. “There’s no single point of failure,” Clint notes. “When large companies on AWS face issues, our website keeps running smoothly, and that feels great.”
Clint Bounds
Owner, Plan to Eat
The Crafty Penguins Way

Our Proven Process

Practical Onboarding

We start with your real environment, versions, drivers, and recovery goals, so the plan fits production, not a slide deck.

Deep-Dive Assessment

Our engineers audit configurations, workloads, and failure modes to surface risks before they become outages.

Hands-On Implementation

We build, tune, and harden in your environment with runbooks, monitoring, and rollback plans baked in from day one.

Ongoing Optimization

Continuous monitoring, patch management, and capacity planning keep performance steady as your workloads evolve.

Questions

FAQ

What is the difference between NFS and SMB/CIFS?
NFS is the standard for file sharing in Linux and Unix environments. SMB is the standard for Windows environments. Both allow network-based file access, but they use different protocols, authentication models, and have different strengths. In mixed environments, it's common to run both, NFS for Linux workloads and SMB for Windows users.
Which version of NFS should I be using?
NFSv4 or later for anything in production. NFSv3 still works but lacks stateful connections, has weaker security, and doesn't handle high-latency networks as gracefully. NFSv4.1 and 4.2 add further improvements including parallel access and server-side copy, and are worth targeting on platforms that support them.
Is NFS secure enough for production use?
With NFSv4 and proper network segmentation, yes. NFSv4 supports Kerberos authentication and can be configured with encrypted connections. The key requirement is that NFS should only ever be accessible on trusted, well-controlled network segments. It is not designed to be exposed to untrusted or public networks.
Can NFS be used as shared storage for virtual machines?
Yes, and it frequently is. Both Proxmox and VMware support NFS as a shared storage backend, enabling features like live migration that require multiple hypervisor hosts to access the same storage simultaneously. Performance depends heavily on the underlying storage and network quality.
What causes NFS performance problems?
The most common culprits are misconfigured mount options, network congestion or high latency, and async/sync write settings that don't match the workload. Running NFS over a shared network that's contended with other traffic is another frequent issue. In most cases, NFS performance problems are configuration or infrastructure problems rather than fundamental limitations of the protocol.
Get Started

Ready to Have Us on Your Team?

Let's discuss how we can help support, grow, and optimize your Linux infrastructure, done right the first time.