Thomas Maier-Komor writes: > > and slog through the output to find the offender. > > > > Great! I found it. It's hanging somewhere in NFS:
That looks exactly like CR 6406650. Was this a forced unmount? > Is there a way to resolve this hanging CV? Or can one determine the NFS > resource in question. I guess it might be something caused by one of our > Linux NFS servers... It looks like an internal deadlock, not something that can be resolved externally. The fix is in Nevada build 43. The only "workaround" seems to be to use the default NFSv4 instead of NFSv3. -- James Carlson, KISS Network <[EMAIL PROTECTED]> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
