From: Erik Walthinsen <omega@temple-baptist.com>
To: nfs@lists.sourceforge.net
Subject: Breaking locks on a lame server?
Date: Tue, 02 May 2006 20:17:04 -0700 [thread overview]
Message-ID: <445820B0.8080107@temple-baptist.com> (raw)
We've got a configuration with a NAS machine (3ware SATA RAID) running a
2.4.26 kernel is in use by a number of client machines, each running
multiple instances of user-mode-linux. Most all "block devices" presented
to the UML instances are located on the NAS, exported via NFS. The clients
are currently a mix of 2.4.26 and 2.6.15.6.
The problem is, whenever there's any kind of abnormal shutdown of either a
UML instance or the machine that's running it, a NFS lock is left in place.
This means that UML refuses to start up again using those files, unless I
patch the UML kernel to avoid F_SETLK, which is of course very unsafe (two
UMLs touching the same file means EDEADFILE).
I've seen other suggestions for breaking locks that involve restarting statd
on the clients, etc., but the problem is this: these locks are persistent
across reboots of the clients. IIRC they're also persistent *between*
clients, so I can't start a UML instance on an alternate machine either.
We're planning an upgrade of the NAS box to 2.6 as soon as we can, but that
means a system-wide shutdown of all our customer's UML instances, which
isn't something we do lightly.
1) am I to expect 2.6's NFS server implementation to somehow solve this?
2) if not, and in the meantime, are there any means by which I can inspect
(lslk does nothing) and hopefully kill these locks?
(I'm not on the list, already on too many, so please make sure to send to:
or cc: me)
Thankx,
Omega
aka Erik Walthinsen
omega@vcolo.com
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2006-05-03 3:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-03 3:17 Erik Walthinsen [this message]
2006-05-03 14:33 ` Breaking locks on a lame server? Jeff Layton
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=445820B0.8080107@temple-baptist.com \
--to=omega@temple-baptist.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.