On Thu, Dec 24, 2015 at 01:44:21AM -0500, Raghavendra Gowdappa wrote: > > Seems to be hung. May be a hung syscall? I've tried to kill it, but seems > > like its not dead. May be patch #12594 is causing some issues on netbsd. It > > has passed gluster regression. ps -axl shows PID 1394 (umount) waiting on tstile, which is used for spinlocks. No process should sit there for long, unless there is a kernel locking problem (which may be a userland locking problem thanks to FUSE). Using crash(8) I can see umount is awaiting for a vnode lock. There is certainly something to investigate but I lack time for now. I issued a reboot. Please tell me if you can reproduce it. -- Emmanuel Dreyfus manu@xxxxxxxxxx _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel