Date: Sat, 31 Jul 2010 21:37:10 -0400 (EDT) From: Rick Macklem <rmacklem@uoguelph.ca> To: pluknet <pluknet@gmail.com> Cc: freebsd-stable <freebsd-stable@freebsd.org> Subject: Re: umount -f <nfs> forces to panic Message-ID: <1298502209.215859.1280626630797.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <AANLkTimTi=6yP-NK0ksB%2BdJc8jHXPakMN86pXcWiHqPT@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> From: "pluknet" <pluknet@gmail.com> > To: "freebsd-stable" <freebsd-stable@freebsd.org> > Sent: Friday, July 30, 2010 12:53:08 PM > Subject: umount -f <nfs> forces to panic > Hi. > > This is 8.1 booted from NFS. > I did installworld to NFS on idle system, then it started > to print repeatedly "nfs server foo:mp lockd not responding". > umount returned EBUSY, umount -f dropped to panic: > I can't help w.r.t. fixing the lockd (NLM protocol). If you don't need locking to work across multiple clients for a given file, you can use the "nolockd" mount option. If you need locking on a given file to work across multiple clients, then you could consider trying NFSv4, which does have integrated file locking in the protocol. I am aware that "umount -f" crashes the system and hope to have a working "hard forced umount" implemented for 8.2. rick
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1298502209.215859.1280626630797.JavaMail.root>