Why NFS Sucks — 3 Network File System Drawbacks

Crack #1: NSF Bottleneck — There Can Be Only One…Unfortunately

OK, NFS v1 predated Highlander by two years, but the core idea remains: many clients talking to a single server. That was NFS’s beauty — and now its main flaw.

Crack #2: NFS Failover Fails…Over and Over

Failover capability has been bolted onto NFS in fits and starts over the years; it’s not native to the file system. As a result, failover functionality often feels like a slapped-together workaround.

Crack #3: Checksum Doesn’t Check Out

We’re not saying it’s aliens, but…it could be aliens. More likely, it’s cosmic rays, materials degradation, a buggy router, or some similar cause. While the source of randomly flipped bits — when a 0 changes unbidden to a 1 or vice versa in data in transit or at rest — often remains opaque, the effects can be devastating.

Scale-out Storage Instead of NFS

With Quobyte storage, when data arrives from the operating system, the first order of business is to checksum that data. The checksum is tied to that data forever.


After all this criticism, you may ask, “If NFS is so bad, why is it the de facto standard for today’s enterprise storage?”



Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store



Quobyte empowers customers by providing real software storage so that they can keep up with the ever-increasing amounts of data in today’s data-driven world.