From owner-freebsd-hardware@FreeBSD.ORG  Fri Mar  8 07:07:07 2013
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
Delivered-To: freebsd-hardware@freebsd.org
Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115])
 by hub.freebsd.org (Postfix) with ESMTP id 9D090821
 for <freebsd-hardware@freebsd.org>; Fri,  8 Mar 2013 07:07:07 +0000 (UTC)
 (envelope-from gosha-necr@yandex.ru)
Received: from forward1.mail.yandex.net (forward1.mail.yandex.net
 [IPv6:2a02:6b8:0:602::1])
 by mx1.freebsd.org (Postfix) with ESMTP id 4CBDCCDC
 for <freebsd-hardware@freebsd.org>; Fri,  8 Mar 2013 07:07:07 +0000 (UTC)
Received: from web16d.yandex.ru (web16d.yandex.ru [77.88.47.161])
 by forward1.mail.yandex.net (Yandex) with ESMTP id E3B8A1241CED
 for <freebsd-hardware@freebsd.org>; Fri,  8 Mar 2013 11:07:05 +0400 (MSK)
Received: from 127.0.0.1 (localhost.localdomain [127.0.0.1])
 by web16d.yandex.ru (Yandex) with ESMTP id 109466790322;
 Fri,  8 Mar 2013 11:07:05 +0400 (MSK)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail;
 t=1362726425; bh=8tC1kMRTkOsN5udwKfF9wa5I+ZD2dRpWZZR0fNIN2V4=;
 h=From:To:In-Reply-To:References:Subject:Date;
 b=u9c6YPNjvmgcHBwwQZ3iHlK67BXxFV+USlxuS0Hv+KiA8fFzyrIxaX/TPJFQ9eFTL
 Afw7UlYfdT+Fq0Q0wKTvDr5oZbXo0f/sTCHY2SfXhly7xhBMfecGEZUIlEkBw0pDZc
 WlbBCNKcmCAdqb/8YthV9YNX5a2w5xo6w+NoItW8=
Received: from pptp-2-115-59.kamensktel.ru (pptp-2-115-59.kamensktel.ru
 [78.139.115.59]) by web16d.yandex.ru with HTTP; 
 Fri, 08 Mar 2013 11:07:04 +0400
From: =?koi8-r?B?59XM0cXXIOfP28E=?= <gosha-necr@yandex.ru>
To: "freebsd-hardware@freebsd.org" <freebsd-hardware@freebsd.org>
In-Reply-To: <kh594r$v3g$2@ger.gmane.org>
References: <261461361939965@web1e.yandex.ru> <kh594r$v3g$2@ger.gmane.org>
Subject: Re: Strange performance problems with I/O subsystem
Message-Id: <1256991362726424@web16d.yandex.ru>
X-Mailer: Yamail [ http://yandex.ru ] 5.0
Date: Fri, 08 Mar 2013 13:07:04 +0600
X-Mailman-Approved-At: Fri, 08 Mar 2013 12:34:42 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="koi8-r"
X-Content-Filtered-By: Mailman/MimeDel 2.1.14
X-BeenThere: freebsd-hardware@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: General discussion of FreeBSD hardware <freebsd-hardware.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-hardware>, 
 <mailto:freebsd-hardware-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hardware>
List-Post: <mailto:freebsd-hardware@freebsd.org>
List-Help: <mailto:freebsd-hardware-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>, 
 <mailto:freebsd-hardware-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Mar 2013 07:07:07 -0000

   05.03.2013, 23:14, "Ivan Voras" <ivoras@freebsd.org>:

     On 27/02/2013 05:39, Гуляев Гоша wrote:

     And when I have some intensive I/O tasks (csup -g /root/mysupfile,
     or
     portsnap fetch update, or rm -rf /usr/obj, when system working
     sequentialy with many files in general) my system begins
     periodically
     freezes. If I see gstat it shows me 100% I\O on disk.

     It usually means some kind of incompatibility of your disk drive and
     the
     system, its controller or its driver.
     Sometimes it could me that the disk is broken.

   Ivan, thank for answer! I think there is no any hardware problem,
   because as I say before, in other OS'es all works fine, without
   performance problems. How I can diagnose problem deeply, and maybe give
   some useful information for resolving that issue?

   --------------------------------------------
   С уважением, Гуляев Гоша.