James Carlson wrote: > 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? >
could be - this process is hanging since quite some time and I just thought that a silent Friday afternoon is the right time to investigate this issue ;-) >> 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. > Thanks for the information - that was very helpful. Cheers, Tom _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
