From owner-freebsd-questions@FreeBSD.ORG Sat May 30 09:12:22 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C143F1065672 for ; Sat, 30 May 2009 09:12:22 +0000 (UTC) (envelope-from utisoft@googlemail.com) Received: from mail-bw0-f213.google.com (mail-bw0-f213.google.com [209.85.218.213]) by mx1.freebsd.org (Postfix) with ESMTP id 349EB8FC22 for ; Sat, 30 May 2009 09:12:21 +0000 (UTC) (envelope-from utisoft@googlemail.com) Received: by bwz9 with SMTP id 9so6683012bwz.43 for ; Sat, 30 May 2009 02:12:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:reply-to:in-reply-to :references:from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=oBcFEqdYAnXTBYOqNKeWrEBfkIPb9Ynu0+axhblMr68=; b=CbvgULx56WWtb8C1pcDfSVhYNdZbn6aI68PMgRL3Cigi2n7XzifiOUfb6VtMJ2/jx9 Oi49UXlNxrJV1KsEnBBFsOZp6/fbFpXpWA6mLojZHrajyAIo/aCQzjIb5TIxcYsLWzVQ rhXe/aj8/GYWu70WeSWR1v7wk/dTNjV/3u0yc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:content-transfer-encoding; b=LmHrsnR5NRw33iyLJVSiOVQta8Zzfkm4BBmbpkpPuvrYBb0mBSN1D2OPqA5UGluJRP JhAtQ+F7wEW392vjoYao8hfZ3BZpfdU7TS+cEUEpq/7I/DXdgjCYJkJ8LcyxftG8kvRM 7yvQWjBINzNqF5yASpQQJ15OGCMIpU3U3lzlc= MIME-Version: 1.0 Received: by 10.204.117.203 with SMTP id s11mr3302162bkq.153.1243674741124; Sat, 30 May 2009 02:12:21 -0700 (PDT) In-Reply-To: <4f760c6a0905291329w31d0df93he5aa004a3ab9bd87@mail.gmail.com> References: <4f760c6a0905291329w31d0df93he5aa004a3ab9bd87@mail.gmail.com> From: Chris Rees Date: Sat, 30 May 2009 10:12:01 +0100 Message-ID: To: claudiu vasadi Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: system reboot because of hdd X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: utisoft@gmail.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 May 2009 09:12:23 -0000 2009/5/29 claudiu vasadi : > Hello ppl. > > > Straight to business. > > FreeBSD 7.1-stable > > 2 hdd. 1 is ad2 and the other is ad6. ad2 is the BSD hdd, and ad6 is just > for data (movies, music, etc). ad2 is a 80GB Samsung P-ata133 and ad6 is a > WD 250GB S-ata2. > > While running a process that was trying to create a 25GB file on a 30 GB > partition on the second hdd (ad2) I experienced ssh outage. Everything came > back to life after a short perioud of ~2 minutes. So, again I started the > process. This time, the outage was about 5 minutes. I was busy with > something else and did not run the process again. 2 minutes after that i get > a call from a customer that some thing is not working. so I check it and > surprize, the OS rebooted itself. > > so, went to the logs and this is what i found out (/var/log/messages): > > May 29 22:26:30 da1 kernel: ad6: TIMEOUT - WRITE_DMA48 retrying (1 retry > left) LBA=419468447 > May 29 22:26:35 da1 kernel: ad6: TIMEOUT - WRITE_DMA48 retrying (0 retries > left) LBA=419468447 > May 29 22:26:41 da1 kernel: ad6: FAILURE - WRITE_DMA48 timed out > LBA=419468447 > May 29 22:26:41 da1 kernel: g_vfs_done():ad6s1f[WRITE(offset=19447808, > length=16384)]error = 5 > May 29 22:26:35 da1 syslogd: kernel boot file is /boot/kernel/kernel > May 29 22:26:35 da1 kernel: ad6: FAILURE - device detached > May 29 22:26:35 da1 kernel: subdisk6: detached > May 29 22:26:35 da1 kernel: ad6: detached > May 29 22:26:35 da1 kernel: g_vfs_done():ad6s1f[WRITE(offset=36683776, > length=16384)]error = 6 > May 29 22:26:35 da1 kernel: g_vfs_done():ad6s1f[WRITE(offset=16908288, > length=16384)]error = 6 > May 29 22:26:35 da1 kernel: g_vfs_done():ad6s1f[WRITE(offset=36700160, > length=16384)]error = 6 > May 29 22:26:35 da1 kernel: g_vfs_done():ad6s1f[WRITE(offset=114688, > length=16384)]error = 6 > May 29 22:26:35 da1 kernel: panic: vinvalbuf: dirty bufs > May 29 22:26:35 da1 kernel: cpuid = 0 > May 29 22:26:35 da1 kernel: Uptime: 45d22h15m29s > May 29 22:26:35 da1 kernel: Physical memory: 1003 MB > May 29 22:26:35 da1 kernel: Dumping 232 MB: 217 201 185 169 153 137 121 105 > 89 73 57 41 25 9 > > > > > and (/var/log/all.log): > > > May 29 22:54:49 da1 fsck: /dev/ad6s1f: 6 files, 12 used, 17132271 free (31 > frags, 2141530 blocks, 0.0% fragmentation) > > > exacly where the file was created. but it was 1 not 6 files that i wanted to > create but 1. > > > > > the process that I run is "dsmfmt" of TSM server for Sun. it creates a file > volume of a specific size for use in tsm server itself for defining storage > pool capacity. > > so, I know that the hdd was to the limit. It could be a hardware issue I > know, but right now dnt have resources to try somewere else so I'm asking a > oppinion. Has anyone dealt with this situation before ? OS reboot because of > high hdd load ? How much RAM have you got? Chris -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in a mailing list?