From owner-freebsd-bugs@FreeBSD.ORG Tue Jun 7 13:10:12 2011 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 03D4E106567A for ; Tue, 7 Jun 2011 13:10:12 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id E85F08FC12 for ; Tue, 7 Jun 2011 13:10:11 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p57DABM0009622 for ; Tue, 7 Jun 2011 13:10:11 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p57DABkO009621; Tue, 7 Jun 2011 13:10:11 GMT (envelope-from gnats) Date: Tue, 7 Jun 2011 13:10:11 GMT Message-Id: <201106071310.p57DABkO009621@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: "Eugene M. Zheganin" Cc: Subject: Re: kern/157534: [mpt] freeze when disk is removed/died from geom_mirror/zfs raid X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Eugene M. Zheganin" List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Jun 2011 13:10:12 -0000 The following reply was made to PR kern/157534; it has been noted by GNATS. From: "Eugene M. Zheganin" To: bug-followup@FreeBSD.org, eugene@zhegan.in Cc: Subject: Re: kern/157534: [mpt] freeze when disk is removed/died from geom_mirror/zfs raid Date: Tue, 07 Jun 2011 19:00:19 +0600 Seems like its more zfs-related freeze. geom_mirror(4) seems to be able to detect that one of the providers is gone in about a minute. When dealing with a zfs mirrored pool, the console is constantly updated with these messages: [...] mpt0: completing timedout/aborted req 0xffffff80002be9c0:2484 mpt0: completing timedout/aborted req 0xffffff80002be6f0:2483 mpt0: completing timedout/aborted req 0xffffff80002be810:2482 mpt0: completing timedout/aborted req 0xffffff80002bde80:2481 mpt0: abort of req 0xffffff80002bde80:0 completed mpt0: request 0xffffff80002be660:2486 timed out for ccb 0xffffff00035ea800 (req>ccb 0xffffff00035ea800) mpt0: request 0xffffff80002be930:2487 timed out for ccb 0xffffff00035da000 (req>ccb 0xffffff00035da000) mpt0: completing timedout/aborted req 0xffffff80002aff30:2582 mpt0: abort of req 0xffffff80002aff30:0 completed2486 function 0 mpt0: request 0xffffff80002afb40:2584 timed out for ccb 0xffffff00035c0000 (req>ccb 0xffffff00035c0000) mpt0: attempting to abort req 0xffffff80002afb40:2584 function 0 mpt0: completing timedout/aborted req 0xffffff80002afb40:2584 [...] This is 100% reproduceable. Unfortunately, I got like 11 of these servers. I can provide root ssh and local console (vie IP KVM) to one of them, along with my help in any destructive testing.