From owner-freebsd-stable@FreeBSD.ORG Thu Jun 29 13:32:52 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2745E16A412 for ; Thu, 29 Jun 2006 13:32:52 +0000 (UTC) (envelope-from bymer@infostore.org) Received: from tetis.uazone.net (uazone.net [212.109.44.44]) by mx1.FreeBSD.org (Postfix) with ESMTP id 40E9143D78 for ; Thu, 29 Jun 2006 13:32:45 +0000 (GMT) (envelope-from bymer@infostore.org) Received: from bzone (energylife.com.ua [62.149.0.141]) by tetis.uazone.net (8.13.3/01.001) with ESMTP id k5TDZ7q4055969 for ; Thu, 29 Jun 2006 16:35:07 +0300 (EEST) (envelope-from bymer@infostore.org) Date: Thu, 29 Jun 2006 16:32:41 +0300 From: bymer X-Mailer: The Bat! (v2.12.00) X-Priority: 3 (Normal) Message-ID: <1381607590.20060629163241@infostore.org> To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: detached disk & fsck lock X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bymer List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Jun 2006 13:32:52 -0000 Hi all, I have several computers of different configurations (other motherboards, controllers). Each have 14-20 hdd devices (ATA & SATA). All hdd is WDC WDxxxxJD or WDC WDxxxxJB. Computers periodically crashed with "disk detached" (random disk id) error: subdisk10: detached ad10: detached g_vfs_done():ad10s1h[READ(offset=289109770240, length=65536)]error = 6 g_vfs_done():ad10s1h[READ(offset=289297481728, length=131072)]error = 6 g_vfs_done():ad10s1h[READ(offset=296795766784, length=131072)]error = 6 -- skipped -- panic: vinvalbuf: dirty bufs Uptime: 13h32m44s Cannot dump. No dump device defined. Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... After reboot, it's quite likely (20-30 percents) that fsck (running in background mode) lock in ufs state and can't be killed even by SIGKILL. After it all others processes working with that device lock in ufs state too. It's appear on all FreeBSD 6 versions, from 6.0 RELEASE to 6.1-STABLE. -- Best regards, bymer mailto:bymer@infostore.org