From: graeme.russ@gmail.com (Graeme Russ)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Is it possible to use a local drive to cache an NFS share
Date: Mon, 03 Sep 2012 23:00:45 +1000 [thread overview]
Message-ID: <5044A9FD.5010401@gmail.com> (raw)
Hi All,
I am mounting /home over NFS which is great, but it really kills compile
times. So I have a local HDD which I have copied all my source code over
from which I do my coding and compiling.
What I would love to do is use the local drive to cache /home. Specifically
one user directory under /home - only one machine will ever be modifying
the contents of this directory.
Or should I just use rsync?
On a side note - I moved my source code from a 1TB HDD on a 3Gb/s SATA port
to an Intel 510 series 250GB SSD on a 6Gb/s SATA port. But I didn't see an
appreciable increase in compile speed.
Regards,
Graeme
next reply other threads:[~2012-09-03 13:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-03 13:00 Graeme Russ [this message]
2012-09-03 15:26 ` Is it possible to use a local drive to cache an NFS share michi1 at michaelblizek.twilightparadox.com
2012-09-03 15:27 ` Mulyadi Santosa
2012-09-04 5:14 ` michi1 at michaelblizek.twilightparadox.com
2012-09-03 19:51 ` Rajat Sharma
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=5044A9FD.5010401@gmail.com \
--to=graeme.russ@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.