From: Chip Salzenberg <chip@pobox.com>
To: nfs@lists.sourceforge.net
Subject: Debian Bug#203077: Locks not released on NFS client reboot
Date: Sun, 27 Jul 2003 12:31:24 -0400 [thread overview]
Message-ID: <20030727163124.GC19877@perlsupport.com> (raw)
In-Reply-To: <Pine.OSF.4.56.0307271137050.10355@grover.WPI.EDU>
I confess I don't quite understand this bug report. Is this person
asking for something that NFS can't do, or is there perhaps some error
in configuration ... ?
Please advise.
The report is again Debian stable (woody), which uses nfs-utils 1.02.
According to Nick Nassar:
> File locks on NFS clients are not released on reboot. When machines shut
> down unexpectedly for whatever reason, the locks stay there with no
> apparent way to clear them except restarting NFS on the server.
>
> See "I'm having a lock file problem. What do I do?" in
> http://www.gnome.org/projects/gconf/ for an example of the kind of problem
> caused by this.
>
> The machine that I'm specifically having the trouble with is using a stock
> 2.4.20 kernel that I compiled from source.
--
Chip Salzenberg - a.k.a. - <chip@pobox.com>
"I wanted to play hopscotch with the impenetrable mystery of existence,
but he stepped in a wormhole and had to go in early." // MST3K
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next parent reply other threads:[~2003-07-27 16:31 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.OSF.4.56.0307271137050.10355@grover.WPI.EDU>
2003-07-27 16:31 ` Chip Salzenberg [this message]
2003-07-28 0:56 ` Debian Bug#203077: Locks not released on NFS client reboot Neil Brown
2005-01-14 1:51 ` Ara.T.Howard
2005-01-14 2:29 ` Neil Brown
2005-01-14 2:57 ` Ara.T.Howard
2005-01-14 16:05 ` Ara.T.Howard
2005-01-14 19:43 ` Trond Myklebust
2005-01-14 19:50 ` Ara.T.Howard
2005-01-18 20:59 ` Ara.T.Howard
2005-01-14 17:47 ` Dan Stromberg
2005-01-14 18:19 ` Ara.T.Howard
2005-01-14 21:20 ` Dan Stromberg
2005-01-21 0:24 ` Ara.T.Howard
2005-01-21 0:52 ` Trond Myklebust
2005-01-21 18:32 ` Ara.T.Howard
2005-01-21 18:40 ` Dan Stromberg
2005-01-21 18:59 ` Ara.T.Howard
2005-01-21 19:05 ` Dan Stromberg
2005-01-21 19:10 ` Ara.T.Howard
2005-01-14 3:01 ` Trond Myklebust
2005-01-14 14:53 ` Ara.T.Howard
2005-01-14 21:23 Lever, Charles
2005-01-14 21:32 ` Ara.T.Howard
-- strict thread matches above, loose matches on Subject: below --
2005-01-14 21:46 Lever, Charles
2005-01-15 5:44 ` Ara.T.Howard
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=20030727163124.GC19877@perlsupport.com \
--to=chip@pobox.com \
--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 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.