From mboxrd@z Thu Jan 1 00:00:00 1970 From: pete@nomadlogic.org (Pete Wright) Date: Fri, 29 Sep 2017 10:27:48 -0700 Subject: [TUHS] RFS was: Re: UNIX of choice these days? In-Reply-To: <20170929170246.GA65710@wopr> References: <201709270844.v8R8i2kd021180@freefriends.org> <201709281349.v8SDnHp2005910@freefriends.org> <20170928222056.GD28606@mcvoy.com> <20170929085923.nclqn5g4xang4vii@client.local> <21d2ce3b-dd08-bc7d-b6bc-b1ae4acfaa1b@tnetconsulting.net> <20170929170246.GA65710@wopr> Message-ID: <48e7c92a-8b0d-0fe8-bda2-9cfe552bef0a@nomadlogic.org> On 09/29/2017 10:02, Kurt H Maier wrote: > On Fri, Sep 29, 2017 at 10:46:16AM -0600, Grant Taylor wrote: >> I am guessing dhcp and / or bootp, combined with tftp for kernel >> image, and NFS for root. > > I run linux workstations and a few supercomputers by PXE booting via > DHCP, serving a kernel and initrd over tftp, then having init download a > rootfs tarball, which gets extracted to a ramdisk. switch_root(8) makes > it easy. xCAT automates it. I had a similar setup at a large special effects studio I used to work at. We were trying solve NFSv3 contention issues - especially with large directory tree's creating tons of metadata requests on Linux (issue with client side caching IIRC) so we experimented with using UnionFS to allow for writes to pass-through to local disk.  It was mostly intermediary data and initial testing was promising, in that it alleviated the load on our filers and seemed to speed up some rendering processes. I had left before it made it to wide deployment - but it is something I've kept in my toolbox since then as an option. -pete -- Pete Wright pete at nomadlogic.org @nomadlogicLA