From owner-freebsd-bugs@FreeBSD.ORG Mon Aug 13 10:10:10 2007 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 6011916A419 for ; Mon, 13 Aug 2007 10:10:10 +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 43D3013C45E for ; Mon, 13 Aug 2007 10:10:10 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.1/8.14.1) with ESMTP id l7DAA9cP043765 for ; Mon, 13 Aug 2007 10:10:09 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.1/8.14.1/Submit) id l7DAA9co043761; Mon, 13 Aug 2007 10:10:09 GMT (envelope-from gnats) Date: Mon, 13 Aug 2007 10:10:09 GMT Message-Id: <200708131010.l7DAA9co043761@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Michael Dosser Cc: Subject: Re: kern/107608: Raid Problem beim Zugriff auf Raid X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Michael Dosser List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Aug 2007 10:10:10 -0000 The following reply was made to PR kern/107608; it has been noted by GNATS. From: Michael Dosser To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/107608: Raid Problem beim Zugriff auf Raid Date: Mon, 13 Aug 2007 11:45:40 +0200 Hi, I had exactly the same messages (lots of them) on the screen of one of our servers last saturday: swap_pager: indefinite wait buffer: [couldn't type from the terminal] The machine gave back pongs when pinging, but login was impossible. All services were unresponsive. This machine acts as a web-, database- and mailserver. Before the machine was unresponsive, I saw about 300 MB of swap used. Now I see the following: # swapinfo Device 1K-blocks Used Avail Capacity /dev/da0s1b 4096380 2288 4094092 0% # uname -a FreeBSD xxx.xxxx.xx 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Fri Feb 2 15:05:26 CET 2007 root@xxx.xxxx.xx:/usr/obj/usr/src/sys/XXX i386 The machine is running since February 2007 as a production machine and this never happened. I can provide munin statistics of page in/out since February if needed. There was far more swap activity before that day what I can see from the graphs. This machine is a "Intel(R) Core(TM)2 CPU 6300 @ 1.86GHz" with four gigabyte of RAM installed. # tw_cli /c0 show all /c0 Driver Version = 3.60.02.012 /c0 Model = 9550SXU-4LP /c0 Memory Installed = 112MB /c0 Firmware Version = FE9X 3.02.00.016 /c0 Bios Version = BE9X 3.01.00.027 /c0 Monitor Version = BL9X 3.02.00.001 /c0 Serial Number = L320909A6200350 /c0 PCB Version = Rev 032 /c0 PCHIP Version = 1.60 /c0 ACHIP Version = 1.90 /c0 Number of Ports = 4 /c0 Number of Units = 2 /c0 Number of Drives = 4 /c0 Total Optimal Units = 2 /c0 Not Optimal Units = 0 /c0 JBOD Export Policy = off /c0 Disk Spinup Policy = 1 /c0 Spinup Stagger Time Policy (sec) = 2 /c0 Auto-Carving Policy = off /c0 Auto-Carving Size = 2048 GB /c0 Auto-Rebuild Policy = on /c0 Controller Bus Type = PCIX /c0 Controller Bus Width = 64 bits /c0 Controller Bus Speed = 133 Mhz Unit UnitType Status %RCmpl %V/I/M Stripe Size(GB) Cache AVrfy ------------------------------------------------------------------------------ u0 RAID-1 OK - - - 298.013 ON OFF u1 RAID-1 OK - - - 149.001 ON OFF Port Status Unit Size Blocks Serial --------------------------------------------------------------- p0 OK u0 298.09 GB 625142448 WD-WCAPD3473759 p1 OK u0 298.09 GB 625142448 WD-WCAPD3473574 p2 OK u1 149.01 GB 312500000 Y4D9GSGE p3 OK u1 149.01 GB 312500000 Y4D9GTCE Unit "u0" is the array were swap is located (and also "/", "/tmp", "/usr", "/usr/home" and "/var"), "u1" is a backup array ("/mnt"). Disks are verified via S.M.A.R.T. and they are OK. Also the controller says, the disks are functional. After a hard reset the machine was up again, no rebuild of the RAID-1 arrays were necessary. Of course background fsck was running. Is there some other information I can provide? Thanks for your help! Michael Dosser