From owner-freebsd-stable@FreeBSD.ORG Sun Aug 19 02:07:22 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7511416A417 for ; Sun, 19 Aug 2007 02:07:22 +0000 (UTC) (envelope-from vivek@khera.org) Received: from yertle.kcilink.com (thingy.kcilink.com [74.92.149.59]) by mx1.freebsd.org (Postfix) with ESMTP id 4918B13C442 for ; Sun, 19 Aug 2007 02:07:22 +0000 (UTC) (envelope-from vivek@khera.org) Received: from [192.168.135.92] (unknown [192.168.135.92]) by yertle.kcilink.com (Postfix) with ESMTP id 3183BB80D for ; Sat, 18 Aug 2007 22:07:21 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v752.2) In-Reply-To: <20070818080912.GA6704@voi.aagh.net> References: <31BB09D7-B58A-47AC-8DD1-6BB8141170D8@khera.org> <20070818080912.GA6704@voi.aagh.net> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Vivek Khera Date: Sat, 18 Aug 2007 22:07:19 -0400 To: FreeBSD Stable X-Mailer: Apple Mail (2.752.2) Subject: Re: large RAID volume partition strategy X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Aug 2007 02:07:22 -0000 On Aug 18, 2007, at 4:09 AM, Thomas Hurst wrote: > Best temper your fear with some thorough testing then. If you are > going > to use ZFS in such a situation, though, I might be strongly tempted to > use Solaris instead. > > Why the long gaps between maintenance? This is a DB server for a 24x7 service. Maintenance involves moving the DB master server to one of the replicas, and this involves downtime, so we like to do it as infrequently as possible. Also, it is not exposed to the internet at large, and runs on a closed private network, so remote and local attacks are not a major concern. From owner-freebsd-stable@FreeBSD.ORG Sun Aug 19 06:26:45 2007 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9CC3616A419 for ; Sun, 19 Aug 2007 06:26:45 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.freebsd.org (Postfix) with ESMTP id 505EE13C467 for ; Sun, 19 Aug 2007 06:26:45 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2.sentex.ca [199.212.134.9]) by smarthost2.sentex.ca (8.14.1/8.13.8) with ESMTP id l7J64d29029453; Sun, 19 Aug 2007 02:04:41 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-stable.sentex.ca (freebsd-stable.sentex.ca [64.7.128.103]) by smtp2.sentex.ca (8.14.1/8.14.1) with ESMTP id l7J64cr5044382; Sun, 19 Aug 2007 02:04:38 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-stable.sentex.ca (Postfix, from userid 666) id 0A667241A2; Sun, 19 Aug 2007 02:04:49 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20070819060450.0A667241A2@freebsd-stable.sentex.ca> Date: Sun, 19 Aug 2007 02:04:49 -0400 (EDT) X-Virus-Scanned: ClamAV version 0.91.1, clamav-milter version 0.91.1 on clamscanner2 X-Virus-Status: Clean Cc: Subject: [releng_6 tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Aug 2007 06:26:45 -0000 TB --- 2007-08-19 04:15:22 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2007-08-19 04:15:22 - starting RELENG_6 tinderbox run for amd64/amd64 TB --- 2007-08-19 04:15:22 - cleaning the object tree TB --- 2007-08-19 04:16:14 - checking out the source tree TB --- 2007-08-19 04:16:14 - cd /tinderbox/RELENG_6/amd64/amd64 TB --- 2007-08-19 04:16:14 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_6 src TB --- 2007-08-19 04:26:18 - building world (CFLAGS=-O2 -pipe) TB --- 2007-08-19 04:26:18 - cd /src TB --- 2007-08-19 04:26:18 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> stage 5.1: building 32 bit shim libraries TB --- 2007-08-19 05:59:38 - generating LINT kernel config TB --- 2007-08-19 05:59:38 - cd /src/sys/amd64/conf TB --- 2007-08-19 05:59:38 - /usr/bin/make -B LINT TB --- 2007-08-19 05:59:38 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2007-08-19 05:59:38 - cd /src TB --- 2007-08-19 05:59:38 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sun Aug 19 05:59:38 UTC 2007 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] /src/sys/dev/cxgb/cxgb_main.c: In function `cxgb_set_rxmode': /src/sys/dev/cxgb/cxgb_main.c:1739: error: `SA_LOCKED' undeclared (first use in this function) /src/sys/dev/cxgb/cxgb_main.c: In function `cxgb_stop_locked': /src/sys/dev/cxgb/cxgb_main.c:1750: error: `SA_LOCKED' undeclared (first use in this function) /src/sys/dev/cxgb/cxgb_main.c:1751: error: `SA_UNLOCKED' undeclared (first use in this function) /src/sys/dev/cxgb/cxgb_main.c: In function `cxgb_start_tx': /src/sys/dev/cxgb/cxgb_main.c:1934: warning: implicit declaration of function `m_sanity' /src/sys/dev/cxgb/cxgb_main.c:1934: warning: nested extern declaration of `m_sanity' *** Error code 1 Stop in /obj/amd64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2007-08-19 06:04:49 - WARNING: /usr/bin/make returned exit code 1 TB --- 2007-08-19 06:04:49 - ERROR: failed to build lint kernel TB --- 2007-08-19 06:04:49 - tinderbox aborted TB --- 1.57 user 5.04 system 6567.17 real http://tinderbox.des.no/tinderbox-releng_6-RELENG_6-amd64-amd64.full From owner-freebsd-stable@FreeBSD.ORG Sun Aug 19 07:33:36 2007 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0F3C416A417; Sun, 19 Aug 2007 07:33:36 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id B0B4413C45A; Sun, 19 Aug 2007 07:33:35 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.13.8/8.13.8) with ESMTP id l7J7XYQX079155; Sun, 19 Aug 2007 03:33:34 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-stable.sentex.ca (freebsd-stable.sentex.ca [64.7.128.103]) by smtp2.sentex.ca (8.14.1/8.14.1) with ESMTP id l7J7XYSE034893; Sun, 19 Aug 2007 03:33:34 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-stable.sentex.ca (Postfix, from userid 666) id 3A15F241A2; Sun, 19 Aug 2007 03:33:46 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20070819073346.3A15F241A2@freebsd-stable.sentex.ca> Date: Sun, 19 Aug 2007 03:33:46 -0400 (EDT) X-Virus-Scanned: ClamAV version 0.91.1, clamav-milter version 0.91.1 on clamscanner2 X-Virus-Status: Clean Cc: Subject: [releng_6 tinderbox] failure on i386/i386 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Aug 2007 07:33:36 -0000 TB --- 2007-08-19 06:04:50 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2007-08-19 06:04:50 - starting RELENG_6 tinderbox run for i386/i386 TB --- 2007-08-19 06:04:50 - cleaning the object tree TB --- 2007-08-19 06:05:29 - checking out the source tree TB --- 2007-08-19 06:05:29 - cd /tinderbox/RELENG_6/i386/i386 TB --- 2007-08-19 06:05:29 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_6 src TB --- 2007-08-19 06:18:34 - building world (CFLAGS=-O2 -pipe) TB --- 2007-08-19 06:18:34 - cd /src TB --- 2007-08-19 06:18:34 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2007-08-19 07:28:03 - generating LINT kernel config TB --- 2007-08-19 07:28:03 - cd /src/sys/i386/conf TB --- 2007-08-19 07:28:03 - /usr/bin/make -B LINT TB --- 2007-08-19 07:28:03 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2007-08-19 07:28:03 - cd /src TB --- 2007-08-19 07:28:03 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sun Aug 19 07:28:03 UTC 2007 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] /src/sys/dev/cxgb/cxgb_main.c: In function `cxgb_set_rxmode': /src/sys/dev/cxgb/cxgb_main.c:1739: error: `SA_LOCKED' undeclared (first use in this function) /src/sys/dev/cxgb/cxgb_main.c: In function `cxgb_stop_locked': /src/sys/dev/cxgb/cxgb_main.c:1750: error: `SA_LOCKED' undeclared (first use in this function) /src/sys/dev/cxgb/cxgb_main.c:1751: error: `SA_UNLOCKED' undeclared (first use in this function) /src/sys/dev/cxgb/cxgb_main.c: In function `cxgb_start_tx': /src/sys/dev/cxgb/cxgb_main.c:1934: warning: implicit declaration of function `m_sanity' /src/sys/dev/cxgb/cxgb_main.c:1934: warning: nested extern declaration of `m_sanity' *** Error code 1 Stop in /obj/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2007-08-19 07:33:46 - WARNING: /usr/bin/make returned exit code 1 TB --- 2007-08-19 07:33:46 - ERROR: failed to build lint kernel TB --- 2007-08-19 07:33:46 - tinderbox aborted TB --- 1.25 user 3.95 system 5335.94 real http://tinderbox.des.no/tinderbox-releng_6-RELENG_6-i386-i386.full From owner-freebsd-stable@FreeBSD.ORG Sun Aug 19 08:53:33 2007 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 23D1316A420; Sun, 19 Aug 2007 08:53:33 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.freebsd.org (Postfix) with ESMTP id C76ED13C469; Sun, 19 Aug 2007 08:53:32 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by smarthost2.sentex.ca (8.14.1/8.13.8) with ESMTP id l7J8rVQM036384; Sun, 19 Aug 2007 04:53:32 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-stable.sentex.ca (freebsd-stable.sentex.ca [64.7.128.103]) by smtp1.sentex.ca (8.14.1/8.14.1) with ESMTP id l7J8rVN5087428; Sun, 19 Aug 2007 04:53:31 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-stable.sentex.ca (Postfix, from userid 666) id 79228241A2; Sun, 19 Aug 2007 04:53:42 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20070819085342.79228241A2@freebsd-stable.sentex.ca> Date: Sun, 19 Aug 2007 04:53:42 -0400 (EDT) X-Virus-Scanned: ClamAV version devel-20070102, clamav-milter version devel-111206 on clamscanner3 X-Virus-Status: Clean Cc: Subject: [releng_6 tinderbox] failure on i386/pc98 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Aug 2007 08:53:33 -0000 TB --- 2007-08-19 07:33:46 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2007-08-19 07:33:46 - starting RELENG_6 tinderbox run for i386/pc98 TB --- 2007-08-19 07:33:46 - cleaning the object tree TB --- 2007-08-19 07:34:21 - checking out the source tree TB --- 2007-08-19 07:34:21 - cd /tinderbox/RELENG_6/i386/pc98 TB --- 2007-08-19 07:34:21 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_6 src TB --- 2007-08-19 07:44:36 - building world (CFLAGS=-O2 -pipe) TB --- 2007-08-19 07:44:36 - cd /src TB --- 2007-08-19 07:44:36 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2007-08-19 08:48:35 - generating LINT kernel config TB --- 2007-08-19 08:48:35 - cd /src/sys/pc98/conf TB --- 2007-08-19 08:48:35 - /usr/bin/make -B LINT TB --- 2007-08-19 08:48:35 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2007-08-19 08:48:35 - cd /src TB --- 2007-08-19 08:48:35 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sun Aug 19 08:48:35 UTC 2007 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] /src/sys/dev/cxgb/cxgb_main.c: In function `cxgb_set_rxmode': /src/sys/dev/cxgb/cxgb_main.c:1739: error: `SA_LOCKED' undeclared (first use in this function) /src/sys/dev/cxgb/cxgb_main.c: In function `cxgb_stop_locked': /src/sys/dev/cxgb/cxgb_main.c:1750: error: `SA_LOCKED' undeclared (first use in this function) /src/sys/dev/cxgb/cxgb_main.c:1751: error: `SA_UNLOCKED' undeclared (first use in this function) /src/sys/dev/cxgb/cxgb_main.c: In function `cxgb_start_tx': /src/sys/dev/cxgb/cxgb_main.c:1934: warning: implicit declaration of function `m_sanity' /src/sys/dev/cxgb/cxgb_main.c:1934: warning: nested extern declaration of `m_sanity' *** Error code 1 Stop in /obj/pc98/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2007-08-19 08:53:42 - WARNING: /usr/bin/make returned exit code 1 TB --- 2007-08-19 08:53:42 - ERROR: failed to build lint kernel TB --- 2007-08-19 08:53:42 - tinderbox aborted TB --- 1.28 user 3.91 system 4795.78 real http://tinderbox.des.no/tinderbox-releng_6-RELENG_6-i386-pc98.full From owner-freebsd-stable@FreeBSD.ORG Mon Aug 20 01:09:17 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5501B16A468 for ; Mon, 20 Aug 2007 01:09:17 +0000 (UTC) (envelope-from root@runemedia.net) Received: from runemedia.net (206-225-83-111.dedicated.abac.net [206.225.83.111]) by mx1.freebsd.org (Postfix) with ESMTP id 42F3613C47E for ; Mon, 20 Aug 2007 01:09:17 +0000 (UTC) (envelope-from root@runemedia.net) Received: (qmail 1247 invoked by uid 0); 19 Aug 2007 14:30:29 -0400 Date: 19 Aug 2007 14:30:29 -0400 Message-ID: <20070819183029.1243.qmail@runemedia.net> To: freebsd-stable@freebsd.org From: dating24 MIME-Version: 1.0 Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Your account on dating24.ro Enjoy! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2007 01:09:17 -0000 [1]www.dating24.ro - anunturi - prietenii - intalniri - matrimoniale - - chat privat - chat public - poze - [2]Intra si tu alaturi de prietenii tai in comunitatea dating24.ro Te asteptam! [3]Inregistreaza-te acum! _________________________________________________________________ Utilizatorii Yahoo, Gmail sau Hotmail! In cazul in care ati primit acest mesaj in Bulk va rugam sa adaugati adresa noreply@dating24.ro in Adress Book sau la Contacte Personale, dupa caz. Va multumim pentru intelegere si va uram succes in continuare. Echipa [4]dating24.ro References 1. http://www.dating24.ro/ 2. http://www.dating24.ro/ 3. http://www.dating24.ro/inregistrare_pas1.php 4. http://www.dating24.ro/ From owner-freebsd-stable@FreeBSD.ORG Mon Aug 20 09:17:45 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B749916A469 for ; Mon, 20 Aug 2007 09:17:45 +0000 (UTC) (envelope-from kometen@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.227]) by mx1.freebsd.org (Postfix) with ESMTP id 757C213C45D for ; Mon, 20 Aug 2007 09:17:45 +0000 (UTC) (envelope-from kometen@gmail.com) Received: by wx-out-0506.google.com with SMTP id i29so1085937wxd for ; Mon, 20 Aug 2007 02:17:44 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=jqrMzUQ9e3Mvn88iHLAZJ8EeHXKKg2gE4eN03x/oyiwqe4BNAv+7QSIG7LGHwL1Hl01ycPkJQgvKsXLcONWFQguMP+gmmw6eEc1sWTuhw0roNXw//7loutN0T7cpNOHpaoG2wGLU61RFf203XltOXAgs1C/SgwRbde26IfHWbp4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=KKyh0wUaQMfVr6fp7jDLNWcM0oFYP6WD6i4q70PnZKfqQDG3F3TVMzpN/OOxE8p5yLMjkIT3lbBUqUyQExP00tt2PfUqON/lNc9i60HOzt6kRqwkLLRSHKpYpC6sOZimadRzq6rtKESUx+jVm/Pm22QPTwd+JgKQOMPdNvySy18= Received: by 10.70.65.8 with SMTP id n8mr10346763wxa.1187601464551; Mon, 20 Aug 2007 02:17:44 -0700 (PDT) Received: by 10.70.109.20 with HTTP; Mon, 20 Aug 2007 02:17:44 -0700 (PDT) Message-ID: Date: Mon, 20 Aug 2007 11:17:44 +0200 From: "Claus Guttesen" To: "Vivek Khera" In-Reply-To: <3A05E0E7-403E-4203-9B9B-AC78549D4E17@khera.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <31BB09D7-B58A-47AC-8DD1-6BB8141170D8@khera.org> <3A05E0E7-403E-4203-9B9B-AC78549D4E17@khera.org> Cc: FreeBSD Stable Subject: Re: large RAID volume partition strategy X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2007 09:17:45 -0000 > > If you want to avoid the long fsck-times your remaining options are a > > journaling filesystem or zfs, either requires an upgrade from freebsd > > 6.2. I have used zfs and had a serverstop due to powerutage in out > > area. Our zfs-samba-server came up fine with no data corruption. So I > > will suggest freebsd 7.0 with zfs. > > But, if I don't go with zfs, which would be a better way to slice the > space up: RAID volumes exported as individual disks to freebsd, or > one RAID volume divided into multiple logical partitions with disklabel? If you want to place data and the transaction-log on different partitions you want to be shure they reside on different physical disks so you probably want option 1. -- regards Claus When lenity and cruelty play for a kingdom, the gentlest gamester is the soonest winner. Shakespeare From owner-freebsd-stable@FreeBSD.ORG Mon Aug 20 16:17:50 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 82B9D16A419 for ; Mon, 20 Aug 2007 16:17:50 +0000 (UTC) (envelope-from robert.slawson@charter.net) Received: from que02.charter.net (que02.charter.net [209.225.8.190]) by mx1.freebsd.org (Postfix) with ESMTP id 2A0BE13C48D for ; Mon, 20 Aug 2007 16:17:48 +0000 (UTC) (envelope-from robert.slawson@charter.net) Received: from aa02.charter.net ([10.20.200.154]) by mtao03.charter.net (InterMail vM.7.08.02.00 201-2186-121-20061213) with ESMTP id <20070820151346.ZDMB10962.mtao03.charter.net@aa02.charter.net> for ; Mon, 20 Aug 2007 11:13:46 -0400 Received: from [192.168.0.101] (really [24.182.204.212]) by aa02.charter.net with ESMTP id <20070820151345.QCAJ26124.aa02.charter.net@[192.168.0.101]> for ; Mon, 20 Aug 2007 11:13:45 -0400 Mime-Version: 1.0 (Apple Message framework v752.3) Content-Transfer-Encoding: 7bit Message-Id: <2306ABA6-49A6-412E-81CD-CBABAE885EB2@charter.net> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: freebsd-stable@freebsd.org From: Robert Slawson Date: Mon, 20 Aug 2007 10:13:42 -0500 X-Mailer: Apple Mail (2.752.3) X-Chzlrs: 0 Subject: Marvel Yukon using the sk driver X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2007 16:17:50 -0000 Greetings, I have a marvel yukon pci gigabit ethernet card. For some reason, after a period of time it will not transmit unless I make it transmit by pinging via the console. It is very annoying as I cannot ssh into the machine until I "wake up" the card by telling it to ping something. I am using 6.2 stable and just yesterday rebuilt the kernel and world hoping this would fix the problem. But nothing seems to help. I think the card needs to use the msk driver , which is installed, but the card keeps using the sk driver. Is there a way to have freebsd re identify the card correctly and use the proper driver? Thanks in advance, Bob From owner-freebsd-stable@FreeBSD.ORG Mon Aug 20 19:01:35 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4BEB516A4EE for ; Mon, 20 Aug 2007 19:01:34 +0000 (UTC) (envelope-from nik@mail.optim-mol.cemu.ru) Received: from mail.optim-mol.cemu.ru (mail.optim-mol.cemu.ru [83.102.188.27]) by mx1.freebsd.org (Postfix) with ESMTP id 8C0FE13C48A for ; Mon, 20 Aug 2007 19:01:34 +0000 (UTC) (envelope-from nik@mail.optim-mol.cemu.ru) Received: from user-105na47.cable.mindspring.com ([64.91.168.135] helo=[192.168.2.254]) by mail.optim-mol.cemu.ru with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67 (FreeBSD)) (envelope-from ) id 1INBeI-000NwC-8T; Mon, 20 Aug 2007 22:06:49 +0400 Message-ID: <46C9D817.1070704@optim.com.ru> Date: Mon, 20 Aug 2007 13:06:15 -0500 From: Nikolay Mirin Organization: =?UTF-8?B?0J7Qn9Ci0JjQnA==?= User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: Robert Slawson , freebsd-stable@freebsd.org References: <2306ABA6-49A6-412E-81CD-CBABAE885EB2@charter.net> In-Reply-To: <2306ABA6-49A6-412E-81CD-CBABAE885EB2@charter.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: nik@mail.optim-mol.cemu.ru X-SA-Exim-Connect-IP: 64.91.168.135 X-SA-Exim-Mail-From: nik@mail.optim-mol.cemu.ru X-SA-Exim-Scanned: No (on mail.optim-mol.cemu.ru); SAEximRunCond expanded to false Cc: Subject: Re: Marvel Yukon using the sk driver X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2007 19:01:35 -0000 Hi, what I can tell. I had a terrible problem with this card (PCI-E version) exactly one week ago. Both drivers msk from the system and myk from the vendor show similar behavior. On high loads, like 2-3 users from Samba domain pulling their profiles at the same time, the card just chokes. No ping, and "buffer overflow message". I mean I had to bring the interface down and up again. Absolutely disgusting. No tweak helps. I mean, we tested it over the weekend and it was fine, till folks come there on Monday and start massively using the server. We downgraded the hardware and put good old 3Com509 PCI or whatever works with xl driver. Robert Slawson said the following on 20.08.2007 10:13: > Greetings, > > I have a marvel yukon pci gigabit ethernet card. For some reason, > after a period of time it will not transmit unless I make it transmit > by pinging via the console. It is very annoying as I cannot ssh into > the machine until I "wake up" the card by telling it to ping something. > > I am using 6.2 stable and just yesterday rebuilt the kernel and world > hoping this would fix the problem. But nothing seems to help. > > I think the card needs to use the msk driver , which is installed, but > the card keeps using the sk driver. Is there a way to have freebsd re > identify the card correctly and use the proper driver? > > Thanks in advance, > Bob > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Mon Aug 20 21:06:03 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4CE6B16A417 for ; Mon, 20 Aug 2007 21:06:03 +0000 (UTC) (envelope-from clay@milos.co.za) Received: from bart.milos.co.za (bart.milos.co.za [196.38.18.66]) by mx1.freebsd.org (Postfix) with ESMTP id F3B8013C45A for ; Mon, 20 Aug 2007 21:06:01 +0000 (UTC) (envelope-from clay@milos.co.za) Received: (qmail 67762 invoked by uid 89); 20 Aug 2007 21:08:14 -0000 Received: by simscan 1.2.0 ppid: 67757, pid: 67759, t: 0.6886s scanners: attach: 1.2.0 clamav: 0.88.7/m:43/d:3604 Received: from unknown (HELO claylaptop) (clay@milos.za.net@84.203.53.189) by bart.milos.co.za with ESMTPA; 20 Aug 2007 21:08:14 -0000 Message-ID: <006c01c7e36d$e67f95d0$0701a8c0@claylaptop> From: "Clayton Milos" To: References: <2306ABA6-49A6-412E-81CD-CBABAE885EB2@charter.net> <46C9D817.1070704@optim.com.ru> Date: Mon, 20 Aug 2007 22:05:53 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="UTF-8"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 Subject: Re: Marvel Yukon using the sk driver X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2007 21:06:03 -0000 > Hi, what I can tell. > I had a terrible problem with this card (PCI-E version) exactly one week > ago. Both drivers msk from the system and myk from the vendor show similar > behavior. > On high loads, like 2-3 users from Samba domain pulling their profiles at > the same time, the card just chokes. No ping, and > "buffer overflow message". > I mean I had to bring the interface down and up again. Absolutely > disgusting. > No tweak helps. > > I mean, we tested it over the weekend and it was fine, till folks come > there on Monday and start massively using the server. > > We downgraded the hardware and put good old 3Com509 PCI or whatever works > with xl driver. > > > Robert Slawson said the following on 20.08.2007 10:13: >> Greetings, >> >> I have a marvel yukon pci gigabit ethernet card. For some reason, after a >> period of time it will not transmit unless I make it transmit by pinging >> via the console. It is very annoying as I cannot ssh into the machine >> until I "wake up" the card by telling it to ping something. >> >> I am using 6.2 stable and just yesterday rebuilt the kernel and world >> hoping this would fix the problem. But nothing seems to help. >> >> I think the card needs to use the msk driver , which is installed, but >> the card keeps using the sk driver. Is there a way to have freebsd re >> identify the card correctly and use the proper driver? >> >> Thanks in advance, >> Bob >From my experience it always pays to use good hardware. I use 3com/Broadcom or Intel NIC's. Nothing else. Ever! They get much better throughput with less CPU overhead. And the real advantage is they have good suport in UNIX systems. I know Jack Vogel did his best and sorted out the issues with mine and many other people's Intel gigabit (em based) cards when there were issues. My em card is flying along happily now like it should be. The last server I bought had dual onboard Broadcom NIC's and I've had not issues throwing 500Mbit/s through them. Haven't had a chance to really push them to the limits yet. I know I'm not really helping you directly here but my advice would be to throw an Intel gigabit desktop adapter in there and your problems will disappear. They're only $20-$30 nowadays and it's going to take your headache away. -Clay From owner-freebsd-stable@FreeBSD.ORG Mon Aug 20 22:38:46 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3411116A417 for ; Mon, 20 Aug 2007 22:38:46 +0000 (UTC) (envelope-from matrix@itlegion.ru) Received: from corpmail.itlegion.ru (corpmail.itlegion.ru [84.21.226.211]) by mx1.freebsd.org (Postfix) with SMTP id 7678C13C4DA for ; Mon, 20 Aug 2007 22:38:45 +0000 (UTC) (envelope-from matrix@itlegion.ru) Received: (qmail 86233 invoked from network); 21 Aug 2007 02:38:43 +0400 Received: from unknown (HELO Artem) (192.168.0.12) by 84.21.226.211 with SMTP; 21 Aug 2007 02:38:43 +0400 X-AntiVirus: Checked by Dr.Web [version: 4.33, engine: 4.33.5.10110, virus records: 238958, updated: 20.08.2007] Message-ID: <028f01c7e37a$d8f441b0$0c00a8c0@Artem> From: "Artem Kuchin" To: Date: Tue, 21 Aug 2007 02:38:34 +0400 Organization: IT Legion MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="koi8-r"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 Subject: A little story of failed raid5 (3ware 8000 series) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2007 22:38:46 -0000 Hello! Here is the newest story of mine about how one should never use raid5. Controller is 8xxx-4LP. I have a simple 360GB raid5 with 4 drives since 2004. Only about a year ago i realized how much speed i have wasted be saving lousy 120GB. I should have choosen bigger driver and setup two mirrors instead. But that's no the point. A week ago one driver just totally failed. It fell out of the unit and when i tried to rebuild the unit it failed. It seemed like the driver electronis failed. ANyhow, i have found newest 160gb seagate driver for replacement (twice as thin, very nicely done electornics on it). A day ago at 11 am i have turn off the server, pull out the old driver, installed a new one, turned of the server and started rebuild in an hour from remote location via web interface. After about 5 minuted the machine became unresponsive. Tried rebooting - nothing. I went to the machine and fingure out, that rebuild failed (0%) and some data cannot be read because of bad sectors. Well, hell, i thoght. Maybe i could tell teh controller to ignore all the errors and just some rebuilding and the figure out which driver failed, replace it, rebuild again and restore corrupted data from backup. Noway, controller said. - i cannot make it ignore read errors - i cannot figure out which driver has bad sectors (maybe someone know it?) But i don't understand how and why it happened. ONly 6 hours ago (a night before) all those files were backed up fine w/o any read error. And now, right after replacing the driver and starting rebuild it said that there are bad sectors all over those file. How come? Well. Since we have a buch of full and inceremnetal paraoid backups no data was lost and we are in process of recovering. However, i simply imaged what would happed if one more driver completelly failed. That would mean that we have lost all data, since any of the disk which left do not contain any readable copy of one data (unlink mirror, for example). So, we are migrating to mirror config with huge disks. I am thinking about raid10 for more perfomance. It seems a lot more safe, since if any pair of disks failed the data is still readable and even if all disks have bad block the data can be easily recovered by fairly simply script from the couterpart. But the problem, however, So, no raid5 or even raid 6 for me any more. Never! -- Regards, Artem From owner-freebsd-stable@FreeBSD.ORG Tue Aug 21 00:10:49 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3E1EC16A417 for ; Tue, 21 Aug 2007 00:10:49 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id EC3F913C45A for ; Tue, 21 Aug 2007 00:10:48 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from phobos.samsco.home (phobos.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.8/8.13.8) with ESMTP id l7L0AjIx058033; Mon, 20 Aug 2007 18:10:45 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <46CA2D83.1070109@samsco.org> Date: Mon, 20 Aug 2007 18:10:43 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.6) Gecko/20070802 SeaMonkey/1.1.4 MIME-Version: 1.0 To: Artem Kuchin References: <028f01c7e37a$d8f441b0$0c00a8c0@Artem> In-Reply-To: <028f01c7e37a$d8f441b0$0c00a8c0@Artem> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (pooker.samsco.org [168.103.85.57]); Mon, 20 Aug 2007 18:10:45 -0600 (MDT) X-Spam-Status: No, score=-1.4 required=5.5 tests=ALL_TRUSTED autolearn=failed version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org Cc: freebsd-stable@freebsd.org Subject: Re: A little story of failed raid5 (3ware 8000 series) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 00:10:49 -0000 Artem Kuchin wrote: > > So, no raid5 or even raid 6 for me any more. Never! > > A better policy is to invest in a higher quality RAID controller. Also, always use a battery backup on the controller, and always have an extra disk configured as a hot spare. Data integrity is expensive, unfortunately. Scott From owner-freebsd-stable@FreeBSD.ORG Tue Aug 21 00:39:48 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AC89D16A41A for ; Tue, 21 Aug 2007 00:39:48 +0000 (UTC) (envelope-from lists@pingle.org) Received: from willow.pingle.org (willow.pingle.org [208.149.144.13]) by mx1.freebsd.org (Postfix) with ESMTP id 842B213C442 for ; Tue, 21 Aug 2007 00:39:48 +0000 (UTC) (envelope-from lists@pingle.org) Received: from localhost (unknown [127.0.0.1]) by willow.pingle.org (Postfix) with ESMTP id 00C5F11498; Mon, 20 Aug 2007 20:39:48 -0400 (EDT) X-Virus-Scanned: amavisd-new at pingle.org Received: from willow.pingle.org ([127.0.0.1]) by localhost (willow.pingle.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hgrt6-eoa4kF; Mon, 20 Aug 2007 20:39:46 -0400 (EDT) Received: from [192.168.0.4] (josie.pingle.org [209.125.59.4]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jim) by willow.pingle.org (Postfix) with ESMTP id 063FB11496; Mon, 20 Aug 2007 20:39:45 -0400 (EDT) Message-ID: <46CA3445.2020003@pingle.org> Date: Mon, 20 Aug 2007 20:39:33 -0400 From: Jim Pingle User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: Artem Kuchin References: <028f01c7e37a$d8f441b0$0c00a8c0@Artem> In-Reply-To: <028f01c7e37a$d8f441b0$0c00a8c0@Artem> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: A little story of failed raid5 (3ware 8000 series) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 00:39:48 -0000 Artem Kuchin wrote: > A day ago at 11 am i have turn off the server, > pull out the old driver, installed a new one, turned of the server > and started rebuild in an hour from remote location via web interface. > After about 5 minuted the machine became unresponsive. Tried rebooting > - nothing. I went to the machine and fingure out, that rebuild failed (0%) > and some data cannot be read because of bad sectors. We had a similar failure a few years ago, in fact every drive in the array had bad sectors, but one failed completely. Rebuild would not work no matter what we did. Yet another reason to be sure your RAID disks come from different manufacturing batches! > - i cannot make it ignore read errors > - i cannot figure out which driver has bad sectors > (maybe someone know it?) We recovered from that situation like so: 1. Power off the server 2. Pull each drive, attach to another box w/o RAID adapter and use diagnostic tools to run a surface scan/remap on each disk. (These were SCSI disks, not sure if the same applies to PATA/SATA) 3. Put all drives back, including a replacement for the truly failed drive 4. Let the array rebuild Many crossed fingers/toes/eyes later, it came back to life. We replaced the whole box shortly thereafter. The downside was the entire server was offline for the duration of the process, instead of being online during a normal rebuild. > So, no raid5 or even raid 6 for me any more. Never! If it's done properly, with hot spares and other failsafe measures, it isn't too bad. Sometimes it's the best available option due to budget/hardware/etc constraints, especially on older systems. RAID can be a tough beast, though. We had one server that ran fine for nearly 5 years on a single PATA disk. Two months after I rebuild it with a proper SCSI RAID setup, it has a multi-drive failure and bombs. Sometimes all the safety measures in the world can't make up for what passes for hardware quality these days... Jim From owner-freebsd-stable@FreeBSD.ORG Tue Aug 21 00:49:53 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1775416A41B for ; Tue, 21 Aug 2007 00:49:53 +0000 (UTC) (envelope-from nik@mail.optim-mol.cemu.ru) Received: from mail.optim-mol.cemu.ru (mail.optim-mol.cemu.ru [83.102.188.27]) by mx1.freebsd.org (Postfix) with ESMTP id C593313C45D for ; Tue, 21 Aug 2007 00:49:52 +0000 (UTC) (envelope-from nik@mail.optim-mol.cemu.ru) Received: from user-105na47.cable.mindspring.com ([64.91.168.135] helo=[192.168.2.254]) by mail.optim-mol.cemu.ru with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67 (FreeBSD)) (envelope-from ) id 1INHwK-000P4H-BO; Tue, 21 Aug 2007 04:49:51 +0400 Message-ID: <46CA368D.3010505@optim.com.ru> Date: Mon, 20 Aug 2007 19:49:17 -0500 From: Nikolay Mirin Organization: =?UTF-8?B?0J7Qn9Ci0JjQnA==?= User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: Clayton Milos , freebsd-stable@freebsd.org References: <2306ABA6-49A6-412E-81CD-CBABAE885EB2@charter.net> <46C9D817.1070704@optim.com.ru> <006c01c7e36d$e67f95d0$0701a8c0@claylaptop> In-Reply-To: <006c01c7e36d$e67f95d0$0701a8c0@claylaptop> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: nik@mail.optim-mol.cemu.ru X-SA-Exim-Connect-IP: 64.91.168.135 X-SA-Exim-Mail-From: nik@mail.optim-mol.cemu.ru X-SA-Exim-Scanned: No (on mail.optim-mol.cemu.ru); SAEximRunCond expanded to false Cc: Subject: Re: Marvel Yukon using the sk driver X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 00:49:53 -0000 I agree, the second card we have there is Intel with fxp driver. One correction. The message said: "no buffer space available", when you ping something through that card. Clayton Milos said the following on 20.08.2007 16:05: >> Hi, what I can tell. >> I had a terrible problem with this card (PCI-E version) exactly one >> week ago. Both drivers msk from the system and myk from the vendor >> show similar behavior. >> On high loads, like 2-3 users from Samba domain pulling their >> profiles at the same time, the card just chokes. No ping, and >> "buffer overflow message". >> I mean I had to bring the interface down and up again. Absolutely >> disgusting. >> No tweak helps. >> >> I mean, we tested it over the weekend and it was fine, till folks >> come there on Monday and start massively using the server. >> >> We downgraded the hardware and put good old 3Com509 PCI or whatever >> works with xl driver. >> >> >> Robert Slawson said the following on 20.08.2007 10:13: >>> Greetings, >>> >>> I have a marvel yukon pci gigabit ethernet card. For some reason, >>> after a period of time it will not transmit unless I make it >>> transmit by pinging via the console. It is very annoying as I cannot >>> ssh into the machine until I "wake up" the card by telling it to >>> ping something. >>> >>> I am using 6.2 stable and just yesterday rebuilt the kernel and >>> world hoping this would fix the problem. But nothing seems to help. >>> >>> I think the card needs to use the msk driver , which is installed, >>> but the card keeps using the sk driver. Is there a way to have >>> freebsd re identify the card correctly and use the proper driver? >>> >>> Thanks in advance, >>> Bob > >> From my experience it always pays to use good hardware. I use >> 3com/Broadcom > or Intel NIC's. Nothing else. Ever! > They get much better throughput with less CPU overhead. And the real > advantage is they have good suport in UNIX systems. > I know Jack Vogel did his best and sorted out the issues with mine and > many other people's Intel gigabit (em based) cards when there were > issues. My em card is flying along happily now like it should be. > The last server I bought had dual onboard Broadcom NIC's and I've had > not issues throwing 500Mbit/s through them. Haven't had a chance to > really push them to the limits yet. > > I know I'm not really helping you directly here but my advice would be > to throw an Intel gigabit desktop adapter in there and your problems > will disappear. They're only $20-$30 nowadays and it's going to take > your headache away. > > -Clay > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Tue Aug 21 01:46:26 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8892016A419 for ; Tue, 21 Aug 2007 01:46:26 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.177]) by mx1.freebsd.org (Postfix) with ESMTP id 228EF13C461 for ; Tue, 21 Aug 2007 01:46:25 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by py-out-1112.google.com with SMTP id u77so2411323pyb for ; Mon, 20 Aug 2007 18:46:24 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:received:received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=raqXCurWYLUnztS5a1yz5bXGAjYRhnqVzOp+eIeLOBm1QjRc+x+jOj9GqR2fckPczvcN0Z92E1MAGcnd7upRh6Q8IHg3huXAcmaXT18fPy5tu3oggSSJSZ7ng8kY8mGFHTUsJJbVwRil3xO0KePZUDobri/wauAKscxI0voxQBk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=Nc71pAgGcdj/FwPmyu3MSwc+ysUjyoJnd6veaDGb3iPj7n7NZ7krLz1I5Cs+CHKfZEziDp9OQuQ4UaNhq5cR0qANKfemnkI1EfN9c1OeIVeG9RhoHFiTCdHQy5vmbP0Wb0TQQJREHvJYr6cUjy8FEEnieOCEWNgpxJ7GYSaCYhQ= Received: by 10.114.199.1 with SMTP id w1mr881320waf.1187660783813; Mon, 20 Aug 2007 18:46:23 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id n37sm8631542wag.2007.08.20.18.46.11 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 20 Aug 2007 18:46:13 -0700 (PDT) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id l7L1k1ZN059014 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 21 Aug 2007 10:46:01 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id l7L1juja059013; Tue, 21 Aug 2007 10:45:56 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Tue, 21 Aug 2007 10:45:56 +0900 From: Pyun YongHyeon To: Robert Slawson Message-ID: <20070821014556.GB58574@cdnetworks.co.kr> References: <2306ABA6-49A6-412E-81CD-CBABAE885EB2@charter.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2306ABA6-49A6-412E-81CD-CBABAE885EB2@charter.net> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org Subject: Re: Marvel Yukon using the sk driver X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 01:46:26 -0000 On Mon, Aug 20, 2007 at 10:13:42AM -0500, Robert Slawson wrote: > Greetings, > > I have a marvel yukon pci gigabit ethernet card. For some reason, > after a period of time it will not transmit unless I make it transmit > by pinging via the console. It is very annoying as I cannot ssh into > the machine until I "wake up" the card by telling it to ping something. > Did sk(4) spew some messages such as "watchdog timeout"? After the "wake up" sk(4) works without further intervention? > I am using 6.2 stable and just yesterday rebuilt the kernel and world > hoping this would fix the problem. But nothing seems to help. > > I think the card needs to use the msk driver , which is installed, > but the card keeps using the sk driver. Is there a way to have > freebsd re identify the card correctly and use the proper driver? > sk(4) is for SysKonnect SK-984X/SK-982X and Marvell Yukon controllers. msk(4) just supports newer Marvell Yukon II based controllers so your NIC would be old Yukon based one. Would you show me the output of "pciconf -lcv"? > Thanks in advance, > Bob -- Regards, Pyun YongHyeon From owner-freebsd-stable@FreeBSD.ORG Tue Aug 21 01:50:51 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AC3EC16A419 for ; Tue, 21 Aug 2007 01:50:51 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0910.google.com (rv-out-0910.google.com [209.85.198.191]) by mx1.freebsd.org (Postfix) with ESMTP id 7CB8013C442 for ; Tue, 21 Aug 2007 01:50:51 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0910.google.com with SMTP id l15so1059457rvb for ; Mon, 20 Aug 2007 18:50:51 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:received:received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=taCWJu8Z1XUD008S1oAZ8y0lkuDjxyfERIvyI7DgnHvNO4Ta7d/86eltypOJhateBD9c0PasH2jh9ODg+7tkwFYksI6+YZyulw7O2gD0YTUJY2Kc9sbFxxDwELMRqgpnzrRB2TXv+ZWLKFqxnbkTRk/JdG46qR2Qan+Au1XFoQw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=dkXAjN5gK7y2hP6laKs1sLsmBEC4LHuc7+3yOT37RYhnnxTg4AYsTUKM+Mi8nc+K4IpPN6zPrSjews/7Gqjrxb6EqUdc4QqbdhkxyFbwUU4KFevQl7kimo/ukobkcCDJb565z3m8mJdtLZnOUZpqs0XiJ1M6slN3xAvDQBpD7Xc= Received: by 10.114.27.20 with SMTP id a20mr552432waa.1187661050935; Mon, 20 Aug 2007 18:50:50 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id l28sm6380997waf.2007.08.20.18.50.40 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 20 Aug 2007 18:50:41 -0700 (PDT) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id l7L1oXf5059028 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 21 Aug 2007 10:50:33 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id l7L1oRwo059027; Tue, 21 Aug 2007 10:50:27 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Tue, 21 Aug 2007 10:50:27 +0900 From: Pyun YongHyeon To: Nikolay Mirin Message-ID: <20070821015027.GC58574@cdnetworks.co.kr> References: <2306ABA6-49A6-412E-81CD-CBABAE885EB2@charter.net> <46C9D817.1070704@optim.com.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <46C9D817.1070704@optim.com.ru> User-Agent: Mutt/1.4.2.1i Cc: Robert Slawson , freebsd-stable@freebsd.org Subject: Re: Marvel Yukon using the sk driver X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 01:50:51 -0000 On Mon, Aug 20, 2007 at 01:06:15PM -0500, Nikolay Mirin wrote: > Hi, what I can tell. > I had a terrible problem with this card (PCI-E version) exactly one week > ago. Both drivers msk from the system and myk from the vendor show > similar behavior. > On high loads, like 2-3 users from Samba domain pulling their profiles > at the same time, the card just chokes. No ping, and > "buffer overflow message". > I mean I had to bring the interface down and up again. Absolutely > disgusting. Show me verbosed boot dmesg and the output of "pciconf -lcv". Did you see watchdog timeout messages on your console? > No tweak helps. > > I mean, we tested it over the weekend and it was fine, till folks come > there on Monday and start massively using the server. > > We downgraded the hardware and put good old 3Com509 PCI or whatever > works with xl driver. > > > Robert Slawson said the following on 20.08.2007 10:13: > >Greetings, > > > >I have a marvel yukon pci gigabit ethernet card. For some reason, > >after a period of time it will not transmit unless I make it transmit > >by pinging via the console. It is very annoying as I cannot ssh into > >the machine until I "wake up" the card by telling it to ping something. > > > >I am using 6.2 stable and just yesterday rebuilt the kernel and world > >hoping this would fix the problem. But nothing seems to help. > > > >I think the card needs to use the msk driver , which is installed, but > >the card keeps using the sk driver. Is there a way to have freebsd re > >identify the card correctly and use the proper driver? > > > >Thanks in advance, > >Bob -- Regards, Pyun YongHyeon From owner-freebsd-stable@FreeBSD.ORG Tue Aug 21 02:26:14 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9EBB616A417 for ; Tue, 21 Aug 2007 02:26:14 +0000 (UTC) (envelope-from davids@webmaster.com) Received: from mail1.webmaster.com (mail1.webmaster.com [216.152.64.169]) by mx1.freebsd.org (Postfix) with ESMTP id 875C613C474 for ; Tue, 21 Aug 2007 02:26:14 +0000 (UTC) (envelope-from davids@webmaster.com) Received: from however by webmaster.com (MDaemon.PRO.v8.1.3.R) with ESMTP id md50001646705.msg for ; Mon, 20 Aug 2007 19:25:46 -0700 From: "David Schwartz" To: Date: Mon, 20 Aug 2007 19:25:11 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: <028f01c7e37a$d8f441b0$0c00a8c0@Artem> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 Importance: Normal X-Authenticated-Sender: joelkatz@webmaster.com X-Spam-Processed: mail1.webmaster.com, Mon, 20 Aug 2007 19:25:46 -0700 (not processed: message from trusted or authenticated source) X-MDRemoteIP: 206.171.168.138 X-Return-Path: davids@webmaster.com X-MDaemon-Deliver-To: freebsd-stable@freebsd.org X-MDAV-Processed: mail1.webmaster.com, Mon, 20 Aug 2007 19:25:46 -0700 Subject: RE: A little story of failed raid5 (3ware 8000 series) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: davids@webmaster.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 02:26:14 -0000 > A day ago at 11 am i have turn off the server, > pull out the old driver, installed a new one, turned of the server > and started rebuild in an hour from remote location via web interface. > After about 5 minuted the machine became unresponsive. Tried rebooting > - nothing. I went to the machine and fingure out, that rebuild failed (0%) > and some data cannot be read because of bad sectors. Why would you power cycle a RAID 5 array with a failed drive? That's like the biggest no-no that there is. When you lose a drive on a RAID 5 array, you are vulnerable until a replacement drive is configured and the array is rebuilt. Any high risk operations during that time would be foolhardy. > So, no raid5 or even raid 6 for me any more. Never! Since RAID6 would have saved you from what presumably was a drive failure before a rebuild could be done, it's hard to understand why you would say this is a reason to avoid RAID 6. Perhaps you would do better to understand your failure and avoid the causes of the failure rather than avoiding the things you happened to be using at the time of the failure. If you get food poisoning while wearing a blue shirt, the solution is not to avoid blue shirts in the future. DS From owner-freebsd-stable@FreeBSD.ORG Tue Aug 21 03:25:31 2007 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2F34716A418 for ; Tue, 21 Aug 2007 03:25:31 +0000 (UTC) (envelope-from shannon@widomaker.com) Received: from wilma.widomaker.com (wilma.widomaker.com [204.17.220.5]) by mx1.freebsd.org (Postfix) with ESMTP id 0955B13C468 for ; Tue, 21 Aug 2007 03:25:30 +0000 (UTC) (envelope-from shannon@widomaker.com) Received: from [69.72.99.201] (helo=escape.goid.lan) by wilma.widomaker.com with esmtp (Exim 3.36 #1) id 1INKMz-0008ed-00 for stable@freebsd.org; Mon, 20 Aug 2007 23:25:29 -0400 Received: from daydream (daydream.goid.lan [192.168.1.10]) by escape.goid.lan (Postfix) with ESMTP id 95444A503 for ; Mon, 20 Aug 2007 23:25:28 -0400 (EDT) Date: Mon, 20 Aug 2007 23:25:20 -0400 From: Charles Shannon Hendrix To: stable@freebsd.org Message-ID: <20070820232520.662b32d4@daydream> Organization: Multi Endian X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.10.11; i486-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Subject: console message suppression during boot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 03:25:31 -0000 I am trying to create a custom FreeBSD install that suppresses most console output during the boot. In fact, the only thing I want to see is my custom menu in the third stage, the stuff written in Forth. I added the -q and -m options to /boot.config, and it mostly works, but with two serious problems: - it does not suppress the loading output just before and just after the 3rd stage menu is displayed. - it suppresses console output even *after* the boot, which I don't want. For example, when I boot and third stage loader runs, I see this: [output showing loader code being loaded, a spinner, and some notes about the available drives] My Custom Menu 1 .......... 2 .......... and so on [output show chosen slice and kernel being booted] I want to suppress the stuff in []'s, but still show the menu. Also, when I run a shutdown, I don't see any console output, which makes it hard to tell when the system has halted. Any help appreciated. -- shannon | Tara is grass, and behold how Troy lieth | low--And even the English, perchance their | hour will come! From owner-freebsd-stable@FreeBSD.ORG Tue Aug 21 04:58:00 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D886916A419 for ; Tue, 21 Aug 2007 04:58:00 +0000 (UTC) (envelope-from matrix@itlegion.ru) Received: from corpmail.itlegion.ru (corpmail.itlegion.ru [84.21.226.211]) by mx1.freebsd.org (Postfix) with SMTP id 2A97713C457 for ; Tue, 21 Aug 2007 04:57:59 +0000 (UTC) (envelope-from matrix@itlegion.ru) Received: (qmail 96391 invoked from network); 21 Aug 2007 08:57:58 +0400 Received: from unknown (HELO Artem) (192.168.0.12) by 84.21.226.211 with SMTP; 21 Aug 2007 08:57:58 +0400 X-AntiVirus: Checked by Dr.Web [version: 4.33, engine: 4.33.5.10110, virus records: 238958, updated: 20.08.2007] Message-ID: <02fe01c7e3af$d3b86ed0$0c00a8c0@Artem> From: "Artem Kuchin" To: , References: Date: Tue, 21 Aug 2007 08:57:22 +0400 Organization: IT Legion MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="koi8-r"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 Cc: Subject: Re: A little story of failed raid5 (3ware 8000 series) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 04:58:00 -0000 David Schwartz wrote: >> A day ago at 11 am i have turn off the server, >> pull out the old driver, installed a new one, turned of the server >> and started rebuild in an hour from remote location via web >> interface. After about 5 minuted the machine became unresponsive. >> Tried rebooting - nothing. I went to the machine and fingure out, >> that rebuild failed (0%) and some data cannot be read because of bad >> sectors. > > Why would you power cycle a RAID 5 array with a failed drive? That's > like the biggest no-no that there is. When you lose a drive on a RAID > 5 array, you are vulnerable until a replacement drive is configured > and the array is rebuilt. Any high risk operations during that time > would be foolhardy. Um.. it is because i did not have a map of hot swap baskets to conroller ports and i needed to check every driver basket to understand which port it sits on. I have no choise, i think. >> So, no raid5 or even raid 6 for me any more. Never! > > Since RAID6 would have saved you from what presumably was a drive > failure before a rebuild could be done, it's hard to understand why > you would say this is a reason to avoid RAID 6. Perhaps you would do > better to understand your failure and avoid the causes of the failure > rather than avoiding the things you happened to be using at the time > of the failure. > > If you get food poisoning while wearing a blue shirt, the solution is > not to avoid blue shirts in the future. Read the post before. I still don't known which driver has the bad sectors. And it is very posible that EACH driver has them. RAID6 would not help then. -- Artem From owner-freebsd-stable@FreeBSD.ORG Tue Aug 21 05:46:20 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9BF3516A418 for ; Tue, 21 Aug 2007 05:46:20 +0000 (UTC) (envelope-from martin@gneto.com) Received: from proxy2.bredband.net (proxy2.bredband.net [195.54.101.72]) by mx1.freebsd.org (Postfix) with ESMTP id 5EFC313C459 for ; Tue, 21 Aug 2007 05:46:20 +0000 (UTC) (envelope-from martin@gneto.com) Received: from mailbox.gneto.com (83.227.181.30) by proxy2.bredband.net (7.3.127) id 46C9A3900003390F; Tue, 21 Aug 2007 07:25:15 +0200 Received: from euklides.gneto.com (euklides.gneto.com [192.168.10.11]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailbox.gneto.com (Postfix) with ESMTP id A550528429; Tue, 21 Aug 2007 07:23:16 +0200 (CEST) Message-ID: <46CA7681.3070909@gneto.com> Date: Tue, 21 Aug 2007 07:22:09 +0200 From: Martin Nilsson User-Agent: Thunderbird 2.0.0.6 (X11/20070802) MIME-Version: 1.0 To: Artem Kuchin References: <028f01c7e37a$d8f441b0$0c00a8c0@Artem> In-Reply-To: <028f01c7e37a$d8f441b0$0c00a8c0@Artem> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: A little story of failed raid5 (3ware 8000 series) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 05:46:20 -0000 Artem Kuchin wrote: > But i don't understand how and why it happened. ONly 6 hours ago (a > night before) > all those files were backed up fine w/o any read error. And now, right > after replacing > the driver and starting rebuild it said that there are bad sectors all > over those file. > How come? That is what patrol read is intended to detect before it is a problem. In a RAID5 array the checksums are only used when reconstructing data, if you have a bad block in a checksum sector it will not be detected until a drive have failed and you try to rebuild the array, unfortunately at that time it is too late... Beware that OS software solutions like diskcheckd will not find this as it only reads the data, not the checksums, it must be done on the controller. Regards, Martin From owner-freebsd-stable@FreeBSD.ORG Tue Aug 21 06:00:04 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F09DF16A418 for ; Tue, 21 Aug 2007 06:00:04 +0000 (UTC) (envelope-from matrix@itlegion.ru) Received: from corpmail.itlegion.ru (corpmail.itlegion.ru [84.21.226.211]) by mx1.freebsd.org (Postfix) with SMTP id 2E11B13C46E for ; Tue, 21 Aug 2007 06:00:03 +0000 (UTC) (envelope-from matrix@itlegion.ru) Received: (qmail 98128 invoked from network); 21 Aug 2007 10:00:02 +0400 Received: from unknown (HELO Artem) (192.168.0.12) by 84.21.226.211 with SMTP; 21 Aug 2007 10:00:02 +0400 X-AntiVirus: Checked by Dr.Web [version: 4.33, engine: 4.33.5.10110, virus records: 238958, updated: 20.08.2007] Message-ID: <03bc01c7e3b8$7f9a3a50$0c00a8c0@Artem> From: "Artem Kuchin" To: "Martin Nilsson" References: <028f01c7e37a$d8f441b0$0c00a8c0@Artem> <46CA7681.3070909@gneto.com> Date: Tue, 21 Aug 2007 09:59:51 +0400 Organization: IT Legion MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 Cc: freebsd-stable@freebsd.org Subject: Re: A little story of failed raid5 (3ware 8000 series) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 06:00:05 -0000 Martin Nilsson wrote: > Artem Kuchin wrote: >> But i don't understand how and why it happened. ONly 6 hours ago (a >> night before) >> all those files were backed up fine w/o any read error. And now, >> right after replacing >> the driver and starting rebuild it said that there are bad sectors >> all over those file. >> How come? > > That is what patrol read is intended to detect before it is a problem. > In a RAID5 array the checksums are only used when reconstructing data, > if you have a bad block in a checksum sector it will not be detected > until a drive have failed and you try to rebuild the array, > unfortunately at that time it is too late... > > Beware that OS software solutions like diskcheckd will not find this > as it only reads the data, not the checksums, it must be done on the > controller. That exactly was i was talking about. I don't acess to individual disks behind raid unit, so, i cannot doit. I don't know it controller VERIFY command does it right. If it doesm then i shoudl put it into a cron job and do it on weekly basis. Also, it would halpfull it i could get access to number of left reserved sector for remapping. Any idea about these two for 3ware controllers? Also, someone should mention, that while using raid MUST do verifies often. -- Artem From owner-freebsd-stable@FreeBSD.ORG Tue Aug 21 06:36:08 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6493716A418 for ; Tue, 21 Aug 2007 06:36:08 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id ED5BC13C457 for ; Tue, 21 Aug 2007 06:36:07 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (inchoate.gsoft.com.au [203.31.81.61]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id l7L6a2iQ006579 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 21 Aug 2007 16:06:03 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-stable@freebsd.org Date: Tue, 21 Aug 2007 16:05:58 +0930 User-Agent: KMail/1.9.7 References: <028f01c7e37a$d8f441b0$0c00a8c0@Artem> <46CA7681.3070909@gneto.com> <03bc01c7e3b8$7f9a3a50$0c00a8c0@Artem> In-Reply-To: <03bc01c7e3b8$7f9a3a50$0c00a8c0@Artem> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1809293.mZWdIzdBdN"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200708211606.00429.doconnor@gsoft.com.au> X-Spam-Score: -3.977 () ALL_TRUSTED,BAYES_00 X-Scanned-By: MIMEDefang 2.58 on 203.31.81.10 Cc: Artem Kuchin , Martin Nilsson Subject: Re: A little story of failed raid5 (3ware 8000 series) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 06:36:08 -0000 --nextPart1809293.mZWdIzdBdN Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tue, 21 Aug 2007, Artem Kuchin wrote: > could get access to number of left reserved sector for remapping. Any > idea about these two for 3ware controllers? Also, someone should > mention, that while using raid MUST do verifies often. You can run smartmontools on disks behind 3ware controllers, eg /dev/twe0 -d 3ware,0 -a -o on -S on -m root@localhost /dev/twe0 -d 3ware,1 -a -o on -S on -m root@localhost =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart1809293.mZWdIzdBdN Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQBGyofQ5ZPcIHs/zowRAjh2AKCPOUrWrQTT8dde4jlv6pOCQLDXVgCdG7WT dRgAzsG6hGB+ZbyIcmsnj/M= =IxXR -----END PGP SIGNATURE----- --nextPart1809293.mZWdIzdBdN-- From owner-freebsd-stable@FreeBSD.ORG Tue Aug 21 06:44:37 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4AB5D16A417 for ; Tue, 21 Aug 2007 06:44:37 +0000 (UTC) (envelope-from freebsd@bitfreak.org) Received: from mail.twinthornes.com (mail.twinthornes.com [65.75.198.147]) by mx1.freebsd.org (Postfix) with ESMTP id 2AF0713C45E for ; Tue, 21 Aug 2007 06:44:36 +0000 (UTC) (envelope-from freebsd@bitfreak.org) Received: from [10.9.70.100] (pool-72-90-106-233.ptldor.fios.verizon.net [72.90.106.233]) by mail.twinthornes.com (Postfix) with ESMTP id 1468F869; Mon, 20 Aug 2007 23:24:49 -0700 (PDT) Message-ID: <46CA8507.5000803@bitfreak.org> Date: Mon, 20 Aug 2007 23:24:07 -0700 From: Darren Pilgrim User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: Artem Kuchin References: <028f01c7e37a$d8f441b0$0c00a8c0@Artem> <46CA7681.3070909@gneto.com> <03bc01c7e3b8$7f9a3a50$0c00a8c0@Artem> In-Reply-To: <03bc01c7e3b8$7f9a3a50$0c00a8c0@Artem> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: A little story of failed raid5 (3ware 8000 series) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 06:44:37 -0000 Artem Kuchin wrote: > That exactly was i was talking about. I don't acess to individual disks > behind raid unit, so, i cannot doit. I don't know it controller > VERIFY command does it right. If it doesm then i shoudl put it into a cron > job and do it on weekly basis. Also, it would halpfull it i could get access to > number of left reserved sector for remapping. Any idea about these two for > 3ware controllers? Also, someone should mention, that while using raid MUST > do verifies often. The 3dm2 software (sysutils/3dm port) can dump the SMART data from individual disks. It can also schedule verify and self-test tasks and identify individual drives by blinking the activity light for the drive. From owner-freebsd-stable@FreeBSD.ORG Tue Aug 21 06:57:59 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4D6A616A418 for ; Tue, 21 Aug 2007 06:57:59 +0000 (UTC) (envelope-from freebsd.macgregor@blueyonder.co.uk) Received: from the-macgregors.org (82-46-96-74.cable.ubr06.stav.blueyonder.co.uk [82.46.96.74]) by mx1.freebsd.org (Postfix) with ESMTP id AEAF513C480 for ; Tue, 21 Aug 2007 06:57:58 +0000 (UTC) (envelope-from freebsd.macgregor@blueyonder.co.uk) X-Urban-Legend: Mail headers contain urban legends Received: from [192.168.32.126] (macabout.macgregor [192.168.32.126]) (user=rob mech=CRAM-MD5 bits=0) by the-macgregors.org (8.14.1/8.14.1) with ESMTP id l7L6cJeu000633 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 21 Aug 2007 06:38:20 GMT Message-ID: <46CA883F.3080103@blueyonder.co.uk> Date: Tue, 21 Aug 2007 07:37:51 +0100 From: Rob MacGregor User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-GB; rv:1.8.1.6) Gecko/20070728 Thunderbird/2.0.0.6 Mnenhy/0.7.5.666 MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <028f01c7e37a$d8f441b0$0c00a8c0@Artem> In-Reply-To: <028f01c7e37a$d8f441b0$0c00a8c0@Artem> X-Enigmail-Version: 0.95.3 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new Subject: Re: A little story of failed raid5 (3ware 8000 series) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 06:57:59 -0000 Artem Kuchin unleashed the infinite monkeys on 20/08/2007 23:38 producing: <---SNIP---> > But i don't understand how and why it happened. ONly 6 hours ago (a > night before) > all those files were backed up fine w/o any read error. And now, right > after replacing > the driver and starting rebuild it said that there are bad sectors all > over those file. I've had that happen on a RAID1 setup before. Because all the bad sectors were in different positions the array worked fine until one of the disks failed. As I'm fond of saying at work, RAID is no substitute for regular, tested, backups. Regarding your problem - you can download the (very detailed) manuals for the 3Ware cards and their software from the 3Ware website. A quick scan suggests you need the "mediascan" command (P48). Newer controllers (9000 series) support scheduling of their equivalent. -- Rob | Oh my God! They killed init! You bastards! From owner-freebsd-stable@FreeBSD.ORG Tue Aug 21 06:58:36 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6CF9A16A418 for ; Tue, 21 Aug 2007 06:58:36 +0000 (UTC) (envelope-from daniel_k_eriksson@telia.com) Received: from pne-smtpout2-sn2.hy.skanova.net (pne-smtpout2-sn2.hy.skanova.net [81.228.8.164]) by mx1.freebsd.org (Postfix) with ESMTP id 1EB7513C457 for ; Tue, 21 Aug 2007 06:58:36 +0000 (UTC) (envelope-from daniel_k_eriksson@telia.com) Received: from royal64.emp.zapto.org (195.198.193.104) by pne-smtpout2-sn2.hy.skanova.net (7.2.075) id 46245DE101DA99B8 for freebsd-stable@freebsd.org; Tue, 21 Aug 2007 08:58:34 +0200 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Tue, 21 Aug 2007 08:56:46 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5.7235.2 Message-ID: <4F9C9299A10AE74E89EA580D14AA10A61A17E0@royal64.emp.zapto.org> In-Reply-To: <46CA8507.5000803@bitfreak.org> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: A little story of failed raid5 (3ware 8000 series) Thread-Index: AcfjvsuDCJPZ0UJiTZaDlgbJEz4YhQAANl+Q References: <028f01c7e37a$d8f441b0$0c00a8c0@Artem> <46CA7681.3070909@gneto.com><03bc01c7e3b8$7f9a3a50$0c00a8c0@Artem> <46CA8507.5000803@bitfreak.org> From: "Daniel Eriksson" To: Subject: RE: A little story of failed raid5 (3ware 8000 series) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 06:58:36 -0000 While we are on the subject: What is the practical difference between VERIFY and REBUILD with regards to a RAID-5 array? My Highpoint RocketRAID 2320 and 2340 cards can be scheduled to perform either verify or rebuild. I currently have them set to verify the arrays weekly. Is that reasonably often? Do I want to rebuild regularly also (or instead of verify)? /Daniel Eriksson From owner-freebsd-stable@FreeBSD.ORG Tue Aug 21 09:35:20 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3A2D016A41B for ; Tue, 21 Aug 2007 09:35:20 +0000 (UTC) (envelope-from matrix@itlegion.ru) Received: from corpmail.itlegion.ru (corpmail.itlegion.ru [84.21.226.211]) by mx1.freebsd.org (Postfix) with SMTP id 469C213C469 for ; Tue, 21 Aug 2007 09:35:19 +0000 (UTC) (envelope-from matrix@itlegion.ru) Received: (qmail 3615 invoked from network); 21 Aug 2007 13:35:17 +0400 Received: from unknown (HELO Artem) (192.168.0.12) by 84.21.226.211 with SMTP; 21 Aug 2007 13:35:17 +0400 X-AntiVirus: Checked by Dr.Web [version: 4.33, engine: 4.33.5.10110, virus records: 238991, updated: 21.08.2007] Message-ID: <00a101c7e3d6$9140fb90$0c00a8c0@Artem> From: "Artem Kuchin" To: "Darren Pilgrim" References: <028f01c7e37a$d8f441b0$0c00a8c0@Artem> <46CA7681.3070909@gneto.com><03bc01c7e3b8$7f9a3a50$0c00a8c0@Artem> <46CA8507.5000803@bitfreak.org> Date: Tue, 21 Aug 2007 13:18:03 +0400 Organization: IT Legion MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 Cc: freebsd-stable@freebsd.org Subject: Re: A little story of failed raid5 (3ware 8000 series) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 09:35:20 -0000 Darren Pilgrim wrote: > Artem Kuchin wrote: >> That exactly was i was talking about. I don't acess to individual >> disks >> behind raid unit, so, i cannot doit. I don't know it controller >> VERIFY command does it right. If it doesm then i shoudl put it into >> a cron >> job and do it on weekly basis. Also, it would halpfull it i could >> get access to number of left reserved sector for remapping. Any idea >> about these two for 3ware controllers? Also, someone should mention, >> that while using raid MUST >> do verifies often. > > The 3dm2 software (sysutils/3dm port) can dump the SMART data from > individual disks. It can also schedule verify and self-test tasks and > identify individual drives by blinking the activity light for the > drive. _______________________________________________ Problems are: 1) how to parse this dump of data? 2) No scheduling is available on 7000,8000 on 4 port models -- Artem From owner-freebsd-stable@FreeBSD.ORG Tue Aug 21 09:59:10 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 055FB16A418 for ; Tue, 21 Aug 2007 09:59:10 +0000 (UTC) (envelope-from matrix@itlegion.ru) Received: from corpmail.itlegion.ru (corpmail.itlegion.ru [84.21.226.211]) by mx1.freebsd.org (Postfix) with SMTP id 490CB13C48A for ; Tue, 21 Aug 2007 09:59:09 +0000 (UTC) (envelope-from matrix@itlegion.ru) Received: (qmail 4182 invoked from network); 21 Aug 2007 13:59:07 +0400 Received: from unknown (HELO Artem) (192.168.0.12) by 84.21.226.211 with SMTP; 21 Aug 2007 13:59:07 +0400 X-AntiVirus: Checked by Dr.Web [version: 4.33, engine: 4.33.5.10110, virus records: 238998, updated: 21.08.2007] Message-ID: <00c901c7e3d9$e6134760$0c00a8c0@Artem> From: "Artem Kuchin" To: "Daniel O'Connor" , References: <028f01c7e37a$d8f441b0$0c00a8c0@Artem> <46CA7681.3070909@gneto.com><03bc01c7e3b8$7f9a3a50$0c00a8c0@Artem> <200708211606.00429.doconnor@gsoft.com.au> Date: Tue, 21 Aug 2007 13:57:25 +0400 Organization: IT Legion MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 Cc: Martin Nilsson Subject: Re: A little story of failed raid5 (3ware 8000 series) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 09:59:10 -0000 >You can run smartmontools on disks behind 3ware controllers, eg >/dev/twe0 -d 3ware,0 -a -o on -S on -m root@localhost >/dev/twe0 -d 3ware,1 -a -o on -S on -m root@localhost did this: smartctl /dev/twe0 -d 3ware,1 -a for each driver on another server. Two driver are pretty old, the driver on port 2 is less than a month old. However, ALL of the drives have the same values for this 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 How come the number are the same? Even more, what does this 100 mean? 100% of backup sector space is free or just 100 sectors are available? How many total of them in there. Why does it say "Pre-fail" if it is WAY above the threshold? This data seems to be useless. Now, i did the same for the raid which failed and got me into so many trobles and has bad sectors now (some files are unredable): smartctl /dev/twe0 -d 3ware,0 -A 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 smartctl /dev/twe0 -d 3ware,1 -A 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 39 smartctl /dev/twe0 -d 3ware,2 -A 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 9 Now this is BS!!! Agaim accroding to SMART i shoud lookup at VALUE (100) and see if it is below THRES (36). If it is then i am in trouble. No, it does no work this way. Now, if we look at raw number we see 39 for disk1 and 9 for disk 2 For 39 disk1 also 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 22 1 Raw_Read_Error_Rate 0x000f 058 055 006 Pre-fail Always - 170185544 195 Hardware_ECC_Recovered 0x001a 058 055 000 Old_age Always - 170185544 7 Seek_Error_Rate 0x000f 087 060 030 Pre-fail Always - 524461066 Even for the newly inserted ( 24 hours ago, absulutelly new) driver: 7 Seek_Error_Rate 0x000f 069 060 030 Pre-fail Always - 8525167 195 Hardware_ECC_Recovered 0x001a 069 066 000 Old_age Always - 8433725 Now, as i undertand the main indication is "Offline_Uncorrectable" is raw value of it any more than 0 - REPLACE DRIVER ASAP (or maybe it is too late and it is "replace driver asap" as soon as Reallocated_Sector_Ct >0 ?) Now, what i don't understand is why Hardware_ECC_Recovered and Seek_Error_Rate are so hight. The first one is maybe relate to cabling problem. The driver are all in hot swap baskets of supermicro 2u case. Maybe backpanel is no so good? Seek_Error_Rate is a mistety for me. Any idea? -- Artem From owner-freebsd-stable@FreeBSD.ORG Tue Aug 21 11:02:11 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CFC9E16A417 for ; Tue, 21 Aug 2007 11:02:11 +0000 (UTC) (envelope-from davids@webmaster.com) Received: from mail1.webmaster.com (mail1.webmaster.com [216.152.64.169]) by mx1.freebsd.org (Postfix) with ESMTP id B87B013C45B for ; Tue, 21 Aug 2007 11:02:11 +0000 (UTC) (envelope-from davids@webmaster.com) Received: from however by webmaster.com (MDaemon.PRO.v8.1.3.R) with ESMTP id md50001647420.msg for ; Tue, 21 Aug 2007 04:02:12 -0700 From: "David Schwartz" To: Date: Tue, 21 Aug 2007 04:01:40 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) Importance: Normal In-Reply-To: <4F9C9299A10AE74E89EA580D14AA10A61A17E0@royal64.emp.zapto.org> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 X-Authenticated-Sender: joelkatz@webmaster.com X-Spam-Processed: mail1.webmaster.com, Tue, 21 Aug 2007 04:02:12 -0700 (not processed: message from trusted or authenticated source) X-MDRemoteIP: 206.171.168.138 X-Return-Path: davids@webmaster.com X-MDaemon-Deliver-To: freebsd-stable@freebsd.org X-MDAV-Processed: mail1.webmaster.com, Tue, 21 Aug 2007 04:02:13 -0700 Subject: RE: A little story of failed raid5 (3ware 8000 series) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: davids@webmaster.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 11:02:11 -0000 > While we are on the subject: > > What is the practical difference between VERIFY and REBUILD with regards > to a RAID-5 array? Verify should at a minimum read all the data. Ideally, it would read the checksum blocks too to make sure they are still valid, but it might not. Rebuild should read all the data and write out new checksum blocks. It might also validate that it can read back the checksum. > My Highpoint RocketRAID 2320 and 2340 cards can be scheduled to perform > either verify or rebuild. I currently have them set to verify the arrays > weekly. Is that reasonably often? Do I want to rebuild regularly also > (or instead of verify)? It really depends what these functions actually do. Ideally, verify would read the data and the checksum and so would ensure that all data can be read, even if one drive fails. If so, that would really be all you need to do periodically. DS From owner-freebsd-stable@FreeBSD.ORG Tue Aug 21 11:12:19 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 576BB16A41A for ; Tue, 21 Aug 2007 11:12:19 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id D984913C442 for ; Tue, 21 Aug 2007 11:12:18 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (ppp121-45-132-77.lns11.adl6.internode.on.net [121.45.132.77]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id l7LBCGRb014430 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 21 Aug 2007 20:42:16 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: "Artem Kuchin" Date: Tue, 21 Aug 2007 20:42:05 +0930 User-Agent: KMail/1.9.7 References: <028f01c7e37a$d8f441b0$0c00a8c0@Artem> <200708211606.00429.doconnor@gsoft.com.au> <00c901c7e3d9$e6134760$0c00a8c0@Artem> In-Reply-To: <00c901c7e3d9$e6134760$0c00a8c0@Artem> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2107297.NndngpDhcW"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200708212042.13616.doconnor@gsoft.com.au> X-Spam-Score: -2.312 () BAYES_00 X-Scanned-By: MIMEDefang 2.58 on 203.31.81.10 Cc: freebsd-stable@freebsd.org, Martin Nilsson Subject: Re: A little story of failed raid5 (3ware 8000 series) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 11:12:19 -0000 --nextPart2107297.NndngpDhcW Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tue, 21 Aug 2007, Artem Kuchin wrote: > Now, what i don't understand is why Hardware_ECC_Recovered and > Seek_Error_Rate are so hight. The first one is maybe relate > to cabling problem. The driver are all in hot swap baskets of > supermicro 2u case. Maybe backpanel is no so good? > > Seek_Error_Rate is a mistety for me. Any idea? I don't know what the problem is, I would have expected the drive to=20 report errors in it's log if it is genuinely failing (I've seen this on=20 my laptop) Have you tried running SMART tests on the disk? I'm not saying SMART is the be all and end all of failure monitoring but=20 it has indicated problems to me in the past :) =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart2107297.NndngpDhcW Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQBGysiN5ZPcIHs/zowRAoeyAJwOzhe5HiVwAY4Bi0xhYooj160g2gCgm6tc EtimjogslakzOF4xIRBxCHc= =A8yi -----END PGP SIGNATURE----- --nextPart2107297.NndngpDhcW-- From owner-freebsd-stable@FreeBSD.ORG Tue Aug 21 12:32:44 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0183016A469; Tue, 21 Aug 2007 12:32:44 +0000 (UTC) (envelope-from johan@stromnet.se) Received: from av12-2-sn2.hy.skanova.net (av12-2-sn2.hy.skanova.net [81.228.8.186]) by mx1.freebsd.org (Postfix) with ESMTP id 7F3FE13C4B3; Tue, 21 Aug 2007 12:32:43 +0000 (UTC) (envelope-from johan@stromnet.se) Received: by av12-2-sn2.hy.skanova.net (Postfix, from userid 502) id 59158382DC; Tue, 21 Aug 2007 14:15:25 +0200 (CEST) Received: from smtp4-2-sn2.hy.skanova.net (smtp4-2-sn2.hy.skanova.net [81.228.8.93]) by av12-2-sn2.hy.skanova.net (Postfix) with ESMTP id ACDAA382E0; Tue, 21 Aug 2007 14:15:24 +0200 (CEST) Received: from phomca.stromnet.se (90-224-172-102-no129.tbcn.telia.com [90.224.172.102]) by smtp4-2-sn2.hy.skanova.net (Postfix) with ESMTP id 8EB9037E4B; Tue, 21 Aug 2007 14:15:24 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by phomca.stromnet.se (Postfix) with ESMTP id 437EAB826; Tue, 21 Aug 2007 14:15:24 +0200 (CEST) X-Virus-Scanned: amavisd-new at stromnet.se Received: from phomca.stromnet.se ([127.0.0.1]) by localhost (phomca.stromnet.se [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zn2q1mt5l5gb; Tue, 21 Aug 2007 14:15:18 +0200 (CEST) Received: from [172.28.1.102] (jstrom-mb.stromnet.se [172.28.1.102]) by phomca.stromnet.se (Postfix) with ESMTP id 07AA0B824; Tue, 21 Aug 2007 14:15:18 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v752.3) Content-Transfer-Encoding: quoted-printable Message-Id: <8039436E-1824-4C2E-915B-9069DEF23B10@stromnet.se> Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed To: freebsd-geom@freebsd.org, freebsd-stable@freebsd.org From: =?ISO-8859-1?Q?Johan_Str=F6m?= Date: Tue, 21 Aug 2007 14:15:08 +0200 X-Mailer: Apple Mail (2.752.3) Cc: Subject: Crashed gmirror, single disk marked SYNC and wont boot... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 12:32:44 -0000 Hi FreeBSD gw-1.stromnet.se 6.2-RELEASE-p1 FreeBSD 6.2-RELEASE-p1 #7: =20 Tue Feb 13 18:24:34 CET 2007 johan@elfi.stromnet.se:/usr/obj/usr/=20 src/sys/ROUTER.POLLING i386 (ROUTER.POLLING is GENERIC + options DEVICE_POLLING and ALTQ, =20 IPSEC, also pfsync and carp) This weekend I had a disk failing on me in a machine running gmirror =20 gm0 with 2 providers (ad0 and ad6). The whole box froze with no =20 screen output, and on hard reboot I got some LBA errors etc from ad0, =20= after a few reboots it got up and running though (I wasnt at the =20 screen, had do do it by phone so couldn't really debug very well). As soon as the box got up, I removed ad0 from the gmirror, so ad6 was =20= the only provider. Today I got a new disk that would replace ad0.. Now remeber, ad6 was the only disk in the mirror. I took the box down =20= fine, replaced the disk. ad0 was now gone and instead I hade ad4 (ad4=20 +6 is SATA, ad0 was IDE). Changed so I booted of the old SATA.. =20 Okay, there came the first problem; the boot loader gave me the usual =20= options F1 FreeBSD F5 Disk 2 (or whatever it said).. If I pressed F1 =20 i got the same prompt again.. F5 nothing at all.. Funny!... The =20 system refused to load the loader (or whatever the 1-9 menu thingy is =20= called) kernel or anything.. So I finally plugged the old ad0 disk into the machine to at least =20 get it booted, thinking it would go up on the gmirror.. Nope..: (got the new ad4 out here) ad0: 38166MB at ata0-master UDMA100 ad6: 152627MB at ata3-master SATA150 GEOM_MIRROR: Device gm0 created (id=3D4029378995). GEOM_MIRROR: Device gm0: provider ad6 detected. Root mount waiting for: GMIRROR Root mount waiting for: GMIRROR Root mount waiting for: GMIRROR Root mount waiting for: GMIRROR GEOM_MIRROR: Force device gm0 start due to timeout. Trying to mount root from ufs:/dev/mirror/gm0s1a Manual root filesystem specification: : Mount using filesystem eg. ufs:da0s1a ? List valid disk boot devices Abort manual input mountroot> Okey... so why wouldnt it load my mirror from ad6 now?? I just did a =20 clean shutdown without problems.. It didnt even recognize any slices =20 on ad6s1 (altough the ad6s1 was found)... I entered ad0s1 as root and booted from there, ofcourse i got to =20 emergency shell since fstab looked for the gmirror devices, which =20 didnt exist.. Some more digging into gmirror, I did a gmirror dump ad6: Metadata on /dev/ad6: magic: GEOM::MIRROR version: 3 name: gm0 mid: 4029378995 did: 449032193 all: 3 genid: 0 syncid: 5 priority: 0 slice: 4096 balance: round-robin mediasize: 20416757248 sectorsize: 512 syncoffset: 0 mflags: NONE dflags: SYNCHRONIZING hcprovider: provsize: 160041885696 MD5 hash: 6e1e8ca80a27e0e1b0460feab595c39f Some googling indicated that SYNCHRONIZING means that its not =20 "complete" and wont mount? Is that correct? Why would it be in that =20 state then, I just shut it down fine... And where the f*ck did my =20 slices go??.. Did a sysctl kern.geom.mirror.debug=3D2 and tried to gmirror activate =20= the mirror: GEOM_MIRROR[1]: Creating device gm0 (id=3D4029378995). GEOM_MIRROR[0]: Device gm0 created (id=3D4029378995). GEOM_MIRROR[1]: root_mount_hold 0xc3539510 GEOM_MIRROR[1]: Adding disk ad6 to gm0. GEOM_MIRROR[2]: Adding disk ad6. GEOM_MIRROR[2]: Disk ad6 connected. GEOM_MIRROR[1]: Disk ad6 state changed from NONE to NEW (device gm0). GEOM_MIRROR[0]: Device gm0: provider ad6 detected. GEOM_MIRROR[2]: Tasting ad6s1. GEOM_MIRROR[0]: Force device gm0 start due to timeout. GEOM_MIRROR[1]: root_mount_rel[2169] 0xc3539510 GEOM_MIRROR[2]: No I/O requests for gm0, it can be destroyed. GEOM_MIRROR[2]: Metadata on ad6 updated. GEOM_MIRROR[2]: Access ad6 r-1w-1e-1 =3D 0 GEOM_MIRROR[0]: Device gm0 destroyed. GEOM_MIRROR[1]: Thread exiting. GEOM_MIRROR[1]: Consumer ad6 destroyed. Soo.. What is going on here? Anyone with some clues? Currently =20 running on the ad0 disk, no raid at all.. Lets hope it doesnt die on =20 me (havent had any signs of that since sunday when it froze and gave =20 boot errors now so I'm hoping..). The data loss from using ad0 =20 instead of ad6 is probably minimal, its a router so its more or less =20 only logging that seems to been lost... For now I just want to get =20 clear about wth happened here and how to prevent it, and how to get =20 back up on a gmirror with ad6 and ad4 (to be plugged in) so I can =20 throw ad0 out... Thanks -- Johan Str=F6m Stromnet johan@stromnet.se http://www.stromnet.se/ From owner-freebsd-stable@FreeBSD.ORG Tue Aug 21 15:00:15 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 69CD916A46C for ; Tue, 21 Aug 2007 15:00:15 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.freebsd.org (Postfix) with ESMTP id 6BE1A13C4B3 for ; Tue, 21 Aug 2007 15:00:14 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id E9D7048804; Tue, 21 Aug 2007 16:32:44 +0200 (CEST) Received: from localhost (pjd.wheel.pl [10.0.1.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 7D5F4487F4; Tue, 21 Aug 2007 16:32:34 +0200 (CEST) Date: Tue, 21 Aug 2007 16:31:36 +0200 From: Pawel Jakub Dawidek To: Johan =?iso-8859-1?Q?Str=F6m?= Message-ID: <20070821143136.GD1132@garage.freebsd.pl> References: <8039436E-1824-4C2E-915B-9069DEF23B10@stromnet.se> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="GpGaEY17fSl8rd50" Content-Disposition: inline In-Reply-To: <8039436E-1824-4C2E-915B-9069DEF23B10@stromnet.se> User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-5.9 required=3.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-stable@freebsd.org, freebsd-geom@freebsd.org Subject: Re: Crashed gmirror, single disk marked SYNC and wont boot... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 15:00:15 -0000 --GpGaEY17fSl8rd50 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Aug 21, 2007 at 02:15:08PM +0200, Johan Str=F6m wrote: > Hi >=20 > FreeBSD gw-1.stromnet.se 6.2-RELEASE-p1 FreeBSD 6.2-RELEASE-p1 #7: =20 > Tue Feb 13 18:24:34 CET 2007 johan@elfi.stromnet.se:/usr/obj/usr/=20 > src/sys/ROUTER.POLLING i386 >=20 > (ROUTER.POLLING is GENERIC + options DEVICE_POLLING and ALTQ, =20 > IPSEC, also pfsync and carp) >=20 > This weekend I had a disk failing on me in a machine running gmirror =20 > gm0 with 2 providers (ad0 and ad6). The whole box froze with no =20 > screen output, and on hard reboot I got some LBA errors etc from ad0, =20 > after a few reboots it got up and running though (I wasnt at the =20 > screen, had do do it by phone so couldn't really debug very well). > As soon as the box got up, I removed ad0 from the gmirror, so ad6 was =20 > the only provider. Today I got a new disk that would replace ad0.. > Now remeber, ad6 was the only disk in the mirror. I took the box down =20 > fine, replaced the disk. ad0 was now gone and instead I hade ad4 (ad4=20 > +6 is SATA, ad0 was IDE). Changed so I booted of the old SATA.. =20 > Okay, there came the first problem; the boot loader gave me the usual =20 > options F1 FreeBSD F5 Disk 2 (or whatever it said).. If I pressed F1 =20 > i got the same prompt again.. F5 nothing at all.. Funny!... The =20 > system refused to load the loader (or whatever the 1-9 menu thingy is =20 > called) kernel or anything.. > So I finally plugged the old ad0 disk into the machine to at least =20 > get it booted, thinking it would go up on the gmirror.. Nope..: >=20 > (got the new ad4 out here) > ad0: 38166MB at ata0-master UDMA100 > ad6: 152627MB at ata3-master SATA150 > GEOM_MIRROR: Device gm0 created (id=3D4029378995). > GEOM_MIRROR: Device gm0: provider ad6 detected. > Root mount waiting for: GMIRROR > Root mount waiting for: GMIRROR > Root mount waiting for: GMIRROR > Root mount waiting for: GMIRROR > GEOM_MIRROR: Force device gm0 start due to timeout. > Trying to mount root from ufs:/dev/mirror/gm0s1a >=20 > Manual root filesystem specification: > : Mount using filesystem > eg. ufs:da0s1a > ? List valid disk boot devices > Abort manual input >=20 > mountroot> >=20 > Okey... so why wouldnt it load my mirror from ad6 now?? I just did a =20 > clean shutdown without problems.. It didnt even recognize any slices =20 > on ad6s1 (altough the ad6s1 was found)... It loaded your mirror just fine, you confuse things. Gmirror started in degraded state, as one could expect, but it seems there is no 'a' partition on your gm0s1 slice (or entire bsdlabel is gone). You could try to recreate it based on bsdlabel from ad0 (if it should be the same), but I've no idea how it disapeared. Anyway, gmirror seems to work properly. > Some more digging into gmirror, I did a gmirror dump ad6: >=20 > Metadata on /dev/ad6: > magic: GEOM::MIRROR > version: 3 > name: gm0 > mid: 4029378995 > did: 449032193 > all: 3 You have 3-way mirror? > genid: 0 > syncid: 5 > priority: 0 > slice: 4096 > balance: round-robin > mediasize: 20416757248 > sectorsize: 512 > syncoffset: 0 > mflags: NONE > dflags: SYNCHRONIZING > hcprovider: > provsize: 160041885696 > MD5 hash: 6e1e8ca80a27e0e1b0460feab595c39f BTW. Your provider size is 149GB and mirror only use 19GB, which means you mirrored 149GB disk with 19GB disk and you waste 130GB (it's unused). > Some googling indicated that SYNCHRONIZING means that its not =20 > "complete" and wont mount? Is that correct? Why would it be in that =20 > state then, I just shut it down fine... And where the f*ck did my =20 > slices go??.. SYNCHRONIZING means that this component was/is being synchronized. It seems that you removed/lost the master disk, while it was synchronizing. It should work anyway. BTW. You confuse things again. Your slice is just fine (ad6s1), you don't have partitions, AFAIU. All in all, your partition table seems to be gone. If you created it on gmirror before (gm0s1) you may still have the same partition table on the other half of the mirror. You can try to move it to ad6 with bsdlabel and verify if you can see file system inside partitions. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --GpGaEY17fSl8rd50 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFGyvdIForvXbEpPzQRAg8tAKCTRE6mtq95mSw7U9+v/rxBORcPFgCg87ij O6NQsf8IfYiTO3oDCzovUBU= =wWSe -----END PGP SIGNATURE----- --GpGaEY17fSl8rd50-- From owner-freebsd-stable@FreeBSD.ORG Tue Aug 21 15:43:58 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0FF2516A417 for ; Tue, 21 Aug 2007 15:43:58 +0000 (UTC) (envelope-from meff@spherevision.org) Received: from smtp114.sbc.mail.re2.yahoo.com (smtp114.sbc.mail.re2.yahoo.com [68.142.229.91]) by mx1.freebsd.org (Postfix) with SMTP id B89D913C4A6 for ; Tue, 21 Aug 2007 15:43:57 +0000 (UTC) (envelope-from meff@spherevision.org) Received: (qmail 42737 invoked from network); 21 Aug 2007 15:17:17 -0000 Received: from unknown (HELO ?10.1.1.10?) (meff@sbcglobal.net@70.243.81.214 with plain) by smtp114.sbc.mail.re2.yahoo.com with SMTP; 21 Aug 2007 15:17:16 -0000 X-YMail-OSG: UHJMaP8VM1kbriz3uGdFl4b8EClTX56beTDOigJaWApaBsf4.6W7oQFWuT0bsoHpOLfAVNb5PDnuBtGv2OvuDirqrXCsd3Csat1SbbrU7GERxtqTs2eTD7V.YY2fSoWeX_GA63TibUJnkSk- From: Rodney Gordon II To: freebsd-stable@freebsd.org Content-Type: multipart/mixed; boundary="=-0HU8HiDd1sabfYvOzzVc" Date: Tue, 21 Aug 2007 10:17:12 -0500 Message-Id: <1187709432.26320.4.camel@ghreen.sphere> Mime-Version: 1.0 X-Mailer: Evolution 2.10.3 FreeBSD GNOME Team Port Subject: Gathering entropy freeze on "point-to-point" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 15:43:58 -0000 --=-0HU8HiDd1sabfYvOzzVc Content-Type: text/plain Content-Transfer-Encoding: 7bit FreeBSD ghreen.sphere 6.2-STABLE FreeBSD 6.2-STABLE #0: Sun Aug 19 20:10:46 CDT 2007 root@ghreen.sphere:/usr/obj/usr/src/sys/GHREEN i386 Attached dmesg, attached kernel config. During bootup about 1 out of 5 times my box freezes right after it enters userland at the "Gathering entropy:" spot, specifically right after it says "point-to-point". Everything is hard locked and I have to reboot with the button in my case. TIA -r --=-0HU8HiDd1sabfYvOzzVc Content-Disposition: attachment; filename=GHREEN-6.2-STABLE Content-Type: text/plain; name=GHREEN-6.2-STABLE; charset=us-ascii Content-Transfer-Encoding: 7bit ## meff 200708134 # add debugging symbols makeoptions DEBUG=-g # base machine i386 cpu I686_CPU ident GHREEN options HZ=1000 options SCHED_ULE options PREEMPTION options _KPOSIX_PRIORITY_SCHEDULING options ADAPTIVE_GIANT device pty device md # smp device apic options SMP options IPI_PREEMPTION # filesystem options FFS options SOFTUPDATES options UFS_DIRHASH options MD_ROOT options MSDOSFS options NTFS options CD9660 options PROCFS options PSEUDOFS # binary compatability options COMPAT_43 options COMPAT_FREEBSD4 options COMPAT_FREEBSD5 # sysv compatibility options SYSVSHM options SYSVMSG options SYSVSEM # busses device pci device agp # ports device sio device ppc device ppbus device lpt # usb device uhci device ehci device usb device ugen device uhid device ukbd #device ulpt (hp drivers use ugen) device umass device ums # floppy device fdc # ata device ata device atadisk device atapicd device atapicam options ATA_STATIC_ID # scsi device scbus device cd device pass # pwr mgmt, etc device acpi # networking device ether device loop device bpf device tap device tun device if_bridge device pf device pflog device pfsync device ppp options PPP_BSDCOMP options PPP_DEFLATE options PPP_FILTER device miibus device msk options INET options INET6 # ipv6 device gif device faith device stf # linux abi emu options COMPAT_LINUX options LINPROCFS options LINSYSFS # keyboard / mouse device atkbdc device atkbd device psm options KBD_INSTALL_CDEV # video device vga device splash device sc # sound device sound device snd_emu10k1 # altq options ALTQ options ALTQ_CBQ options ALTQ_RED options ALTQ_HFSC options ALTQ_CDNR options ALTQ_PRIQ options ALTQ_NOPCC # smbus / i2c device smbus device smb device intpm device alpm device ichsmb device viapm device amdpm device amdsmb device nfpm device nfsmb device iicbus device iicbb device ic device iic device iicsmb # misc device random device joy options KTRACE --=-0HU8HiDd1sabfYvOzzVc Content-Disposition: attachment; filename=dmesg Content-Type: text/plain; name=dmesg; charset=us-ascii Content-Transfer-Encoding: 7bit Copyright (c) 1992-2007 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 6.2-STABLE #0: Sun Aug 19 20:10:46 CDT 2007 root@ghreen.sphere:/usr/obj/usr/src/sys/GHREEN Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) D CPU 3.00GHz (3010.67-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf44 Stepping = 4 Features=0xbfebfbff Features2=0x649d> AMD Features=0x20100000 Cores per package: 2 real memory = 1610153984 (1535 MB) avail memory = 1560137728 (1487 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0 irqs 0-23 on motherboard acpi0: <\M^?\M^?\M^?\M^?\M^?\M^? \M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?> on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 acpi_throttle0: on cpu0 cpu1: on acpi0 acpi_throttle1: on cpu1 acpi_throttle1: failed to attach P_CNT device_attach: acpi_throttle1 attach returned 6 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: irq 16 at device 1.0 on pci0 pci4: on pcib1 nvidia0: port 0xe800-0xe87f mem 0xcf000000-0xcfffffff,0xd0000000-0xdfffffff,0xce000000-0xceffffff irq 16 at device 0.0 on pci4 nvidia0: [GIANT-LOCKED] pcib2: irq 16 at device 28.0 on pci0 pci3: on pcib2 pcib3: irq 19 at device 28.3 on pci0 pci2: on pcib3 mskc0: port 0xc800-0xc8ff mem 0xcdefc000-0xcdefffff irq 19 at device 0.0 on pci2 msk0: on mskc0 msk0: Ethernet address: 00:13:d4:17:ec:35 miibus0: on msk0 e1000phy0: on miibus0 e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto mskc0: [FAST] uhci0: port 0x8000-0x801f irq 20 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0x8400-0x841f irq 17 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0x8800-0x881f irq 18 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] usb2: on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered uhci3: port 0x9000-0x901f irq 19 at device 29.3 on pci0 uhci3: [GIANT-LOCKED] usb3: on uhci3 usb3: USB revision 1.0 uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered ehci0: mem 0xcdcff800-0xcdcffbff irq 20 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] usb4: EHCI version 1.0 usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4: on ehci0 usb4: USB revision 2.0 uhub4: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub4: 8 ports with 8 removable, self powered pcib4: at device 30.0 on pci0 pci1: on pcib4 pcm0: port 0xb400-0xb43f irq 22 at device 2.0 on pci1 pcm0: pci1: at device 2.2 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 31.1 on pci0 ata0: on atapci0 ata1: on atapci0 atapci1: port 0xa800-0xa807,0xa400-0xa403,0xa000-0xa007,0x9800-0x9803,0x9400-0x940f mem 0xcdcffc00-0xcdcfffff irq 23 at device 31.2 on pci0 ata2: on atapci1 ata3: on atapci1 ichsmb0: port 0x400-0x41f irq 23 at device 31.3 on pci0 ichsmb0: [GIANT-LOCKED] smbus0: on ichsmb0 smb0: on smbus0 acpi_button0: on acpi0 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: port 0x378-0x37f,0x778-0x77f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold ppbus0: on ppc0 lpt0: on ppbus0 lpt0: Interrupt-driven port atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model MouseMan+, device ID 0 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 uhub5: ALCOR Generic USB Hub, class 9/0, rev 1.10/3.12, addr 2 uhub5: 4 ports with 4 removable, self powered uhid0: Logitech Logitech Dual Action, rev 1.10/2.00, addr 3, iclass 3/0 ugen0: hp deskjet 5550, rev 2.00/1.00, addr 2 ugen1: American Power Conversion Smart-UPS 750 FW:651.12.D USB FW:4.2, rev 1.10/0.06, addr 3 Timecounters tick every 1.000 msec acd0: DVDR at ata0-master UDMA66 acd1: DVDR at ata0-slave UDMA66 ad4: 476940MB at ata2-master SATA150 ad6: 476940MB at ata3-master SATA150 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 acd1: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 acd1: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 SMP: AP CPU #1 Launched! cd0 at ata0 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 66.000MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present cd1 at ata0 bus 0 target 1 lun 0 cd1: Removable CD-ROM SCSI-0 device cd1: 66.000MB/s transfers cd1: Attempt to query device size failed: NOT READY, Medium not present Trying to mount root from ufs:/dev/ad4s1a --=-0HU8HiDd1sabfYvOzzVc-- From owner-freebsd-stable@FreeBSD.ORG Tue Aug 21 15:53:37 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3779C16A469; Tue, 21 Aug 2007 15:53:37 +0000 (UTC) (envelope-from johan@stromnet.se) Received: from av12-1-sn2.hy.skanova.net (av12-1-sn2.hy.skanova.net [81.228.8.185]) by mx1.freebsd.org (Postfix) with ESMTP id 99A6B13C481; Tue, 21 Aug 2007 15:53:36 +0000 (UTC) (envelope-from johan@stromnet.se) Received: by av12-1-sn2.hy.skanova.net (Postfix, from userid 502) id C8093381E0; Tue, 21 Aug 2007 17:53:34 +0200 (CEST) Received: from smtp4-2-sn2.hy.skanova.net (smtp4-2-sn2.hy.skanova.net [81.228.8.93]) by av12-1-sn2.hy.skanova.net (Postfix) with ESMTP id 83772380EF; Tue, 21 Aug 2007 17:53:34 +0200 (CEST) Received: from phomca.stromnet.se (90-224-172-102-no129.tbcn.telia.com [90.224.172.102]) by smtp4-2-sn2.hy.skanova.net (Postfix) with ESMTP id 6D70337E45; Tue, 21 Aug 2007 17:53:34 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by phomca.stromnet.se (Postfix) with ESMTP id 109ADB826; Tue, 21 Aug 2007 17:53:34 +0200 (CEST) X-Virus-Scanned: amavisd-new at stromnet.se Received: from phomca.stromnet.se ([127.0.0.1]) by localhost (phomca.stromnet.se [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5W9nHAK4Txym; Tue, 21 Aug 2007 17:53:27 +0200 (CEST) Received: from [172.28.1.102] (jstrom-mb.stromnet.se [172.28.1.102]) by phomca.stromnet.se (Postfix) with ESMTP id D4AF3B824; Tue, 21 Aug 2007 17:53:27 +0200 (CEST) In-Reply-To: <20070821143136.GD1132@garage.freebsd.pl> References: <8039436E-1824-4C2E-915B-9069DEF23B10@stromnet.se> <20070821143136.GD1132@garage.freebsd.pl> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed Message-Id: <441B87F4-5846-441B-B6B4-34694B483C73@stromnet.se> Content-Transfer-Encoding: quoted-printable From: =?ISO-8859-1?Q?Johan_Str=F6m?= Date: Tue, 21 Aug 2007 17:53:19 +0200 To: Pawel Jakub Dawidek X-Mailer: Apple Mail (2.752.3) Cc: freebsd-stable@freebsd.org, freebsd-geom@freebsd.org Subject: Re: Crashed gmirror, single disk marked SYNC and wont boot... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 15:53:37 -0000 On Aug 21, 2007, at 16:31 , Pawel Jakub Dawidek wrote: > On Tue, Aug 21, 2007 at 02:15:08PM +0200, Johan Str=F6m wrote: >> Hi >> >> FreeBSD gw-1.stromnet.se 6.2-RELEASE-p1 FreeBSD 6.2-RELEASE-p1 #7: >> Tue Feb 13 18:24:34 CET 2007 johan@elfi.stromnet.se:/usr/obj/usr/ >> src/sys/ROUTER.POLLING i386 >> >> (ROUTER.POLLING is GENERIC + options DEVICE_POLLING and ALTQ, >> IPSEC, also pfsync and carp) >> >> This weekend I had a disk failing on me in a machine running gmirror >> gm0 with 2 providers (ad0 and ad6). The whole box froze with no >> screen output, and on hard reboot I got some LBA errors etc from ad0, >> after a few reboots it got up and running though (I wasnt at the >> screen, had do do it by phone so couldn't really debug very well). >> As soon as the box got up, I removed ad0 from the gmirror, so ad6 was >> the only provider. Today I got a new disk that would replace ad0.. >> Now remeber, ad6 was the only disk in the mirror. I took the box down >> fine, replaced the disk. ad0 was now gone and instead I hade ad4 (ad4 >> +6 is SATA, ad0 was IDE). Changed so I booted of the old SATA.. >> Okay, there came the first problem; the boot loader gave me the usual >> options F1 FreeBSD F5 Disk 2 (or whatever it said).. If I pressed F1 >> i got the same prompt again.. F5 nothing at all.. Funny!... The >> system refused to load the loader (or whatever the 1-9 menu thingy is >> called) kernel or anything.. >> So I finally plugged the old ad0 disk into the machine to at least >> get it booted, thinking it would go up on the gmirror.. Nope..: >> >> (got the new ad4 out here) >> ad0: 38166MB at ata0-master UDMA100 >> ad6: 152627MB at ata3-master SATA150 >> GEOM_MIRROR: Device gm0 created (id=3D4029378995). >> GEOM_MIRROR: Device gm0: provider ad6 detected. >> Root mount waiting for: GMIRROR >> Root mount waiting for: GMIRROR >> Root mount waiting for: GMIRROR >> Root mount waiting for: GMIRROR >> GEOM_MIRROR: Force device gm0 start due to timeout. >> Trying to mount root from ufs:/dev/mirror/gm0s1a >> >> Manual root filesystem specification: >> : Mount using filesystem >> eg. ufs:da0s1a >> ? List valid disk boot devices >> Abort manual input >> >> mountroot> >> >> Okey... so why wouldnt it load my mirror from ad6 now?? I just did a >> clean shutdown without problems.. It didnt even recognize any slices >> on ad6s1 (altough the ad6s1 was found)... > > It loaded your mirror just fine, you confuse things. Gmirror =20 > started in > degraded state, as one could expect, but it seems there is no 'a' > partition on your gm0s1 slice (or entire bsdlabel is gone). > You could try to recreate it based on bsdlabel from ad0 (if it =20 > should be > the same), but I've no idea how it disapeared. Anyway, gmirror =20 > seems to > work properly. Okay.. So it tries to load, find no partition table, and ignores and =20 unloads gm0? > >> Some more digging into gmirror, I did a gmirror dump ad6: >> >> Metadata on /dev/ad6: >> magic: GEOM::MIRROR >> version: 3 >> name: gm0 >> mid: 4029378995 >> did: 449032193 >> all: 3 > > You have 3-way mirror? Uhm.. never had more than 2 disks in this machine.. > >> genid: 0 >> syncid: 5 >> priority: 0 >> slice: 4096 >> balance: round-robin >> mediasize: 20416757248 >> sectorsize: 512 >> syncoffset: 0 >> mflags: NONE >> dflags: SYNCHRONIZING >> hcprovider: >> provsize: 160041885696 >> MD5 hash: 6e1e8ca80a27e0e1b0460feab595c39f > > BTW. Your provider size is 149GB and mirror only use 19GB, which means > you mirrored 149GB disk with 19GB disk and you waste 130GB (it's > unused). Yes, the ad0 disk was (is) only 40GB so only first 40 Gb of that disk =20= was in mirror (the rest was in another slice with its own label.. =20 altough if I'm doing fdisk on the disk it seems to not be there at =20 all..) But hum, 19??.. It should be 40 (or somewhere around there at =20 least).. =46rom ad0 mount: Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/ad0s1a 507630 85142 381878 18% / /dev/ad0s1e 507630 20 467000 0% /tmp /dev/ad0s1f 10154158 1176410 8165416 13% /usr /dev/ad0s1d 1506190 80326 1305370 6% /var /dev/ad0s1g 24174212 6939804 15300472 31% /var/squid swapinfo: /dev/ad0s1b 1022536 0 1022536 0% ~35Gb... Compared slice 1 on ad0 vs ad6, both have the exact same size. > >> Some googling indicated that SYNCHRONIZING means that its not >> "complete" and wont mount? Is that correct? Why would it be in that >> state then, I just shut it down fine... And where the f*ck did my >> slices go??.. > > SYNCHRONIZING means that this component was/is being synchronized. It > seems that you removed/lost the master disk, while it was =20 > synchronizing. > It should work anyway. Okay thats odd.. ad6 was the only disk in the mirror when I shut down =20= (shutdown -p now, and it powered off by itself..) so it should have =20 been good.. > > BTW. You confuse things again. Your slice is just fine (ad6s1), you > don't have partitions, AFAIU. Seems I did yes, thanks. Disks have slices (which on windows/dos/=20 linux world is called partitions) which have partitions.. check :) > > All in all, your partition table seems to be gone. If you created =20 > it on > gmirror before (gm0s1) you may still have the same partition table on > the other half of the mirror. You can try to move it to ad6 with > bsdlabel and verify if you can see file system inside partitions. Okay, tried that now.. Saved ad0s1 label, reloaded it onto ad6s1.. =20 Now I got same partition table on ad6s1 as on ad0s1... Trying to mount any though gives me incorrect super block... fsck =20 cannot find any superblocks either.. So.. What to do now then? Just for get ad6 and start from scratch =20 from ad2? (as i said, the data isnt very old realy)... Im thinking about doing complete reinstall on ad4+ad6 then.. Can I do =20= that? fdisk both with full partition on both, create a new gmirror =20 between ad6s1/ad4s1 (or should i go on ad4/ad6?), create slices, use =20 dump | restore (of course with apps shutdown so no data is changed.. =20 or at least nothing that I care about) to copy all files from ad2 to =20 new mirror.. what do I need to do more? bsdlabel -B on both to write =20 boot blocks? Is there anything else to think about? Thanks for your help..:) From owner-freebsd-stable@FreeBSD.ORG Tue Aug 21 16:12:57 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2170516A468 for ; Tue, 21 Aug 2007 16:12:57 +0000 (UTC) (envelope-from freebsd@bitfreak.org) Received: from mail.twinthornes.com (mail.twinthornes.com [65.75.198.147]) by mx1.freebsd.org (Postfix) with ESMTP id F018D13C4B0 for ; Tue, 21 Aug 2007 16:12:56 +0000 (UTC) (envelope-from freebsd@bitfreak.org) Received: from [10.9.70.100] (pool-72-90-106-233.ptldor.fios.verizon.net [72.90.106.233]) by mail.twinthornes.com (Postfix) with ESMTP id 5C0D07C4; Tue, 21 Aug 2007 09:12:56 -0700 (PDT) Message-ID: <46CB0EDE.3010806@bitfreak.org> Date: Tue, 21 Aug 2007 09:12:14 -0700 From: Darren Pilgrim User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: Artem Kuchin References: <028f01c7e37a$d8f441b0$0c00a8c0@Artem> <46CA7681.3070909@gneto.com><03bc01c7e3b8$7f9a3a50$0c00a8c0@Artem> <46CA8507.5000803@bitfreak.org> <00a101c7e3d6$9140fb90$0c00a8c0@Artem> In-Reply-To: <00a101c7e3d6$9140fb90$0c00a8c0@Artem> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: A little story of failed raid5 (3ware 8000 series) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 16:12:57 -0000 Artem Kuchin wrote: > Darren Pilgrim wrote: >> Artem Kuchin wrote: >>> That exactly was i was talking about. I don't acess to individual >>> disks >>> behind raid unit, so, i cannot doit. I don't know it controller >>> VERIFY command does it right. If it doesm then i shoudl put it into >>> a cron >>> job and do it on weekly basis. Also, it would halpfull it i could >>> get access to number of left reserved sector for remapping. Any idea >>> about these two for 3ware controllers? Also, someone should mention, >>> that while using raid MUST >>> do verifies often. >> The 3dm2 software (sysutils/3dm port) can dump the SMART data from >> individual disks. It can also schedule verify and self-test tasks and >> identify individual drives by blinking the activity light for the >> drive. _______________________________________________ > > Problems are: > 1) how to parse this dump of data? Actually smartctl (part of smartmontools) can read the SMART data through a 3ware controller. > 2) No scheduling is available on 7000,8000 on 4 port models Use tw_sched then. From owner-freebsd-stable@FreeBSD.ORG Tue Aug 21 20:18:12 2007 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 408EA16A419 for ; Tue, 21 Aug 2007 20:18:12 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Received: from mu-out-0910.google.com (mu-out-0910.google.com [209.85.134.191]) by mx1.freebsd.org (Postfix) with ESMTP id AB3EF13C45E for ; Tue, 21 Aug 2007 20:18:11 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Received: by mu-out-0910.google.com with SMTP id w9so1857935mue for ; Tue, 21 Aug 2007 13:18:10 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:received:received:date:from:to:subject:message-id:mail-followup-to:mime-version:content-type:content-disposition:user-agent; b=LNZ9c13YcNs+SwELFF+Gr7zzSRrnDEv51xsrxwZ442bPkfvwHQKHBtOgCzY18i8s7L4oHDHLxSRrhMsy0EZGYYgIQ5FNFhvnY6LuDp3t9eRqe0f809cKG9wsfFOxRGpfZutwEbfhe3WjaWK82/Nvd7Gn8nfSbRjADR1QoGYNSM8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:date:from:to:subject:message-id:mail-followup-to:mime-version:content-type:content-disposition:user-agent; b=N1kWVOWhvoh5igijRYdFrdGU7excWov8F45EOt7RsEqitzHzGFFKx1HVhO1htisNcLwpfAVk2P309W4OB21kOknyY7rfk2WWVhi6H0htWJExH7DYFJXU9MiuncMO1uDixBK8kcRexknYGEkWEyqww7KlBrvNcQiMrKq7FWaDkxI= Received: by 10.82.111.8 with SMTP id j8mr11156121buc.1187725849549; Tue, 21 Aug 2007 12:50:49 -0700 (PDT) Received: from roadrunner.spoerlein.net ( [85.180.178.208]) by mx.google.com with ESMTPS id g1sm25145053muf.2007.08.21.12.50.47 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 21 Aug 2007 12:50:48 -0700 (PDT) Received: from roadrunner.spoerlein.net (localhost [127.0.0.1]) by roadrunner.spoerlein.net (8.14.1/8.14.1) with ESMTP id l7LJoiYE003710 for ; Tue, 21 Aug 2007 21:50:44 +0200 (CEST) (envelope-from uspoerlein@gmail.com) Received: (from q@localhost) by roadrunner.spoerlein.net (8.14.1/8.14.1/Submit) id l7LJoh7C003709 for stable@freebsd.org; Tue, 21 Aug 2007 21:50:43 +0200 (CEST) (envelope-from uspoerlein@gmail.com) Date: Tue, 21 Aug 2007 21:50:43 +0200 From: Ulrich Spoerlein To: stable@freebsd.org Message-ID: <20070821195043.GA1464@roadrunner.spoerlein.net> Mail-Followup-To: stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.15 (2007-04-06) Cc: Subject: pam_group vs. multiple group lines X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 20:18:12 -0000 Hi, I think I found a deficiency wrt. to pam_group (which also hits sudo(8) so this might be libc related instead). I found this while trying to migrate groups into LDAP, but you don't need LDAP to reproduce this, simply place the following in /etc/group wheel:*:0:root wheel:*:0:us % getent group|grep wheel;id wheel:*:0:root wheel:*:0:us uid=1001(us) gid=1000(us) groups=1000(us),0(wheel),80(www) As you can see, getent(1) and id(1) work fine. File access also works like expected, except for su(8) (because of pam_group group=wheel in pam.d/su) % su - su: Sorry Combine the wheel entries back into one line and su(8) suddenly starts working again. Same problem hits sudo(8) if your are using a %wheel line. Since there is no pam.d/sudo on my system I think the bug probably lies in libc itself. Is this expected behaviour? I'd classify it as bug ... Cheers, Ulrich Spoerlein -- It is better to remain silent and be thought a fool, than to speak, and remove all doubt. From owner-freebsd-stable@FreeBSD.ORG Tue Aug 21 20:43:33 2007 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5912616A417 for ; Tue, 21 Aug 2007 20:43:33 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from mail-out3.apple.com (mail-out3.apple.com [17.254.13.22]) by mx1.freebsd.org (Postfix) with ESMTP id 420FD13C478 for ; Tue, 21 Aug 2007 20:43:33 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from relay11.apple.com (relay11.apple.com [17.128.113.48]) by mail-out3.apple.com (Postfix) with ESMTP id 0FC00F16441; Tue, 21 Aug 2007 13:24:43 -0700 (PDT) Received: from relay11.apple.com (unknown [127.0.0.1]) by relay11.apple.com (Symantec Mail Security) with ESMTP id E5E75287BC; Tue, 21 Aug 2007 13:24:42 -0700 (PDT) X-AuditID: 11807130-a71a1bb000006012-cc-46cb4a0ab9b7 Received: from [17.214.13.96] (cswiger1.apple.com [17.214.13.96]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by relay11.apple.com (Symantec Mail Security) with ESMTP id CE17D284C2; Tue, 21 Aug 2007 13:24:42 -0700 (PDT) In-Reply-To: <20070821195043.GA1464@roadrunner.spoerlein.net> References: <20070821195043.GA1464@roadrunner.spoerlein.net> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Chuck Swiger Date: Tue, 21 Aug 2007 13:24:42 -0700 To: Ulrich Spoerlein X-Mailer: Apple Mail (2.752.2) X-Brightmail-Tracker: AAAAAA== Cc: stable@freebsd.org Subject: Re: pam_group vs. multiple group lines X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 20:43:33 -0000 On Aug 21, 2007, at 12:50 PM, Ulrich Spoerlein wrote: > I found this while trying to migrate groups into LDAP, but you don't > need LDAP to reproduce this, simply place the following in /etc/group > > wheel:*:0:root > wheel:*:0:us That's a misconfiguration. From "man 5 group": The group field is the group name used for granting file access to users who are members of the group. The gid field is the number associated with the group name. They should both be unique across the system (and ^^^^^^^^^^^^^^^^^^^^^ often across a group of systems) since they control file access. -- -Chuck From owner-freebsd-stable@FreeBSD.ORG Tue Aug 21 21:29:25 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2C1A816A417 for ; Tue, 21 Aug 2007 21:29:25 +0000 (UTC) (envelope-from rbsfou@yahoo.co.uk) Received: from smtp009.mail.ukl.yahoo.com (smtp009.mail.ukl.yahoo.com [217.12.11.63]) by mx1.freebsd.org (Postfix) with SMTP id 9E39913C48D for ; Tue, 21 Aug 2007 21:29:24 +0000 (UTC) (envelope-from rbsfou@yahoo.co.uk) Received: (qmail 35150 invoked from network); 21 Aug 2007 21:02:43 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.co.uk; h=Received:X-YMail-OSG:Mime-Version:In-Reply-To:References:Content-Type:Message-Id:Content-Transfer-Encoding:From:Subject:Date:To:X-Mailer; b=HN67DpAnOWfNIAD1gMR4AP4XudBtnO8dS2tIod+XqskIqEg3wtTUHbx9I1F3CZpMoudVoGXExVuS1Wn362ipOi8lDT0w5DA9tPPJvKkEJdJsMckA7UsvWloY2gwuR3zTJLZJ8rpwwxr6Phhh5DG+WmbR4fsxVZyetMqFg0+NhXY= ; Received: from unknown (HELO ?192.168.101.169?) (rbsfou@82.34.33.119 with plain) by smtp009.mail.ukl.yahoo.com with SMTP; 21 Aug 2007 21:02:43 -0000 X-YMail-OSG: 1Ql7ZckVM1mJDs2BqOSMqPVkX92kHTCJMNwCWXLzac_295B4Mk0Vt9hwhcflnRisghG.B1njLBSz5YJf58VyK9B8KPJTrj2.4.N0du3drT3abLUFqsxztD6NBtQ- Mime-Version: 1.0 (Apple Message framework v752.2) In-Reply-To: References: <20070821195043.GA1464@roadrunner.spoerlein.net> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <64A1102C-0697-4C4D-AF3B-B1F2ED224792@yahoo.co.uk> Content-Transfer-Encoding: 7bit From: Richard Foulkes Date: Tue, 21 Aug 2007 22:02:42 +0100 To: freebsd-stable@freebsd.org X-Mailer: Apple Mail (2.752.2) Subject: Re: pam_group vs. multiple group lines X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 21:29:25 -0000 Ok, so how are you supposed to control membership of the wheel group via ldap? Ok, you COULD remove the local wheel entry in /etc/group, but this would probably be a bad idea if the ldap server were unavailable. I've had a similar problem to this where group names are duplicated across different operating systems (i use gentoo, freebsd and ubuntu on my network) but the gid's are different. For instance the 'audio' group on gentoo has a different gid to the 'audio' group on ubuntu. This would appear to have something to do with nss_base_group configuration option in the ldap.conf file used by nss_ldap and pam_ldap - something to do with the "search scope" - whereby i can configure the ldap.conf file for one os to look a sub-tree of my "groups" ou for additional groups specific to that OS - but documentation on the PADL site on this topic is almost non-existant! Can anyone help? On 21 Aug 2007, at 21:24, Chuck Swiger wrote: > On Aug 21, 2007, at 12:50 PM, Ulrich Spoerlein wrote: >> I found this while trying to migrate groups into LDAP, but you don't >> need LDAP to reproduce this, simply place the following in /etc/group >> >> wheel:*:0:root >> wheel:*:0:us > > That's a misconfiguration. From "man 5 group": > > The group field is the group name used for granting file access > to users > who are members of the group. The gid field is the number > associated > with the group name. They should both be unique across the > system (and > ^^^^^^^^^^^^^^^^^^^^^ > often across a group of systems) since they control file access. > > -- > -Chuck > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable- > unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Wed Aug 22 00:08:37 2007 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C309F16A478 for ; Wed, 22 Aug 2007 00:08:37 +0000 (UTC) (envelope-from Brian.Scott@det.nsw.edu.au) Received: from hplmx1.det.nsw.edu.au (hplmx1.det.nsw.edu.au [153.107.41.145]) by mx1.freebsd.org (Postfix) with ESMTP id 72B3013C4F7 for ; Wed, 22 Aug 2007 00:07:45 +0000 (UTC) (envelope-from Brian.Scott@det.nsw.edu.au) Received: from itfsmtp7.central.det.win (externalmail.det.nsw.edu.au [153.107.8.159]) by hplmx1.det.nsw.edu.au (8.13.1/8.13.1) with ESMTP id l7LNiF56028315; Wed, 22 Aug 2007 09:44:15 +1000 Received: from itfexhub4.central.det.win (Not Verified[153.107.9.31]) by itfsmtp7.central.det.win with MailMarshal (v6, 1, 8, 2137) id ; Wed, 22 Aug 2007 09:44:15 +1000 Received: from ALF6.riverina.det.win ([172.18.8.14]) by itfexhub4.central.det.win with Microsoft SMTPSVC(6.0.3790.3959); Wed, 22 Aug 2007 09:44:15 +1000 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5 Date: Wed, 22 Aug 2007 09:44:14 +1000 Message-ID: <93F091C9B5CFAF409180B07728D682E9EBEAF6@ALF6.riverina.det.win> In-Reply-To: <20070821195043.GA1464@roadrunner.spoerlein.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: pam_group vs. multiple group lines Thread-Index: AcfkMLWrsTBeZ4QVSPy7VUVEiFLU2wAG/bnw From: "Scott, Brian" To: "Ulrich Spoerlein" , X-OriginalArrivalTime: 21 Aug 2007 23:44:15.0222 (UTC) FILETIME=[2ECE1160:01C7E44D] Cc: Subject: RE: pam_group vs. multiple group lines X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Aug 2007 00:08:37 -0000 Try: wheel:*:0:root,us It looks like pam was stopping at the first matching line as you would expect from the man page for the group file. If there is a bug it is in the more liberal interpretation by other software. -----Original Message----- From: owner-freebsd-stable@freebsd.org [mailto:owner-freebsd-stable@freebsd.org] On Behalf Of Ulrich Spoerlein Sent: Wednesday, 22 August 2007 5:51 AM To: stable@freebsd.org Subject: pam_group vs. multiple group lines Hi, I think I found a deficiency wrt. to pam_group (which also hits sudo(8) so this might be libc related instead). I found this while trying to migrate groups into LDAP, but you don't need LDAP to reproduce this, simply place the following in /etc/group wheel:*:0:root wheel:*:0:us % getent group|grep wheel;id wheel:*:0:root wheel:*:0:us uid=3D1001(us) gid=3D1000(us) groups=3D1000(us),0(wheel),80(www) As you can see, getent(1) and id(1) work fine. File access also works like expected, except for su(8) (because of pam_group group=3Dwheel in pam.d/su) % su - su: Sorry Combine the wheel entries back into one line and su(8) suddenly starts working again. Same problem hits sudo(8) if your are using a %wheel line. Since there is no pam.d/sudo on my system I think the bug probably lies in libc itself. Is this expected behaviour? I'd classify it as bug ... Cheers, Ulrich Spoerlein --=20 It is better to remain silent and be thought a fool, than to speak, and remove all doubt. _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" ********************************************************************** This message is intended for the addressee named and may contain privileged information or confidential information or both. If you are not the intended recipient please delete it and notify the sender. ********************************************************************** From owner-freebsd-stable@FreeBSD.ORG Wed Aug 22 00:12:26 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1A93816A418 for ; Wed, 22 Aug 2007 00:12:26 +0000 (UTC) (envelope-from jonc@chen.org.nz) Received: from drone1.qsi.net.nz (drone1-svc-skyt.qsi.net.nz [202.89.128.1]) by mx1.freebsd.org (Postfix) with ESMTP id B169413C474 for ; Wed, 22 Aug 2007 00:12:25 +0000 (UTC) (envelope-from jonc@chen.org.nz) Received: (qmail 14135 invoked by uid 0); 21 Aug 2007 23:38:35 -0000 Received: from unknown (HELO chen.org.nz) ([202.89.146.5]) (envelope-sender ) by 0 (qmail-ldap-1.03) with SMTP for ; 21 Aug 2007 23:38:33 -0000 Received: by chen.org.nz (Postfix, from userid 1000) id E976C7E84E; Wed, 22 Aug 2007 11:38:21 +1200 (NZST) Date: Wed, 22 Aug 2007 11:38:21 +1200 From: Jonathan Chen To: freebsd-stable@freebsd.org Message-ID: <20070821233821.GA6611@osiris.chen.org.nz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Subject: NZ Daylight Savings changes. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Aug 2007 00:12:26 -0000 Hi, Would it be possible for a committer to take a look at: http://www.freebsd.org/cgi/query-pr.cgi?pr=115697 There's only about a month or so before the new daylight savings rule becomes effective, and it would be nice if -STABLE had the changes committed before then. Cheers. -- Jonathan Chen ----------------------------------------------------------------------- "I love deadlines. I like the whooshing sound they make as they fly by" - Douglas Adams From owner-freebsd-stable@FreeBSD.ORG Wed Aug 22 00:19:03 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6D8E716A41A for ; Wed, 22 Aug 2007 00:19:03 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from mail-out3.apple.com (mail-out3.apple.com [17.254.13.22]) by mx1.freebsd.org (Postfix) with ESMTP id 5632513C4A5 for ; Wed, 22 Aug 2007 00:19:03 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from relay13.apple.com (relay13.apple.com [17.128.113.29]) by mail-out3.apple.com (Postfix) with ESMTP id 55EF9F1B211; Tue, 21 Aug 2007 17:18:53 -0700 (PDT) Received: from relay13.apple.com (unknown [127.0.0.1]) by relay13.apple.com (Symantec Mail Security) with ESMTP id 39119294FF; Tue, 21 Aug 2007 17:18:53 -0700 (PDT) X-AuditID: 1180711d-a1a1ebb000001006-34-46cb80ece4c5 Received: from [17.214.13.96] (cswiger1.apple.com [17.214.13.96]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by relay13.apple.com (Symantec Mail Security) with ESMTP id 83EA1294EE; Tue, 21 Aug 2007 17:18:52 -0700 (PDT) In-Reply-To: <64A1102C-0697-4C4D-AF3B-B1F2ED224792@yahoo.co.uk> References: <20070821195043.GA1464@roadrunner.spoerlein.net> <64A1102C-0697-4C4D-AF3B-B1F2ED224792@yahoo.co.uk> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <1D83A750-03FD-49EF-B99D-BA9B7F7E7BD0@mac.com> Content-Transfer-Encoding: 7bit From: Chuck Swiger Date: Tue, 21 Aug 2007 17:18:51 -0700 To: Richard Foulkes X-Mailer: Apple Mail (2.752.2) X-Brightmail-Tracker: AAAAAA== Cc: freebsd-stable@freebsd.org Subject: Re: pam_group vs. multiple group lines X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Aug 2007 00:19:03 -0000 On Aug 21, 2007, at 2:02 PM, Richard Foulkes wrote: > Ok, so how are you supposed to control membership of the wheel > group via ldap? Ok, you COULD remove the local wheel entry in /etc/ > group, but this would probably be a bad idea if the ldap server > were unavailable. You've aptly summarized my thoughts on the matter-- I would not rely on LDAP to provide information about root or the wheel group. > I've had a similar problem to this where group names are duplicated > across different operating systems (i use gentoo, freebsd and > ubuntu on my network) but the gid's are different. For instance the > 'audio' group on gentoo has a different gid to the 'audio' group on > ubuntu. This would appear to have something to do with > nss_base_group configuration option in the ldap.conf file used by > nss_ldap and pam_ldap - something to do with the "search scope" - > whereby i can configure the ldap.conf file for one os to look a sub- > tree of my "groups" ou for additional groups specific to that OS - > but documentation on the PADL site on this topic is almost non- > existant! > > Can anyone help? The solutions to these problems are somewhat painful; looking into the experience of those using YP/NIS or NetInfo will probably give some insight which applies to using the newfangled directory services (aka "LDAP", "Active Directory", "Open Directory", etc). You can replace the existing flatfile groups with a unified version which your site is happy with across all of the platforms you use, and then use "find -nogroup" and things like mtree or rsync to reset the permissions appropriately. -- -Chuck From owner-freebsd-stable@FreeBSD.ORG Wed Aug 22 00:21:11 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EE83816A47D for ; Wed, 22 Aug 2007 00:21:11 +0000 (UTC) (envelope-from edwin@mavetju.org) Received: from mail5out.barnet.com.au (mail5.barnet.com.au [202.83.178.78]) by mx1.freebsd.org (Postfix) with ESMTP id AD65213C48A for ; Wed, 22 Aug 2007 00:21:11 +0000 (UTC) (envelope-from edwin@mavetju.org) Received: by mail5out.barnet.com.au (Postfix, from userid 1001) id C06A92219D10; Wed, 22 Aug 2007 10:21:10 +1000 (EST) X-Viruscan-Id: <46CB8176000128158E29C6@BarNet> Received: from mail5auth.barnet.com.au (mail5.barnet.com.au [202.83.178.78]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mail5.barnet.com.au (Postfix) with ESMTP id 89AB421B28FB; Wed, 22 Aug 2007 10:21:10 +1000 (EST) Received: from k7.mavetju (k7.mavetju.org [10.251.1.18]) by mail5auth.barnet.com.au (Postfix) with ESMTP id 3F8822219D18; Wed, 22 Aug 2007 10:21:10 +1000 (EST) Received: by k7.mavetju (Postfix, from userid 1001) id 4BF1723B; Wed, 22 Aug 2007 10:21:13 +1000 (EST) Date: Wed, 22 Aug 2007 10:21:13 +1000 From: Edwin Groothuis To: Jonathan Chen Message-ID: <20070822002113.GB1393@k7.mavetju> Mail-Followup-To: Edwin Groothuis , Jonathan Chen , freebsd-stable@freebsd.org References: <20070821233821.GA6611@osiris.chen.org.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070821233821.GA6611@osiris.chen.org.nz> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org Subject: Re: NZ Daylight Savings changes. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Aug 2007 00:21:12 -0000 On Wed, Aug 22, 2007 at 11:38:21AM +1200, Jonathan Chen wrote: > Would it be possible for a committer to take a look at: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=115697 > > There's only about a month or so before the new daylight savings rule > becomes effective, and it would be nice if -STABLE had the changes > committed before then. The port misc/zoneinfo has been updated with the 2007g version of the zoneinfo files, I'm going to see if I can get approval of re@ to commit this. Edwin -- Edwin Groothuis | Personal website: http://www.mavetju.org edwin@mavetju.org | Weblog: http://www.mavetju.org/weblog/ From owner-freebsd-stable@FreeBSD.ORG Wed Aug 22 00:31:05 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9973016A41A for ; Wed, 22 Aug 2007 00:31:05 +0000 (UTC) (envelope-from marka@isc.org) Received: from drugs.dv.isc.org (drugs.dv.isc.org [IPv6:2001:470:1f00:820:214:22ff:fed9:fbdc]) by mx1.freebsd.org (Postfix) with ESMTP id 551BA13C457 for ; Wed, 22 Aug 2007 00:31:05 +0000 (UTC) (envelope-from marka@isc.org) Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (8.14.1/8.14.1) with ESMTP id l7M0UvDc050391; Wed, 22 Aug 2007 10:30:57 +1000 (EST) (envelope-from marka@drugs.dv.isc.org) Message-Id: <200708220030.l7M0UvDc050391@drugs.dv.isc.org> To: Edwin Groothuis , Jonathan Chen , freebsd-stable@freebsd.org From: Mark Andrews Mail-Followup-To: Edwin Groothuis , Jonathan Chen , freebsd-stable@freebsd.org In-reply-to: Your message of "Wed, 22 Aug 2007 10:21:13 +1000." <20070822002113.GB1393@k7.mavetju> Date: Wed, 22 Aug 2007 10:30:57 +1000 Sender: marka@isc.org Cc: Subject: Re: NZ Daylight Savings changes. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Aug 2007 00:31:05 -0000 > On Wed, Aug 22, 2007 at 11:38:21AM +1200, Jonathan Chen wrote: > > Would it be possible for a committer to take a look at: > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=115697 > > > > There's only about a month or so before the new daylight savings rule > > becomes effective, and it would be nice if -STABLE had the changes > > committed before then. > > The port misc/zoneinfo has been updated with the 2007g version of > the zoneinfo files, I'm going to see if I can get approval of re@ > to commit this. Which really needs to be properly integrated into the base system with a NO_something to prevent the database being clobbered when the system is rebuilt. > Edwin > > -- > Edwin Groothuis | Personal website: http://www.mavetju.org > edwin@mavetju.org | Weblog: http://www.mavetju.org/weblog/ > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: Mark_Andrews@isc.org From owner-freebsd-stable@FreeBSD.ORG Wed Aug 22 08:19:22 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 56E1816A419 for ; Wed, 22 Aug 2007 08:19:22 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.191]) by mx1.freebsd.org (Postfix) with ESMTP id DEF6613C468 for ; Wed, 22 Aug 2007 08:19:21 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so78815nfb for ; Wed, 22 Aug 2007 01:19:20 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=YXMlJse2X4l+BRHAE2aVLW4tCiIqf9+Vp6ep8Yi7xiXO7vNKEd8kv/erqBWT6fLwYsUq9UVx1T6vyop/JwgNt8XD3V0c0SCZbAogk5oxoE8Uvt0rOnKQHZq4aTK8N1ThcV21w05aZkYKizXI4zZMaslw26DGHXt+aquNliG6aWw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=FelSiJctaysf7jwgwkeBpNrEJO0EYY2RBa3UBMzdyojSvV/dJY/Iwu4QscESgAGapN/Lyo2YiMJVBtFn7kTVjTC0mm1x8XcLdD/XrvwUSl6hFbGFh2RCWvQWpDIFwl8l6b7nkWDDARm4q7gCBADEDqU/teisrt0i0ZYTvC1toHY= Received: by 10.78.170.17 with SMTP id s17mr263816hue.1187769222527; Wed, 22 Aug 2007 00:53:42 -0700 (PDT) Received: by 10.78.168.7 with HTTP; Wed, 22 Aug 2007 00:53:42 -0700 (PDT) Message-ID: <7ad7ddd90708220053k147f4c5cq87430a4ee897180d@mail.gmail.com> Date: Wed, 22 Aug 2007 09:53:42 +0200 From: "Ulrich Spoerlein" To: "Chuck Swiger" In-Reply-To: <1D83A750-03FD-49EF-B99D-BA9B7F7E7BD0@mac.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070821195043.GA1464@roadrunner.spoerlein.net> <64A1102C-0697-4C4D-AF3B-B1F2ED224792@yahoo.co.uk> <1D83A750-03FD-49EF-B99D-BA9B7F7E7BD0@mac.com> Cc: Richard Foulkes , freebsd-stable@freebsd.org Subject: Re: pam_group vs. multiple group lines X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Aug 2007 08:19:22 -0000 On 8/22/07, Chuck Swiger wrote: > On Aug 21, 2007, at 2:02 PM, Richard Foulkes wrote: > > Ok, so how are you supposed to control membership of the wheel > > group via ldap? Ok, you COULD remove the local wheel entry in /etc/ > > group, but this would probably be a bad idea if the ldap server > > were unavailable. > > You've aptly summarized my thoughts on the matter-- I would not rely > on LDAP to provide information about root or the wheel group. That is exactly the gist of my question. Of course I know that a group oneliner is the way to go. However, I saw people suggest splitting groups into multiple lines, if the lines are too long or too many groups per line (something to do with the /etc/group parser, I guess). Anyway, I want the LDAP groups to *augment* system groups. Removing wheel from /etc/group and relying on a complex network service .... not funny. Besides, it *does* work for file permissions etc. so some basic system calls *do* get this right. Uli From owner-freebsd-stable@FreeBSD.ORG Wed Aug 22 08:28:43 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 76D5816A417 for ; Wed, 22 Aug 2007 08:28:43 +0000 (UTC) (envelope-from hausen@punkt.de) Received: from kagate.punkt.de (kagate.punkt.de [217.29.33.131]) by mx1.freebsd.org (Postfix) with ESMTP id E1EA113C48A for ; Wed, 22 Aug 2007 08:28:42 +0000 (UTC) (envelope-from hausen@punkt.de) Received: from hugo10.ka.punkt.de (hugo10.ka.punkt.de [10.0.0.110]) by kagate2.punkt.de with ESMTP id l7M8Sf2t043787 for ; Wed, 22 Aug 2007 10:28:41 +0200 (CEST) Received: from hugo10.ka.punkt.de (localhost [127.0.0.1]) by hugo10.ka.punkt.de (8.13.6/8.13.6) with ESMTP id l7M8SerQ075906; Wed, 22 Aug 2007 10:28:40 +0200 (CEST) (envelope-from ry93@hugo10.ka.punkt.de) Received: (from ry93@localhost) by hugo10.ka.punkt.de (8.13.6/8.13.6/Submit) id l7M8SeQL075905; Wed, 22 Aug 2007 10:28:40 +0200 (CEST) (envelope-from ry93) Date: Wed, 22 Aug 2007 10:28:40 +0200 From: "Patrick M. Hausen" To: Ulrich Spoerlein Message-ID: <20070822082840.GB74165@hugo10.ka.punkt.de> References: <20070821195043.GA1464@roadrunner.spoerlein.net> <64A1102C-0697-4C4D-AF3B-B1F2ED224792@yahoo.co.uk> <1D83A750-03FD-49EF-B99D-BA9B7F7E7BD0@mac.com> <7ad7ddd90708220053k147f4c5cq87430a4ee897180d@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <7ad7ddd90708220053k147f4c5cq87430a4ee897180d@mail.gmail.com> User-Agent: Mutt/1.5.15 (2007-04-06) Cc: freebsd-stable@freebsd.org, Richard Foulkes Subject: Re: pam_group vs. multiple group lines X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Aug 2007 08:28:43 -0000 Hi, all! On Wed, Aug 22, 2007 at 09:53:42AM +0200, Ulrich Spoerlein wrote: > On 8/22/07, Chuck Swiger wrote: > > On Aug 21, 2007, at 2:02 PM, Richard Foulkes wrote: > > > Ok, so how are you supposed to control membership of the wheel > > > group via ldap? Ok, you COULD remove the local wheel entry in /etc/ > > > group, but this would probably be a bad idea if the ldap server > > > were unavailable. > > > > You've aptly summarized my thoughts on the matter-- I would not rely > > on LDAP to provide information about root or the wheel group. > > That is exactly the gist of my question. Of course I know that a group > oneliner is the way to go. However, I saw people suggest splitting > groups into multiple lines, if the lines are too long or too many > groups per line (something to do with the /etc/group parser, I guess). > > Anyway, I want the LDAP groups to *augment* system groups. Removing > wheel from /etc/group and relying on a complex network service .... > not funny. I've only followed this thread loosely, so I apologize if this has already been stated or if I'm completely missing the point, but here goes: We do not use LDAP yet, but have been using NIS in our internal office network for years. If you use the magic "+" token to merge your NIS database with the static files for passwd and group information, then _if_ the group entry in the static file does not contain any users _then_ the information from NIS is merged in So you can keep a "wheel" group around as the _primary_ group for root, toor, whatnot ... and all the additional members that have "wheel" as an auxiliary group come from NIS. Possibly this works for LDAP, too? IMHO at least it should ;-)) Kind regards, Patrick -- punkt.de GmbH * Vorholzstr. 25 * 76137 Karlsruhe Tel. 0721 9109 0 * Fax 0721 9109 100 info@punkt.de http://www.punkt.de Gf: Jürgen Egeling AG Mannheim 108285 From owner-freebsd-stable@FreeBSD.ORG Wed Aug 22 10:20:10 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8323916A417; Wed, 22 Aug 2007 10:20:10 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from msrv.matik.com.br (msrv.matik.com.br [200.152.83.14]) by mx1.freebsd.org (Postfix) with ESMTP id A8EA113C458; Wed, 22 Aug 2007 10:20:08 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from ap-h.matik.com.br (ap-h.matik.com.br [200.152.83.36]) by msrv.matik.com.br (8.14.1/8.13.1) with ESMTP id l7MAK7TH078827; Wed, 22 Aug 2007 07:20:08 -0300 (BRT) (envelope-from joao@matik.com.br) From: JoaoBR Organization: Infomatik To: freebsd-acpi@freebsd.org Date: Wed, 22 Aug 2007 07:24:24 -0300 User-Agent: KMail/1.9.7 References: <200707271109.51334.joao@matik.com.br> <46AB160D.6040207@freebsd.org> <200708060928.36154.joao@matik.com.br> In-Reply-To: <200708060928.36154.joao@matik.com.br> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200708220724.25330.joao@matik.com.br> X-Virus-Scanned: ClamAV version 0.90.3, clamav-milter version 0.90.3 on msrv.matik.com.br X-Virus-Status: Clean Cc: freebsd-stable@freebsd.org Subject: Re: powerd freeze with amd 5000 X2 but not with lower cpus X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Aug 2007 10:20:10 -0000 On Monday 06 August 2007 09:28:35 JoaoBR wrote: =2E.... > > I had a chance to test several MBs with the same 6000+, 5000+ and 4600+ c= pu > > At the end seems that the problem is mb/hardware related since some > combinations hung even with latest BIOS installed and others not. > not sure if somebody still wants to hear about this but it is kind of=20 interesting I guess for my understandings in first place the MB and Bios is most important thin= g=20 and there are vendor bios out which say they support the higher freq CPUs b= ut=20 certainly they don't or at least not all of them even so I gut freezes on all kind of combinations and seems that xorg and i= t's=20 video drv are kind of very sensitive to certain settings, also with glx and= =20 dri disabled I still got freezings sooner or later I got a new monitor this days and that brought the real stuff up, seems tha= t=20 xorg is not liking when the HorizSync and VertRefresh rates are not 100%=20 correct and what then cause the kill. In order to doublecheck this I took m= y=20 old monitor back with correct settings and i got no further freezes either= =20 with any of the CPU/MB combinations I tested before. I have an LCD which can 1280x1024 at 75hz , the former could 1024x768 at 75= hz=20 and with both it works now fine with VertRefresh 50-100 HorizSync 31.5 - 82.0 before I had VertRefresh 50 - 90 HorizSync 30 - 75 one thing more I did which caused a sysctl error on boot. There is a funny= =20 line in /etc/rc.s/power_profile as 'highest_value=3D"C1"' which I commented= out=20 but I guess that has nothing to do since the setting was not accepted anyway xorg seems to have problems when enabling DPMS and returns wrong=20 values. The vesa driver seems to work better or is less sensitive than sis= =20 and nv and ati but with the correct monitor rates all are working fine. well, I believe that's it because I have now two different MATX MBs running= =20 24h with Athlon 5000 without any problem, since friday night =20 =2D-=20 Jo=E3o A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br From owner-freebsd-stable@FreeBSD.ORG Wed Aug 22 10:21:11 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2E85A16A419; Wed, 22 Aug 2007 10:21:11 +0000 (UTC) (envelope-from edwin@mavetju.org) Received: from mail5out.barnet.com.au (mail5.barnet.com.au [202.83.178.78]) by mx1.freebsd.org (Postfix) with ESMTP id DC56413C478; Wed, 22 Aug 2007 10:21:10 +0000 (UTC) (envelope-from edwin@mavetju.org) Received: by mail5out.barnet.com.au (Postfix, from userid 1001) id 3310C2219D23; Wed, 22 Aug 2007 20:21:10 +1000 (EST) X-Viruscan-Id: <46CC0E1600014E534EF676@BarNet> Received: from mail5auth.barnet.com.au (mail5.barnet.com.au [202.83.178.78]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mail5.barnet.com.au (Postfix) with ESMTP id EF4BC21B290D; Wed, 22 Aug 2007 20:21:09 +1000 (EST) Received: from k7.mavetju (k7.mavetju.org [10.251.1.18]) by mail5auth.barnet.com.au (Postfix) with ESMTP id 746CF2219D10; Wed, 22 Aug 2007 20:21:08 +1000 (EST) Received: by k7.mavetju (Postfix, from userid 1001) id 19153DE; Wed, 22 Aug 2007 20:21:01 +1000 (EST) Date: Wed, 22 Aug 2007 20:21:01 +1000 From: Edwin Groothuis To: Jonathan Chen , freebsd-stable@freebsd.org Message-ID: <20070822102101.GC1393@k7.mavetju> Mail-Followup-To: Edwin Groothuis , Jonathan Chen , freebsd-stable@freebsd.org, remko@freebsd.org References: <20070822002113.GB1393@k7.mavetju> <200708220030.l7M0UvDc050391@drugs.dv.isc.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200708220030.l7M0UvDc050391@drugs.dv.isc.org> User-Agent: Mutt/1.4.2.3i Cc: remko@freebsd.org Subject: Re: NZ Daylight Savings changes. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Aug 2007 10:21:11 -0000 On Wed, Aug 22, 2007 at 10:30:57AM +1000, Mark Andrews wrote: > > On Wed, Aug 22, 2007 at 11:38:21AM +1200, Jonathan Chen wrote: > > > Would it be possible for a committer to take a look at: > > > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=115697 > > > > > > There's only about a month or so before the new daylight savings rule > > > becomes effective, and it would be nice if -STABLE had the changes > > > committed before then. > > > > The port misc/zoneinfo has been updated with the 2007g version of > > the zoneinfo files, I'm going to see if I can get approval of re@ > > to commit this. > > Which really needs to be properly integrated into the base > system with a NO_something to prevent the database being > clobbered when the system is rebuilt. http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/104713 I've poked remko@ in this email to ask him the status about the MFC. He said he didn't want me to do the MFC, so it's on his plate. I saw at http://www.freebsd.org/cgi/cvsweb.cgi/src/share/zoneinfo/australasia that the 2007f is also not MFCed. Edwin -- Edwin Groothuis | Personal website: http://www.mavetju.org edwin@mavetju.org | Weblog: http://www.mavetju.org/weblog/ From owner-freebsd-stable@FreeBSD.ORG Wed Aug 22 10:30:43 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 40E5F16A41B; Wed, 22 Aug 2007 10:30:43 +0000 (UTC) (envelope-from remko@FreeBSD.org) Received: from galain.elvandar.org (redqueen.elvandar.org [217.148.169.55]) by mx1.freebsd.org (Postfix) with ESMTP id 04AD613C45E; Wed, 22 Aug 2007 10:30:43 +0000 (UTC) (envelope-from remko@FreeBSD.org) Received: from evilcoder.xs4all.nl ([195.64.94.120] helo=elvandar.local) by galain.elvandar.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1INnTx-000H2W-Q8; Wed, 22 Aug 2007 12:30:37 +0200 Message-ID: <46CC1063.2040508@FreeBSD.org> Date: Wed, 22 Aug 2007 12:30:59 +0200 From: Remko Lodder User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Edwin Groothuis , Jonathan Chen , freebsd-stable@freebsd.org, remko@freebsd.org References: <20070822002113.GB1393@k7.mavetju> <200708220030.l7M0UvDc050391@drugs.dv.isc.org> <20070822102101.GC1393@k7.mavetju> In-Reply-To: <20070822102101.GC1393@k7.mavetju> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: Re: NZ Daylight Savings changes. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Aug 2007 10:30:43 -0000 Edwin Groothuis wrote: > On Wed, Aug 22, 2007 at 10:30:57AM +1000, Mark Andrews wrote: >>> On Wed, Aug 22, 2007 at 11:38:21AM +1200, Jonathan Chen wrote: >>>> Would it be possible for a committer to take a look at: >>>> >>>> http://www.freebsd.org/cgi/query-pr.cgi?pr=115697 >>>> >>>> There's only about a month or so before the new daylight savings rule >>>> becomes effective, and it would be nice if -STABLE had the changes >>>> committed before then. >>> The port misc/zoneinfo has been updated with the 2007g version of >>> the zoneinfo files, I'm going to see if I can get approval of re@ >>> to commit this. >> Which really needs to be properly integrated into the base >> system with a NO_something to prevent the database being >> clobbered when the system is rebuilt. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/104713 > > I've poked remko@ in this email to ask him the status about the > MFC. He said he didn't want me to do the MFC, so it's on his plate. > > I saw at > http://www.freebsd.org/cgi/cvsweb.cgi/src/share/zoneinfo/australasia that > the 2007f is also not MFCed. > > Edwin > Indeed, I want to do my own MFC's, the implementation in -current is different for older branches because the new logic is not in place for older versions. That said with or without the NO/WITHOUT_ZONEINFO stuff in the tree, you can update the zoneinfo part so do not point at me for that. -- Remko Lodder ** remko@elvandar.org FreeBSD ** remko@FreeBSD.org /* Quis custodiet ipsos custodes */ From owner-freebsd-stable@FreeBSD.ORG Wed Aug 22 11:54:25 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5F9C216A468; Wed, 22 Aug 2007 11:54:25 +0000 (UTC) (envelope-from edwin@mavetju.org) Received: from mail5out.barnet.com.au (mail5.barnet.com.au [202.83.178.78]) by mx1.freebsd.org (Postfix) with ESMTP id 10D9A13C465; Wed, 22 Aug 2007 11:54:24 +0000 (UTC) (envelope-from edwin@mavetju.org) Received: by mail5out.barnet.com.au (Postfix, from userid 1001) id 90FEC2219D24; Wed, 22 Aug 2007 21:54:23 +1000 (EST) X-Viruscan-Id: <46CC23EF00003C5EFEEE4B@BarNet> Received: from mail5auth.barnet.com.au (mail5.barnet.com.au [202.83.178.78]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mail5.barnet.com.au (Postfix) with ESMTP id 5B5C321B290D; Wed, 22 Aug 2007 21:54:23 +1000 (EST) Received: from k7.mavetju (k7.mavetju.org [10.251.1.18]) by mail5auth.barnet.com.au (Postfix) with ESMTP id 0C5112219D18; Wed, 22 Aug 2007 21:54:23 +1000 (EST) Received: by k7.mavetju (Postfix, from userid 1001) id 145E1189; Wed, 22 Aug 2007 21:54:26 +1000 (EST) Date: Wed, 22 Aug 2007 21:54:26 +1000 From: Edwin Groothuis To: Remko Lodder Message-ID: <20070822115426.GD1393@k7.mavetju> Mail-Followup-To: Edwin Groothuis , Remko Lodder , Jonathan Chen , freebsd-stable@freebsd.org References: <20070822002113.GB1393@k7.mavetju> <200708220030.l7M0UvDc050391@drugs.dv.isc.org> <20070822102101.GC1393@k7.mavetju> <46CC1063.2040508@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <46CC1063.2040508@FreeBSD.org> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org Subject: Re: NZ Daylight Savings changes. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Aug 2007 11:54:25 -0000 On Wed, Aug 22, 2007 at 12:30:59PM +0200, Remko Lodder wrote: > Edwin Groothuis wrote: > > On Wed, Aug 22, 2007 at 10:30:57AM +1000, Mark Andrews wrote: > >>> On Wed, Aug 22, 2007 at 11:38:21AM +1200, Jonathan Chen wrote: > >>>> Would it be possible for a committer to take a look at: > >>>> > >>>> http://www.freebsd.org/cgi/query-pr.cgi?pr=115697 > >>>> > >>>> There's only about a month or so before the new daylight savings rule > >>>> becomes effective, and it would be nice if -STABLE had the changes > >>>> committed before then. > >>> The port misc/zoneinfo has been updated with the 2007g version of > >>> the zoneinfo files, I'm going to see if I can get approval of re@ > >>> to commit this. > >> Which really needs to be properly integrated into the base > >> system with a NO_something to prevent the database being > >> clobbered when the system is rebuilt. > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/104713 > > > > I've poked remko@ in this email to ask him the status about the > > MFC. He said he didn't want me to do the MFC, so it's on his plate. > > > > I saw at > > http://www.freebsd.org/cgi/cvsweb.cgi/src/share/zoneinfo/australasia that > > the 2007f is also not MFCed. > > > > Edwin > > > > Indeed, I want to do my own MFC's, the implementation in -current > is different for older branches because the new logic is not in > place for older versions. That said with or without the > NO/WITHOUT_ZONEINFO stuff in the tree, you can update the zoneinfo part > so do not point at me for that. It might be different between -current and the older branches, but it fits in with the code used in the patch given by Mark which you had to modify two months ago to fit in with the new logic. Edwin -- Edwin Groothuis | Personal website: http://www.mavetju.org edwin@mavetju.org | Weblog: http://www.mavetju.org/weblog/ From owner-freebsd-stable@FreeBSD.ORG Wed Aug 22 11:57:21 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DCBA816A419 for ; Wed, 22 Aug 2007 11:57:21 +0000 (UTC) (envelope-from fulvia.costa@pd.infn.it) Received: from bsdsz2.pd.infn.it (bsdsz2.pd.infn.it [192.84.143.16]) by mx1.freebsd.org (Postfix) with ESMTP id 6DCDF13C442 for ; Wed, 22 Aug 2007 11:57:21 +0000 (UTC) (envelope-from fulvia.costa@pd.infn.it) Received: from [193.205.57.113] (xpeffeci.pd.infn.it [193.205.57.113]) (authenticated bits=0) by bsdsz2.pd.infn.it (8.13.6/8.13.6) with ESMTP id l7MBecx1095711 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 22 Aug 2007 13:40:38 +0200 (CEST) (envelope-from fulvia.costa@pd.infn.it) DomainKey-Signature: a=rsa-sha1; s=mail2; d=pd.infn.it; c=nofws; q=dns; h=message-id:date:from:user-agent:mime-version:to:subject: content-type:content-transfer-encoding:x-greylist:x-scanned-by; b=Hnf1c3A/NO41OHudfbi4kepbYCqOHTnK2f3hAND1H7WCx183idxT7tnUCduEhY39s fpG0GmEpb5gXon8b5qAT3Tk94b7sDyDwV/VFBuQ0SUrGF42YzVlTTv3iziripMR2fg8 D/dotbSjHa9k9zrm7VvWiqeZBwdozX1ASZLw0iY= Message-ID: <46CC20B6.7070109@pd.infn.it> Date: Wed, 22 Aug 2007 13:40:38 +0200 From: Fulvia Costa User-Agent: Thunderbird 1.5.0.8 (Windows/20061025) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (bsdsz2.pd.infn.it [192.84.143.16]); Wed, 22 Aug 2007 13:40:38 +0200 (CEST) X-Scanned-By: MIMEDefang 2.57 on 192.84.143.16 Subject: Leading blank in username X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Aug 2007 11:57:21 -0000 I run FreeBSD 6.2 and 6.1 in my mail servers. I use ldap via pam for authentication. The output of the commands: id "username" id " username" is the same (user and group number) if username is defined in ldap database, while the second one issues "user unknown" if username is defined in passwd file. Someone has found this problem? Thanks, Fulvia From owner-freebsd-stable@FreeBSD.ORG Wed Aug 22 11:57:53 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9805516A46C; Wed, 22 Aug 2007 11:57:53 +0000 (UTC) (envelope-from remko@FreeBSD.org) Received: from galain.elvandar.org (redqueen.elvandar.org [217.148.169.55]) by mx1.freebsd.org (Postfix) with ESMTP id 5765E13C494; Wed, 22 Aug 2007 11:57:53 +0000 (UTC) (envelope-from remko@FreeBSD.org) Received: from evilcoder.xs4all.nl ([195.64.94.120] helo=elvandar.local) by galain.elvandar.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1INoqN-000Hm1-Oc; Wed, 22 Aug 2007 13:57:51 +0200 Message-ID: <46CC24D5.1080201@FreeBSD.org> Date: Wed, 22 Aug 2007 13:58:13 +0200 From: Remko Lodder User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Edwin Groothuis , Remko Lodder , Jonathan Chen , freebsd-stable@freebsd.org References: <20070822002113.GB1393@k7.mavetju> <200708220030.l7M0UvDc050391@drugs.dv.isc.org> <20070822102101.GC1393@k7.mavetju> <46CC1063.2040508@FreeBSD.org> <20070822115426.GD1393@k7.mavetju> In-Reply-To: <20070822115426.GD1393@k7.mavetju> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: Re: NZ Daylight Savings changes. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Aug 2007 11:57:53 -0000 Edwin Groothuis wrote: > On Wed, Aug 22, 2007 at 12:30:59PM +0200, Remko Lodder wrote: >> Edwin Groothuis wrote: >>> On Wed, Aug 22, 2007 at 10:30:57AM +1000, Mark Andrews wrote: >>>>> On Wed, Aug 22, 2007 at 11:38:21AM +1200, Jonathan Chen wrote: >>>>>> Would it be possible for a committer to take a look at: >>>>>> >>>>>> http://www.freebsd.org/cgi/query-pr.cgi?pr=115697 >>>>>> >>>>>> There's only about a month or so before the new daylight savings rule >>>>>> becomes effective, and it would be nice if -STABLE had the changes >>>>>> committed before then. >>>>> The port misc/zoneinfo has been updated with the 2007g version of >>>>> the zoneinfo files, I'm going to see if I can get approval of re@ >>>>> to commit this. >>>> Which really needs to be properly integrated into the base >>>> system with a NO_something to prevent the database being >>>> clobbered when the system is rebuilt. >>> http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/104713 >>> >>> I've poked remko@ in this email to ask him the status about the >>> MFC. He said he didn't want me to do the MFC, so it's on his plate. >>> >>> I saw at >>> http://www.freebsd.org/cgi/cvsweb.cgi/src/share/zoneinfo/australasia that >>> the 2007f is also not MFCed. >>> >>> Edwin >>> >> Indeed, I want to do my own MFC's, the implementation in -current >> is different for older branches because the new logic is not in >> place for older versions. That said with or without the >> NO/WITHOUT_ZONEINFO stuff in the tree, you can update the zoneinfo part >> so do not point at me for that. > > It might be different between -current and the older branches, but > it fits in with the code used in the patch given by Mark which you > had to modify two months ago to fit in with the new logic. > > Edwin Not everyone is as great as you Edwin, sorry there are lesser people around in the world. I would prefer it if you stop behaving like this (You did that recently in another group, in private and now on public lists). It does not suit you being this kind of person, perhaps you can have a walk on the outside or something. If you do and you see the more subtle and kind Edwin, please ask him to take place at the helm. Thanks. -- Remko Lodder ** remko@elvandar.org FreeBSD ** remko@FreeBSD.org /* Quis custodiet ipsos custodes */ From owner-freebsd-stable@FreeBSD.ORG Wed Aug 22 14:19:28 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7F26816A418 for ; Wed, 22 Aug 2007 14:19:28 +0000 (UTC) (envelope-from moruku@gmail.com) Received: from fk-out-0910.google.com (fk-out-0910.google.com [209.85.128.191]) by mx1.freebsd.org (Postfix) with ESMTP id DE5BF13C483 for ; Wed, 22 Aug 2007 14:19:27 +0000 (UTC) (envelope-from moruku@gmail.com) Received: by fk-out-0910.google.com with SMTP id b27so190537fka for ; Wed, 22 Aug 2007 07:19:26 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ngKCXfz9pEk12WDbR/brubA2+k2nX2zi05KP01SsOdj07lPNXenIHalZIyGY2R095oKKZGCjZeDusbkVRjy6D2PhdC9ZKWlGKOtJwIoh2Lf3mn+1EdzQObvoIv/pRxueSJU2dllY7ZKpWL7Qy7wWtIAA0hXJ72GCBejcs/bDLVU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Msr1/vY2mr24NEOpKVVV+1GWhCGV1mwUJjlXoLE3NBxrAwb8K2S2HyoQDq8a0BmA5s0+LWri1kfubY/kadzOjSL1U+6PkoHcyrd5acyAnqgeSejIDrmLCvch7OguAQ8+06SGpl4jxNF6uEie46PxiMFfDu2Za0gDtdzHxYeisxE= Received: by 10.82.151.14 with SMTP id y14mr1545645bud.1187790870451; Wed, 22 Aug 2007 06:54:30 -0700 (PDT) Received: by 10.82.159.2 with HTTP; Wed, 22 Aug 2007 06:54:30 -0700 (PDT) Message-ID: <94e0cac00708220654j6a7f7ab0mf084b982963de7be@mail.gmail.com> Date: Wed, 22 Aug 2007 15:54:30 +0200 From: "Marcus Kaatari" To: freebsd-stable@freebsd.org In-Reply-To: <20070822071827.5C4B713C4B0@mx1.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070822071827.5C4B713C4B0@mx1.freebsd.org> Subject: Re: Undelivered Mail Returned to Sender X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: moruku@moruku.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Aug 2007 14:19:28 -0000 Any clue when the first beta might be available? -- email: moruku@moruku.org website: moruku.org () ascii ribbon campaign - against html mail /\ - against microsoft attachments From owner-freebsd-stable@FreeBSD.ORG Wed Aug 22 17:23:34 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DA3FE16A417 for ; Wed, 22 Aug 2007 17:23:34 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.191]) by mx1.freebsd.org (Postfix) with ESMTP id 4230713C4B4 for ; Wed, 22 Aug 2007 17:23:33 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so208797nfb for ; Wed, 22 Aug 2007 10:23:32 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:received:received:date:from:to:cc:subject:message-id:mail-followup-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=jZNxhN81YM9LSsSSES/lV9XS47K0eoQL7csyTY5P6pRCthqg2dHaJIRnPMJurAs1IT1ITyW6lzZCSnnST50Ft9FQUBxMsNmtI0i91l86frYv+2q90D9MemJxNgXSwXEzHCIA3c/wOFesWqithh5Vum3W1PI6oSoi19PiJxDJzB4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:date:from:to:cc:subject:message-id:mail-followup-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=flMLVzAbg/5gelrlvZP0Wfktojxf+7AV+kknvMB84bGPJHqMOUCj92oKjl2X/KSrMPAJR2xDEgQHExNKeKANSzWcULwKvuhDSAvRDUF4Z9H8ZbCL0KDq/Bll4wVUt6itAmILiZD2KeU/jcGub85k4dJHlR2qn/7fdbx5sntqpv8= Received: by 10.86.77.5 with SMTP id z5mr665774fga.1187803412055; Wed, 22 Aug 2007 10:23:32 -0700 (PDT) Received: from roadrunner.spoerlein.net ( [85.180.142.240]) by mx.google.com with ESMTPS id j12sm1714169fkf.2007.08.22.10.23.30 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 22 Aug 2007 10:23:31 -0700 (PDT) Received: from roadrunner.spoerlein.net (localhost [127.0.0.1]) by roadrunner.spoerlein.net (8.14.1/8.14.1) with ESMTP id l7MHMDur002509; Wed, 22 Aug 2007 19:22:13 +0200 (CEST) (envelope-from uspoerlein@gmail.com) Received: (from q@localhost) by roadrunner.spoerlein.net (8.14.1/8.14.1/Submit) id l7MHMCUf002508; Wed, 22 Aug 2007 19:22:12 +0200 (CEST) (envelope-from uspoerlein@gmail.com) Date: Wed, 22 Aug 2007 19:22:12 +0200 From: Ulrich Spoerlein To: "Patrick M. Hausen" Message-ID: <20070822172212.GB1426@roadrunner.spoerlein.net> Mail-Followup-To: "Patrick M. Hausen" , Chuck Swiger , Richard Foulkes , freebsd-stable@freebsd.org References: <20070821195043.GA1464@roadrunner.spoerlein.net> <64A1102C-0697-4C4D-AF3B-B1F2ED224792@yahoo.co.uk> <1D83A750-03FD-49EF-B99D-BA9B7F7E7BD0@mac.com> <7ad7ddd90708220053k147f4c5cq87430a4ee897180d@mail.gmail.com> <20070822082840.GB74165@hugo10.ka.punkt.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070822082840.GB74165@hugo10.ka.punkt.de> User-Agent: Mutt/1.5.15 (2007-04-06) Cc: freebsd-stable@freebsd.org, Richard Foulkes Subject: Re: pam_group vs. multiple group lines X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Aug 2007 17:23:34 -0000 On Wed, 22.08.2007 at 10:28:40 +0200, Patrick M. Hausen wrote: > On Wed, Aug 22, 2007 at 09:53:42AM +0200, Ulrich Spoerlein wrote: > > On 8/22/07, Chuck Swiger wrote: > > > On Aug 21, 2007, at 2:02 PM, Richard Foulkes wrote: > > > > Ok, so how are you supposed to control membership of the wheel > > > > group via ldap? Ok, you COULD remove the local wheel entry in /etc/ > > > > group, but this would probably be a bad idea if the ldap server > > > > were unavailable. > > > > > > You've aptly summarized my thoughts on the matter-- I would not rely > > > on LDAP to provide information about root or the wheel group. > > > > That is exactly the gist of my question. Of course I know that a group > > oneliner is the way to go. However, I saw people suggest splitting > > groups into multiple lines, if the lines are too long or too many > > groups per line (something to do with the /etc/group parser, I guess). > > > > Anyway, I want the LDAP groups to *augment* system groups. Removing > > wheel from /etc/group and relying on a complex network service .... > > not funny. > > We do not use LDAP yet, but have been using NIS in our internal > office network for years. If you use the magic "+" token to merge > your NIS database with the static files for passwd and group > information, then I'm not using the compat setting, my nsswitch.conf contains passwd: files ldap group: files ldap > _if_ the group entry in the static file does not contain any users > _then_ the information from NIS is merged in > > So you can keep a "wheel" group around as the _primary_ group > for root, toor, whatnot ... and all the additional members > that have "wheel" as an auxiliary group come from NIS. > > Possibly this works for LDAP, too? IMHO at least it should ;-)) THANK YOU! It is indeed working for LDAP too. But it fails for sudo(8). Luckily I could replace the %wheel directive with a few user id directives. It's still a shortcoming of some sort and I guess I'll file a PR if noone else has any more information on the issue. getent group now has the following wheel entries % getent group|grep wheel wheel:*:0 wheel:*:0:us,root As I said, su(1) is happy, sudo(8) not yet. Cheers, Ulrich Spoerlein -- It is better to remain silent and be thought a fool, than to speak, and remove all doubt. From owner-freebsd-stable@FreeBSD.ORG Wed Aug 22 18:47:46 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DD54D16A41B for ; Wed, 22 Aug 2007 18:47:45 +0000 (UTC) (envelope-from swhetzel@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.189]) by mx1.freebsd.org (Postfix) with ESMTP id 4854B13C483 for ; Wed, 22 Aug 2007 18:47:45 +0000 (UTC) (envelope-from swhetzel@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so230193nfb for ; Wed, 22 Aug 2007 11:47:43 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=eCAYUATDgFlAe7Dmxo9pZiGQNRuaQvWU+m2O2Vdb9AtgZF6FTqD/9pu3+YqtpF6qFRQGvlfxacZbVjsk5dA6tl2kE+EcMn1uK6lMeIY7JQTvOtpcqB2BiUXcvkFhLwRR4ZDya7Ca0Gq2pG44pZul0JOm4Py1YZ4aA49Vd1hwCb0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=chpHlOCT8DEzv8jU1Y7bU4FhOh8yqxH6pvI1UagIqDvWEFMvd3VGsjDXwN+tAcSl6AsldRveSXnA+52ZVOURb3tqrNPZwVvk2QPD/jUiICReylvoXNHeNHEhWU0U9GvNeUXRDE+2Zj43cIBzikpsinJT20wAYPdcuWDZ8nbpTHY= Received: by 10.86.57.9 with SMTP id f9mr699811fga.1187808463504; Wed, 22 Aug 2007 11:47:43 -0700 (PDT) Received: by 10.86.59.6 with HTTP; Wed, 22 Aug 2007 11:47:43 -0700 (PDT) Message-ID: <790a9fff0708221147u40104228k5ff7e08180dd5b41@mail.gmail.com> Date: Wed, 22 Aug 2007 13:47:43 -0500 From: "Scot Hetzel" To: "Ulrich Spoerlein" In-Reply-To: <20070822172212.GB1426@roadrunner.spoerlein.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070821195043.GA1464@roadrunner.spoerlein.net> <64A1102C-0697-4C4D-AF3B-B1F2ED224792@yahoo.co.uk> <1D83A750-03FD-49EF-B99D-BA9B7F7E7BD0@mac.com> <7ad7ddd90708220053k147f4c5cq87430a4ee897180d@mail.gmail.com> <20070822082840.GB74165@hugo10.ka.punkt.de> <20070822172212.GB1426@roadrunner.spoerlein.net> Cc: freebsd-stable@freebsd.org Subject: Re: pam_group vs. multiple group lines X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Aug 2007 18:47:46 -0000 On 8/22/07, Ulrich Spoerlein wrote: > On Wed, 22.08.2007 at 10:28:40 +0200, Patrick M. Hausen wrote: > > On Wed, Aug 22, 2007 at 09:53:42AM +0200, Ulrich Spoerlein wrote: > > > That is exactly the gist of my question. Of course I know that a group > > > oneliner is the way to go. However, I saw people suggest splitting > > > groups into multiple lines, if the lines are too long or too many > > > groups per line (something to do with the /etc/group parser, I guess). > > > > > > Anyway, I want the LDAP groups to *augment* system groups. Removing > > > wheel from /etc/group and relying on a complex network service .... > > > not funny. > > > > We do not use LDAP yet, but have been using NIS in our internal > > office network for years. If you use the magic "+" token to merge > > your NIS database with the static files for passwd and group > > information, then > > I'm not using the compat setting, my nsswitch.conf contains > > passwd: files ldap > group: files ldap > > > _if_ the group entry in the static file does not contain any users > > _then_ the information from NIS is merged in > > > > So you can keep a "wheel" group around as the _primary_ group > > for root, toor, whatnot ... and all the additional members > > that have "wheel" as an auxiliary group come from NIS. > > > > Possibly this works for LDAP, too? IMHO at least it should ;-)) > > THANK YOU! It is indeed working for LDAP too. But it fails for sudo(8). > Luckily I could replace the %wheel directive with a few user id > directives. > > It's still a shortcoming of some sort and I guess I'll file a PR if > noone else has any more information on the issue. > > getent group now has the following wheel entries > % getent group|grep wheel > wheel:*:0 > wheel:*:0:us,root > > As I said, su(1) is happy, sudo(8) not yet. > Does the following work for you: passwd: ldap [notfound=return] files group: ldap [notfound=return] files This sets ldap as the authoritative source for users and groups, unless the ldap service is down, then it will use the files for the source (useful when ldap server is down). This will require that you place all of the users/groups into the ldap server. (modified from the nis example in the nsswitch.conf(5) man page) You could also try the following: passwd: ldap files group: ldap [success=continue] files Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. From owner-freebsd-stable@FreeBSD.ORG Wed Aug 22 20:00:14 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 582CB16A469 for ; Wed, 22 Aug 2007 20:00:14 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.189]) by mx1.freebsd.org (Postfix) with ESMTP id C0F3613C4A8 for ; Wed, 22 Aug 2007 20:00:13 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so247238nfb for ; Wed, 22 Aug 2007 13:00:12 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:received:received:date:from:to:cc:subject:message-id:mail-followup-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=Ppq/GyotlvQeYbfm75ZICnW1zwY7rv3qIuhM71w8ltTgiXXGRTcQFjZDQx5/msdDYz4AEjX735+PIOWUEg/MmlmHJTOEaCrlr7iDVNdoF04wlFLOj96xd6LehOebS8O+42avpQKJBdTr+eYF/98oxO/igW11K0C3AhIqYNZ3m6Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:date:from:to:cc:subject:message-id:mail-followup-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=qWRorLGYbvAsGmzM00v1jZJZjVYUF2cEgt4QHgo3VPC6fL2AVCktDBHQiP106raBUaVEKZlTorlbLXcLHT9+xMtdAe/L3snb9vsSVsxCQEXugKNbzjpk3M90ppFSqEN8WFOgNbpTcTHRxZfblt3TIN+TTNbYhdFh8L5igHsxWHM= Received: by 10.86.79.19 with SMTP id c19mr747885fgb.1187812812124; Wed, 22 Aug 2007 13:00:12 -0700 (PDT) Received: from roadrunner.spoerlein.net ( [85.180.142.240]) by mx.google.com with ESMTPS id 22sm2004522fkr.2007.08.22.13.00.11 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 22 Aug 2007 13:00:11 -0700 (PDT) Received: from roadrunner.spoerlein.net (localhost [127.0.0.1]) by roadrunner.spoerlein.net (8.14.1/8.14.1) with ESMTP id l7MK05Bq004208; Wed, 22 Aug 2007 22:00:05 +0200 (CEST) (envelope-from uspoerlein@gmail.com) Received: (from q@localhost) by roadrunner.spoerlein.net (8.14.1/8.14.1/Submit) id l7MK05mk004207; Wed, 22 Aug 2007 22:00:05 +0200 (CEST) (envelope-from uspoerlein@gmail.com) Date: Wed, 22 Aug 2007 22:00:05 +0200 From: Ulrich Spoerlein To: Scot Hetzel Message-ID: <20070822200005.GC1426@roadrunner.spoerlein.net> Mail-Followup-To: Scot Hetzel , freebsd-stable@freebsd.org References: <20070821195043.GA1464@roadrunner.spoerlein.net> <64A1102C-0697-4C4D-AF3B-B1F2ED224792@yahoo.co.uk> <1D83A750-03FD-49EF-B99D-BA9B7F7E7BD0@mac.com> <7ad7ddd90708220053k147f4c5cq87430a4ee897180d@mail.gmail.com> <20070822082840.GB74165@hugo10.ka.punkt.de> <20070822172212.GB1426@roadrunner.spoerlein.net> <790a9fff0708221147u40104228k5ff7e08180dd5b41@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <790a9fff0708221147u40104228k5ff7e08180dd5b41@mail.gmail.com> User-Agent: Mutt/1.5.15 (2007-04-06) Cc: freebsd-stable@freebsd.org Subject: Re: pam_group vs. multiple group lines X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Aug 2007 20:00:14 -0000 On Wed, 22.08.2007 at 13:47:43 -0500, Scot Hetzel wrote: > Does the following work for you: > > passwd: ldap [notfound=return] files > group: ldap [notfound=return] files > > This sets ldap as the authoritative source for users and groups, > unless the ldap service is down, then it will use the files for the > source (useful when ldap server is down). This will require that you > place all of the users/groups into the ldap server. (modified from the > nis example in the nsswitch.conf(5) man page) Thanks for you suggestion! In the end, I did it the other way round, using: passwd: files ldap group: files [success=continue] ldap This has the effect of "merging" the multiple group sources into one, as can be seen here % getent group|grep wheel wheel:*:0:root,us I now have to play a little bit with bootup (no LDAP present) and what happens when LDAP goes offline, etc. Thanks again! Cheers, Ulrich Spoerlein -- It is better to remain silent and be thought a fool, than to speak, and remove all doubt. From owner-freebsd-stable@FreeBSD.ORG Thu Aug 23 03:18:25 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B392716A41A for ; Thu, 23 Aug 2007 03:18:25 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from gaia.nimnet.asn.au (nimbin.lnk.telstra.net [139.130.45.143]) by mx1.freebsd.org (Postfix) with ESMTP id 1B74713C45B for ; Thu, 23 Aug 2007 03:18:23 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from localhost (smithi@localhost) by gaia.nimnet.asn.au (8.8.8/8.8.8R1.5) with SMTP id NAA28554; Thu, 23 Aug 2007 13:17:57 +1000 (EST) (envelope-from smithi@nimnet.asn.au) Date: Thu, 23 Aug 2007 13:17:56 +1000 (EST) From: Ian Smith To: JoaoBR In-Reply-To: <200708220724.25330.joao@matik.com.br> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-acpi@freebsd.org, freebsd-stable@freebsd.org Subject: Re: powerd freeze with amd 5000 X2 but not with lower cpus X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Aug 2007 03:18:25 -0000 On Wed, 22 Aug 2007, JoaoBR wrote: > On Monday 06 August 2007 09:28:35 JoaoBR wrote: > ..... > > > > I had a chance to test several MBs with the same 6000+, 5000+ and 4600+ cpu > > > > At the end seems that the problem is mb/hardware related since some > > combinations hung even with latest BIOS installed and others not. > > > > not sure if somebody still wants to hear about this but it is kind of > interesting I guess [.. leaving out your video / xorg / DPMS stuff without comment ..] > one thing more I did which caused a sysctl error on boot. There is a funny > line in /etc/rc.s/power_profile as 'highest_value="C1"' which I commented out > but I guess that has nothing to do since the setting was not accepted Call me curious, but (assuming that you're tuning for performance, not economy, and so will always run these boxes on AC power, not battery): a) why you think that line in /etc/rc.d/power_profile is 'funny'? b) what value for performance_cx_lowest you would consider more appropriate to use than C1, and why? c) whether you have overridden the /etc/defaults/rc.conf values for {performance,economy}_cx_lowest or {performance,economy}_cpu_freq ? Cheers, Ian From owner-freebsd-stable@FreeBSD.ORG Thu Aug 23 12:10:57 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6456C16A418; Thu, 23 Aug 2007 12:10:57 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from msrv.matik.com.br (msrv.matik.com.br [200.152.83.14]) by mx1.freebsd.org (Postfix) with ESMTP id DFC5D13C442; Thu, 23 Aug 2007 12:10:56 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from anb.matik.com.br (anb.matik.com.br [200.152.83.34]) by msrv.matik.com.br (8.14.1/8.13.1) with ESMTP id l7NCAs60014317; Thu, 23 Aug 2007 09:10:55 -0300 (BRT) (envelope-from joao@matik.com.br) From: JoaoBR Organization: Infomatik To: freebsd-stable@freebsd.org Date: Thu, 23 Aug 2007 09:10:51 -0300 User-Agent: KMail/1.9.7 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200708230910.52163.joao@matik.com.br> X-Virus-Scanned: ClamAV version 0.90.3, clamav-milter version 0.90.3 on msrv.matik.com.br X-Virus-Status: Clean Cc: freebsd-acpi@freebsd.org, Ian Smith Subject: Re: powerd freeze with amd 5000 X2 but not with lower cpus X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Aug 2007 12:10:57 -0000 On Thursday 23 August 2007 00:17:56 Ian Smith wrote: > > Call me curious, but (assuming that you're tuning for performance, not > economy, and so will always run these boxes on AC power, not battery): > > a) why you think that line in /etc/rc.d/power_profile is 'funny'? > well, in first place because it gave an error, I haven't looked deeper at t= hat=20 moment because I was after something else so now I did because of your question and it seems the power_profile script= =20 has a bug I tries to set hw.acpi.cpu.cx_lowest=3DC1 but I guess it should be dev.cpu.0.cx_lowest > b) what value for performance_cx_lowest you would consider more > appropriate to use than C1, and why? > I didn't said that, My comment was not regarding the value but the error pe= r=20 se > c) whether you have overridden the /etc/defaults/rc.conf values for > {performance,economy}_cx_lowest or {performance,economy}_cpu_freq ? > no =2D-=20 Jo=E3o A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br From owner-freebsd-stable@FreeBSD.ORG Thu Aug 23 15:51:12 2007 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 29F1716A417 for ; Thu, 23 Aug 2007 15:51:12 +0000 (UTC) (envelope-from freebsd@chillt.de) Received: from dd15624.kasserver.com (dd15624.kasserver.com [85.13.136.215]) by mx1.freebsd.org (Postfix) with ESMTP id B607513C480 for ; Thu, 23 Aug 2007 15:51:11 +0000 (UTC) (envelope-from freebsd@chillt.de) Received: from hundertwasser.cs.tcd.ie (dslb-084-060-112-077.pools.arcor-ip.net [84.60.112.77]) by dd15624.kasserver.com (Postfix) with ESMTP id E0F5B182EF9C3 for ; Thu, 23 Aug 2007 17:23:03 +0200 (CEST) Message-ID: <46CDA657.9080201@chillt.de> Date: Thu, 23 Aug 2007 16:23:03 +0100 From: Bartosz Fabianowski User-Agent: Thunderbird 2.0.0.6 (X11/20070810) MIME-Version: 1.0 To: stable@freebsd.org Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Panic and reboot with USB hard disk X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Aug 2007 15:51:12 -0000 Hi list A 2.5" USB hard disk I recently got has been giving me a lot of trouble. When using the disk, I routinely get panics or random data corruption. This happens with two separate machines, both running 6-STABLE. I found that one file residing on the disk, when read, always makes the kernel panic. While I know this smells of a hardware error (bad sector, reads failing), the disk repeatedly passed badblocks' tests, both read-only and read-write, with no errors. I am therefore thinking that this may have something to do with FreeBSD's USB stack. A kernel with no debugger simply reboots when it encounters the error, without producing a crash dump. When KDB and DDB are compiled in, I end up in the debugger prompt where "trace" points to a routine apparently handling USB interrupts. Unfortunately, I have to run "call doadump" to get a crash dump, after which kgdb seems to show backtraces of the doadump call, not of the original error. I would really appreciate any help in debugging this problem. I have debug kernels on both machines, have a working test case and am happy to run any debugger commands required. The output of a kgdb backtrace is attached, although I fear it's not of much use. As a final note, the disk is 160GB in size, has a single UFS partition and is GELI encrypted. panic: vm_fault: fault on nofault entry, addr: db4f9000 KDB: enter: panic panic: from debugger Uptime: 30s kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode fault virtual address = 0xdb4f9000 fault code = supervisor write, page not present instruction pointer = 0x20:0xc06d7580 stack pointer = 0x28:0xde342464 frame pointer = 0x28:0xde342498 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = resume, IOPL = 0 current process = 21 (irq11: cbb0 bfe0+*) Dumping 767 MB (2 chunks) chunk 0: 1MB (159 pages) ... ok chunk 1: 767MB (196270 pages) 751 735 719 703 687 671 655 639 623 607 591 575 559 543 527 511 495 479 463 447 431 415 399 383 367 351 335 319 303 287 271 255 239 223 207 191 175 159 143 127 111 95 79 63 47 31 15 #0 doadump () at pcpu.h:165 165 __asm __volatile("movl %%fs:0,%0" : "=r" (td)); (kgdb) bt #0 doadump () at pcpu.h:165 #1 0xc044d196 in db_fncall (dummy1=0, dummy2=0, dummy3=1999, dummy4=0xde342294 "") at /usr/src/sys/ddb/db_command.c:492 #2 0xc044cf12 in db_command (last_cmdp=0xc07761a4, cmd_table=0x0, aux_cmd_tablep=0xc07367e0, aux_cmd_tablep_end=0xc07367e4) at /usr/src/sys/ddb/db_command.c:350 #3 0xc044d025 in db_command_loop () at /usr/src/sys/ddb/db_command.c:458 #4 0xc044f265 in db_trap (type=12, code=0) at /usr/src/sys/ddb/db_main.c:222 #5 0xc0575f07 in kdb_trap (type=0, code=0, tf=0xde342424) at /usr/src/sys/kern/subr_kdb.c:473 #6 0xc06d98db in trap_fatal (frame=0xde342424, eva=0) at /usr/src/sys/i386/i386/trap.c:829 #7 0xc06d8ef4 in trap (frame= {tf_fs = -567017464, tf_es = -1066532824, tf_ds = -567017432, tf_edi = -615542784, tf_esi = -402886656, tf_ebp = -567008104, tf_isp = -567008176, tf_ebx = -1001486592, tf_edx = 0, tf_ecx = 1024, tf_eax = -615563264, tf_trapno = 12, tf_err = 2, tf_eip = -1066568320, tf_cs = 32, tf_eflags = 589830, tf_esp = -1001501696, tf_ss = 0}) at /usr/src/sys/i386/i386/trap.c:270 #8 0xc06c376a in calltrap () at /usr/src/sys/i386/i386/exception.s:139 #9 0xc06d7580 in memcpy () at /usr/src/sys/i386/i386/support.s:681 Previous frame inner to this frame (corrupt stack?) From owner-freebsd-stable@FreeBSD.ORG Thu Aug 23 16:56:42 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E9FB016A46B for ; Thu, 23 Aug 2007 16:56:42 +0000 (UTC) (envelope-from mike@jellydonut.org) Received: from mail2.secureworks.net (mail2.secureworks.net [65.114.32.154]) by mx1.freebsd.org (Postfix) with ESMTP id C1FD213C461 for ; Thu, 23 Aug 2007 16:56:40 +0000 (UTC) (envelope-from mike@jellydonut.org) Received: from localhost (localhost [127.0.0.1]) by mail2.secureworks.net (Postfix) with ESMTP id C3F5F170DA for ; Thu, 23 Aug 2007 12:56:39 -0400 (EDT) X-Virus-Scanned: amavisd-new at secureworks.net Received: from mail2.secureworks.net ([127.0.0.1]) by localhost (mail2.secureworks.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 73V-sTFO6-zg for ; Thu, 23 Aug 2007 12:56:39 -0400 (EDT) Received: from descartes.internal.secureworks.net (mole1.secureworks.net [63.239.86.3]) by mail2.secureworks.net (Postfix) with ESMTP id 50AA5170C9 for ; Thu, 23 Aug 2007 12:56:39 -0400 (EDT) Message-ID: <46CDBC47.8060507@jellydonut.org> Date: Thu, 23 Aug 2007 12:56:39 -0400 From: Michael Proto User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.6) Gecko/20070806 Thunderbird/2.0.0.6 Mnenhy/0.7.5.666 MIME-Version: 1.0 To: FreeBSD stable References: <46C488EC.5090609@jellydonut.org> In-Reply-To: <46C488EC.5090609@jellydonut.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: update from RELEASE to STABLE changed /dev/ad or geom behavior? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Aug 2007 16:56:43 -0000 Michael Proto wrote: > Hello all, > > To fix a bug in PF I recently updated my home firewall platform (a > shrunk-down install of FreeBSD 6 on a CompactFlash card mounted > read-only as /dev/ad0a) from the RELENG_6_2 to the RELENG_6 branch. All > went very well there and the PF problem is resolved, but now I've run > across a new issue. > > Previously, when updating my CompactFlash image "in the field", I would > boot the system into single-user mode via serial console, setup a small > memory filesystem big enough to hold gzip, dd, and reboot (and their > required libraries, with LD_LIBRARY_FLAGS set appropriately), copy the > new flash image to the mfs, and run (from the MFS) "gzip -dc | dd of=/dev/ad0 bs=8k" and then run "reboot -lnq" to reboot into the > new image. > > This all worked well and good until the update to RELENG_6, and now I > see the following when I try to dd the new image: > > # sysctl kern.geom.debugflags=16 > kern.geom.debugflags: 0 -> 16 > > # gzip -dc dd: /dev/ad0: Invalid argument > 298+1 records in > 298+0 records out > 1220608 bytes transferred in 1.330433 secs (917452 bytes/sec) > > > With the above kern.geom.debugflags sysctl, I thought I would have the > ability to directly write to /dev/ad0 via dd, and this was the case with > RELENG_6_2. Is this no longer the case? Didn't see anything in > /usr/src/UPDATING to indicate any sort of change, and I'm not sure where > in the RELENG_6 code this would exist (GEOM perhaps)? > > Anyone have any ideas or suggestions as to why this doesn't work anymore? > I found a solution to this problem that I'd like to share with the list. Here's my problem: # gzip -dc Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DE76816A419; Thu, 23 Aug 2007 17:38:15 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from gaia.nimnet.asn.au (nimbin.lnk.telstra.net [139.130.45.143]) by mx1.freebsd.org (Postfix) with ESMTP id 2F38613C468; Thu, 23 Aug 2007 17:38:13 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from localhost (smithi@localhost) by gaia.nimnet.asn.au (8.8.8/8.8.8R1.5) with SMTP id DAA22954; Fri, 24 Aug 2007 03:37:58 +1000 (EST) (envelope-from smithi@nimnet.asn.au) Date: Fri, 24 Aug 2007 03:37:57 +1000 (EST) From: Ian Smith To: JoaoBR In-Reply-To: <200708230910.52163.joao@matik.com.br> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-acpi@freebsd.org, freebsd-stable@freebsd.org Subject: Re: powerd freeze with amd 5000 X2 but not with lower cpus X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Aug 2007 17:38:16 -0000 On Thu, 23 Aug 2007, JoaoBR wrote: > On Thursday 23 August 2007 00:17:56 Ian Smith wrote: > > > > > Call me curious, but (assuming that you're tuning for performance, not > > economy, and so will always run these boxes on AC power, not battery): > > > > a) why you think that line in /etc/rc.d/power_profile is 'funny'? > > > > well, in first place because it gave an error, I haven't looked deeper at that > moment because I was after something else > > so now I did because of your question and it seems the power_profile script > has a bug > > I tries to set hw.acpi.cpu.cx_lowest=C1 > > but I guess it should be dev.cpu.0.cx_lowest Ah, ok. Updated in HEAD but not STABLE: http://www.freebsd.org/cgi/cvsweb.cgi/src/etc/rc.d/power_profile.diff?r1=text&tr1=1.7&r2=text&tr2=1.11 But http://www.freebsd.org/cgi/cvsweb.cgi/src/etc/rc.d/power_profile indicates that hw.acpi.cpu.cx_lowest should still work anyway, to set all cpus the same? What is the error message you're getting? Cheers, Ian From owner-freebsd-stable@FreeBSD.ORG Thu Aug 23 21:05:34 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C7EB516A41A; Thu, 23 Aug 2007 21:05:34 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from msrv.matik.com.br (msrv.matik.com.br [200.152.83.14]) by mx1.freebsd.org (Postfix) with ESMTP id 4E46C13C45E; Thu, 23 Aug 2007 21:05:34 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from ap-h.matik.com.br (ap-h.matik.com.br [200.152.83.36]) by msrv.matik.com.br (8.14.1/8.13.1) with ESMTP id l7NL5ZRO069252; Thu, 23 Aug 2007 18:05:36 -0300 (BRT) (envelope-from joao@matik.com.br) From: JoaoBR Organization: Infomatik To: freebsd-stable@freebsd.org Date: Thu, 23 Aug 2007 18:09:49 -0300 User-Agent: KMail/1.9.7 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200708231809.50623.joao@matik.com.br> X-Virus-Scanned: ClamAV version 0.90.3, clamav-milter version 0.90.3 on msrv.matik.com.br X-Virus-Status: Clean Cc: freebsd-acpi@freebsd.org, Ian Smith Subject: Re: powerd freeze with amd 5000 X2 but not with lower cpus X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Aug 2007 21:05:34 -0000 On Thursday 23 August 2007 14:37:57 Ian Smith wrote: > On Thu, 23 Aug 2007, JoaoBR wrote: > > On Thursday 23 August 2007 00:17:56 Ian Smith wrote: > > > Call me curious, but (assuming that you're tuning for performance, n= ot > > > economy, and so will always run these boxes on AC power, not battery= ): > > > > > > a) why you think that line in /etc/rc.d/power_profile is 'funny'? > > > > well, in first place because it gave an error, I haven't looked deeper > > at that moment because I was after something else > > > > so now I did because of your question and it seems the power_profile > > script has a bug > > > > I tries to set hw.acpi.cpu.cx_lowest=3DC1 > > > > but I guess it should be dev.cpu.0.cx_lowest > > Ah, ok. Updated in HEAD but not STABLE: > http://www.freebsd.org/cgi/cvsweb.cgi/src/etc/rc.d/power_profile.diff?r1= =3Dte >xt&tr1=3D1.7&r2=3Dtext&tr2=3D1.11 > > But http://www.freebsd.org/cgi/cvsweb.cgi/src/etc/rc.d/power_profile > indicates that hw.acpi.cpu.cx_lowest should still work anyway, to set > all cpus the same? What is the error message you're getting? > no it not working # sysctl hw.acpi.cpu.cx_lowest=3DC1 hw.acpi.cpu.cx_lowest: C1 sysctl: hw.acpi.cpu.cx_lowest: Invalid argument =2D-=20 Jo=E3o A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br From owner-freebsd-stable@FreeBSD.ORG Fri Aug 24 01:29:18 2007 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4EE7416A417 for ; Fri, 24 Aug 2007 01:29:18 +0000 (UTC) (envelope-from freebsd@chillt.de) Received: from dd15624.kasserver.com (dd15624.kasserver.com [85.13.136.215]) by mx1.freebsd.org (Postfix) with ESMTP id 123FD13C457 for ; Fri, 24 Aug 2007 01:29:17 +0000 (UTC) (envelope-from freebsd@chillt.de) Received: from takahe.local (84-203-32-212.mysmart.ie [84.203.32.212]) by dd15624.kasserver.com (Postfix) with ESMTP id 912B11830AD10 for ; Fri, 24 Aug 2007 03:29:15 +0200 (CEST) Message-ID: <46CE346A.1020301@chillt.de> Date: Fri, 24 Aug 2007 02:29:14 +0100 From: Bartosz Fabianowski User-Agent: Thunderbird 2.0.0.6 (X11/20070811) MIME-Version: 1.0 To: stable@freebsd.org References: <46CDA657.9080201@chillt.de> In-Reply-To: <46CDA657.9080201@chillt.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: Panic and reboot with USB hard disk X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Aug 2007 01:29:18 -0000 With the help of some folks in #freebsd on freenode, I have since been able to fix this problem. Here is the solution for future reference: There is a bug in GELI that makes it corrupt data and panic kernels when certain non-standard settings are used. I had set the GELI sector size to 8192 and the AES key length to 256. After reinitializing GELI with sector size 4096 and AES key length 128, the problems have vanished. Even under extreme I/O load to the drive, the kernel does not panic and no data corruptions occur. From owner-freebsd-stable@FreeBSD.ORG Fri Aug 24 02:23:15 2007 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CC29E16A418 for ; Fri, 24 Aug 2007 02:23:15 +0000 (UTC) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.org (trang.nuxi.org [74.95.12.85]) by mx1.freebsd.org (Postfix) with ESMTP id 7C06113C45A for ; Fri, 24 Aug 2007 02:23:15 +0000 (UTC) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.org (obrien@localhost [127.0.0.1]) by dragon.nuxi.org (8.14.1/8.14.1) with ESMTP id l7O1xvJ6017675 for ; Thu, 23 Aug 2007 19:00:02 -0700 (PDT) (envelope-from obrien@dragon.nuxi.org) Received: (from obrien@localhost) by dragon.nuxi.org (8.14.1/8.14.1/Submit) id l7O1xv9Y017674 for stable@freebsd.org; Thu, 23 Aug 2007 18:59:57 -0700 (PDT) (envelope-from obrien) Date: Thu, 23 Aug 2007 18:59:57 -0700 From: "David O'Brien" To: stable@freebsd.org Message-ID: <20070824015956.GA17604@dragon.NUXI.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: FreeBSD 7.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 User-Agent: Mutt/1.5.11 Cc: Subject: MFC 7.0 calcru changes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: obrien@freebsd.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Aug 2007 02:23:15 -0000 This is a patch to MFC what I think are all the calcru-related changes that occurred since 6-STABLE was branched and 7.0 continued forward. If anyone spots some changes I missed, please yell out. -- -- David (obrien@FreeBSD.org) Index: amd64/amd64/mp_machdep.c =================================================================== RCS file: /home/ncvs/src/sys/amd64/amd64/mp_machdep.c,v retrieving revision 1.260.2.11 diff -u -p -r1.260.2.11 mp_machdep.c --- amd64/amd64/mp_machdep.c 5 May 2007 21:13:16 -0000 1.260.2.11 +++ amd64/amd64/mp_machdep.c 23 Aug 2007 18:05:54 -0000 @@ -577,7 +577,7 @@ init_secondary(void) spinlock_exit(); KASSERT(curthread->td_md.md_spinlock_count == 1, ("invalid count")); - binuptime(PCPU_PTR(switchtime)); + PCPU_SET(switchtime, cpu_ticks()); PCPU_SET(switchticks, ticks); cpu_throw(NULL, choosethread()); /* doesn't return */ Index: amd64/amd64/trap.c =================================================================== RCS file: /home/ncvs/src/sys/amd64/amd64/trap.c,v retrieving revision 1.289.2.6 diff -u -p -r1.289.2.6 trap.c --- amd64/amd64/trap.c 14 Aug 2007 19:42:51 -0000 1.289.2.6 +++ amd64/amd64/trap.c 23 Aug 2007 20:28:33 -0000 @@ -162,7 +162,7 @@ trap(frame) { struct thread *td = curthread; struct proc *p = td->td_proc; - u_int sticks = 0, type; + u_int type; int i = 0, ucode = 0, code; PCPU_LAZY_INC(cnt.v_trap); @@ -242,7 +242,7 @@ trap(frame) if (ISPL(frame.tf_cs) == SEL_UPL) { /* user trap */ - sticks = td->td_sticks; + td->td_pticks = 0; td->td_frame = &frame; if (td->td_ucred != p->p_ucred) cred_update_thread(td); @@ -488,7 +488,7 @@ trap(frame) #endif user: - userret(td, &frame, sticks); + userret(td, &frame); mtx_assert(&Giant, MA_NOTOWNED); userout: out: @@ -703,7 +703,6 @@ syscall(frame) struct thread *td = curthread; struct proc *p = td->td_proc; register_t orig_tf_rflags; - u_int sticks; int error; int narg; register_t args[8]; @@ -728,7 +727,7 @@ syscall(frame) reg = 0; regcnt = 6; - sticks = td->td_sticks; + td->td_pticks = 0; td->td_frame = &frame; if (td->td_ucred != p->p_ucred) cred_update_thread(td); @@ -851,7 +850,7 @@ syscall(frame) /* * Handle reschedule and other end-of-syscall issues */ - userret(td, &frame, sticks); + userret(td, &frame); CTR4(KTR_SYSC, "syscall exit thread %p pid %d proc %s code %d", td, td->td_proc->p_pid, td->td_proc->p_comm, code); Index: amd64/amd64/tsc.c =================================================================== RCS file: /home/ncvs/src/sys/amd64/amd64/tsc.c,v retrieving revision 1.205 diff -u -p -r1.205 tsc.c --- amd64/amd64/tsc.c 17 Nov 2003 08:58:13 -0000 1.205 +++ amd64/amd64/tsc.c 23 Aug 2007 20:32:25 -0000 @@ -77,6 +77,7 @@ init_TSC(void) tsc_freq = tscval[1] - tscval[0]; if (bootverbose) printf("TSC clock: %lu Hz\n", tsc_freq); + set_cputicker(rdtsc, tsc_freq, 1); } Index: amd64/ia32/ia32_syscall.c =================================================================== RCS file: /home/ncvs/src/sys/amd64/ia32/ia32_syscall.c,v retrieving revision 1.8.2.2 diff -u -p -r1.8.2.2 ia32_syscall.c --- amd64/ia32/ia32_syscall.c 11 Aug 2006 18:42:48 -0000 1.8.2.2 +++ amd64/ia32/ia32_syscall.c 23 Aug 2007 18:11:09 -0000 @@ -96,7 +96,6 @@ ia32_syscall(struct trapframe frame) struct thread *td = curthread; struct proc *p = td->td_proc; register_t orig_tf_rflags; - u_int sticks; int error; int narg; u_int32_t args[8]; @@ -109,7 +108,7 @@ ia32_syscall(struct trapframe frame) */ PCPU_LAZY_INC(cnt.v_syscall); - sticks = td->td_sticks; + td->td_pticks = 0; td->td_frame = &frame; if (td->td_ucred != p->p_ucred) cred_update_thread(td); @@ -239,7 +238,7 @@ ia32_syscall(struct trapframe frame) /* * Handle reschedule and other end-of-syscall issues */ - userret(td, &frame, sticks); + userret(td, &frame); CTR4(KTR_SYSC, "syscall exit thread %p pid %d proc %s code %d", td, td->td_proc->p_pid, td->td_proc->p_comm, code); Index: arm/arm/trap.c =================================================================== RCS file: /home/ncvs/src/sys/arm/arm/trap.c,v retrieving revision 1.17.2.3 diff -u -p -r1.17.2.3 trap.c --- arm/arm/trap.c 26 Feb 2007 20:38:31 -0000 1.17.2.3 +++ arm/arm/trap.c 23 Aug 2007 20:27:08 -0000 @@ -230,7 +230,6 @@ data_abort_handler(trapframe_t *tf) vm_prot_t ftype; void *onfault; vm_offset_t va; - u_int sticks = 0; int error = 0; struct ksig ksig; struct proc *p; @@ -257,7 +256,8 @@ data_abort_handler(trapframe_t *tf) user = TRAP_USERMODE(tf); if (user) { - sticks = td->td_sticks; td->td_frame = tf; + td->td_pticks = 0; + td->td_frame = tf; if (td->td_ucred != td->td_proc->p_ucred) cred_update_thread(td); if (td->td_pflags & TDP_SA) @@ -463,7 +463,7 @@ do_trapsignal: out: /* If returning to user mode, make sure to invoke userret() */ if (user) - userret(td, tf, sticks); + userret(td, tf); } /* @@ -705,7 +705,6 @@ prefetch_abort_handler(trapframe_t *tf) struct vm_map *map; vm_offset_t fault_pc, va; int error = 0; - u_int sticks = 0; struct ksig ksig; @@ -755,7 +754,7 @@ prefetch_abort_handler(trapframe_t *tf) /* Prefetch aborts cannot happen in kernel mode */ if (__predict_false(!TRAP_USERMODE(tf))) dab_fatal(tf, 0, tf->tf_pc, NULL, &ksig); - sticks = td->td_sticks; + td->td_pticks = 0; /* Ok validate the address, can only execute in USER space */ @@ -810,7 +809,7 @@ do_trapsignal: call_trapsignal(td, ksig.signb, ksig.code); out: - userret(td, tf, sticks); + userret(td, tf); } @@ -872,10 +871,9 @@ syscall(struct thread *td, trapframe_t * register_t *ap, *args, copyargs[MAXARGS]; struct sysent *callp; int locked = 0; - u_int sticks = 0; PCPU_LAZY_INC(cnt.v_syscall); - sticks = td->td_sticks; + td->td_pticks = 0; if (td->td_ucred != td->td_proc->p_ucred) cred_update_thread(td); switch (insn & SWI_OS_MASK) { @@ -884,11 +882,11 @@ syscall(struct thread *td, trapframe_t * break; default: trapsignal(td, SIGILL, 0); - userret(td, frame, td->td_sticks); + userret(td, frame); return; } code = insn & 0x000fffff; - sticks = td->td_sticks; + td->td_pticks = 0; ap = &frame->tf_r0; if (code == SYS_syscall) { code = *ap++; @@ -974,7 +972,7 @@ bad: mtx_unlock(&Giant); - userret(td, frame, sticks); + userret(td, frame); CTR4(KTR_SYSC, "syscall exit thread %p pid %d proc %s code %d", td, td->td_proc->p_pid, td->td_proc->p_comm, code); @@ -996,6 +994,7 @@ swi_handler(trapframe_t *frame) td->td_frame = frame; + td->td_pticks = 0; if (td->td_proc->p_flag & P_SA) thread_user_enter(td); /* @@ -1004,7 +1003,7 @@ swi_handler(trapframe_t *frame) */ if (__predict_false(((frame->tf_pc - INSN_SIZE) & 3) != 0)) { trapsignal(td, SIGILL, 0); - userret(td, frame, td->td_sticks); + userret(td, frame); return; } insn = *(u_int32_t *)(frame->tf_pc - INSN_SIZE); Index: i386/i386/geode.c =================================================================== RCS file: /home/ncvs/src/sys/i386/i386/geode.c,v retrieving revision 1.5.8.2 diff -u -p -r1.5.8.2 geode.c --- i386/i386/geode.c 30 Mar 2007 19:17:37 -0000 1.5.8.2 +++ i386/i386/geode.c 23 Aug 2007 20:32:25 -0000 @@ -110,6 +110,20 @@ static struct timecounter geode_timecoun 1000 }; +static uint64_t +geode_cputicks(void) +{ + unsigned c; + static unsigned last; + static uint64_t offset; + + c = inl(geode_counter); + if (c < last) + offset += (1LL << 32); + last = c; + return (offset | c); +} + /* * The GEODE watchdog runs from a 32kHz frequency. One period of that is * 31250 nanoseconds which we round down to 2^14 nanoseconds. The watchdog @@ -176,6 +190,7 @@ geode_probe(device_t self) tc_init(&geode_timecounter); EVENTHANDLER_REGISTER(watchdog_list, geode_watchdog, NULL, 0); + set_cputicker(geode_cputicks, 27000000, 0); } } else if (pci_get_devid(self) == 0x0510100b) { gpio = pci_read_config(self, PCIR_BAR(0), 4); Index: i386/i386/mp_machdep.c =================================================================== RCS file: /home/ncvs/src/sys/i386/i386/mp_machdep.c,v retrieving revision 1.252.2.11 diff -u -p -r1.252.2.11 mp_machdep.c --- i386/i386/mp_machdep.c 2 May 2007 16:16:57 -0000 1.252.2.11 +++ i386/i386/mp_machdep.c 23 Aug 2007 18:05:54 -0000 @@ -650,7 +650,7 @@ init_secondary(void) spinlock_exit(); KASSERT(curthread->td_md.md_spinlock_count == 1, ("invalid count")); - binuptime(PCPU_PTR(switchtime)); + PCPU_SET(switchtime, cpu_ticks()); PCPU_SET(switchticks, ticks); cpu_throw(NULL, choosethread()); /* doesn't return */ Index: i386/i386/trap.c =================================================================== RCS file: /home/ncvs/src/sys/i386/i386/trap.c,v retrieving revision 1.277.2.6 diff -u -p -r1.277.2.6 trap.c --- i386/i386/trap.c 14 Aug 2007 19:42:52 -0000 1.277.2.6 +++ i386/i386/trap.c 23 Aug 2007 20:27:51 -0000 @@ -176,7 +176,7 @@ trap(frame) { struct thread *td = curthread; struct proc *p = td->td_proc; - u_int sticks = 0, type; + u_int type; int i = 0, ucode = 0, code; vm_offset_t eva; #ifdef POWERFAIL_NMI @@ -275,7 +275,7 @@ trap(frame) !(PCPU_GET(curpcb)->pcb_flags & PCB_VM86CALL))) { /* user trap */ - sticks = td->td_sticks; + td->td_pticks = 0; td->td_frame = &frame; if (td->td_ucred != p->p_ucred) cred_update_thread(td); @@ -650,7 +650,7 @@ trap(frame) #endif user: - userret(td, &frame, sticks); + userret(td, &frame); mtx_assert(&Giant, MA_NOTOWNED); userout: out: @@ -881,7 +881,6 @@ syscall(frame) struct thread *td = curthread; struct proc *p = td->td_proc; register_t orig_tf_eflags; - u_int sticks; int error; int narg; int args[8]; @@ -902,7 +901,7 @@ syscall(frame) } #endif - sticks = td->td_sticks; + td->td_pticks = 0; td->td_frame = &frame; if (td->td_ucred != p->p_ucred) cred_update_thread(td); @@ -1032,7 +1031,7 @@ syscall(frame) /* * Handle reschedule and other end-of-syscall issues */ - userret(td, &frame, sticks); + userret(td, &frame); CTR4(KTR_SYSC, "syscall exit thread %p pid %d proc %s code %d", td, td->td_proc->p_pid, td->td_proc->p_comm, code); Index: i386/i386/tsc.c =================================================================== RCS file: /home/ncvs/src/sys/i386/i386/tsc.c,v retrieving revision 1.204 diff -u -p -r1.204 tsc.c --- i386/i386/tsc.c 21 Oct 2003 18:28:34 -0000 1.204 +++ i386/i386/tsc.c 23 Aug 2007 20:32:25 -0000 @@ -86,6 +86,7 @@ init_TSC(void) tsc_freq = tscval[1] - tscval[0]; if (bootverbose) printf("TSC clock: %ju Hz\n", (intmax_t)tsc_freq); + set_cputicker(rdtsc, tsc_freq, 1); } Index: ia64/ia32/ia32_trap.c =================================================================== RCS file: /home/ncvs/src/sys/ia64/ia32/ia32_trap.c,v retrieving revision 1.5.2.3 diff -u -p -r1.5.2.3 ia32_trap.c --- ia64/ia32/ia32_trap.c 19 Sep 2006 12:38:08 -0000 1.5.2.3 +++ ia64/ia32/ia32_trap.c 23 Aug 2007 20:29:46 -0000 @@ -217,7 +217,6 @@ ia32_trap(int vector, struct trapframe * struct thread *td; uint64_t ucode; int sig; - u_int sticks; KASSERT(TRAPF_USERMODE(tf), ("%s: In kernel mode???", __func__)); @@ -226,7 +225,7 @@ ia32_trap(int vector, struct trapframe * td = curthread; td->td_frame = tf; - sticks = td->td_sticks; + td->td_pticks = 0; p = td->td_proc; if (td->td_ucred != p->p_ucred) cred_update_thread(td); @@ -304,7 +303,7 @@ ia32_trap(int vector, struct trapframe * trapsignal(td, sig, ucode); out: - userret(td, tf, sticks); + userret(td, tf); mtx_assert(&Giant, MA_NOTOWNED); do_ast(tf); } Index: ia64/ia64/mp_machdep.c =================================================================== RCS file: /home/ncvs/src/sys/ia64/ia64/mp_machdep.c,v retrieving revision 1.55.2.2 diff -u -p -r1.55.2.2 mp_machdep.c --- ia64/ia64/mp_machdep.c 14 Feb 2006 03:40:49 -0000 1.55.2.2 +++ ia64/ia64/mp_machdep.c 23 Aug 2007 18:05:54 -0000 @@ -136,7 +136,7 @@ ia64_ap_startup(void) mtx_lock_spin(&sched_lock); - binuptime(PCPU_PTR(switchtime)); + PCPU_SET(switchtime, cpu_ticks()); PCPU_SET(switchticks, ticks); ia64_set_tpr(0); Index: ia64/ia64/trap.c =================================================================== RCS file: /home/ncvs/src/sys/ia64/ia64/trap.c,v retrieving revision 1.113.2.3 diff -u -p -r1.113.2.3 trap.c --- ia64/ia64/trap.c 19 Sep 2006 12:38:08 -0000 1.113.2.3 +++ ia64/ia64/trap.c 23 Aug 2007 20:29:30 -0000 @@ -362,7 +362,6 @@ trap(int vector, struct trapframe *tf) struct thread *td; uint64_t ucode; int error, sig, user; - u_int sticks; user = TRAPF_USERMODE(tf) ? 1 : 0; @@ -374,12 +373,11 @@ trap(int vector, struct trapframe *tf) if (user) { ia64_set_fpsr(IA64_FPSR_DEFAULT); - sticks = td->td_sticks; + td->td_pticks = 0; td->td_frame = tf; if (td->td_ucred != p->p_ucred) cred_update_thread(td); } else { - sticks = 0; /* XXX bogus -Wuninitialized warning */ KASSERT(cold || td->td_ucred != NULL, ("kernel trap doesn't have ucred")); #ifdef KDB @@ -875,7 +873,7 @@ trap(int vector, struct trapframe *tf) out: if (user) { - userret(td, tf, sticks); + userret(td, tf); mtx_assert(&Giant, MA_NOTOWNED); do_ast(tf); } @@ -941,7 +939,6 @@ syscall(struct trapframe *tf) struct thread *td; uint64_t *args; int code, error; - u_int sticks; ia64_set_fpsr(IA64_FPSR_DEFAULT); @@ -954,7 +951,7 @@ syscall(struct trapframe *tf) td->td_frame = tf; p = td->td_proc; - sticks = td->td_sticks; + td->td_pticks = 0; if (td->td_ucred != p->p_ucred) cred_update_thread(td); if (p->p_flag & P_SA) @@ -1035,7 +1032,7 @@ syscall(struct trapframe *tf) /* * Handle reschedule and other end-of-syscall issues */ - userret(td, tf, sticks); + userret(td, tf); CTR4(KTR_SYSC, "syscall exit thread %p pid %d proc %s code %d", td, td->td_proc->p_pid, td->td_proc->p_comm, code); Index: kern/init_main.c =================================================================== RCS file: /home/ncvs/src/sys/kern/init_main.c,v retrieving revision 1.256.2.5 diff -u -p -r1.256.2.5 init_main.c --- kern/init_main.c 28 Sep 2006 18:27:01 -0000 1.256.2.5 +++ kern/init_main.c 23 Aug 2007 18:05:54 -0000 @@ -460,11 +460,10 @@ proc0_post(void *dummy __unused) sx_slock(&allproc_lock); LIST_FOREACH(p, &allproc, p_list) { microuptime(&p->p_stats->p_start); - p->p_rux.rux_runtime.sec = 0; - p->p_rux.rux_runtime.frac = 0; + p->p_rux.rux_runtime = 0; } sx_sunlock(&allproc_lock); - binuptime(PCPU_PTR(switchtime)); + PCPU_SET(switchtime, cpu_ticks()); PCPU_SET(switchticks, ticks); /* Index: kern/kern_clock.c =================================================================== RCS file: /home/ncvs/src/sys/kern/kern_clock.c,v retrieving revision 1.178.2.4 diff -u -p -r1.178.2.4 kern_clock.c --- kern/kern_clock.c 20 Feb 2007 22:56:28 -0000 1.178.2.4 +++ kern/kern_clock.c 23 Aug 2007 20:32:25 -0000 @@ -421,7 +421,7 @@ statclock(frame) */ if (p->p_flag & P_SA) thread_statclock(1); - p->p_rux.rux_uticks++; + td->td_uticks++; if (p->p_nice > NZERO) cp_time[CP_NICE]++; else @@ -441,13 +441,13 @@ statclock(frame) */ if ((td->td_pflags & TDP_ITHREAD) || td->td_intr_nesting_level >= 2) { - p->p_rux.rux_iticks++; + td->td_iticks++; cp_time[CP_INTR]++; } else { if (p->p_flag & P_SA) thread_statclock(0); + td->td_pticks++; td->td_sticks++; - p->p_rux.rux_sticks++; if (td != PCPU_GET(idlethread)) cp_time[CP_SYS]++; else Index: kern/kern_fork.c =================================================================== RCS file: /home/ncvs/src/sys/kern/kern_fork.c,v retrieving revision 1.252.2.6 diff -u -p -r1.252.2.6 kern_fork.c --- kern/kern_fork.c 19 Jul 2007 18:46:32 -0000 1.252.2.6 +++ kern/kern_fork.c 23 Aug 2007 18:11:10 -0000 @@ -856,7 +856,7 @@ fork_return(td, frame) struct trapframe *frame; { - userret(td, frame, 0); + userret(td, frame); #ifdef KTRACE if (KTRPOINT(td, KTR_SYSRET)) ktrsysret(SYS_fork, 0, 0); Index: kern/kern_proc.c =================================================================== RCS file: /home/ncvs/src/sys/kern/kern_proc.c,v retrieving revision 1.230.2.5 diff -u -p -r1.230.2.5 kern_proc.c --- kern/kern_proc.c 29 Sep 2006 07:41:24 -0000 1.230.2.5 +++ kern/kern_proc.c 23 Aug 2007 20:32:25 -0000 @@ -621,7 +621,6 @@ fill_kinfo_proc_only(struct proc *p, str struct thread *td0; struct tty *tp; struct session *sp; - struct timeval tv; struct ucred *cred; struct sigacts *ps; @@ -692,8 +691,7 @@ fill_kinfo_proc_only(struct proc *p, str kp->ki_swtime = p->p_swtime; kp->ki_pid = p->p_pid; kp->ki_nice = p->p_nice; - bintime2timeval(&p->p_rux.rux_runtime, &tv); - kp->ki_runtime = tv.tv_sec * (u_int64_t)1000000 + tv.tv_usec; + kp->ki_runtime = cputick2usec(p->p_rux.rux_runtime); mtx_unlock_spin(&sched_lock); if ((p->p_sflag & PS_INMEM) && p->p_stats != NULL) { kp->ki_start = p->p_stats->p_start; Index: kern/kern_resource.c =================================================================== RCS file: /home/ncvs/src/sys/kern/kern_resource.c,v retrieving revision 1.148.2.3 diff -u -p -r1.148.2.3 kern_resource.c --- kern/kern_resource.c 19 Jul 2007 18:46:32 -0000 1.148.2.3 +++ kern/kern_resource.c 23 Aug 2007 21:25:37 -0000 @@ -694,125 +694,132 @@ getrlimit(td, uap) } /* - * Transform the running time and tick information in proc p into user, - * system, and interrupt time usage. + * Transform the running time and tick information for children of proc p + * into user and system time usage. */ void -calcru(p, up, sp) +calccru(p, up, sp) struct proc *p; struct timeval *up; struct timeval *sp; { - struct bintime bt; + + PROC_LOCK_ASSERT(p, MA_OWNED); + calcru1(p, &p->p_crux, up, sp); +} + +/* + * Transform the running time and tick information in proc p into user + * and system time usage. If appropriate, include the current time slice + * on this CPU. + */ +void +calcru(struct proc *p, struct timeval *up, struct timeval *sp) +{ struct rusage_ext rux; struct thread *td; - int bt_valid; + uint64_t u; PROC_LOCK_ASSERT(p, MA_OWNED); mtx_assert(&sched_lock, MA_NOTOWNED); - bt_valid = 0; mtx_lock_spin(&sched_lock); - rux = p->p_rux; - FOREACH_THREAD_IN_PROC(p, td) { - if (TD_IS_RUNNING(td)) { - /* - * Adjust for the current time slice. This is - * actually fairly important since the error here is - * on the order of a time quantum which is much - * greater than the precision of binuptime(). - */ - KASSERT(td->td_oncpu != NOCPU, - ("%s: running thread has no CPU", __func__)); - if (!bt_valid) { - binuptime(&bt); - bt_valid = 1; - } - bintime_add(&rux.rux_runtime, &bt); - bintime_sub(&rux.rux_runtime, - &pcpu_find(td->td_oncpu)->pc_switchtime); - } + + /* + * If we are getting stats for the current process, then add in the + * stats that this thread has accumulated in its current time slice. + * We reset the thread and CPU state as if we had performed a context + * switch right here. + */ + if (curthread->td_proc == p) { + td = curthread; + u = cpu_ticks(); + p->p_rux.rux_runtime += u - PCPU_GET(switchtime); + PCPU_SET(switchtime, u); + p->p_rux.rux_uticks += td->td_uticks; + td->td_uticks = 0; + p->p_rux.rux_iticks += td->td_iticks; + td->td_iticks = 0; + p->p_rux.rux_sticks += td->td_sticks; + td->td_sticks = 0; } + /* Work on a copy of p_rux so we can let go of sched_lock */ + rux = p->p_rux; mtx_unlock_spin(&sched_lock); calcru1(p, &rux, up, sp); + /* Update the result from the p_rux copy */ p->p_rux.rux_uu = rux.rux_uu; p->p_rux.rux_su = rux.rux_su; - p->p_rux.rux_iu = rux.rux_iu; -} - -void -calccru(p, up, sp) - struct proc *p; - struct timeval *up; - struct timeval *sp; -{ - - PROC_LOCK_ASSERT(p, MA_OWNED); - calcru1(p, &p->p_crux, up, sp); + p->p_rux.rux_tu = rux.rux_tu; } static void -calcru1(p, ruxp, up, sp) - struct proc *p; - struct rusage_ext *ruxp; - struct timeval *up; - struct timeval *sp; +calcru1(struct proc *p, struct rusage_ext *ruxp, struct timeval *up, + struct timeval *sp) { - struct timeval tv; - /* {user, system, interrupt, total} {ticks, usec}; previous tu: */ - u_int64_t ut, uu, st, su, it, iu, tt, tu, ptu; + /* {user, system, interrupt, total} {ticks, usec}: */ + u_int64_t ut, uu, st, su, it, tt, tu; ut = ruxp->rux_uticks; st = ruxp->rux_sticks; it = ruxp->rux_iticks; tt = ut + st + it; if (tt == 0) { + /* Avoid divide by zero */ st = 1; tt = 1; } - bintime2timeval(&ruxp->rux_runtime, &tv); - tu = (u_int64_t)tv.tv_sec * 1000000 + tv.tv_usec; - ptu = ruxp->rux_uu + ruxp->rux_su + ruxp->rux_iu; - if (tu < ptu) { - printf( -"calcru: runtime went backwards from %ju usec to %ju usec for pid %d (%s)\n", - (uintmax_t)ptu, (uintmax_t)tu, p->p_pid, p->p_comm); - tu = ptu; - } + tu = cputick2usec(ruxp->rux_runtime); if ((int64_t)tu < 0) { + /* XXX: this should be an assert /phk */ printf("calcru: negative runtime of %jd usec for pid %d (%s)\n", (intmax_t)tu, p->p_pid, p->p_comm); - tu = ptu; + tu = ruxp->rux_tu; } - /* Subdivide tu. */ - uu = (tu * ut) / tt; - su = (tu * st) / tt; - iu = tu - uu - su; - - /* Enforce monotonicity. */ - if (uu < ruxp->rux_uu || su < ruxp->rux_su || iu < ruxp->rux_iu) { + if (tu >= ruxp->rux_tu) { + /* + * The normal case, time increased. + * Enforce monotonicity of bucketed numbers. + */ + uu = (tu * ut) / tt; if (uu < ruxp->rux_uu) uu = ruxp->rux_uu; - else if (uu + ruxp->rux_su + ruxp->rux_iu > tu) - uu = tu - ruxp->rux_su - ruxp->rux_iu; - if (st == 0) + su = (tu * st) / tt; + if (su < ruxp->rux_su) su = ruxp->rux_su; - else { - su = ((tu - uu) * st) / (st + it); - if (su < ruxp->rux_su) - su = ruxp->rux_su; - else if (uu + su + ruxp->rux_iu > tu) - su = tu - uu - ruxp->rux_iu; - } - KASSERT(uu + su + ruxp->rux_iu <= tu, - ("calcru: monotonisation botch 1")); - iu = tu - uu - su; - KASSERT(iu >= ruxp->rux_iu, - ("calcru: monotonisation botch 2")); + } else if (tu + 3 > ruxp->rux_tu || 101 * tu > 100 * ruxp->rux_tu) { + /* + * When we calibrate the cputicker, it is not uncommon to + * see the presumably fixed frequency increase slightly over + * time as a result of thermal stabilization and NTP + * discipline (of the reference clock). We therefore ignore + * a bit of backwards slop because we expect to catch up + * shortly. We use a 3 microsecond limit to catch low + * counts and a 1% limit for high counts. + */ + uu = ruxp->rux_uu; + su = ruxp->rux_su; + tu = ruxp->rux_tu; + } else { /* tu < ruxp->rux_tu */ + /* + * What happene here was likely that a laptop, which ran at + * a reduced clock frequency at boot, kicked into high gear. + * The wisdom of spamming this message in that case is + * dubious, but it might also be indicative of something + * serious, so lets keep it and hope laptops can be made + * more truthful about their CPU speed via ACPI. + */ + printf("calcru: runtime went backwards from %ju usec " + "to %ju usec for pid %d (%s)\n", + (uintmax_t)ruxp->rux_tu, (uintmax_t)tu, + p->p_pid, p->p_comm); + uu = (tu * ut) / tt; + su = (tu * st) / tt; } + ruxp->rux_uu = uu; ruxp->rux_su = su; - ruxp->rux_iu = iu; + ruxp->rux_tu = tu; up->tv_sec = uu / 1000000; up->tv_usec = uu % 1000000; @@ -883,13 +890,13 @@ ruadd(ru, rux, ru2, rux2) register long *ip, *ip2; register int i; - bintime_add(&rux->rux_runtime, &rux2->rux_runtime); + rux->rux_runtime += rux2->rux_runtime; rux->rux_uticks += rux2->rux_uticks; rux->rux_sticks += rux2->rux_sticks; rux->rux_iticks += rux2->rux_iticks; rux->rux_uu += rux2->rux_uu; rux->rux_su += rux2->rux_su; - rux->rux_iu += rux2->rux_iu; + rux->rux_tu += rux2->rux_tu; if (ru->ru_maxrss < ru2->ru_maxrss) ru->ru_maxrss = ru2->ru_maxrss; ip = &ru->ru_first; Index: kern/kern_synch.c =================================================================== RCS file: /home/ncvs/src/sys/kern/kern_synch.c,v retrieving revision 1.270.2.6 diff -u -p -r1.270.2.6 kern_synch.c --- kern/kern_synch.c 6 Jul 2006 08:32:50 -0000 1.270.2.6 +++ kern/kern_synch.c 23 Aug 2007 20:32:25 -0000 @@ -337,7 +337,7 @@ wakeup_one(ident) void mi_switch(int flags, struct thread *newtd) { - struct bintime new_switchtime; + uint64_t new_switchtime; struct thread *td; struct proc *p; @@ -366,9 +366,14 @@ mi_switch(int flags, struct thread *newt * Compute the amount of time during which the current * process was running, and add that to its total so far. */ - binuptime(&new_switchtime); - bintime_add(&p->p_rux.rux_runtime, &new_switchtime); - bintime_sub(&p->p_rux.rux_runtime, PCPU_PTR(switchtime)); + new_switchtime = cpu_ticks(); + p->p_rux.rux_runtime += (new_switchtime - PCPU_GET(switchtime)); + p->p_rux.rux_uticks += td->td_uticks; + td->td_uticks = 0; + p->p_rux.rux_iticks += td->td_iticks; + td->td_iticks = 0; + p->p_rux.rux_sticks += td->td_sticks; + td->td_sticks = 0; td->td_generation++; /* bump preempt-detect counter */ @@ -387,7 +392,7 @@ mi_switch(int flags, struct thread *newt * it reaches the max, arrange to kill the process in ast(). */ if (p->p_cpulimit != RLIM_INFINITY && - p->p_rux.rux_runtime.sec >= p->p_cpulimit) { + p->p_rux.rux_runtime >= p->p_cpulimit * cpu_tickrate()) { p->p_sflag |= PS_XCPU; td->td_flags |= TDF_ASTPENDING; } Index: kern/kern_tc.c =================================================================== RCS file: /home/ncvs/src/sys/kern/kern_tc.c,v retrieving revision 1.164 diff -u -p -r1.164 kern_tc.c --- kern/kern_tc.c 26 Mar 2005 20:04:28 -0000 1.164 +++ kern/kern_tc.c 23 Aug 2007 20:32:25 -0000 @@ -116,6 +116,7 @@ TC_STATS(nsetclock); #undef TC_STATS static void tc_windup(void); +static void cpu_tick_calibrate(int); static int sysctl_kern_boottime(SYSCTL_HANDLER_ARGS) @@ -131,6 +132,7 @@ sysctl_kern_boottime(SYSCTL_HANDLER_ARGS #endif return SYSCTL_OUT(req, &boottime, sizeof(boottime)); } + /* * Return the difference between the timehands' counter value now and what * was when we copied it to the timehands' offset_count. @@ -363,6 +365,7 @@ tc_setclock(struct timespec *ts) struct timespec ts2; struct bintime bt, bt2; + cpu_tick_calibrate(1); nsetclock++; binuptime(&bt2); timespec2bintime(ts, &bt); @@ -379,6 +382,7 @@ tc_setclock(struct timespec *ts) (intmax_t)ts2.tv_sec, ts2.tv_nsec, (intmax_t)ts->tv_sec, ts->tv_nsec); } + cpu_tick_calibrate(1); } /* @@ -475,8 +479,8 @@ tc_windup(void) * x = a * 2^32 / 10^9 = a * 4.294967296 * * The range of th_adjustment is +/- 5000PPM so inside a 64bit int - * we can only multiply by about 850 without overflowing, but that - * leaves suitably precise fractions for multiply before divide. + * we can only multiply by about 850 without overflowing, that + * leaves no suitably precise fractions for multiply before divide. * * Divide before multiply with a fraction of 2199/512 results in a * systematic undercompensation of 10PPM of th_adjustment. On a @@ -749,11 +753,16 @@ void tc_ticktock(void) { static int count; + static time_t last_calib; if (++count < tc_tick) return; count = 0; tc_windup(); + if (time_uptime != last_calib && !(time_uptime & 0xf)) { + cpu_tick_calibrate(0); + last_calib = time_uptime; + } } static void @@ -782,3 +791,143 @@ inittimecounter(void *dummy) } SYSINIT(timecounter, SI_SUB_CLOCKS, SI_ORDER_SECOND, inittimecounter, NULL) + +/* Cpu tick handling -------------------------------------------------*/ + +static int cpu_tick_variable; +static uint64_t cpu_tick_frequency; + +static +uint64_t +tc_cpu_ticks(void) +{ + static uint64_t base; + static unsigned last; + unsigned u; + struct timecounter *tc; + + tc = timehands->th_counter; + u = tc->tc_get_timecount(tc) & tc->tc_counter_mask; + if (u < last) + base += tc->tc_counter_mask + 1; + last = u; + return (u + base); +} + +/* + * This function gets called ever 16 seconds on only one designated + * CPU in the system from hardclock() via tc_ticktock(). + * + * Whenever the real time clock is stepped we get called with reset=1 + * to make sure we handle suspend/resume and similar events correctly. + */ + +static void +cpu_tick_calibrate(int reset) +{ + static uint64_t c_last; + uint64_t c_this, c_delta; + static struct bintime t_last; + struct bintime t_this, t_delta; + + if (reset) { + /* The clock was stepped, abort & reset */ + t_last.sec = 0; + return; + } + + /* we don't calibrate fixed rate cputicks */ + if (!cpu_tick_variable) + return; + + getbinuptime(&t_this); + c_this = cpu_ticks(); + if (t_last.sec != 0) { + c_delta = c_this - c_last; + t_delta = t_this; + bintime_sub(&t_delta, &t_last); + if (0 && bootverbose) { + struct timespec ts; + bintime2timespec(&t_delta, &ts); + printf("%ju %ju.%016jx %ju.%09ju", + (uintmax_t)c_delta >> 4, + (uintmax_t)t_delta.sec, (uintmax_t)t_delta.frac, + (uintmax_t)ts.tv_sec, (uintmax_t)ts.tv_nsec); + } + /* + * Validate that 16 +/- 1/256 seconds passed. + * After division by 16 this gives us a precision of + * roughly 250PPM which is sufficient + */ + if (t_delta.sec > 16 || ( + t_delta.sec == 16 && t_delta.frac >= (0x01LL << 56))) { + /* too long */ + if (0 && bootverbose) + printf("\ttoo long\n"); + } else if (t_delta.sec < 15 || + (t_delta.sec == 15 && t_delta.frac <= (0xffLL << 56))) { + /* too short */ + if (0 && bootverbose) + printf("\ttoo short\n"); + } else { + /* just right */ + c_delta >>= 4; + if (c_delta > cpu_tick_frequency) { + if (0 && bootverbose) + printf("\thigher\n"); + cpu_tick_frequency = c_delta; + } else { + if (0 && bootverbose) + printf("\tlower\n"); + } + } + } + c_last = c_this; + t_last = t_this; +} + +void +set_cputicker(cpu_tick_f *func, uint64_t freq, unsigned var) +{ + + if (func == NULL) { + cpu_ticks = tc_cpu_ticks; + } else { + cpu_tick_frequency = freq; + cpu_tick_variable = var; + cpu_ticks = func; + } +} + +uint64_t +cpu_tickrate(void) +{ + + if (cpu_ticks == tc_cpu_ticks) + return (tc_getfrequency()); + return (cpu_tick_frequency); +} + +/* + * We need to be slightly careful converting cputicks to microseconds. + * There is plenty of margin in 64 bits of microseconds (half a million + * years) and in 64 bits at 4 GHz (146 years), but if we do a multiply + * before divide conversion (to retain precision) we find that the + * margin shrinks to 1.5 hours (one millionth of 146y). + * With a three prong approach we never loose significant bits, no + * matter what the cputick rate and length of timeinterval is. + */ + +uint64_t +cputick2usec(uint64_t tick) +{ + + if (tick > 18446744073709551LL) /* floor(2^64 / 1000) */ + return (tick / (cpu_tickrate() / 1000000LL)); + else if (tick > 18446744073709LL) /* floor(2^64 / 1000000) */ + return ((tick * 1000LL) / (cpu_tickrate() / 1000LL)); + else + return ((tick * 1000000LL) / cpu_tickrate()); +} + +cpu_tick_f *cpu_ticks = tc_cpu_ticks; Index: kern/kern_thread.c =================================================================== RCS file: /home/ncvs/src/sys/kern/kern_thread.c,v retrieving revision 1.216.2.6 diff -u -p -r1.216.2.6 kern_thread.c --- kern/kern_thread.c 2 Sep 2006 17:29:57 -0000 1.216.2.6 +++ kern/kern_thread.c 23 Aug 2007 18:05:54 -0000 @@ -448,7 +448,7 @@ thread_free(struct thread *td) void thread_exit(void) { - struct bintime new_switchtime; + uint64_t new_switchtime; struct thread *td; struct proc *p; struct ksegrp *kg; @@ -488,13 +488,14 @@ thread_exit(void) /* * The thread is exiting. scheduler can release its stuff * and collect stats etc. + * XXX this is not very right, since PROC_UNLOCK may still + * need scheduler stuff. */ sched_thread_exit(td); /* Do the same timestamp bookkeeping that mi_switch() would do. */ - binuptime(&new_switchtime); - bintime_add(&p->p_rux.rux_runtime, &new_switchtime); - bintime_sub(&p->p_rux.rux_runtime, PCPU_PTR(switchtime)); + new_switchtime = cpu_ticks(); + p->p_rux.rux_runtime += (new_switchtime - PCPU_GET(switchtime)); PCPU_SET(switchtime, new_switchtime); PCPU_SET(switchticks, ticks); cnt.v_swtch++; Index: kern/subr_trap.c =================================================================== RCS file: /home/ncvs/src/sys/kern/subr_trap.c,v retrieving revision 1.281.2.1 diff -u -p -r1.281.2.1 subr_trap.c --- kern/subr_trap.c 6 Sep 2006 21:43:59 -0000 1.281.2.1 +++ kern/subr_trap.c 23 Aug 2007 18:11:10 -0000 @@ -74,10 +74,7 @@ __FBSDID("$FreeBSD: src/sys/kern/subr_tr * MPSAFE */ void -userret(td, frame, oticks) - struct thread *td; - struct trapframe *frame; - u_int oticks; +userret(struct thread *td, struct trapframe *frame) { struct proc *p = td->td_proc; @@ -127,10 +124,8 @@ userret(td, frame, oticks) * Charge system time if profiling. */ if (p->p_flag & P_PROFIL) { - quad_t ticks; - ticks = td->td_sticks - oticks; - addupc_task(td, TRAPF_PC(frame), (u_int)ticks * psratio); + addupc_task(td, TRAPF_PC(frame), td->td_pticks * psratio); } /* @@ -153,7 +148,6 @@ ast(struct trapframe *framep) struct proc *p; struct ksegrp *kg; struct rlimit rlim; - u_int sticks; int sflag; int flags; int sig; @@ -172,7 +166,7 @@ ast(struct trapframe *framep) mtx_assert(&Giant, MA_NOTOWNED); mtx_assert(&sched_lock, MA_NOTOWNED); td->td_frame = framep; - sticks = td->td_sticks; + td->td_pticks = 0; if ((p->p_flag & P_SA) && (td->td_mailbox == NULL)) thread_user_enter(td); @@ -234,7 +228,7 @@ ast(struct trapframe *framep) PROC_LOCK(p); lim_rlimit(p, RLIMIT_CPU, &rlim); mtx_lock_spin(&sched_lock); - if (p->p_rux.rux_runtime.sec >= rlim.rlim_max) { + if (p->p_rux.rux_runtime >= rlim.rlim_max * cpu_tickrate()) { mtx_unlock_spin(&sched_lock); killproc(p, "exceeded maximum CPU limit"); } else { @@ -272,6 +266,6 @@ ast(struct trapframe *framep) PROC_UNLOCK(p); } - userret(td, framep, sticks); + userret(td, framep); mtx_assert(&Giant, MA_NOTOWNED); } Index: powerpc/powerpc/trap.c =================================================================== RCS file: /home/ncvs/src/sys/powerpc/powerpc/trap.c,v retrieving revision 1.54.2.3 diff -u -p -r1.54.2.3 trap.c --- powerpc/powerpc/trap.c 19 Sep 2006 12:38:08 -0000 1.54.2.3 +++ powerpc/powerpc/trap.c 23 Aug 2007 20:28:18 -0000 @@ -146,7 +146,7 @@ trap(struct trapframe *frame) struct thread *td; struct proc *p; int sig, type, user; - u_int sticks, ucode; + u_int ucode; PCPU_LAZY_INC(cnt.v_trap); @@ -156,13 +156,12 @@ trap(struct trapframe *frame) type = ucode = frame->exc; sig = 0; user = frame->srr1 & PSL_PR; - sticks = 0; CTR3(KTR_TRAP, "trap: %s type=%s (%s)", p->p_comm, trapname(type), user ? "user" : "kernel"); if (user) { - sticks = td->td_sticks; + td->td_pticks = 0; td->td_frame = frame; if (td->td_ucred != p->p_ucred) cred_update_thread(td); @@ -260,7 +259,7 @@ trap(struct trapframe *frame) trapsignal(td, sig, ucode); } - userret(td, frame, sticks); + userret(td, frame); mtx_assert(&Giant, MA_NOTOWNED); } Index: sparc64/sparc64/mp_machdep.c =================================================================== RCS file: /home/ncvs/src/sys/sparc64/sparc64/mp_machdep.c,v retrieving revision 1.29.2.2 diff -u -p -r1.29.2.2 mp_machdep.c --- sparc64/sparc64/mp_machdep.c 4 Sep 2006 18:28:32 -0000 1.29.2.2 +++ sparc64/sparc64/mp_machdep.c 23 Aug 2007 18:05:54 -0000 @@ -363,7 +363,7 @@ cpu_mp_bootstrap(struct pcpu *pc) /* ok, now grab sched_lock and enter the scheduler */ mtx_lock_spin(&sched_lock); spinlock_exit(); - binuptime(PCPU_PTR(switchtime)); + PCPU_SET(switchtime, cpu_ticks()); PCPU_SET(switchticks, ticks); cpu_throw(NULL, choosethread()); /* doesn't return */ } Index: sparc64/sparc64/tick.c =================================================================== RCS file: /home/ncvs/src/sys/sparc64/sparc64/tick.c,v retrieving revision 1.16.2.1 diff -u -p -r1.16.2.1 tick.c --- sparc64/sparc64/tick.c 31 Mar 2006 23:38:29 -0000 1.16.2.1 +++ sparc64/sparc64/tick.c 23 Aug 2007 20:32:25 -0000 @@ -64,6 +64,13 @@ SYSCTL_INT(_machdep_tick, OID_AUTO, adju static void tick_hardclock(struct clockframe *); +static uint64_t +tick_cputicks(void) +{ + + return (rd(tick)); +} + void cpu_initclocks(void) { @@ -148,6 +155,8 @@ tick_init(u_long clock) * handled. */ tick_stop(); + + set_cputicker(tick_cputicks, tick_freq, 0); } void Index: sparc64/sparc64/trap.c =================================================================== RCS file: /home/ncvs/src/sys/sparc64/sparc64/trap.c,v retrieving revision 1.74.2.2 diff -u -p -r1.74.2.2 trap.c --- sparc64/sparc64/trap.c 29 Jan 2007 21:32:18 -0000 1.74.2.2 +++ sparc64/sparc64/trap.c 23 Aug 2007 18:11:10 -0000 @@ -234,7 +234,6 @@ trap(struct trapframe *tf) { struct thread *td; struct proc *p; - u_int sticks; int error; int sig; @@ -251,7 +250,7 @@ trap(struct trapframe *tf) KASSERT(td->td_proc != NULL, ("trap: curproc NULL")); p = td->td_proc; - sticks = td->td_sticks; + td->td_pticks = 0; td->td_frame = tf; if (td->td_ucred != p->p_ucred) cred_update_thread(td); @@ -291,7 +290,7 @@ trap(struct trapframe *tf) trapsignal(td, sig, tf->tf_type); } - userret(td, tf, sticks); + userret(td, tf); mtx_assert(&Giant, MA_NOTOWNED); } else { KASSERT((tf->tf_type & T_KERNEL) != 0, @@ -500,7 +499,6 @@ syscall(struct trapframe *tf) register_t args[8]; register_t *argp; struct proc *p; - u_int sticks; u_long code; u_long tpc; int reg; @@ -521,7 +519,7 @@ syscall(struct trapframe *tf) reg = 0; regcnt = REG_MAXARGS; - sticks = td->td_sticks; + td->td_pticks = 0; td->td_frame = tf; if (td->td_ucred != p->p_ucred) cred_update_thread(td); @@ -646,7 +644,7 @@ syscall(struct trapframe *tf) /* * Handle reschedule and other end-of-syscall issues */ - userret(td, tf, sticks); + userret(td, tf); #ifdef KTRACE if (KTRPOINT(td, KTR_SYSRET)) Index: sys/pcpu.h =================================================================== RCS file: /home/ncvs/src/sys/sys/pcpu.h,v retrieving revision 1.16 diff -u -p -r1.16 pcpu.h --- sys/pcpu.h 26 Apr 2005 17:07:40 -0000 1.16 +++ sys/pcpu.h 23 Aug 2007 18:05:54 -0000 @@ -60,7 +60,7 @@ struct pcpu { struct thread *pc_fpcurthread; /* Fp state owner */ struct thread *pc_deadthread; /* Zombie thread or NULL */ struct pcb *pc_curpcb; /* Current pcb */ - struct bintime pc_switchtime; + uint64_t pc_switchtime; int pc_switchticks; u_int pc_cpuid; /* This cpu number */ cpumask_t pc_cpumask; /* This cpu mask */ Index: sys/proc.h =================================================================== RCS file: /home/ncvs/src/sys/sys/proc.h,v retrieving revision 1.432.2.10 diff -u -p -r1.432.2.10 proc.h --- sys/proc.h 11 Jun 2007 11:27:04 -0000 1.432.2.10 +++ sys/proc.h 23 Aug 2007 21:25:37 -0000 @@ -278,7 +278,10 @@ struct thread { struct ucred *td_ucred; /* (k) Reference to credentials. */ struct thread *td_standin; /* (k + a) Use this for an upcall. */ struct kse_upcall *td_upcall; /* (k + j) Upcall structure. */ - u_int64_t td_sticks; /* (k) Statclock hits in system mode. */ + u_int td_pticks; /* (k) Statclock hits for profiling */ + u_int td_sticks; /* (k) Statclock hits in system mode. */ + u_int td_iticks; /* (k) Statclock hits in intr mode. */ + u_int td_uticks; /* (k) Statclock hits in user mode. */ u_int td_uuticks; /* (k) Statclock hits (usr), for UTS. */ u_int td_usticks; /* (k) Statclock hits (sys), for UTS. */ int td_intrval; /* (j) Return value of TDF_INTERRUPT. */ @@ -502,13 +505,13 @@ struct ksegrp { * Locking: (cj) means (j) for p_rux and (c) for p_crux. */ struct rusage_ext { - struct bintime rux_runtime; /* (cj) Real time. */ + u_int64_t rux_runtime; /* (cj) Real time. */ u_int64_t rux_uticks; /* (cj) Statclock hits in user mode. */ u_int64_t rux_sticks; /* (cj) Statclock hits in sys mode. */ u_int64_t rux_iticks; /* (cj) Statclock hits in intr mode. */ u_int64_t rux_uu; /* (c) Previous user time in usec. */ u_int64_t rux_su; /* (c) Previous sys time in usec. */ - u_int64_t rux_iu; /* (c) Previous intr time in usec. */ + u_int64_t rux_tu; /* (c) Previous total time in usec. */ }; /* @@ -910,7 +913,7 @@ extern void (*cpu_idle_hook)(void); /* H void cpu_switch(struct thread *old, struct thread *new); void cpu_throw(struct thread *old, struct thread *new) __dead2; void unsleep(struct thread *); -void userret(struct thread *, struct trapframe *, u_int); +void userret(struct thread *, struct trapframe *); void cpu_exit(struct thread *); void exit1(struct thread *, int) __dead2; Index: sys/systm.h =================================================================== RCS file: /home/ncvs/src/sys/sys/systm.h,v retrieving revision 1.234.2.6 diff -u -p -r1.234.2.6 systm.h --- sys/systm.h 18 Jun 2007 22:44:59 -0000 1.234.2.6 +++ sys/systm.h 23 Aug 2007 20:32:25 -0000 @@ -240,6 +240,12 @@ int setenv(const char *name, const char int unsetenv(const char *name); int testenv(const char *name); +typedef uint64_t (cpu_tick_f)(void); +void set_cputicker(cpu_tick_f *func, uint64_t freq, unsigned var); +extern cpu_tick_f *cpu_ticks; +uint64_t cpu_tickrate(void); +uint64_t cputick2usec(uint64_t tick); + #ifdef APM_FIXUP_CALLTODO struct timeval; void adjust_timeout_calltodo(struct timeval *time_change); From owner-freebsd-stable@FreeBSD.ORG Fri Aug 24 08:57:09 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6AEE616A417 for ; Fri, 24 Aug 2007 08:57:09 +0000 (UTC) (envelope-from feargal@fbi.ie) Received: from mail14.svc.cra.dublin.eircom.net (mail14.svc.cra.dublin.eircom.net [159.134.118.30]) by mx1.freebsd.org (Postfix) with SMTP id 0C86A13C465 for ; Fri, 24 Aug 2007 08:57:08 +0000 (UTC) (envelope-from feargal@fbi.ie) Received: (qmail 97733 messnum 5479374 invoked from network[82.141.233.46/unknown]); 24 Aug 2007 08:57:07 -0000 Received: from unknown (HELO alatar.edhellond.fbi.ie) (82.141.233.46) by mail14.svc.cra.dublin.eircom.net (qp 97733) with SMTP; 24 Aug 2007 08:57:07 -0000 Received: from mablung.edhellond.fbi.ie (mablung.edhellond.fbi.ie [192.168.0.14]) by alatar.edhellond.fbi.ie (8.13.1/8.13.1) with ESMTP id l7O8v2n1096650 for ; Fri, 24 Aug 2007 08:57:07 GMT (envelope-from feargal@fbi.ie) Date: Fri, 24 Aug 2007 09:57:02 +0100 From: Feargal Reilly To: freebsd-stable@freebsd.org Message-ID: <20070824095702.6fe7ee3c@mablung.edhellond.fbi.ie> In-Reply-To: <02fe01c7e3af$d3b86ed0$0c00a8c0@Artem> References: <02fe01c7e3af$d3b86ed0$0c00a8c0@Artem> Organization: FBI X-Mailer: Claws Mail 2.10.0 (GTK+ 2.10.13; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: A little story of failed raid5 (3ware 8000 series) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Aug 2007 08:57:09 -0000 On Tue, 21 Aug 2007 08:57:22 +0400 "Artem Kuchin" wrote: > Um.. it is because i did not have a map of hot swap baskets to > conroller ports and i needed to check every driver basket to > understand which port it sits on. I have no choise, i think. > I'm just going to highlight the importance of knowing which physical disk is which on your system. About a year ago I had to replace a hot-swappable disk from an array, but then realised I had no idea which physical disk it was as the map of the disks was rather helpfully *inside* the case. Due to the physical setup, I had no way or removing the cover without first powering down the server - which defeated the whole point of paying extra for hot-swap disks. So yeah, be sure to label your disk bays, but be sure to put those labels somewhere *useful*. -fr. -- Feargal Reilly, Chief Techie, FBI. PGP Key: 0xBD252C01 (expires: 2006-11-30) Web: http://www.fbi.ie/ | Tel: +353.14988588 | Fax: +353.14988489 Communications House, 11 Sallymount Avenue, Ranelagh, Dublin 6. From owner-freebsd-stable@FreeBSD.ORG Fri Aug 24 09:03:58 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 93E9116A418; Fri, 24 Aug 2007 09:03:58 +0000 (UTC) (envelope-from johan@stromnet.se) Received: from av12-2-sn2.hy.skanova.net (av12-2-sn2.hy.skanova.net [81.228.8.186]) by mx1.freebsd.org (Postfix) with ESMTP id 1C29613C481; Fri, 24 Aug 2007 09:03:58 +0000 (UTC) (envelope-from johan@stromnet.se) Received: by av12-2-sn2.hy.skanova.net (Postfix, from userid 502) id 4798E3854C; Fri, 24 Aug 2007 11:03:56 +0200 (CEST) Received: from smtp4-1-sn2.hy.skanova.net (smtp4-1-sn2.hy.skanova.net [81.228.8.92]) by av12-2-sn2.hy.skanova.net (Postfix) with ESMTP id 000C33854B; Fri, 24 Aug 2007 11:03:55 +0200 (CEST) Received: from phomca.stromnet.se (90-224-172-102-no129.tbcn.telia.com [90.224.172.102]) by smtp4-1-sn2.hy.skanova.net (Postfix) with ESMTP id 5334537E44; Fri, 24 Aug 2007 11:03:52 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by phomca.stromnet.se (Postfix) with ESMTP id B121EB826; Fri, 24 Aug 2007 11:03:51 +0200 (CEST) X-Virus-Scanned: amavisd-new at stromnet.se Received: from phomca.stromnet.se ([127.0.0.1]) by localhost (phomca.stromnet.se [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YJoUwxuVR9F8; Fri, 24 Aug 2007 11:03:48 +0200 (CEST) Received: from [172.28.1.102] (jstrom-mb.stromnet.se [172.28.1.102]) by phomca.stromnet.se (Postfix) with ESMTP id 0F80AB824; Fri, 24 Aug 2007 11:03:48 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v752.3) In-Reply-To: <441B87F4-5846-441B-B6B4-34694B483C73@stromnet.se> References: <8039436E-1824-4C2E-915B-9069DEF23B10@stromnet.se> <20070821143136.GD1132@garage.freebsd.pl> <441B87F4-5846-441B-B6B4-34694B483C73@stromnet.se> Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed Message-Id: <77098FC1-E06C-4A0C-803F-038509F5F8CA@stromnet.se> Content-Transfer-Encoding: quoted-printable From: =?ISO-8859-1?Q?Johan_Str=F6m?= Date: Fri, 24 Aug 2007 11:03:31 +0200 To: freebsd-geom@freebsd.org, freebsd-stable@freebsd.org X-Mailer: Apple Mail (2.752.3) Cc: Subject: Re: Crashed gmirror, single disk marked SYNC and wont boot... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Aug 2007 09:03:58 -0000 On Aug 21, 2007, at 17:53 , Johan Str=F6m wrote: > On Aug 21, 2007, at 16:31 , Pawel Jakub Dawidek wrote: >> >> All in all, your partition table seems to be gone. If you created =20 >> it on >> gmirror before (gm0s1) you may still have the same partition table on >> the other half of the mirror. You can try to move it to ad6 with >> bsdlabel and verify if you can see file system inside partitions. > > Okay, tried that now.. Saved ad0s1 label, reloaded it onto ad6s1.. =20 > Now I got same partition table on ad6s1 as on ad0s1... > Trying to mount any though gives me incorrect super block... fsck =20 > cannot find any superblocks either.. > > So.. What to do now then? Just for get ad6 and start from scratch =20 > from ad2? (as i said, the data isnt very old realy)... > > Im thinking about doing complete reinstall on ad4+ad6 then.. Can I =20 > do that? fdisk both with full partition on both, create a new =20 > gmirror between ad6s1/ad4s1 (or should i go on ad4/ad6?), create =20 > slices, use dump | restore (of course with apps shutdown so no data =20= > is changed.. or at least nothing that I care about) to copy all =20 > files from ad2 to new mirror.. what do I need to do more? bsdlabel -=20= > B on both to write boot blocks? Is there anything else to think about? > Ok just for the record, I plugged both sata disks in, cleared them, =20 created a new mirror on both of them, sliced up and dump -0 -L -f - / =20= | restore -r -f - all filesystems, also bsdlabel -B. and what i =20 missed in the above thext, fdisk -B to write boot0 code.. Now its =20 booted fine on the mirror! altough, one thing that I got curious about. In the fdisk manpage it =20 says -b can be used to change the bootcode.. and that default is /=20 boot/mbr.. What is this? I checked md5 against boot0 and its not the =20 same (altough I guess it might just be some boot0 with different =20 config..). I never found any references to this mbr file in neither =20 man pages or handbook. Again, thanks for the help :) From owner-freebsd-stable@FreeBSD.ORG Fri Aug 24 09:34:49 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2DD9016A418 for ; Fri, 24 Aug 2007 09:34:49 +0000 (UTC) (envelope-from clay@milos.co.za) Received: from bart.milos.co.za (bart.milos.co.za [196.38.18.66]) by mx1.freebsd.org (Postfix) with ESMTP id D0AE713C45A for ; Fri, 24 Aug 2007 09:34:47 +0000 (UTC) (envelope-from clay@milos.co.za) Received: (qmail 55765 invoked by uid 89); 24 Aug 2007 09:36:00 -0000 Received: by simscan 1.2.0 ppid: 55753, pid: 55757, t: 2.0866s scanners: attach: 1.2.0 clamav: 0.88.7/m:43/d:3604 Received: from unknown (HELO claylaptop) (clay@milos.za.net@84.203.141.221) by bart.milos.co.za with ESMTPA; 24 Aug 2007 09:35:58 -0000 Message-ID: <00f001c7e631$fcfc2f00$0701a8c0@claylaptop> From: "Clayton Milos" To: Date: Fri, 24 Aug 2007 10:34:35 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 Subject: Re: A little story of failed raid5 (3ware 8000 series) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Aug 2007 09:34:49 -0000 > On Tue, 21 Aug 2007 08:57:22 +0400 > "Artem Kuchin" wrote: > >> Um.. it is because i did not have a map of hot swap baskets to >> conroller ports and i needed to check every driver basket to >> understand which port it sits on. I have no choise, i think. >> > > I'm just going to highlight the importance of knowing which > physical disk is which on your system. > > About a year ago I had to replace a hot-swappable disk from an > array, but then realised I had no idea which physical disk it > was as the map of the disks was rather helpfully *inside* the > case. Due to the physical setup, I had no way or removing the > cover without first powering down the server - which defeated > the whole point of paying extra for hot-swap disks. > > So yeah, be sure to label your disk bays, but be sure to put > those labels somewhere *useful*. > > -fr. > Useful like on the front of the drive bays ;-) The Areca cards have a nice function called drive identify that lights up the selected drive's LED. I think the 3ware cards have it too. -Clay From owner-freebsd-stable@FreeBSD.ORG Fri Aug 24 09:58:10 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 93DE116A417 for ; Fri, 24 Aug 2007 09:58:10 +0000 (UTC) (envelope-from clay@milos.za.net) Received: from bart.milos.co.za (bart.milos.co.za [196.38.18.66]) by mx1.freebsd.org (Postfix) with ESMTP id 36EC013C45D for ; Fri, 24 Aug 2007 09:58:08 +0000 (UTC) (envelope-from clay@milos.za.net) Received: (qmail 55578 invoked by uid 89); 24 Aug 2007 09:32:41 -0000 Received: by simscan 1.2.0 ppid: 55573, pid: 55575, t: 2.1021s scanners: attach: 1.2.0 clamav: 0.88.7/m:43/d:3604 Received: from unknown (HELO claylaptop) (clay@milos.za.net@84.203.141.221) by bart.milos.co.za with ESMTPA; 24 Aug 2007 09:32:39 -0000 Message-ID: <00c801c7e631$85e3e700$0701a8c0@claylaptop> From: "Clayton Milos" To: References: <02fe01c7e3af$d3b86ed0$0c00a8c0@Artem> <20070824095702.6fe7ee3c@mablung.edhellond.fbi.ie> Date: Fri, 24 Aug 2007 10:31:15 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 Subject: Re: A little story of failed raid5 (3ware 8000 series) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Aug 2007 09:58:10 -0000 > On Tue, 21 Aug 2007 08:57:22 +0400 > "Artem Kuchin" wrote: > >> Um.. it is because i did not have a map of hot swap baskets to >> conroller ports and i needed to check every driver basket to >> understand which port it sits on. I have no choise, i think. >> > > I'm just going to highlight the importance of knowing which > physical disk is which on your system. > > About a year ago I had to replace a hot-swappable disk from an > array, but then realised I had no idea which physical disk it > was as the map of the disks was rather helpfully *inside* the > case. Due to the physical setup, I had no way or removing the > cover without first powering down the server - which defeated > the whole point of paying extra for hot-swap disks. > > So yeah, be sure to label your disk bays, but be sure to put > those labels somewhere *useful*. > > -fr. > Useful like on the front of the drive bays ;-) The Areca cards have a nice function called drive identify that lights up the selected drive's LED. I think the 3ware cards have it too. -Clay From owner-freebsd-stable@FreeBSD.ORG Fri Aug 24 10:48:34 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E3CBC16A41A for ; Fri, 24 Aug 2007 10:48:34 +0000 (UTC) (envelope-from cyberleo@cyberleo.net) Received: from pizzabox.cyberleo.net (alpha.cyberleo.net [198.145.45.10]) by mx1.freebsd.org (Postfix) with ESMTP id A916513C45A for ; Fri, 24 Aug 2007 10:48:34 +0000 (UTC) (envelope-from cyberleo@cyberleo.net) Received: (qmail 99063 invoked from network); 24 Aug 2007 10:21:50 -0000 Received: from adsl-75-3-87-131.dsl.chcgil.sbcglobal.net (HELO ?172.16.44.14?) (cyberleo@cyberleo.net@75.3.87.131) by alpha.cyberleo.net with ESMTPA; 24 Aug 2007 10:21:50 -0000 Message-ID: <46CEB136.1090409@cyberleo.net> Date: Fri, 24 Aug 2007 05:21:42 -0500 From: CyberLeo Kitsana User-Agent: Thunderbird 2.0.0.6 (X11/20070819) MIME-Version: 1.0 To: =?ISO-8859-1?Q?Johan_Str=F6m?= References: <8039436E-1824-4C2E-915B-9069DEF23B10@stromnet.se> <20070821143136.GD1132@garage.freebsd.pl> <441B87F4-5846-441B-B6B4-34694B483C73@stromnet.se> <77098FC1-E06C-4A0C-803F-038509F5F8CA@stromnet.se> In-Reply-To: <77098FC1-E06C-4A0C-803F-038509F5F8CA@stromnet.se> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Cc: freebsd-stable@freebsd.org, freebsd-geom@freebsd.org Subject: Re: Crashed gmirror, single disk marked SYNC and wont boot... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Aug 2007 10:48:35 -0000 Johan Ström wrote: > altough, one thing that I got curious about. In the fdisk manpage it > says -b can be used to change the bootcode.. and that default is > /boot/mbr.. What is this? I checked md5 against boot0 and its not the > same (altough I guess it might just be some boot0 with different > config..). I never found any references to this mbr file in neither man > pages or handbook. boot0 is the pretty 'F1 FreeBSD' type boot menu. mbr is more like your standard MS bootloader, that just boots the active slice of the current disk. The latter is my favorite, as I despise multi-booting. -- Fuzzy love, -CyberLeo Technical Administrator CyberLeo.Net Webhosting http://www.CyberLeo.Net Furry Peace! - http://wwww.fur.com/peace/ From owner-freebsd-stable@FreeBSD.ORG Fri Aug 24 13:17:14 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 450AF16A418 for ; Fri, 24 Aug 2007 13:17:14 +0000 (UTC) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from mail-gw2.york.ac.uk (mail-gw2.york.ac.uk [144.32.128.247]) by mx1.freebsd.org (Postfix) with ESMTP id B8A9613C46A for ; Fri, 24 Aug 2007 13:17:13 +0000 (UTC) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from mail-gw6.york.ac.uk (mail-gw6.york.ac.uk [144.32.129.26]) by mail-gw2.york.ac.uk (8.13.6/8.13.6) with ESMTP id l7ODHBw8018503; Fri, 24 Aug 2007 14:17:11 +0100 (BST) Received: from buffy-128.york.ac.uk ([144.32.128.160] helo=buffy.york.ac.uk) by mail-gw6.york.ac.uk with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1IOZ2E-0004Xy-VN; Fri, 24 Aug 2007 14:17:10 +0100 Received: from buffy.york.ac.uk (localhost [127.0.0.1]) by buffy.york.ac.uk (8.14.1/8.14.1) with ESMTP id l7ODHAiB026869; Fri, 24 Aug 2007 14:17:10 +0100 (BST) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: (from ga9@localhost) by buffy.york.ac.uk (8.14.1/8.14.1/Submit) id l7ODH6hB026868; Fri, 24 Aug 2007 14:17:06 +0100 (BST) (envelope-from gavin.atkinson@ury.york.ac.uk) X-Authentication-Warning: buffy.york.ac.uk: ga9 set sender to gavin.atkinson@ury.york.ac.uk using -f From: Gavin Atkinson To: Larry Rosenman In-Reply-To: <20070801100602.Q59551@thebighonker.lerctr.org> References: <20070727093524.K20208@thebighonker.lerctr.org> <20070801160323.N14630@ury.york.ac.uk> <20070801100602.Q59551@thebighonker.lerctr.org> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Fri, 24 Aug 2007 14:17:05 +0100 Message-Id: <1187961425.26044.21.camel@buffy.york.ac.uk> Mime-Version: 1.0 X-Mailer: Evolution 2.10.1 FreeBSD GNOME Team Port X-York-MailScanner: Found to be clean X-York-MailScanner-From: gavin.atkinson@ury.york.ac.uk Cc: freebsd-stable@freebsd.org Subject: Re: Panic: Page not present: RELENG_6 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Aug 2007 13:17:14 -0000 On Wed, 2007-08-01 at 10:06 -0500, Larry Rosenman wrote: > On Wed, 1 Aug 2007, Gavin Atkinson wrote: > > > On Fri, 27 Jul 2007, Larry Rosenman wrote: > > > >> Fatal trap 12: page fault while in kernel mode > >> cpuid = 0; apic id = 00 > >> fault virtual address = 0xffff803fff800058 > >> fault code = supervisor read data, page not present > >> instruction pointer = 0x8:0xffffffff803abb0e > >> stack pointer = 0x10:0xffffffffb5ebfa40 > >> frame pointer = 0x10:0xffffffffb5ebfa90 > >> code segment = base 0x0, limit 0xfffff, type 0x1b > >> = DPL 0, pres 1, long 1, def32 0, gran 1 > >> processor eflags = interrupt enabled, resume, IOPL = 0 > >> current process = 57526 (sshd) > >> trap number = 12 > >> panic: page fault > >> cpuid = 2 > >> KDB: stack backtrace: > >> panic() at panic+0x253 > >> trap_fatal() at trap_fatal+0x2c6 > >> trap_pfault() at trap_pfault+0x243 > >> trap() at trap+0x298 > >> calltrap() at calltrap+0x5 > >> --- trap 0xc, rip = 0xffffffff803abb0e, rsp = 0xffffffffb5ebfa40, rbp = > >> 0xffffffffb5ebfa90 --- > >> pmap_remove_pages() at pmap_remove_pages+0xde > >> vmspace_exit() at vmspace_exit+0x9a > >> exit1() at exit1+0x38c > >> sys_exit() at sys_exit+0xe > >> syscall() at syscall+0x437 > >> Xfast_syscall() at Xfast_syscall+0xa8 > >> --- syscall (1, FreeBSD ELF64, sys_exit), rip = 0x8016a096c, rsp = > >> 0x7fffffffc038, rbp = 0x53c240 --- > >> Uptime: 36d18h48m54s > > > > How recent is the source used to build this kernel? > > > June 18th. I don't think it is what I suspected it might be then. Can you recreate it with newer sources? Gavin From owner-freebsd-stable@FreeBSD.ORG Fri Aug 24 13:18:32 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A3A9C16A420 for ; Fri, 24 Aug 2007 13:18:32 +0000 (UTC) (envelope-from ler@lerctr.org) Received: from thebighonker.lerctr.org (thebighonker.lerctr.org [192.147.25.65]) by mx1.freebsd.org (Postfix) with ESMTP id 86A0913C45A for ; Fri, 24 Aug 2007 13:18:32 +0000 (UTC) (envelope-from ler@lerctr.org) Received: from thebighonker.lerctr.org ([192.147.25.65]:61899) by thebighonker.lerctr.org with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.67 (FreeBSD)) (envelope-from ) id 1IOZ3W-0001sZ-KO; Fri, 24 Aug 2007 08:18:32 -0500 Date: Fri, 24 Aug 2007 08:18:28 -0500 (CDT) From: Larry Rosenman To: Gavin Atkinson In-Reply-To: <1187961425.26044.21.camel@buffy.york.ac.uk> Message-ID: <20070824081755.H7203@thebighonker.lerctr.org> References: <20070727093524.K20208@thebighonker.lerctr.org> <20070801160323.N14630@ury.york.ac.uk> <20070801100602.Q59551@thebighonker.lerctr.org> <1187961425.26044.21.camel@buffy.york.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Score: -4.4 (----) X-LERCTR-Spam-Score: -4.4 (----) X-Spam-Report: SpamScore (-4.4/5.0) ALL_TRUSTED=-1.8,BAYES_00=-2.599 X-LERCTR-Spam-Report: SpamScore (-4.4/5.0) ALL_TRUSTED=-1.8,BAYES_00=-2.599 DomainKey-Status: no signature Cc: freebsd-stable@freebsd.org Subject: Re: Panic: Page not present: RELENG_6 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Aug 2007 13:18:32 -0000 On Fri, 24 Aug 2007, Gavin Atkinson wrote: > On Wed, 2007-08-01 at 10:06 -0500, Larry Rosenman wrote: >> On Wed, 1 Aug 2007, Gavin Atkinson wrote: >> >>> On Fri, 27 Jul 2007, Larry Rosenman wrote: >>> >>>> Fatal trap 12: page fault while in kernel mode >>>> cpuid = 0; apic id = 00 >>>> fault virtual address = 0xffff803fff800058 >>>> fault code = supervisor read data, page not present >>>> instruction pointer = 0x8:0xffffffff803abb0e >>>> stack pointer = 0x10:0xffffffffb5ebfa40 >>>> frame pointer = 0x10:0xffffffffb5ebfa90 >>>> code segment = base 0x0, limit 0xfffff, type 0x1b >>>> = DPL 0, pres 1, long 1, def32 0, gran 1 >>>> processor eflags = interrupt enabled, resume, IOPL = 0 >>>> current process = 57526 (sshd) >>>> trap number = 12 >>>> panic: page fault >>>> cpuid = 2 >>>> KDB: stack backtrace: >>>> panic() at panic+0x253 >>>> trap_fatal() at trap_fatal+0x2c6 >>>> trap_pfault() at trap_pfault+0x243 >>>> trap() at trap+0x298 >>>> calltrap() at calltrap+0x5 >>>> --- trap 0xc, rip = 0xffffffff803abb0e, rsp = 0xffffffffb5ebfa40, rbp = >>>> 0xffffffffb5ebfa90 --- >>>> pmap_remove_pages() at pmap_remove_pages+0xde >>>> vmspace_exit() at vmspace_exit+0x9a >>>> exit1() at exit1+0x38c >>>> sys_exit() at sys_exit+0xe >>>> syscall() at syscall+0x437 >>>> Xfast_syscall() at Xfast_syscall+0xa8 >>>> --- syscall (1, FreeBSD ELF64, sys_exit), rip = 0x8016a096c, rsp = >>>> 0x7fffffffc038, rbp = 0x53c240 --- >>>> Uptime: 36d18h48m54s >>> >>> How recent is the source used to build this kernel? >>> >> June 18th. > > I don't think it is what I suspected it might be then. Can you recreate > it with newer sources? > > Gavin > I haven't seen it again, and the system is currently running sources from: FreeBSD thebighonker.lerctr.org 6.2-STABLE FreeBSD 6.2-STABLE #1: Sat Aug 4 14:32:38 CDT 2007 root@thebighonker.lerctr.org:/usr/obj/usr/src/sys/THEBIGHONKER amd64 August 4. Thanks! LER -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: ler@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 From owner-freebsd-stable@FreeBSD.ORG Fri Aug 24 14:58:56 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4D51116A419; Fri, 24 Aug 2007 14:58:56 +0000 (UTC) (envelope-from johan@stromnet.se) Received: from av6-1-sn3.vrr.skanova.net (av6-1-sn3.vrr.skanova.net [81.228.9.179]) by mx1.freebsd.org (Postfix) with ESMTP id 026EA13C46C; Fri, 24 Aug 2007 14:58:55 +0000 (UTC) (envelope-from johan@stromnet.se) Received: by av6-1-sn3.vrr.skanova.net (Postfix, from userid 502) id 6895938547; Fri, 24 Aug 2007 16:38:46 +0200 (CEST) Received: from smtp3-2-sn3.vrr.skanova.net (smtp3-2-sn3.vrr.skanova.net [81.228.9.102]) by av6-1-sn3.vrr.skanova.net (Postfix) with ESMTP id 322F238388; Fri, 24 Aug 2007 16:38:46 +0200 (CEST) Received: from phomca.stromnet.se (90-224-172-102-no129.tbcn.telia.com [90.224.172.102]) by smtp3-2-sn3.vrr.skanova.net (Postfix) with ESMTP id D400837E42; Fri, 24 Aug 2007 16:38:45 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by phomca.stromnet.se (Postfix) with ESMTP id 82BC8B826; Fri, 24 Aug 2007 16:38:45 +0200 (CEST) X-Virus-Scanned: amavisd-new at stromnet.se Received: from phomca.stromnet.se ([127.0.0.1]) by localhost (phomca.stromnet.se [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0nAUq8K6BapJ; Fri, 24 Aug 2007 16:38:42 +0200 (CEST) Received: from [172.28.1.102] (jstrom-mb.stromnet.se [172.28.1.102]) by phomca.stromnet.se (Postfix) with ESMTP id 94961B824; Fri, 24 Aug 2007 16:38:42 +0200 (CEST) In-Reply-To: <46CEB136.1090409@cyberleo.net> References: <8039436E-1824-4C2E-915B-9069DEF23B10@stromnet.se> <20070821143136.GD1132@garage.freebsd.pl> <441B87F4-5846-441B-B6B4-34694B483C73@stromnet.se> <77098FC1-E06C-4A0C-803F-038509F5F8CA@stromnet.se> <46CEB136.1090409@cyberleo.net> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed Message-Id: <41D57A88-7C25-43C2-8426-1760EA976BCB@stromnet.se> Content-Transfer-Encoding: quoted-printable From: =?ISO-8859-1?Q?Johan_Str=F6m?= Date: Fri, 24 Aug 2007 16:38:25 +0200 To: CyberLeo Kitsana X-Mailer: Apple Mail (2.752.3) Cc: freebsd-stable@freebsd.org, freebsd-geom@freebsd.org Subject: Re: Crashed gmirror, single disk marked SYNC and wont boot... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Aug 2007 14:58:56 -0000 On Aug 24, 2007, at 12:21 , CyberLeo Kitsana wrote: > Johan Str=F6m wrote: >> altough, one thing that I got curious about. In the fdisk manpage it >> says -b can be used to change the bootcode.. and that default is >> /boot/mbr.. What is this? I checked md5 against boot0 and its not the >> same (altough I guess it might just be some boot0 with different >> config..). I never found any references to this mbr file in =20 >> neither man >> pages or handbook. > > boot0 is the pretty 'F1 FreeBSD' type boot menu. mbr is more like your > standard MS bootloader, that just boots the active slice of the =20 > current > disk. > > The latter is my favorite, as I despise multi-booting. I see. Shouldn't this info be in the manpages/handbook somewhere? =20 Like referenced from boot0cfgs manpage or something, and in the boot =20 section in handbook. From owner-freebsd-stable@FreeBSD.ORG Fri Aug 24 15:47:45 2007 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 55E8816A420 for ; Fri, 24 Aug 2007 15:47:45 +0000 (UTC) (envelope-from fjwcash+freebsd@gmail.com) Received: from smtp.sd73.bc.ca (smtp.sd73.bc.ca [142.24.13.140]) by mx1.freebsd.org (Postfix) with ESMTP id 2E29113C468 for ; Fri, 24 Aug 2007 15:47:44 +0000 (UTC) (envelope-from fjwcash+freebsd@gmail.com) Received: from localhost (localhost [127.0.0.1]) by localhost.sd73.bc.ca (Postfix) with ESMTP id A15781A000B1C for ; Fri, 24 Aug 2007 08:17:22 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at smtp.sd73.bc.ca Received: from smtp.sd73.bc.ca ([127.0.0.1]) by localhost (smtp.sd73.bc.ca [127.0.0.1]) (amavisd-new, port 10024) with LMTP id Z5UocScCSS0h for ; Fri, 24 Aug 2007 08:17:20 -0700 (PDT) Received: from coal (s10.sbo [192.168.0.10]) by smtp.sd73.bc.ca (Postfix) with ESMTP id 3ACE61A000B1E for ; Fri, 24 Aug 2007 08:17:20 -0700 (PDT) From: Freddie Cash Organization: School District 73 To: stable@freebsd.org Date: Fri, 24 Aug 2007 08:17:18 -0700 User-Agent: KMail/1.9.7 References: <20070824095702.6fe7ee3c@mablung.edhellond.fbi.ie> <00c801c7e631$85e3e700$0701a8c0@claylaptop> In-Reply-To: <00c801c7e631$85e3e700$0701a8c0@claylaptop> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200708240817.19113.fjwcash+freebsd@gmail.com> Cc: Subject: Re: A little story of failed raid5 (3ware 8000 series) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Aug 2007 15:47:45 -0000 On August 24, 2007 02:31 am Clayton Milos wrote: > > On Tue, 21 Aug 2007 08:57:22 +0400 > > > > "Artem Kuchin" wrote: > >> Um.. it is because i did not have a map of hot swap baskets to > >> conroller ports and i needed to check every driver basket to > >> understand which port it sits on. I have no choise, i think. > > > > I'm just going to highlight the importance of knowing which > > physical disk is which on your system. > > > > About a year ago I had to replace a hot-swappable disk from an > > array, but then realised I had no idea which physical disk it > > was as the map of the disks was rather helpfully *inside* the > > case. Due to the physical setup, I had no way or removing the > > cover without first powering down the server - which defeated > > the whole point of paying extra for hot-swap disks. > > > > So yeah, be sure to label your disk bays, but be sure to put > > those labels somewhere *useful*. > > > > -fr. > > Useful like on the front of the drive bays ;-) > The Areca cards have a nice function called drive identify that lights > up the selected drive's LED. I think the 3ware cards have it too. That's only useful if the drive LEDs are configured to correctly match the port. :) We've had custom built servers with 4 drive bays arrive with the LEDs either not connected, or connected to different ports on the RAID controller than the drives were on. Very confusing until we started double-checking the connections when the servers arrived. -- Freddie Cash, LPIC-2 CCNT CCLP Network Support Technician School District 73 (250) 377-HELP [377-4357] fjwcash+freebsd@gmail.com From owner-freebsd-stable@FreeBSD.ORG Fri Aug 24 17:38:29 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5279916A418 for ; Fri, 24 Aug 2007 17:38:29 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id 0C3F913C45A for ; Fri, 24 Aug 2007 17:38:28 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from phobos.samsco.home (phobos.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.8/8.13.8) with ESMTP id l7OHcHcZ095593; Fri, 24 Aug 2007 11:38:20 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <46CF1789.4060105@samsco.org> Date: Fri, 24 Aug 2007 11:38:17 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.6) Gecko/20070802 SeaMonkey/1.1.4 MIME-Version: 1.0 To: Feargal Reilly References: <02fe01c7e3af$d3b86ed0$0c00a8c0@Artem> <20070824095702.6fe7ee3c@mablung.edhellond.fbi.ie> In-Reply-To: <20070824095702.6fe7ee3c@mablung.edhellond.fbi.ie> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (pooker.samsco.org [168.103.85.57]); Fri, 24 Aug 2007 11:38:20 -0600 (MDT) X-Spam-Status: No, score=-1.4 required=5.5 tests=ALL_TRUSTED autolearn=failed version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org Cc: freebsd-stable@freebsd.org Subject: Re: A little story of failed raid5 (3ware 8000 series) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Aug 2007 17:38:29 -0000 Feargal Reilly wrote: > On Tue, 21 Aug 2007 08:57:22 +0400 > "Artem Kuchin" wrote: > >> Um.. it is because i did not have a map of hot swap baskets to >> conroller ports and i needed to check every driver basket to >> understand which port it sits on. I have no choise, i think. >> > > I'm just going to highlight the importance of knowing which > physical disk is which on your system. > > About a year ago I had to replace a hot-swappable disk from an > array, but then realised I had no idea which physical disk it > was as the map of the disks was rather helpfully *inside* the > case. Due to the physical setup, I had no way or removing the > cover without first powering down the server - which defeated > the whole point of paying extra for hot-swap disks. > > So yeah, be sure to label your disk bays, but be sure to put > those labels somewhere *useful*. > > -fr. > Most controllers have a function to "blink LED" so you can discover the mapping. Just about every management app that I know of does (yes, they do exist for FreeBSD from many vendors!), and many also have the feature in their BIOS. Scott From owner-freebsd-stable@FreeBSD.ORG Fri Aug 24 18:31:36 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 526E216A419 for ; Fri, 24 Aug 2007 18:31:36 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 0EF7713C45E for ; Fri, 24 Aug 2007 18:31:35 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1IOdwL-0002Uc-Pa for freebsd-stable@freebsd.org; Fri, 24 Aug 2007 20:31:25 +0200 Received: from r5j156.net.upc.cz ([86.49.9.156]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 24 Aug 2007 20:31:25 +0200 Received: from gamato by r5j156.net.upc.cz with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 24 Aug 2007 20:31:25 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: martinko Date: Fri, 24 Aug 2007 20:31:14 +0200 Lines: 28 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: r5j156.net.upc.cz User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.6) Gecko/20070821 SeaMonkey/1.1.4 In-Reply-To: Sender: news Subject: Re: Recent PAM changes worth an UPDATING entry? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Aug 2007 18:31:36 -0000 Doug Barton wrote: > Howdy, > > I just rebuilt and installed my world on my 6-stable box, and ran into a > snag. Like a lot of users I use -DNO_CLEAN in buildworld since this is a > very slow box that I use mostly as a file/dns server. After rebooting I > could ssh in ok (probably because I don't use PAM for sshd) but couldn't > su, or log in at the console. > > After looking at the errors, I figured out that I needed to completely > recompile stuff related to PAM. Just to be on the safe side I did > libpam, login, su, and getty. After that I was able to log in normally > from the console, and su from either terminal. > > IMO this is worth an entry in UPDATING since I probably won't be the > only user who stumbles across this. > > Doug > Doug, Could it possibly be related to the following issue of mine ?? : http://lists.freebsd.org/pipermail/freebsd-questions/2007-July/153137.html Cheers, Martin From owner-freebsd-stable@FreeBSD.ORG Fri Aug 24 19:40:20 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D8E0016A473 for ; Fri, 24 Aug 2007 19:40:20 +0000 (UTC) (envelope-from elias.hartvigson@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.237]) by mx1.freebsd.org (Postfix) with ESMTP id 7FC1E13C48E for ; Fri, 24 Aug 2007 19:40:20 +0000 (UTC) (envelope-from elias.hartvigson@gmail.com) Received: by wr-out-0506.google.com with SMTP id 70so674640wra for ; Fri, 24 Aug 2007 12:40:19 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=DIkPZ3h9QZQqNYJ+ofB6gH6+7AD5qKfQMgzsZF1do5WtC0n9PVNMFaUgFKXAgC93LZA3W+qyjPCfwP+KWMvwfKJ5C20jYyQxXYDgMHD7kgdkoNEJouio3D0VEY0LzbI7yn5mufH1Y0RpXTSnGwv+ZneXKAUP/j5SLzl7dd1u/xk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=KS30PaCnY8bM4Ur4IJchLgmw7LFFPTBC040GOe5fnroCOdiXdRB82hRLgdT6ChQXExxf6LH0oEdcILWVHIhXpyV8w0XqC6jnjn4wY5uwNQmBeKuPHL5yFgd9tAHhKa9RPm2HNN5V7LpkTan/xH5o9VgLzLw+EkLHlk02jaFQbaQ= Received: by 10.90.93.6 with SMTP id q6mr9336925agb.1187982820833; Fri, 24 Aug 2007 12:13:40 -0700 (PDT) Received: by 10.100.173.16 with HTTP; Fri, 24 Aug 2007 12:13:40 -0700 (PDT) Message-ID: Date: Fri, 24 Aug 2007 21:13:40 +0200 From: "Elias Hartvigson" To: "Scott Long" In-Reply-To: <46CF1789.4060105@samsco.org> MIME-Version: 1.0 References: <02fe01c7e3af$d3b86ed0$0c00a8c0@Artem> <20070824095702.6fe7ee3c@mablung.edhellond.fbi.ie> <46CF1789.4060105@samsco.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Feargal Reilly , freebsd-stable@freebsd.org Subject: Re: A little story of failed raid5 (3ware 8000 series) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Aug 2007 19:40:21 -0000 =C4r precis nyinflyttad i G=F6teborg, s=E5 jag vet inte riktigt var Linn=E9= staden ligger, sj=E4lv bor jag vid guldheden ett stenkast fr=E5n wavrinsky platsen= . F=F6rmiddagen passar mig b=E4st ocks=E5 d=E5 jag =E4r upptagen p=E5 em :) On 8/24/07, Scott Long wrote: > > Feargal Reilly wrote: > > On Tue, 21 Aug 2007 08:57:22 +0400 > > "Artem Kuchin" wrote: > > > >> Um.. it is because i did not have a map of hot swap baskets to > >> conroller ports and i needed to check every driver basket to > >> understand which port it sits on. I have no choise, i think. > >> > > > > I'm just going to highlight the importance of knowing which > > physical disk is which on your system. > > > > About a year ago I had to replace a hot-swappable disk from an > > array, but then realised I had no idea which physical disk it > > was as the map of the disks was rather helpfully *inside* the > > case. Due to the physical setup, I had no way or removing the > > cover without first powering down the server - which defeated > > the whole point of paying extra for hot-swap disks. > > > > So yeah, be sure to label your disk bays, but be sure to put > > those labels somewhere *useful*. > > > > -fr. > > > > Most controllers have a function to "blink LED" so you can discover > the mapping. Just about every management app that I know of does (yes, > they do exist for FreeBSD from many vendors!), and many also have the > feature in their BIOS. > > Scott > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-stable@FreeBSD.ORG Fri Aug 24 20:02:07 2007 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C553A16A474 for ; Fri, 24 Aug 2007 20:02:07 +0000 (UTC) (envelope-from clay@milos.co.za) Received: from bart.milos.co.za (bart.milos.co.za [196.38.18.66]) by mx1.freebsd.org (Postfix) with ESMTP id 6B57613C48A for ; Fri, 24 Aug 2007 20:02:05 +0000 (UTC) (envelope-from clay@milos.co.za) Received: (qmail 78380 invoked by uid 89); 24 Aug 2007 19:36:30 -0000 Received: by simscan 1.2.0 ppid: 78375, pid: 78377, t: 0.5453s scanners: attach: 1.2.0 clamav: 0.88.7/m:43/d:3604 Received: from unknown (HELO claylaptop) (clay@milos.za.net@84.203.41.94) by bart.milos.co.za with ESMTPA; 24 Aug 2007 19:36:29 -0000 Message-ID: <003101c7e685$e74005c0$0401a8c0@claylaptop> From: "Clayton Milos" To: References: <20070824095702.6fe7ee3c@mablung.edhellond.fbi.ie><00c801c7e631$85e3e700$0701a8c0@claylaptop> <200708240817.19113.fjwcash+freebsd@gmail.com> Date: Fri, 24 Aug 2007 19:24:24 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 Cc: Subject: Re: A little story of failed raid5 (3ware 8000 series) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Aug 2007 20:02:07 -0000 > On August 24, 2007 02:31 am Clayton Milos wrote: >> > On Tue, 21 Aug 2007 08:57:22 +0400 >> > >> > "Artem Kuchin" wrote: >> >> Um.. it is because i did not have a map of hot swap baskets to >> >> conroller ports and i needed to check every driver basket to >> >> understand which port it sits on. I have no choise, i think. >> > >> > I'm just going to highlight the importance of knowing which >> > physical disk is which on your system. >> > >> > About a year ago I had to replace a hot-swappable disk from an >> > array, but then realised I had no idea which physical disk it >> > was as the map of the disks was rather helpfully *inside* the >> > case. Due to the physical setup, I had no way or removing the >> > cover without first powering down the server - which defeated >> > the whole point of paying extra for hot-swap disks. >> > >> > So yeah, be sure to label your disk bays, but be sure to put >> > those labels somewhere *useful*. >> > >> > -fr. >> >> Useful like on the front of the drive bays ;-) >> The Areca cards have a nice function called drive identify that lights >> up the selected drive's LED. I think the 3ware cards have it too. > > That's only useful if the drive LEDs are configured to correctly match the > port. :) We've had custom built servers with 4 drive bays arrive with > the LEDs either not connected, or connected to different ports on the > RAID controller than the drives were on. Very confusing until we started > double-checking the connections when the servers arrived. People that do that should be lynched! It's that kind of poor workmanship that would make me never touch their gear again. Then again if I had to discover this when I replaced the wrong drive in a failed array I'd be doing the lynching myself! -Clay From owner-freebsd-stable@FreeBSD.ORG Fri Aug 24 20:14:46 2007 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 99C3816A417 for ; Fri, 24 Aug 2007 20:14:46 +0000 (UTC) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.freebsd.org (Postfix) with ESMTP id 6536113C461 for ; Fri, 24 Aug 2007 20:14:46 +0000 (UTC) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.14.1/8.13.7) with ESMTP id l7OK4bZr085583 for ; Fri, 24 Aug 2007 13:04:37 -0700 (PDT) Received: (from dillon@localhost) by apollo.backplane.com (8.14.1/8.13.4/Submit) id l7OK4bOg085582; Fri, 24 Aug 2007 13:04:37 -0700 (PDT) Date: Fri, 24 Aug 2007 13:04:37 -0700 (PDT) From: Matthew Dillon Message-Id: <200708242004.l7OK4bOg085582@apollo.backplane.com> To: References: <20070824095702.6fe7ee3c@mablung.edhellond.fbi.ie><00c801c7e631$85e3e700$0701a8c0@claylaptop> <200708240817.19113.fjwcash+freebsd@gmail.com> <003101c7e685$e74005c0$0401a8c0@claylaptop> Cc: Subject: Re: A little story of failed raid5 (3ware 8000 series) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Aug 2007 20:14:46 -0000 A friend of mine once told me that the only worthwhile RAID systems are the ones that email you a detailed message when something goes south. -Matt From owner-freebsd-stable@FreeBSD.ORG Fri Aug 24 20:53:58 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 024AE16A419 for ; Fri, 24 Aug 2007 20:53:58 +0000 (UTC) (envelope-from carloshpf@oi.com.br) Received: from smtp6.oi.com.br (smtp6.oi.com.br [200.222.115.69]) by mx1.freebsd.org (Postfix) with ESMTP id BC1FF13C458 for ; Fri, 24 Aug 2007 20:53:57 +0000 (UTC) (envelope-from carloshpf@oi.com.br) Received: from smtp1.oi.com.br (smtp1.oi.com.br [200.222.115.16]) by smtp6.oi.com.br (Postfix) with ESMTP id DAD6120FC07 for ; Fri, 24 Aug 2007 17:53:59 -0300 (BRT) Received: from smtp1.oi.com.br (localhost.localdomain [127.0.0.1]) by smtp1.oi.com.br (Postfix) with ESMTP id CFA768020DED for ; Fri, 24 Aug 2007 17:23:46 -0300 (BRT) Received: from [192.168.0.152] (unknown [189.12.114.222]) by smtp1.oi.com.br (Postfix) with ESMTP id 8C7F180202C6 for ; Fri, 24 Aug 2007 17:13:09 -0300 (BRT) Message-ID: <46CF3BBC.1040206@oi.com.br> Date: Fri, 24 Aug 2007 17:12:44 -0300 From: Carlos Porto Filho User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: error - snmp_bridge X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Aug 2007 20:53:58 -0000 During the make buildworld (6stable) i got this: Change begemotBridgeBaseName > bridge_oid.h line 31: '(' expected at begin of node context: " TruthValue ENUM ( *** Error code 1 Stop in /usr/src/usr.sbin/bsnmpd/modules/snmp_bridge. . . . any idea? tia From owner-freebsd-stable@FreeBSD.ORG Fri Aug 24 21:22:52 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6D1D016A420 for ; Fri, 24 Aug 2007 21:22:52 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mail.cksoft.de (mail.cksoft.de [62.111.66.27]) by mx1.freebsd.org (Postfix) with ESMTP id 2D34213C457 for ; Fri, 24 Aug 2007 21:22:52 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from localhost (amavis.str.cksoft.de [192.168.74.71]) by mail.cksoft.de (Postfix) with ESMTP id 149D641C691; Fri, 24 Aug 2007 23:05:06 +0200 (CEST) X-Virus-Scanned: amavisd-new at cksoft.de Received: from mail.cksoft.de ([62.111.66.27]) by localhost (amavis.str.cksoft.de [192.168.74.71]) (amavisd-new, port 10024) with ESMTP id Xf2MY1vwbahp; Fri, 24 Aug 2007 23:05:05 +0200 (CEST) Received: by mail.cksoft.de (Postfix, from userid 66) id 9DC0741C6A1; Fri, 24 Aug 2007 23:05:05 +0200 (CEST) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id 50FCC444885; Fri, 24 Aug 2007 21:04:45 +0000 (UTC) Date: Fri, 24 Aug 2007 21:04:45 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: Carlos Porto Filho In-Reply-To: <46CF3BBC.1040206@oi.com.br> Message-ID: <20070824210217.H87821@maildrop.int.zabbadoz.net> References: <46CF3BBC.1040206@oi.com.br> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: error - snmp_bridge X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Aug 2007 21:22:52 -0000 On Fri, 24 Aug 2007, Carlos Porto Filho wrote: Hi, > During the make buildworld (6stable) i got this: > Change begemotBridgeBaseName > bridge_oid.h > line 31: '(' expected at begin of node > context: " TruthValue ENUM ( > *** Error code 1 > Stop in /usr/src/usr.sbin/bsnmpd/modules/snmp_bridge. > > . . . > > any idea? Are you sure your entire source tree is in sync? -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT Software is harder than hardware so better get it right the first time. From owner-freebsd-stable@FreeBSD.ORG Fri Aug 24 22:24:35 2007 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7286116A417; Fri, 24 Aug 2007 22:24:35 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id 33BC613C428; Fri, 24 Aug 2007 22:24:35 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.13.8/8.13.8) with ESMTP id l7OMOYbL023234; Fri, 24 Aug 2007 18:24:34 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-stable.sentex.ca (freebsd-stable.sentex.ca [64.7.128.103]) by smtp2.sentex.ca (8.14.1/8.14.1) with ESMTP id l7OMOYik089972; Fri, 24 Aug 2007 18:24:34 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-stable.sentex.ca (Postfix, from userid 666) id 6D02A241A2; Fri, 24 Aug 2007 18:24:39 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20070824222439.6D02A241A2@freebsd-stable.sentex.ca> Date: Fri, 24 Aug 2007 18:24:39 -0400 (EDT) X-Virus-Scanned: ClamAV version 0.91.1, clamav-milter version 0.91.1 on news X-Virus-Status: Clean Cc: Subject: [releng_6 tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Aug 2007 22:24:35 -0000 TB --- 2007-08-24 20:32:50 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2007-08-24 20:32:50 - starting RELENG_6 tinderbox run for amd64/amd64 TB --- 2007-08-24 20:32:50 - cleaning the object tree TB --- 2007-08-24 20:33:30 - checking out the source tree TB --- 2007-08-24 20:33:30 - cd /tinderbox/RELENG_6/amd64/amd64 TB --- 2007-08-24 20:33:30 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_6 src TB --- 2007-08-24 20:43:48 - building world (CFLAGS=-O2 -pipe) TB --- 2007-08-24 20:43:48 - cd /src TB --- 2007-08-24 20:43:48 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> stage 5.1: building 32 bit shim libraries TB --- 2007-08-24 22:18:05 - generating LINT kernel config TB --- 2007-08-24 22:18:05 - cd /src/sys/amd64/conf TB --- 2007-08-24 22:18:05 - /usr/bin/make -B LINT TB --- 2007-08-24 22:18:05 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2007-08-24 22:18:05 - cd /src TB --- 2007-08-24 22:18:05 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Fri Aug 24 22:18:05 UTC 2007 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/dev/ath -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -pg -mprofiler-epilogue /src/sys/dev/mcd/mcd_isa.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/dev/ath -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/dev/md/md.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/dev/ath -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/dev/mem/memdev.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/dev/ath -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/dev/mfi/mfi.c /src/sys/dev/mfi/mfi.c: In function `mfi_ldprobe': /src/sys/dev/mfi/mfi.c:877: error: `SA_XLOCKED' undeclared (first use in this function) /src/sys/dev/mfi/mfi.c:877: error: (Each undeclared identifier is reported only once /src/sys/dev/mfi/mfi.c:877: error: for each function it appears in.) *** Error code 1 Stop in /obj/amd64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2007-08-24 22:24:39 - WARNING: /usr/bin/make returned exit code 1 TB --- 2007-08-24 22:24:39 - ERROR: failed to build lint kernel TB --- 2007-08-24 22:24:39 - tinderbox aborted TB --- 1.61 user 4.85 system 6708.82 real http://tinderbox.des.no/tinderbox-releng_6-RELENG_6-amd64-amd64.full From owner-freebsd-stable@FreeBSD.ORG Fri Aug 24 23:45:56 2007 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E10BA16A419; Fri, 24 Aug 2007 23:45:55 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.freebsd.org (Postfix) with ESMTP id A34BF13C469; Fri, 24 Aug 2007 23:45:55 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by smarthost2.sentex.ca (8.14.1/8.13.8) with ESMTP id l7ONjsG6001929; Fri, 24 Aug 2007 19:45:54 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-stable.sentex.ca (freebsd-stable.sentex.ca [64.7.128.103]) by smtp1.sentex.ca (8.14.1/8.14.1) with ESMTP id l7ONjs4j089913; Fri, 24 Aug 2007 19:45:54 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-stable.sentex.ca (Postfix, from userid 666) id A9A8D241A2; Fri, 24 Aug 2007 19:46:09 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20070824234609.A9A8D241A2@freebsd-stable.sentex.ca> Date: Fri, 24 Aug 2007 19:46:09 -0400 (EDT) X-Virus-Scanned: ClamAV version devel-20070102, clamav-milter version devel-111206 on clamscanner4 X-Virus-Status: Clean Cc: Subject: [releng_6 tinderbox] failure on i386/i386 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Aug 2007 23:45:56 -0000 TB --- 2007-08-24 22:24:39 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2007-08-24 22:24:39 - starting RELENG_6 tinderbox run for i386/i386 TB --- 2007-08-24 22:24:39 - cleaning the object tree TB --- 2007-08-24 22:25:16 - checking out the source tree TB --- 2007-08-24 22:25:16 - cd /tinderbox/RELENG_6/i386/i386 TB --- 2007-08-24 22:25:16 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_6 src TB --- 2007-08-24 22:35:27 - building world (CFLAGS=-O2 -pipe) TB --- 2007-08-24 22:35:27 - cd /src TB --- 2007-08-24 22:35:27 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2007-08-24 23:39:15 - generating LINT kernel config TB --- 2007-08-24 23:39:15 - cd /src/sys/i386/conf TB --- 2007-08-24 23:39:15 - /usr/bin/make -B LINT TB --- 2007-08-24 23:39:15 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2007-08-24 23:39:15 - cd /src TB --- 2007-08-24 23:39:15 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Fri Aug 24 23:39:15 UTC 2007 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/dev/ath -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -ffreestanding -pg -mprofiler-epilogue /src/sys/dev/mcd/mcd_isa.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/dev/ath -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/dev/md/md.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/dev/ath -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/dev/mem/memdev.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/dev/ath -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/dev/mfi/mfi.c /src/sys/dev/mfi/mfi.c: In function `mfi_ldprobe': /src/sys/dev/mfi/mfi.c:877: error: `SA_XLOCKED' undeclared (first use in this function) /src/sys/dev/mfi/mfi.c:877: error: (Each undeclared identifier is reported only once /src/sys/dev/mfi/mfi.c:877: error: for each function it appears in.) *** Error code 1 Stop in /obj/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2007-08-24 23:46:09 - WARNING: /usr/bin/make returned exit code 1 TB --- 2007-08-24 23:46:09 - ERROR: failed to build lint kernel TB --- 2007-08-24 23:46:09 - tinderbox aborted TB --- 1.38 user 3.90 system 4889.85 real http://tinderbox.des.no/tinderbox-releng_6-RELENG_6-i386-i386.full From owner-freebsd-stable@FreeBSD.ORG Sat Aug 25 01:09:34 2007 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9C42A16A468; Sat, 25 Aug 2007 01:09:34 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id 593F413C458; Sat, 25 Aug 2007 01:09:34 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1c.sentex.ca [64.7.153.10]) by smarthost1.sentex.ca (8.13.8/8.13.8) with ESMTP id l7P19XnD032185; Fri, 24 Aug 2007 21:09:33 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-stable.sentex.ca (freebsd-stable.sentex.ca [64.7.128.103]) by smtp1.sentex.ca (8.14.1/8.14.1) with ESMTP id l7P19Xlg052345; Fri, 24 Aug 2007 21:09:33 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-stable.sentex.ca (Postfix, from userid 666) id 18202241A2; Fri, 24 Aug 2007 21:09:49 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20070825010949.18202241A2@freebsd-stable.sentex.ca> Date: Fri, 24 Aug 2007 21:09:49 -0400 (EDT) X-Virus-Scanned: ClamAV version devel-20070102, clamav-milter version devel-111206 on clamscanner3 X-Virus-Status: Clean Cc: Subject: [releng_6 tinderbox] failure on i386/pc98 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Aug 2007 01:09:34 -0000 TB --- 2007-08-24 23:46:09 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2007-08-24 23:46:09 - starting RELENG_6 tinderbox run for i386/pc98 TB --- 2007-08-24 23:46:09 - cleaning the object tree TB --- 2007-08-24 23:46:45 - checking out the source tree TB --- 2007-08-24 23:46:45 - cd /tinderbox/RELENG_6/i386/pc98 TB --- 2007-08-24 23:46:45 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_6 src TB --- 2007-08-25 00:00:42 - building world (CFLAGS=-O2 -pipe) TB --- 2007-08-25 00:00:42 - cd /src TB --- 2007-08-25 00:00:42 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2007-08-25 01:04:32 - generating LINT kernel config TB --- 2007-08-25 01:04:32 - cd /src/sys/pc98/conf TB --- 2007-08-25 01:04:32 - /usr/bin/make -B LINT TB --- 2007-08-25 01:04:32 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2007-08-25 01:04:32 - cd /src TB --- 2007-08-25 01:04:32 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sat Aug 25 01:04:32 UTC 2007 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/dev/ath -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -ffreestanding -pg -mprofiler-epilogue /src/sys/dev/mcd/mcd_isa.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/dev/ath -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/dev/md/md.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/dev/ath -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/dev/mem/memdev.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/dev/ath -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/dev/mfi/mfi.c /src/sys/dev/mfi/mfi.c: In function `mfi_ldprobe': /src/sys/dev/mfi/mfi.c:877: error: `SA_XLOCKED' undeclared (first use in this function) /src/sys/dev/mfi/mfi.c:877: error: (Each undeclared identifier is reported only once /src/sys/dev/mfi/mfi.c:877: error: for each function it appears in.) *** Error code 1 Stop in /obj/pc98/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2007-08-25 01:09:48 - WARNING: /usr/bin/make returned exit code 1 TB --- 2007-08-25 01:09:48 - ERROR: failed to build lint kernel TB --- 2007-08-25 01:09:48 - tinderbox aborted TB --- 1.23 user 4.04 system 5019.04 real http://tinderbox.des.no/tinderbox-releng_6-RELENG_6-i386-pc98.full From owner-freebsd-stable@FreeBSD.ORG Sat Aug 25 02:32:38 2007 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0AECE16A41A; Sat, 25 Aug 2007 02:32:38 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.freebsd.org (Postfix) with ESMTP id D944E13C465; Sat, 25 Aug 2007 02:32:37 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by smarthost2.sentex.ca (8.14.1/8.13.8) with ESMTP id l7P2Wbon009654; Fri, 24 Aug 2007 22:32:37 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-stable.sentex.ca (freebsd-stable.sentex.ca [64.7.128.103]) by smtp1.sentex.ca (8.14.1/8.14.1) with ESMTP id l7P2WaoI012925; Fri, 24 Aug 2007 22:32:36 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-stable.sentex.ca (Postfix, from userid 666) id 642FB241A2; Fri, 24 Aug 2007 22:32:52 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20070825023252.642FB241A2@freebsd-stable.sentex.ca> Date: Fri, 24 Aug 2007 22:32:52 -0400 (EDT) X-Virus-Scanned: ClamAV version devel-20070102, clamav-milter version devel-111206 on clamscanner4 X-Virus-Status: Clean Cc: Subject: [releng_6 tinderbox] failure on sparc64/sparc64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Aug 2007 02:32:38 -0000 TB --- 2007-08-25 01:09:49 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2007-08-25 01:09:49 - starting RELENG_6 tinderbox run for sparc64/sparc64 TB --- 2007-08-25 01:09:49 - cleaning the object tree TB --- 2007-08-25 01:10:19 - checking out the source tree TB --- 2007-08-25 01:10:19 - cd /tinderbox/RELENG_6/sparc64/sparc64 TB --- 2007-08-25 01:10:19 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_6 src TB --- 2007-08-25 01:24:13 - building world (CFLAGS=-O2 -pipe) TB --- 2007-08-25 01:24:13 - cd /src TB --- 2007-08-25 01:24:13 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2007-08-25 02:27:54 - generating LINT kernel config TB --- 2007-08-25 02:27:54 - cd /src/sys/sparc64/conf TB --- 2007-08-25 02:27:54 - /usr/bin/make -B LINT TB --- 2007-08-25 02:27:54 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2007-08-25 02:27:54 - cd /src TB --- 2007-08-25 02:27:54 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sat Aug 25 02:27:54 UTC 2007 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/dev/ath -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medlow -msoft-float -ffreestanding /src/sys/dev/mcd/mcd_isa.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/dev/ath -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medlow -msoft-float -ffreestanding -Werror /src/sys/dev/md/md.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/dev/ath -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medlow -msoft-float -ffreestanding -Werror /src/sys/dev/mem/memdev.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/dev/ath -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medlow -msoft-float -ffreestanding -Werror /src/sys/dev/mfi/mfi.c /src/sys/dev/mfi/mfi.c: In function `mfi_ldprobe': /src/sys/dev/mfi/mfi.c:877: error: `SA_XLOCKED' undeclared (first use in this function) /src/sys/dev/mfi/mfi.c:877: error: (Each undeclared identifier is reported only once /src/sys/dev/mfi/mfi.c:877: error: for each function it appears in.) *** Error code 1 Stop in /obj/sparc64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2007-08-25 02:32:52 - WARNING: /usr/bin/make returned exit code 1 TB --- 2007-08-25 02:32:52 - ERROR: failed to build lint kernel TB --- 2007-08-25 02:32:52 - tinderbox aborted TB --- 1.00 user 3.65 system 4982.87 real http://tinderbox.des.no/tinderbox-releng_6-RELENG_6-sparc64-sparc64.full From owner-freebsd-stable@FreeBSD.ORG Sat Aug 25 07:20:59 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BAF0616A41B for ; Sat, 25 Aug 2007 07:20:59 +0000 (UTC) (envelope-from tom@samplonius.org) Received: from ly.sdf.com (ly.sdf.com [216.113.193.83]) by mx1.freebsd.org (Postfix) with ESMTP id 8DD1B13C491 for ; Sat, 25 Aug 2007 07:20:59 +0000 (UTC) (envelope-from tom@samplonius.org) Received: from localhost (localhost [127.0.0.1]) by ly.sdf.com (Postfix) with ESMTP id AE4ED2283A9; Sat, 25 Aug 2007 00:20:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at X-Spam-Score: -3.971 X-Spam-Level: X-Spam-Status: No, score=-3.971 tagged_above=-10 required=6.6 tests=[ALL_TRUSTED=-1.8, AWL=0.428, BAYES_00=-2.599] Received: from ly.sdf.com ([127.0.0.1]) by localhost (ly.sdf.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wdhQpxedLNek; Sat, 25 Aug 2007 00:20:02 -0700 (PDT) Received: from ly.sdf.com (ly.sdf.com [216.113.193.83]) by ly.sdf.com (Postfix) with ESMTP id A4219228391; Sat, 25 Aug 2007 00:20:02 -0700 (PDT) Date: Sat, 25 Aug 2007 00:20:02 -0700 (PDT) From: Tom Samplonius To: Artem Kuchin Message-ID: <9812134.411188026402612.JavaMail.root@ly.sdf.com> In-Reply-To: <2846335.391188026199158.JavaMail.root@ly.sdf.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [216.113.193.90] Cc: freebsd-stable Subject: Re: A little story of failed raid5 (3ware 8000 series) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Aug 2007 07:20:59 -0000 ----- "Artem Kuchin" wrote: ... > But i don't understand how and why it happened. ONly 6 hours ago (a > night before) > all those files were backed up fine w/o any read error. And now, right > after replacing > the driver and starting rebuild it said that there are bad sectors all > over those file. > How come? What happened to you was an extremely common occurrence. You had a disk develop a media failure sometime ago, but the controller never detected it, because that particular bad area was not read. Your backups worked because they never touched this portion of the disk (ex. empty space, meta data, etc). And then another drive developed a electronics failure, which is instantly detected, putting the array into a degraded mode. When you did a rebuild onto a replace drive, the controller discovered that there was a second failed disk, and this is unrecoverable. RAID, of any level, isn't magic. It is important to understand how it works, an realize that drives can passive fail. BTW, if you were using RAID1 or RAID10, you would likely have had the same problem (well, RAID10 can survive _some_ double-disk failures). RAID6 is the only RAID level that can survive failure of any two disks. The real solution is RAID scrubbing: a low level background process that reads every sector of every disk. All of the real RAID systems do this (usually scheduled weekly, or every other week). Most 3ware RAID card don't have this feature. So rather than not using RAID5 or RAID6 again, you should just not use 3ware anymore. Tom From owner-freebsd-stable@FreeBSD.ORG Sat Aug 25 07:39:19 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C096416A417 for ; Sat, 25 Aug 2007 07:39:19 +0000 (UTC) (envelope-from tom@samplonius.org) Received: from ly.sdf.com (ly.sdf.com [216.113.193.83]) by mx1.freebsd.org (Postfix) with ESMTP id 894EB13C494 for ; Sat, 25 Aug 2007 07:39:19 +0000 (UTC) (envelope-from tom@samplonius.org) Received: from localhost (localhost [127.0.0.1]) by ly.sdf.com (Postfix) with ESMTP id 0F1622283AA; Sat, 25 Aug 2007 00:38:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at X-Spam-Score: -3.971 X-Spam-Level: X-Spam-Status: No, score=-3.971 tagged_above=-10 required=6.6 tests=[ALL_TRUSTED=-1.8, AWL=0.428, BAYES_00=-2.599] Received: from ly.sdf.com ([127.0.0.1]) by localhost (ly.sdf.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZbAGW0yHcQ0F; Sat, 25 Aug 2007 00:38:23 -0700 (PDT) Received: from ly.sdf.com (ly.sdf.com [216.113.193.83]) by ly.sdf.com (Postfix) with ESMTP id 31C42228391; Sat, 25 Aug 2007 00:38:23 -0700 (PDT) Date: Sat, 25 Aug 2007 00:38:23 -0700 (PDT) From: Tom Samplonius To: Martin Nilsson Message-ID: <27560580.441188027503141.JavaMail.root@ly.sdf.com> In-Reply-To: <46CA7681.3070909@gneto.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [216.113.193.90] Cc: Artem Kuchin , freebsd-stable@freebsd.org Subject: Re: A little story of failed raid5 (3ware 8000 series) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Aug 2007 07:39:19 -0000 ----- "Martin Nilsson" wrote: > That is what patrol read is intended to detect before it is a problem. > > In a RAID5 array the checksums are only used when reconstructing data, > > if you have a bad block in a checksum sector it will not be detected > until a drive have failed and you try to rebuild the array, > unfortunately at that time it is too late... > > Beware that OS software solutions like diskcheckd will not find this > as > it only reads the data, not the checksums, it must be done on the > controller. This isn't really accurate. First of all, if the RAID controller isn't confirming checksums before giving the data to the OS, what is the checksum for exactly? It is supposed to be for detecting data corruption, so if the card isn't using the checksum, its kinda of useless. I know some RAID systems do fake their checksums, as they don't actually validate data against the checksums during normal reads because they don't have the processing power. I'd stay away from these type of systems (cough ... Blue Arc ... cough). Second, most RAID systems don't use their own checksums anymore. Netapp is quite famous for their ZCS (zone checksum) drives, and still uses a variation of this technology on their newer systems (which are using 512 sectors). But most RAID vendors just rely on the drives own error detection and correction systems (hamming code based usually, which is actually pretty solid). I'm pretty sure that that 3ware doesn't use any checksums. However, in this particular case, validating checksums would have been unhelpful, since the disk was unreadable. diskcheckd would have detected this issue. It would probably have prevented the problem, if it had been running previously. ZFS is also a good option. It has file level checksumming. ZFS never trusts the disks, and is super paranoid. And ZFS can do background scrubbing too. I can't wait for ZFS in FreeBSD 7, because ZFS in software is going to 10 x better than anything 3ware has. > Regards, > Martin Tom From owner-freebsd-stable@FreeBSD.ORG Sat Aug 25 09:27:49 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C45A316A468 for ; Sat, 25 Aug 2007 09:27:49 +0000 (UTC) (envelope-from davids@webmaster.com) Received: from mail1.webmaster.com (mail1.webmaster.com [216.152.64.169]) by mx1.freebsd.org (Postfix) with ESMTP id A7C9F13C442 for ; Sat, 25 Aug 2007 09:27:49 +0000 (UTC) (envelope-from davids@webmaster.com) Received: from however by webmaster.com (MDaemon.PRO.v8.1.3.R) with ESMTP id md50001653234.msg for ; Sat, 25 Aug 2007 02:27:22 -0700 From: "David Schwartz" To: Date: Sat, 25 Aug 2007 02:26:42 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) Importance: Normal In-Reply-To: <27560580.441188027503141.JavaMail.root@ly.sdf.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 X-Authenticated-Sender: joelkatz@webmaster.com X-Spam-Processed: mail1.webmaster.com, Sat, 25 Aug 2007 02:27:22 -0700 (not processed: message from trusted or authenticated source) X-MDRemoteIP: 206.171.168.138 X-Return-Path: davids@webmaster.com X-MDaemon-Deliver-To: freebsd-stable@freebsd.org X-MDAV-Processed: mail1.webmaster.com, Sat, 25 Aug 2007 02:27:24 -0700 Cc: freebsd-stable@freebsd.org Subject: RE: A little story of failed raid5 (3ware 8000 series) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: davids@webmaster.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Aug 2007 09:27:49 -0000 > This isn't really accurate. First of all, if the RAID=20 > controller isn't confirming checksums before giving the data to=20 > the OS, what is the checksum for exactly? The checksum is used to recover the data in the event one piece of the = data is lost. With all of the data but one piece, and the checksum, the = data can be recovered. Confirming the checksum on every read would be a = waste of time since the individual drives already checks the data for = errors. > It is supposed to be=20 > for detecting data corruption, so if the card isn't using the=20 > checksum, its kinda of useless. You are confused. Checking for data corruption is done, by checking if = the *DATA* is corrupt. This does not require looking at the RAID5 = checksum since the data has its own data checksum. > I know some RAID systems do fake=20 > their checksums, as they don't actually validate data against the=20 > checksums during normal reads because they don't have the=20 > processing power. I'd stay away from these type of systems=20 > (cough ... Blue Arc ... cough). It has nothing to do with processing power. It's simply a waste. The = RAID 5 checksum isn't for verifying the data, it's for recovering the = data if it can't be read. =20 > Second, most RAID systems don't use their own checksums=20 > anymore. Netapp is quite famous for their ZCS (zone checksum)=20 > drives, and still uses a variation of this technology on their=20 > newer systems (which are using 512 sectors). But most RAID=20 > vendors just rely on the drives own error detection and=20 > correction systems (hamming code based usually, which is actually=20 > pretty solid). I'm pretty sure that that 3ware doesn't use any = checksums. You are seriously confused. You are confusing the RAID 5 checksum with = the drive data checksum. We are talking about making sure the RAID 5 = checksums are readable so that, if a drive fails, the data can be = reconstructed from the checksum. =20 > However, in this particular case, validating checksums would=20 > have been unhelpful, since the disk was unreadable. diskcheckd=20 > would have detected this issue. It would probably have prevented=20 > the problem, if it had been running previously. No, it would have saved him. The problem was he lost a drive, and = checksums *ON* *OTHER* *DRIVES* were unreadable. Quite possibly they had = been unreabable for months, but were never checked, since they are only = *needed* to reconstruct the data. =20 > ZFS is also a good option. It has file level checksumming. =20 > ZFS never trusts the disks, and is super paranoid. And ZFS can=20 > do background scrubbing too. I can't wait for ZFS in FreeBSD 7,=20 > because ZFS in software is going to 10 x better than anything 3ware = has. That wouuld not have helped him one bit. When the drive failed, the RAID = 5 checksums on the other drives still would not have been scrubbed. The = RAID 5 checksum (technically an XOR) is only needed to recover the RAID = 5 array if a drive (or sector) fails. The only thing that will fix this is specifically verifying the RAID 5 = checksum blocks. If a controller provides no way to do this, it is badly = broken. If a verify operation does not verify the checksum blocks, it is = broken. DS From owner-freebsd-stable@FreeBSD.ORG Sat Aug 25 09:44:48 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8639016A417; Sat, 25 Aug 2007 09:44:48 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from msrv.matik.com.br (msrv.matik.com.br [200.152.83.14]) by mx1.freebsd.org (Postfix) with ESMTP id 0B5BF13C46C; Sat, 25 Aug 2007 09:44:47 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from ap-h.matik.com.br (ap-h.matik.com.br [200.152.83.36]) by msrv.matik.com.br (8.14.1/8.13.1) with ESMTP id l7P9iiXZ052832; Sat, 25 Aug 2007 06:44:44 -0300 (BRT) (envelope-from joao@matik.com.br) From: JoaoBR Organization: Infomatik To: freebsd-stable@freebsd.org Date: Sat, 25 Aug 2007 06:44:44 -0300 User-Agent: KMail/1.9.7 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200708250644.44972.joao@matik.com.br> X-Virus-Scanned: ClamAV version 0.90.3, clamav-milter version 0.90.3 on msrv.matik.com.br X-Virus-Status: Clean Cc: freebsd-acpi@freebsd.org, Ian Smith Subject: Re: powerd freeze with amd 5000 X2 but not with lower cpus X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Aug 2007 09:44:48 -0000 On Thursday 23 August 2007 14:37:57 Ian Smith wrote: > > so now I did because of your question and it seems the power_profile > > script has a bug > > > > I tries to set hw.acpi.cpu.cx_lowest=3DC1 > > > > but I guess it should be dev.cpu.0.cx_lowest > > Ah, ok. Updated in HEAD but not STABLE: > http://www.freebsd.org/cgi/cvsweb.cgi/src/etc/rc.d/power_profile.diff?r1= =3Dte >xt&tr1=3D1.7&r2=3Dtext&tr2=3D1.11 > well, seems you are mistaken, it is not fixed, the new power_profile I have= on=20 my current is wrong as well # $FreeBSD: src/etc/rc.d/power_profile,v 1.11 2007/04/02 22:53:07=20 it still tries to set hw.acpi.cpu.cx_lowest but should set =20 dev.cpu.0.cx_lowest so it still gives the same erro =2D-=20 Jo=E3o A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br From owner-freebsd-stable@FreeBSD.ORG Sat Aug 25 10:04:47 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 20C1716A418 for ; Sat, 25 Aug 2007 10:04:47 +0000 (UTC) (envelope-from tom@tomjudge.com) Received: from smtp809.mail.ird.yahoo.com (smtp809.mail.ird.yahoo.com [217.146.188.69]) by mx1.freebsd.org (Postfix) with SMTP id 9948313C46A for ; Sat, 25 Aug 2007 10:04:46 +0000 (UTC) (envelope-from tom@tomjudge.com) Received: (qmail 22558 invoked from network); 25 Aug 2007 10:04:45 -0000 Received: from unknown (HELO ?192.168.1.2?) (thomasjudge@btinternet.com@86.140.28.215 with plain) by smtp809.mail.ird.yahoo.com with SMTP; 25 Aug 2007 10:04:44 -0000 X-YMail-OSG: RWhL4G8VM1nwNqoNF1z5kWLXsJ42ww5FCt_jx17PIXpfnKll Message-ID: <46D00CE1.9@tomjudge.com> Date: Sat, 25 Aug 2007 12:05:05 +0100 From: Tom Judge User-Agent: Thunderbird 1.5.0.12 (X11/20070604) MIME-Version: 1.0 To: Tom Samplonius References: <9812134.411188026402612.JavaMail.root@ly.sdf.com> In-Reply-To: <9812134.411188026402612.JavaMail.root@ly.sdf.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Artem Kuchin , freebsd-stable Subject: Re: A little story of failed raid5 (3ware 8000 series) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Aug 2007 10:04:47 -0000 Tom Samplonius wrote: > ----- "Artem Kuchin" wrote: ... >> But i don't understand how and why it happened. ONly 6 hours ago (a >> night before) all those files were backed up fine w/o any read >> error. And now, right after replacing the driver and starting >> rebuild it said that there are bad sectors all over those file. How >> come? > > What happened to you was an extremely common occurrence. You had a > disk develop a media failure sometime ago, but the controller never > detected it, because that particular bad area was not read. Your > backups worked because they never touched this portion of the disk > (ex. empty space, meta data, etc). And then another drive developed > a electronics failure, which is instantly detected, putting the array > into a degraded mode. When you did a rebuild onto a replace drive, > the controller discovered that there was a second failed disk, and > this is unrecoverable. 3ware controllers can recover from this situation, all you need to do is tell the controller not to verify the source data. This is a litle dangerous but it has saved me in the past where 1 drive died in a raid 10 array and 2 of the 3 remaining drives had surface defects. The trick was to replace each drive 1 at a time and rebuild without data verification. After 10 painful hours the array was rebuild with out any noticeable data corruption. > > RAID, of any level, isn't magic. It is important to understand how > it works, an realize that drives can passive fail. BTW, if you were > using RAID1 or RAID10, you would likely have had the same problem > (well, RAID10 can survive _some_ double-disk failures). RAID6 is the > only RAID level that can survive failure of any two disks. This is not all true RAID 1 can survive multiple disk failures as it has the storage capacity of 1 spindle and can tolerate the failure of N-1 spindles where N is the number of spindles in the mirror set. This also is kind of true in RAID 10, the more spindles in your mirror sets the more chance you have of being able to survive multiple failures in the array (Say use 6 disks in 2 3 disk mirror sets striped together). > > The real solution is RAID scrubbing: a low level background process > that reads every sector of every disk. All of the real RAID systems > do this (usually scheduled weekly, or every other week). Most 3ware > RAID card don't have this feature. > > So rather than not using RAID5 or RAID6 again, you should just not > use 3ware anymore. If you use the 3dm2 management interface you can schedule verify and rebuild tasks to run on a regular basis. I think that 7500 series controllers can do this, 9500 and 9550's definitely can. We have 50+ systems that are using 3ware cards (7500-9550 4 and 8 channel models) with 200+ spindles in use (no host spares unfortunately) and drives in that pool failing on average around once a month. We have only ever had trouble recovering from failed drives on 7500 series controllers that have been in production for a reasonably long time. I don't think that you are justified in your slagging off of 3ware controllers. Tom From owner-freebsd-stable@FreeBSD.ORG Sat Aug 25 11:41:24 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4825F16A418 for ; Sat, 25 Aug 2007 11:41:24 +0000 (UTC) (envelope-from shteryana@gmail.com) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.235]) by mx1.freebsd.org (Postfix) with ESMTP id F22FB13C45D for ; Sat, 25 Aug 2007 11:41:23 +0000 (UTC) (envelope-from shteryana@gmail.com) Received: by nz-out-0506.google.com with SMTP id l8so642393nzf for ; Sat, 25 Aug 2007 04:41:23 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:reply-to:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=pV58NCEM2D8sUFpJLzu5KtE8MLMWO98SXug+/x3kg8GORTG2ggH8jKAaw8QuWYuAOzDGOhG6vJ0MGGKHT6inwTKstVgo6TAG5/GYKVNIk3CoTMQEpakrg7ozwa9Pq6ZWodKurw/KD2/3jhEZx1T1icC76yEvX7LBRoxg2D97W7U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:reply-to:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=lJy1YRgsvYR7Qdixg5FR+AYwgyztOCB1wsoYAr5QksJz+XOwspQMj+5TRUZO0BrbXOq/CeKSQqbnvv0JJeaMYwARx74oG1R7P8mKcvUNcE9qEWTjwFU4VBA3Rga8ZHjQAjc4gXjiTu0k4pIITZtRGpE/HVrHpyqg+aF8MKA7TzY= Received: by 10.114.80.4 with SMTP id d4mr1677988wab.1188040575530; Sat, 25 Aug 2007 04:16:15 -0700 (PDT) Received: by 10.114.58.6 with HTTP; Sat, 25 Aug 2007 04:16:15 -0700 (PDT) Message-ID: <61b573980708250416t75b329f6v5e21845baf0987aa@mail.gmail.com> Date: Sat, 25 Aug 2007 14:16:15 +0300 From: "Shteryana Shopova" Sender: shteryana@gmail.com To: "Carlos Porto Filho" In-Reply-To: <20070825110337.J87821@maildrop.int.zabbadoz.net> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070825110337.J87821@maildrop.int.zabbadoz.net> X-Google-Sender-Auth: bea71038c72307e8 Cc: freebsd-stable@freebsd.org Subject: Re: error - snmp_bridge (fwd) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: syrinx@FreeBSD.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Aug 2007 11:41:24 -0000 > Date: Fri, 24 Aug 2007 17:12:44 -0300 > From: Carlos Porto Filho > To: freebsd-stable@freebsd.org > Subject: error - snmp_bridge > > During the make buildworld (6stable) i got this: > Change begemotBridgeBaseName > bridge_oid.h > line 31: '(' expected at begin of node > context: " TruthValue ENUM ( > *** Error code 1 > Stop in /usr/src/usr.sbin/bsnmpd/modules/snmp_bridge. > > . . . > > any idea? > tia You're getting the error most likely because you're updating from a system that has an older version of gensnmptree(1). Compiling and installing gensnmptree(1) before starting buildworld should solve your problem - #cd /usr/src/usr.sbin/bsnmpd/gensnmptree/ #make && make install cheers, Shteryana > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-stable@FreeBSD.ORG Sat Aug 25 14:17:43 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0345F16A418 for ; Sat, 25 Aug 2007 14:17:43 +0000 (UTC) (envelope-from carloshpf@oi.com.br) Received: from smtp6.oi.com.br (smtp6.oi.com.br [200.222.115.69]) by mx1.freebsd.org (Postfix) with ESMTP id A80DE13C480 for ; Sat, 25 Aug 2007 14:17:42 +0000 (UTC) (envelope-from carloshpf@oi.com.br) Received: from smtp1.oi.com.br (smtp1.oi.com.br [200.222.115.16]) by smtp6.oi.com.br (Postfix) with ESMTP id 033BA210998 for ; Sat, 25 Aug 2007 11:17:43 -0300 (BRT) Received: from smtp1.oi.com.br (localhost.localdomain [127.0.0.1]) by smtp1.oi.com.br (Postfix) with ESMTP id 335C2802043B for ; Sat, 25 Aug 2007 11:17:41 -0300 (BRT) Received: from [192.168.0.152] (unknown [189.12.157.250]) by smtp1.oi.com.br (Postfix) with ESMTP id BC3778020523 for ; Sat, 25 Aug 2007 11:17:40 -0300 (BRT) Message-ID: <46D039FB.6040709@oi.com.br> Date: Sat, 25 Aug 2007 11:17:31 -0300 From: Carlos Porto Filho User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: error - snmp_bridge X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Aug 2007 14:17:43 -0000 Bjoern A. Zeeb wrote: > On Fri, 24 Aug 2007, Carlos Porto Filho wrote: > > Hi, > >> During the make buildworld (6stable) i got this: >> Change begemotBridgeBaseName > bridge_oid.h >> line 31: '(' expected at begin of node >> context: " TruthValue ENUM ( >> *** Error code 1 >> Stop in /usr/src/usr.sbin/bsnmpd/modules/snmp_bridge. >> >> . . . >> >> any idea? > > Are you sure your entire source tree is in sync? > yes.. and i tried from different cvs servers... here my supfile: *default host=cvsup9.freebsd.org *default base=/usr *default prefix=/usr *default release=cvs *default tag=RELENG_6 *default delete use-rel-suffix src-all *default tag=. ports-all doc-all From owner-freebsd-stable@FreeBSD.ORG Sat Aug 25 16:03:06 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 335E616A418 for ; Sat, 25 Aug 2007 16:03:06 +0000 (UTC) (envelope-from carloshpf@oi.com.br) Received: from smtp6.oi.com.br (smtp6.oi.com.br [200.222.115.69]) by mx1.freebsd.org (Postfix) with ESMTP id E174A13C46A for ; Sat, 25 Aug 2007 16:03:05 +0000 (UTC) (envelope-from carloshpf@oi.com.br) Received: from smtp2.oi.com.br (smtp2.oi.com.br [200.222.115.17]) by smtp6.oi.com.br (Postfix) with ESMTP id 8671A20FFD3 for ; Sat, 25 Aug 2007 13:03:06 -0300 (BRT) Received: from smtp2.oi.com.br (localhost.localdomain [127.0.0.1]) by smtp2.oi.com.br (Postfix) with ESMTP id C5A737000812 for ; Sat, 25 Aug 2007 13:03:03 -0300 (BRT) Received: from [192.168.0.152] (unknown [189.12.157.250]) by smtp2.oi.com.br (Postfix) with ESMTP id A2E0E7000810 for ; Sat, 25 Aug 2007 13:03:02 -0300 (BRT) Message-ID: <46D052B2.5020709@oi.com.br> Date: Sat, 25 Aug 2007 13:02:58 -0300 From: Carlos Porto Filho User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <20070825110337.J87821@maildrop.int.zabbadoz.net> <61b573980708250416t75b329f6v5e21845baf0987aa@mail.gmail.com> In-Reply-To: <61b573980708250416t75b329f6v5e21845baf0987aa@mail.gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: error - snmp_bridge (solved) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Aug 2007 16:03:06 -0000 Shteryana Shopova wrote: >> Date: Fri, 24 Aug 2007 17:12:44 -0300 >> From: Carlos Porto Filho >> To: freebsd-stable@freebsd.org >> Subject: error - snmp_bridge >> >> During the make buildworld (6stable) i got this: >> Change begemotBridgeBaseName > bridge_oid.h >> line 31: '(' expected at begin of node >> context: " TruthValue ENUM ( >> *** Error code 1 >> Stop in /usr/src/usr.sbin/bsnmpd/modules/snmp_bridge. >> >> . . . >> >> any idea? >> tia >> > > You're getting the error most likely because you're updating from a > system that has an older version of gensnmptree(1). Compiling and > installing gensnmptree(1) before starting buildworld should solve your > problem - > > #cd /usr/src/usr.sbin/bsnmpd/gensnmptree/ > #make && make install > > cheers, > Shteryana > > >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >> >> > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > It worked!! Thank you! :) From owner-freebsd-stable@FreeBSD.ORG Sat Aug 25 19:16:30 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A6BB716A417 for ; Sat, 25 Aug 2007 19:16:30 +0000 (UTC) (envelope-from antik@bsd.ee) Received: from a8.virtuaal.com (a8.virtuaal.com [195.222.15.78]) by mx1.freebsd.org (Postfix) with ESMTP id 5ECB613C45B for ; Sat, 25 Aug 2007 19:16:30 +0000 (UTC) (envelope-from antik@bsd.ee) Received: from [62.65.240.143] (helo=[192.168.2.100]) by a8.virtuaal.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.66) (envelope-from ) id 1IP0Mq-0001Vj-WD for freebsd-stable@freebsd.org; Sat, 25 Aug 2007 21:28:17 +0300 From: Andrei Kolu To: freebsd-stable@freebsd.org Date: Sat, 25 Aug 2007 21:28:17 +0300 User-Agent: KMail/1.9.7 References: <003101c7e685$e74005c0$0401a8c0@claylaptop> <200708242004.l7OK4bOg085582@apollo.backplane.com> In-Reply-To: <200708242004.l7OK4bOg085582@apollo.backplane.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200708252128.17934.antik@bsd.ee> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - a8.virtuaal.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - bsd.ee Subject: Re: A little story of failed raid5 (3ware 8000 series) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Aug 2007 19:16:30 -0000 Friday 24 August 2007 23:04:37 kirjutas Matthew Dillon: > A friend of mine once told me that the only worthwhile RAID systems are > the ones that email you a detailed message when something goes south. > > -Matt > _______________________________________________ AFAIK all good raid hardware producers (3ware, LSI, Areca) got this functionality. From owner-freebsd-stable@FreeBSD.ORG Sat Aug 25 21:41:03 2007 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0F96316A420 for ; Sat, 25 Aug 2007 21:41:03 +0000 (UTC) (envelope-from mikej@rogers.com) Received: from smtp102.rog.mail.re2.yahoo.com (smtp102.rog.mail.re2.yahoo.com [206.190.36.80]) by mx1.freebsd.org (Postfix) with SMTP id 9FB1F13C46E for ; Sat, 25 Aug 2007 21:41:02 +0000 (UTC) (envelope-from mikej@rogers.com) Received: (qmail 44410 invoked from network); 25 Aug 2007 21:14:22 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:X-YMail-OSG:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=RBHFo8ff5AmB0Bq7nRbv/fLmIMxfJBnfBrbEHSXoYUG8TG5n0iRRS1UOpK43ovv+O8udA/RYFCrMYnzLKUYS5UjIZTOBZc6Ds5isDPOxn97X85l8+QLF1Amjn5s+LSenaUzZXh6AmvBBgOMBTsRbaNAl38dZOYFEsDhzQA2vv6Y= ; Received: from unknown (HELO ?172.16.0.165?) (mikej@rogers.com@99.244.15.156 with plain) by smtp102.rog.mail.re2.yahoo.com with SMTP; 25 Aug 2007 21:14:22 -0000 X-YMail-OSG: TqDJAikVM1mPhONPKi0sXJq3QBSsrJAxRnIfGam24b3q8ho7gABXLZtVvOvviL.0sg-- Message-ID: <46D09BA8.7010203@rogers.com> Date: Sat, 25 Aug 2007 17:14:16 -0400 From: Mike Jakubik User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: obrien@freebsd.org References: <20070824015956.GA17604@dragon.NUXI.org> In-Reply-To: <20070824015956.GA17604@dragon.NUXI.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org Subject: Re: MFC 7.0 calcru changes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Aug 2007 21:41:03 -0000 David O'Brien wrote: > This is a patch to MFC what I think are all the calcru-related changes > that occurred since 6-STABLE was branched and 7.0 continued forward. > > If anyone spots some changes I missed, please yell out. > > Thank you so much! My supermicro systems are plagued by calcru messages and timing problems, last time i checked there was no plan to fix this on 6, CURRENT worked fine so this should fix it.