5 ms·
I was surprised to see discussion of NFS. NFS certainly was a big deal "back in the day" but it had its own quirks and headaches. I haven't seen NFS in 20 yea
by gumby 8y ago
I was surprised to see discussion of NFS. NFS certainly was a big deal "back in the day" but it had its own quirks and headaches. I haven't seen NFS in 20 years, but that could simply be because of the particular worlds I live in.
Is it still widely used and I just happen never to see it because the environments in which I work?
Or is it only used for a small number of sites (or certain applications) but they happen to be extremely important ones?
- inyorgroove 8y agoAWS EFS[1] uses NFS which our team used last year for some internal infrastructure. NFS is still around. Also have been looking into more durable storage this year it looks like the Rados gateway[2] in Ceph supports a nfs front end as well. 1: https://aws.amazon.com/efs/ https://aws.amazon.com/efs/ 2: http://docs.ceph.com/docs/master/radosgw/nfs/ http://docs.ceph.com/docs/master/radosgw/nfs/
- kevin_thibedeau 8y agoI use NFS for a media/backup server since I don't want to bother with Samba.
- HankB99 8y agoI was surprised more because I thought it was pretty well settled. I use it in my home LAN to access file shares. (Linux desktops and a Linux server.) Is would be used between 'nix servers and clients? Is it something that would be useful on the home LAN?
- tw04 8y agoI would be shocked if there's a single fortune 500 that doesn't have a significant NFS footprint. Everything from user shares to Oracle or VMware get deployed via NFS.
- happythought 8y agoVMware supports NFS as a storage backend so it ends up being used in a lot of storage arrays in Enterprise shops. Gitlab.com was also using it as of last year, but I’m not sure if that’s still the case.
- muxator 8y agoYes, it has now been replaced by Gitaly: https://about.gitlab.com/2018/09/12/the-road-to-gitaly-1-0/ https://about.gitlab.com/2018/09/12/the-road-to-gitaly-1-0/
- happythought 8y agoFrom the drawing, it looks like gitaly decouples git storage from the workers, but still uses NFS on the backend.
- zaphirplane 8y agoVMware over NFS maybe used in SMB (small medium businesses) enterprises use iscsi or SANs when the NFS server crashes bad things happen and if you are building a redundant multi master NFS it’s a lot simpler to use iscsi and FC SAN
- chousuke 8y agoAt my workplace we run VMware over NFS served by Netapp clusters. It's very stable, performs well, is easy to manage and has functioning HA. We used to have a SAN but Netapp worked well enough that it was decommissioned. My favourite moment operating one cluster was when I intentionally caused a kernel panic and core dump on a live production system to gather debug info for an issue we were having. It had zero observable impact. :) Netapp is not cheap, but they seem to know what they're doing.
- ajdlinux 8y agoNFS is absolutely still in use at my workplace - there's a lot of older infrastructure still in place that makes use of it. Lots of AFS as well. I believe my alma mater's CS department is still using NFS for home directories last I checked.
- arminiusreturns 8y agoYep, it is still widely used as smb/cifs is a horrible protocol and it should feel bad. There are some issues with nfs(v4) on the bleeding edge by default, but it has been really cool to see some of the nfs workarounds to deal with big data.
- 6keZbCECT2uB 8y agoMy bias shows here, but what's your alternative to NFS from *nix? We used AFS at school. I suppose you could keep your data locally and be responsible for your own backups / use version control as backups.
- beagle3 8y agoCIFS / SMB ; Client is in most kernels these days, server (Samba) is easy to install and use. In my experience performance is acceptable (that is, I'm getting >110MB/s on a 1Gb connection), locking semantics if you need them work much better than an NFS - and most importantly, it doesn't hang as bad when a server goes away (NFS behaves like it's 1980 in that respect - the recommended and only consistent way to unhang processes when the server goes away is, I kid you not, start a local NFS server on the client, and add the IP address of the server locally to the client; Then, one of the retries will get an error from the local server, at that point you can deal with it, shutdown the local NFS and remove the extra IP address)
- pfranz 8y agoI'm actually curious to try that next time it comes up, but with automount + NFSv3 if a server goes down and isn't expected to come back up I can 'umount -l' and kill the hung process. With CIFS/SMB throughput wasn't the issue, but dealing with small files seemed to be. With NFS most places served software packages off of it and whenever this was tried with SMB it was unreasonably slow. I'm ignorant enough at the implementation that I could believe this was a configuration thing.
- beagle3 8y ago> I can 'umount -l' and kill the hung process. I don't use automount, but unless automount does some crazy magic ... this doesn't really help; umount -l (or umount -lf) indeed removes the mountpoint from the filesystem (so no new processes can access it and get stuck), but the kernel thread is still stuck waiting for an answer that will never come, and many processes cannot be killed even with "kill -9".
- simula67 8y agoI used to work for a hyper converged infrastructure provider which had an option to aggregate all the disks in a computing cluster and expose it as an NFS filesystem. You can then enable fault tolerance, compression, encryption etc on a file system level.
- pfranz 8y agoI'm curious what your domain is and what tech you've been using? Every Linux shop I've worked in 10+ years has used NFS without any word of an alternative. The few places I've worked that mixed NFS with SMB or exclusively used SMB I've had performance issues when jumping between the two (perhaps due to experience and configuration). My work has mostly been in Linux shops with 10s-100s of workstations+servers. NFS was used for homedirs and shared data. Sometimes servers were hundreds of miles away.
- gumby 8y ago> I'm curious what your domain is and what tech you've been using? It’s good to see these replies as everybody’s experience is different and I learn by asking. Perhaps NFS has improved a lot; I started using it in the 1980s after using client/server filesystems like IFS and Alpine at parc and the per-file protocols we had at mit for the pod-10s and Lispms. With NFS locking and such were painful because it tried hard to look no different from a local filesystem, but couldn’t be. Network mounted homedirs were common to me from the early 80s but under NFS were too painful. I imagine things have improved over the last couple of decades! The environments I’ve used more recently have used a combination of replication (e.g. Dropbox), moved the computation to the data (“cloud” though for me typically this has meant in-house someplace rather than a third party or shared machine) or hybrid (e.g. IMAP). Datasets tend not to be super huge — < 50 TB — so other approaches are used at the back end.
- reacharavindh 8y agoHPC sysadmin here. Our cluster is built around NFS for storage. User home directories are mounted on all compute nodes via NFS. Research datasets are mounted on compute nodes via NFS. It is simple and stable and works very well within our internal network.
- notacoward 8y agoNFS is increasingly becoming an access protocol, to speak to $whatever through some sort of proxy/gateway. $whatever might be Gluster (for which I'm still a maintainer), Ceph, EFS, etc. It's nice because clients are everywhere, they're maintained by someone else, and you can update your own stuff as much as you like without landing in the swamp of updating client software. The people who do maintain those clients - I know a few - deserve our thanks.