public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Sean Hunter" <sean@uncarved.com>
To: Shawn <core@enodev.com>
Cc: Matthias Schniedermeyer <ms@citd.de>,
	"Leonardo H. Machado" <leoh@dcc.ufmg.br>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: cachefs on linux
Date: Tue, 10 Jun 2003 08:29:30 +0000	[thread overview]
Message-ID: <20030610082930.GA26777@uncarved.com> (raw)
In-Reply-To: <1055191776.13435.6.camel@localhost>

On Mon, Jun 09, 2003 at 03:49:36PM -0500, Shawn wrote:
> Well, it's a nice way to simulate writing on r/o filesystems IIRC. Like
> mounting a cdrom then writing to it, but you're not.
> 
> Was that was this was? Anyway, linux also does not have unionFS. If it
> was that big of a deal, someone would write it. As it is, it's a
> whizbang no one cares about enough.

Its particularly handy for fast read-only NFS stuff.  We have thousands
of linux hosts and distributing software to all of them is a pain.  With
cachefs with NFS as the "back" filesystem, you push to the masters and
the clients get the changes over NFS and then store them in their local
cache so your software distribution nightmare becomes no problem at all.
Clients read off the local disk if they can, but fetch over NFS as
required.  You can tune the cache size on all of the client machines so
they can cache more or less of the most recently used NFS junk on its
local disk.

Sean

  parent reply	other threads:[~2003-06-10  8:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-09 19:26 cachefs on linux Leonardo H. Machado
2003-06-09 20:42 ` Matthias Schniedermeyer
2003-06-09 20:49   ` Shawn
2003-06-09 20:56     ` Matthias Schniedermeyer
2003-06-10  8:29     ` Sean Hunter [this message]
2003-06-10 19:15       ` Rob Landley
2003-06-10 20:39         ` Anton Altaparmakov
2003-06-11  0:51           ` Rob Landley
2003-06-11 10:03         ` Bernd Eckenfels
2003-06-11 11:12           ` Hirokazu Takahashi
2003-06-11 22:26             ` J.A. Magallon
  -- strict thread matches above, loose matches on Subject: below --
2003-06-10  7:53 john
2003-06-11 21:01 Perez-Gonzalez, Inaky

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030610082930.GA26777@uncarved.com \
    --to=sean@uncarved.com \
    --cc=core@enodev.com \
    --cc=leoh@dcc.ufmg.br \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ms@citd.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox