[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freebsd-fs
Subject:    [Bug 206634] "panic: ncllock1" from FreeBSD client after NFSv4 server was taken offline and brought 
From:       bugzilla-noreply () freebsd ! org
Date:       2016-02-20 2:36:13
Message-ID: bug-206634-3630-yG7BuT7Xut () https ! bugs ! freebsd ! org/bugzilla/
[Download RAW message or body]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206634

Rick Macklem <rmacklem@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|freebsd-fs@FreeBSD.org      |rmacklem@FreeBSD.org
             Status|New                         |In Progress

--- Comment #4 from Rick Macklem <rmacklem@FreeBSD.org> ---
Created attachment 167209
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=167209&action=edit
Patch to delete panic that no longer applies to current/head

r285632 changed vfs_hash_get() so that it no longer calls vget()
with VI_LOCK() held. As such, this panic() and the VI_UNLOCK() should
not be done. The attached patch (not yet tested by me) makes this change.
(Note that this panic and patch only apply to head/current and not
 stable/10 or earlier.)
Please let me know if you have an NFSv4 server crash/reboot after applying
the patch and whether or not it seems to work.

I will try and test the patch. I cannot commit it to head/current until
mid-April.

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-fs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-fs
To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org"
[prev in list] [next in list] [prev in thread] [next in thread]