From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Christian Reis <kiko@async.com.br>
Cc: Neil Brown <neilb@cse.unsw.edu.au>,
linux-kernel@vger.kernel.org, NFS@lists.sourceforge.net
Subject: Re: [NFS] Re: NFS client locking hangs for period
Date: Mon, 27 Jan 2003 00:02:00 +0100 [thread overview]
Message-ID: <15924.26856.298449.357899@charged.uio.no> (raw)
In-Reply-To: <20030126204711.A25997@blackjesus.async.com.br>
>>>>> " " == Christian Reis <kiko@async.com.br> writes:
> statd(8) does indicate that /var/lib/nfs is private, so I just
> mount it as tmpfs. Should I make it persistent, or is the fact
> those files disappear on an unclean reboot a sign of trouble?
If you want locking to work, then /var/lib/nfs *MUST* be
persistent and unique for each client.
If not then the server will fail to be notified that it needs to
release any POSIX locks it might think you were holding if/when your
NFS client fails to shutdown cleanly.
That again will typically cause a deadlock the next time you try to
access your mailspool (if the server thinks it is already holding a
lock on your behalf).
Cheers,
Trond
next prev parent reply other threads:[~2003-01-26 22:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-24 20:49 Christian Reis
2003-01-25 3:54 ` Neil Brown
2003-01-26 16:02 ` Christian Reis
2003-01-26 21:49 ` [NFS] " Trond Myklebust
2003-01-26 22:47 ` Christian Reis
2003-01-26 23:02 ` Trond Myklebust [this message]
2003-01-26 23:56 ` Christian Reis
2003-01-27 0:06 ` Trond Myklebust
2003-01-27 2:19 ` Dell Latitude CPi keyboard problems since 2.5.42 Tom Sightler
2003-01-28 8:14 ` [NFS] Re: NFS client locking hangs for period Denis Vlasenko
2003-01-28 16:47 ` Christian Reis
2003-01-28 8:00 ` Denis Vlasenko
2003-01-28 16:44 ` Christian Reis
2003-01-29 21:53 ` Daniel Egger
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=15924.26856.298449.357899@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=NFS@lists.sourceforge.net \
--cc=kiko@async.com.br \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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
all inboxes | Powered by JetHome®