From owner-freebsd-stable@FreeBSD.ORG Sun Nov 25 16:24:23 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 63622C84 for ; Sun, 25 Nov 2012 16:24:23 +0000 (UTC) (envelope-from aoyama@peach.ne.jp) Received: from moon.peach.ne.jp (moon.peach.ne.jp [203.141.148.98]) by mx1.freebsd.org (Postfix) with ESMTP id 010F08FC12 for ; Sun, 25 Nov 2012 16:24:22 +0000 (UTC) Received: from moon.peach.ne.jp (localhost [127.0.0.1]) by moon.peach.ne.jp (Postfix) with ESMTP id B83D039D49 for ; Mon, 26 Nov 2012 01:17:51 +0900 (JST) Received: from artemis (unknown [172.18.0.20]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by moon.peach.ne.jp (Postfix) with ESMTPSA id A3FFC39D46 for ; Mon, 26 Nov 2012 01:17:51 +0900 (JST) Message-ID: From: "Daisuke Aoyama" To: Subject: hastctl hang Date: Mon, 26 Nov 2012 01:17:46 +0900 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-2022-jp"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 14.0.8117.416 X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8117.416 X-Virus-Scanned: ClamAV using ClamSMTP X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Nov 2012 16:24:23 -0000 Hello, I'm trying to integrate HAST to NAS4Free (FreeBSD 9.1-RC3). Now I have created version 9.1.0.1.531. http://sourceforge.net/projects/nas4free/files/NAS4Free-9.1.0.1/9.1.0.1.531/ Basic CARP + HAST + iSCSI target setup can be done, but very frequently I get hastctl hang when called: /sbin/hastctl status /sbin/hastctl dump Is it better for this method not to call from a script? or somthing wrong to use it? Also, I don't know how to detect an error of writing to local device from hastd. Does anyone know about it? Thanks, Daisuke Aoyama -- the procstat shows like this: [root@nas4free-nodeb /tmp]# procstat -ka|grep hast 11668 100069 hastd - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep kern_wait sys_wait4 amd64_syscall Xfast_syscall 17981 100406 hastd - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep do_wait __umtx_op_wait_uint_private amd64_syscall Xfast_syscall 17981 100559 hastd - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep soreceive_generic kern_recvit recvit sys_recvfrom amd64_syscall Xfast_syscall 17981 100560 hastd - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep soreceive_generic kern_recvit recvit sys_recvfrom amd64_syscall Xfast_syscall 17981 100561 hastd - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep do_wait __umtx_op_wait_uint_private amd64_syscall Xfast_syscall 17984 100078 hastd - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep do_wait __umtx_op_wait_uint_private amd64_syscall Xfast_syscall 17984 100562 hastd - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep soreceive_generic kern_recvit recvit sys_recvfrom amd64_syscall Xfast_syscall 17984 100563 hastd - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep soreceive_generic kern_recvit recvit sys_recvfrom amd64_syscall Xfast_syscall 17984 100564 hastd - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep do_wait __umtx_op_wait_uint_private amd64_syscall Xfast_syscall 18218 100145 hastctl - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep soreceive_generic kern_recvit recvit sys_recvfrom amd64_syscall Xfast_syscall [root@nas4free-nodeb /tmp]# procstat -ta|grep hast 11668 100069 hastd - 0 120 sleep wait 17979 100557 hastd - 2 120 sleep g_waitid 17981 100406 hastd - 2 120 sleep uwait 17981 100559 hastd - 0 120 sleep sbwait 17981 100560 hastd - 0 120 sleep sbwait 17981 100561 hastd - 1 120 sleep uwait 17984 100078 hastd - 2 121 sleep uwait 17984 100562 hastd - 3 120 sleep sbwait 17984 100563 hastd - 2 120 sleep sbwait 17984 100564 hastd - 1 121 sleep uwait 18218 100145 hastctl - 2 152 sleep sbwait -- the procstat shows like this: