Linux NFS development
 help / color / mirror / Atom feed
From: Gavin Hamill <gdh@acentral.co.uk>
To: nfs@lists.sourceforge.net
Subject: Re: lockd / statd fun (sorry)
Date: Tue, 27 Apr 2004 19:15:59 +0100	[thread overview]
Message-ID: <20040427181559.GA9200@acentral.co.uk> (raw)
In-Reply-To: <1083084557.2616.45.camel@lade.trondhjem.org>

On Tue, Apr 27, 2004 at 12:49:17PM -0400, Trond Myklebust wrote:
> On Tue, 2004-04-27 at 11:47, Gavin Hamill wrote:
> 
> > but again, it's just 'a fix' and not The Solution.
> 
> Neither is keeping /var/lib/nfs on a ramdisk.
> 
> /var/lib/nfs should *always* be on permanent storage if you want to use
> locking.

Ah I'd certainly not taken that into consideration - I assumed (always 
bad, I know) it would reset any locks when the same client remounted the 
same export at reboot.

OK, given that the machines have no local permanent storage, it seems
that's solved the problem for me - I must disable locking completely.

It's fortunate that the rootfs export is mounted read-only, and the
home-directories export are never shared between multiple users. That, 
and the users are not running very demanding applications.

Plus, if the worst happens, it would take only a few minutes to restore 
a corrupted file from backups, or re-create their userprofile entirely.

Thanks for the advice, NFS has been around for a long time, and I've 
known nothing about it until the last few weeks :)

Cheers,
Gavin.



-------------------------------------------------------
This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
For a limited time only, get FREE Ground shipping on all orders of $35
or more. Hurry up and shop folks, this offer expires April 30th!
http://www.thinkgeek.com/freeshipping/?cpg=12297
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

      reply	other threads:[~2004-04-27 18:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-23 10:37 lockd / statd fun (sorry) Gavin Hamill
2004-04-23 11:32 ` Bernd Schubert
2004-04-23 11:48   ` Gavin Hamill
2004-04-23 11:57     ` Olaf Kirch
2004-04-27 13:43       ` Gavin Hamill
2004-04-27 15:32         ` Olaf Kirch
2004-04-27 15:47           ` Gavin Hamill
2004-04-27 15:56             ` Olaf Kirch
2004-04-27 16:49             ` Trond Myklebust
2004-04-27 18:15               ` Gavin Hamill [this message]

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=20040427181559.GA9200@acentral.co.uk \
    --to=gdh@acentral.co.uk \
    --cc=nfs@lists.sourceforge.net \
    /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