From owner-freebsd-current@FreeBSD.ORG Sat Apr 20 08:52:19 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 605DC3AD for ; Sat, 20 Apr 2013 08:52:19 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id 25BF61360 for ; Sat, 20 Apr 2013 08:52:18 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.80.1) for freebsd-current@freebsd.org with esmtp (envelope-from ) id <1UTTWr-0042ps-Lk>; Sat, 20 Apr 2013 10:52:17 +0200 Received: from g231086065.adsl.alicedsl.de ([92.231.86.65] helo=[192.168.0.128]) by inpost2.zedat.fu-berlin.de (Exim 4.80.1) for freebsd-current@freebsd.org with esmtpsa (envelope-from ) id <1UTTWr-001G93-Ii>; Sat, 20 Apr 2013 10:52:17 +0200 Subject: CURRENT: extremely unresponsive disk I/O From: "O. Hartmann" To: FreeBSD Current Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-jpBtBQEDf5w6Q+v10Dqu" Date: Sat, 20 Apr 2013 10:52:17 +0200 Message-ID: <1366447937.1475.35.camel@thor.walstatt.dyndns.org> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port X-Originating-IP: 92.231.86.65 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Apr 2013 08:52:19 -0000 --=-jpBtBQEDf5w6Q+v10Dqu Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Since a couple of weeks now, FreeBSD 10.0-CURRENT is really unresponsive when managing high disk I/O. This is most noticeable when starting the buildworld process, hwen clang 3.3 starts to build the llvm backend libraries and doing some sort of portmaster/portupgrade in parallel: even a "make rmconfig config" takes aprox. a minute to show up. Is there a known issue at this moment? I can not see such a behaviour on FreeBSD 9.1-STABLE (similar hardware). Oliver --=-jpBtBQEDf5w6Q+v10Dqu Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAABAgAGBQJRcldBAAoJEOgBcD7A/5N8zrAIAKSqxbatqLLyiwp/258qD0hi DVfp9P4V5Kz/BmzY+2JDdn4V8pVI9IfyMDxXH0YM9XCYGF8Uir+10O7J4O1mLKCX log7nb6lpM4d3ZqinQ9JTAQ15Ud3iGX5Lk+11xFBU7KOD5Tio+ax4pa8tkQlouCQ /hYw4o+oFWESd0K1ZW18zQTv3ZdF3lMdheWgq8keylHjeqm2b4ycTA+u9gyIMPdx afUIaym35fq/eisni5axhqLrpVAayNTviQmg4KwkS5XZdQGQXq4JxCGJdKs3ngUh RSeT9eYz2on+L1erQ1SS6epL8pIFAcLejzGbDLRlJ8g0AJveY75zUOgBP8PLHUw= =JI6o -----END PGP SIGNATURE----- --=-jpBtBQEDf5w6Q+v10Dqu--