From owner-freebsd-hackers@FreeBSD.ORG Sun Sep 24 10:42:00 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 341F416A403 for ; Sun, 24 Sep 2006 10:42:00 +0000 (UTC) (envelope-from soralx@cydem.org) Received: from pd2mo2so.prod.shaw.ca (shawidc-mo1.cg.shawcable.net [24.71.223.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id D016343D46 for ; Sun, 24 Sep 2006 10:41:59 +0000 (GMT) (envelope-from soralx@cydem.org) Received: from pd5mr7so.prod.shaw.ca (pd5mr7so-qfe3.prod.shaw.ca [10.0.141.183]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0J6300GP0F1Z5RD0@l-daemon> for freebsd-hackers@freebsd.org; Sun, 24 Sep 2006 04:41:59 -0600 (MDT) Received: from pn2ml7so.prod.shaw.ca ([10.0.121.151]) by pd5mr7so.prod.shaw.ca (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0J6300JZDF1ZYFB0@pd5mr7so.prod.shaw.ca> for freebsd-hackers@freebsd.org; Sun, 24 Sep 2006 04:41:59 -0600 (MDT) Received: from soralx.cydem.org ([24.87.27.3]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0J630038XF1Y8S50@l-daemon> for freebsd-hackers@freebsd.org; Sun, 24 Sep 2006 04:41:59 -0600 (MDT) Date: Sun, 24 Sep 2006 03:41:57 -0700 From: soralx@cydem.org In-reply-to: To: freebsd-hackers@freebsd.org Message-id: <200609240341.57424.soralx@cydem.org> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7bit Content-disposition: inline References: <200609141232.k8ECWTXj045191@lurza.secnetix.de> <20060919173421.GA45928@xor.obsecurity.org> User-Agent: KMail/1.9.1 Subject: Re: numbers don't lie ... X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Sep 2006 10:42:00 -0000 > here are a bunch of new numbers: > make: dell 2950 > OS: Freebsd 6.2-PRERELEASE > cpu: XEON 3.20GHz dualcore * 2 > memory: 4GB > > no swap configured/used. > > make buildworld -j 8: > > src & obj real user system hyper > -------------------- --------- ---------- --------- ----- > Dell PERC 5/i RAID 0 24m17.73s 1h4m31.49s 15m47.44s no > Dell PERC 5/i RAID 0 22m3.39s 1h38m46.84s 28m54.18s yes > iSCSI/netapp 26m49.98s 1h4m26.77s 16m12.89s no > > src obj > -------------------- > md Dell PERC 5/i 24m7.22s 1h4m44.94s 16m24.45 no > > so, if numbers are to be believed: > 1- hypert helps in the real time, but user and system are bigger. > allot of sweat for a very small gain. > 2- src in memory made no change. could it be that the src three was already in the memory, cached? or did you do each test after a reboot? > 3- slow disc (iscsi) vs. very fast disk (PERC 5/i RAID 0) - about 1:3 speed, > produced > less than 10% gain in time. > > danny [SorAlx] ridin' VN1500-B2 From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 25 11:32:37 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1334716A523 for ; Mon, 25 Sep 2006 11:32:37 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 92AB643D49 for ; Mon, 25 Sep 2006 11:32:36 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 9D55720C2; Mon, 25 Sep 2006 13:32:32 +0200 (CEST) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: 0.0/3.0 X-Spam-Checker-Version: SpamAssassin 3.1.4 (2006-07-25) on tim.des.no Received: from dwp.des.no (des.no [80.203.243.180]) by tim.des.no (Postfix) with ESMTP id 817162082; Mon, 25 Sep 2006 13:32:32 +0200 (CEST) Received: by dwp.des.no (Postfix, from userid 1001) id E0B49B80E; Mon, 25 Sep 2006 13:32:31 +0200 (CEST) From: des@des.no (Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?=) To: Dmitry Morozovsky References: <200609141232.k8ECWTXj045191@lurza.secnetix.de> <20060919160511.T33371@woozle.rinet.ru> <20060919173421.GA45928@xor.obsecurity.org> <20060920123940.W63482@woozle.rinet.ru> Date: Mon, 25 Sep 2006 13:32:31 +0200 In-Reply-To: <20060920123940.W63482@woozle.rinet.ru> (Dmitry Morozovsky's message of "Wed, 20 Sep 2006 12:45:37 +0400 (MSD)") Message-ID: <86hcywrxkg.fsf@dwp.des.no> User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org, Kris Kennaway Subject: Re: numbers don't lie ... X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Sep 2006 11:32:37 -0000 Dmitry Morozovsky writes: > Kris Kennaway wrote: > > Dmitry Morozovsky writes: > > > My experiments show that if you have enough memory to host radmdrive = for > > > /usr/src you'd better leave it for caching - there were no statistica= lly > > > meaningful performance difference, at least on machines with 1G+ RAM. > > Really? My measurements show the opposite (on a system with 16GB of > > RAM). > My last test on amd64/dualcore with 4G of RAM and -j4 shows > (buildworld+buildkernel): > > =3D=3D> /tmp/buildlog <=3D=3D > 1996.45 real 3032.94 user 624.83 sys > Script done on Tue Sep 19 14:44:54 2006 > > =3D=3D> /tmp/buildlog.md <=3D=3D > 1957.45 real 3033.93 user 585.78 sys > Script done on Tue Sep 19 15:20:42 2006 > > Second one was with 512M/4k/512 swap-backed md, the former with /usr/src = on the > gmirror'ed pair of SATAs. Seems to me that your own numbers contradict you. You saved about 40 seconds (2%) by keeping /usr/src in a ram disk. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 25 11:48:06 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9951516A4AB for ; Mon, 25 Sep 2006 11:48:06 +0000 (UTC) (envelope-from borjamar@sarenet.es) Received: from smtp2.sarenet.es (smtp2.sarenet.es [194.30.0.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1F41643DF6 for ; Mon, 25 Sep 2006 11:46:42 +0000 (GMT) (envelope-from borjamar@sarenet.es) Received: from [127.0.0.1] (matahari.sarenet.es [192.148.167.18]) by smtp2.sarenet.es (Postfix) with ESMTP id 12F3916113 for ; Mon, 25 Sep 2006 13:46:37 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v752.2) Content-Transfer-Encoding: 7bit Message-Id: <7591D6A9-27EE-4ADE-AF09-84F8636ADD98@sarenet.es> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: hackers@freebsd.org From: Borja Marcos Date: Mon, 25 Sep 2006 13:46:42 +0200 X-Mailer: Apple Mail (2.752.2) Cc: Subject: network stack problem in sparc64? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Sep 2006 11:48:06 -0000 Hello, I saw this some time ago but always forgot to report it. I'm running a pair of machines with FreeBSD/sparc64 (various versions, one of them is running -STABLE now), and I've seen a problem with the network stack. Looking at buffer and window sizes, earendil# sysctl net.inet.tcp|fgrep space net.inet.tcp.sendspace: 0 net.inet.tcp.recvspace: 0 earendil# sysctl net.inet.udp net.inet.udp.checksum: 1 net.inet.udp.maxdgram: 0 net.inet.udp.recvspace: 0 When I try to modify them, it doesn't work at all. For example, trying to run nfcapd/nfsen in a sparc64 box, I get an error for a setsockopt() call earendil# /usr/local/etc/rc.d/nfsen start Starting nfsenStarting nfcpad: upstream1setsockopt(SO_RCVBUF,200000): Invalid argument Terminated due to errors. nfcapd exec error: exit: 255, signal: 0, coredump: 0 For x86 machines the values are correctly reported and they work as expected. I have been poking Google for this but I haven't seen any mention of this. Best regards, Borja. P.S: The example machine is running earendil# uname -a FreeBSD earendil.arnor.es 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #0: Fri Sep 22 12:04:44 CEST 2006 root@earendil.arnor.es:/usr/obj/usr/ src/sys/EARENDIL sparc64 From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 25 16:34:56 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2D14B16A494 for ; Mon, 25 Sep 2006 16:34:56 +0000 (UTC) (envelope-from maksim.yevmenkin@savvis.net) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 30BBB43D69 for ; Mon, 25 Sep 2006 16:34:47 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from localhost (localhost.localdomain [127.0.0.1]) by mailgate1b.savvis.net (Postfix) with ESMTP id 761AC3BE57; Mon, 25 Sep 2006 11:34:46 -0500 (CDT) Received: from mailgate1b.savvis.net ([127.0.0.1]) by localhost (mailgate1b.savvis.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 24809-01-21; Mon, 25 Sep 2006 11:34:46 -0500 (CDT) Received: from [10.12.163.251] (unknown [10.12.163.251]) by mailgate1b.savvis.net (Postfix) with ESMTP id 165073BE4E; Mon, 25 Sep 2006 11:34:46 -0500 (CDT) Message-ID: <45180525.3060309@savvis.net> Date: Mon, 25 Sep 2006 09:34:45 -0700 From: Maksim Yevmenkin User-Agent: Thunderbird 1.5.0.5 (X11/20060906) MIME-Version: 1.0 To: Borja Marcos References: <7591D6A9-27EE-4ADE-AF09-84F8636ADD98@sarenet.es> In-Reply-To: <7591D6A9-27EE-4ADE-AF09-84F8636ADD98@sarenet.es> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at savvis.net Cc: hackers@freebsd.org Subject: Re: network stack problem in sparc64? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Sep 2006 16:34:56 -0000 Borja Marcos wrote: > Hello, > > I saw this some time ago but always forgot to report it. > > I'm running a pair of machines with FreeBSD/sparc64 (various versions, > one of them is running -STABLE now), and I've seen a problem with the > network stack. > > Looking at buffer and window sizes, > > earendil# sysctl net.inet.tcp|fgrep space > net.inet.tcp.sendspace: 0 > net.inet.tcp.recvspace: 0 > > earendil# sysctl net.inet.udp > net.inet.udp.checksum: 1 > net.inet.udp.maxdgram: 0 > net.inet.udp.recvspace: 0 > > When I try to modify them, it doesn't work at all. For example, trying > to run nfcapd/nfsen in a sparc64 box, I get an error for a setsockopt() > call > > earendil# /usr/local/etc/rc.d/nfsen start > Starting nfsenStarting nfcpad: upstream1setsockopt(SO_RCVBUF,200000): > Invalid argument > Terminated due to errors. > nfcapd exec error: exit: 255, signal: 0, coredump: 0 > > > For x86 machines the values are correctly reported and they work as > expected. > > I have been poking Google for this but I haven't seen any mention of this. hmmm... how about this (untested) patch? --- tcp_usrreq.c.orig Fri Nov 4 12:26:14 2005 +++ tcp_usrreq.c Mon Sep 25 09:31:42 2006 @@ -1161,10 +1161,10 @@ * sizes, respectively. These are obsolescent (this information should * be set by the route). */ -u_long tcp_sendspace = 1024*32; +int tcp_sendspace = 1024*32; SYSCTL_INT(_net_inet_tcp, TCPCTL_SENDSPACE, sendspace, CTLFLAG_RW, &tcp_sendspace , 0, "Maximum outgoing TCP datagram size"); -u_long tcp_recvspace = 1024*64; +int tcp_recvspace = 1024*64; SYSCTL_INT(_net_inet_tcp, TCPCTL_RECVSPACE, recvspace, CTLFLAG_RW, &tcp_recvspace , 0, "Maximum incoming TCP datagram size"); --- udp_usrreq.c.orig Wed Sep 13 11:19:26 2006 +++ udp_usrreq.c Mon Sep 25 09:32:00 2006 @@ -923,12 +923,12 @@ return (error); } -u_long udp_sendspace = 9216; /* really max datagram size */ +int udp_sendspace = 9216; /* really max datagram size */ /* 40 1K datagrams */ SYSCTL_INT(_net_inet_udp, UDPCTL_MAXDGRAM, maxdgram, CTLFLAG_RW, &udp_sendspace, 0, "Maximum outgoing UDP datagram size"); -u_long udp_recvspace = 40 * (1024 + +int udp_recvspace = 40 * (1024 + #ifdef INET6 sizeof(struct sockaddr_in6) #else thanks, max From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 25 18:38:52 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EFE5D16A403 for ; Mon, 25 Sep 2006 18:38:52 +0000 (UTC) (envelope-from tech@nano.net) Received: from mail.smallweb.com (mail.smallweb.com [216.85.125.111]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C78F43D4C for ; Mon, 25 Sep 2006 18:38:52 +0000 (GMT) (envelope-from tech@nano.net) Received: from Sixpence.mail.smallweb.com (sixpence.nano.net [216.85.125.9]) by mail.smallweb.com (Rockliffe SMTPRA 5.3.11) with ESMTP id for ; Mon, 25 Sep 2006 12:46:42 -0600 Message-Id: <6.2.0.14.2.20060925123108.03038af0@nano.net> X-Mailer: QUALCOMM Windows Eudora Version 6.2.0.14 Date: Mon, 25 Sep 2006 12:38:47 -0600 To: freebsd-hackers@freebsd.org From: tech@nano.net Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: fsck X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Sep 2006 18:38:53 -0000 I've got a /usr partition with some problems. During boot it fails and I'm prompted to run fsck manually. I do so and when fsck has finished it asks me to run it again, and again, and again...it seems to find the same errors each time. It never seems to repair anything. It worked fine on errors it found on the /var partition... I checked the man pages and didn't see anything pertinent. How can I fix this partition? And now for something completely different.... If I can't get the /usr partition to work is there any way to recreate the user directories from the password file? The contents will be lost but nobody uses their folder anyway, I just need all the /usr/home folders created... I could write a script, but I thought I'd check first to see if something already exists....... From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 25 19:07:47 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 31A6816A403 for ; Mon, 25 Sep 2006 19:07:47 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail14.syd.optusnet.com.au (mail14.syd.optusnet.com.au [211.29.132.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id 84BD943D45 for ; Mon, 25 Sep 2006 19:07:46 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail14.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k8PJ7e7R029811 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 26 Sep 2006 05:07:44 +1000 Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.8/8.13.8) with ESMTP id k8PJ7eGj010661; Tue, 26 Sep 2006 05:07:40 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.8/8.13.8/Submit) id k8PJ7ejO010660; Tue, 26 Sep 2006 05:07:40 +1000 (EST) (envelope-from peter) Date: Tue, 26 Sep 2006 05:07:40 +1000 From: Peter Jeremy To: tech@nano.net Message-ID: <20060925190740.GI1154@turion.vk2pj.dyndns.org> References: <6.2.0.14.2.20060925123108.03038af0@nano.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="svExV93C05KqedWb" Content-Disposition: inline In-Reply-To: <6.2.0.14.2.20060925123108.03038af0@nano.net> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.12-2006-07-14 Cc: freebsd-hackers@freebsd.org Subject: Re: fsck X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Sep 2006 19:07:47 -0000 --svExV93C05KqedWb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, 2006-Sep-25 12:38:47 -0600, tech@nano.net wrote: >I've got a /usr partition with some problems. During boot it fails and I'm= =20 >prompted to run fsck manually. I do so and when fsck has finished it asks= =20 >me to run it again, and again, and again...it seems to find the same error= s=20 >each time. Can you give some more details please. What version of FreeBSD is this? What are the errors? What options are you giving fsck? What happened between the last time /usr fsck'd correctly and now? I don't have a script to re-create directories but it would be fairly easy to write one. --=20 Peter Jeremy --svExV93C05KqedWb Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFGCj8/opHv/APuIcRAqx+AJ4jZKt/+MaFlQk4LZen2P/uMgMzKQCgo6P/ HoQXEnD6rk39LOPy6/wn7E0= =DY3K -----END PGP SIGNATURE----- --svExV93C05KqedWb-- From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 25 19:17:44 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8FA3016A407 for ; Mon, 25 Sep 2006 19:17:44 +0000 (UTC) (envelope-from maslanbsd@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.225]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D6E943D4C for ; Mon, 25 Sep 2006 19:17:43 +0000 (GMT) (envelope-from maslanbsd@gmail.com) Received: by wx-out-0506.google.com with SMTP id i27so1955173wxd for ; Mon, 25 Sep 2006 12:17:43 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=loGzS/odpRDEiNuHvysbhtYZRvHwthZ5yFwp1n4r+NGMl2eywcGezQfh1E+TKxF+4ttNgYowaoh8e0N6baJiCfA7ppEYsLrbLjlErAjrEGmG9yHpCkmO6Rm57u9cGDTuSFyP3whFyMcRZYPpiI6xW5SG5tRhPT6qnQIXECFxVsc= Received: by 10.70.80.14 with SMTP id d14mr7694971wxb; Mon, 25 Sep 2006 12:17:43 -0700 (PDT) Received: by 10.70.76.8 with HTTP; Mon, 25 Sep 2006 12:17:43 -0700 (PDT) Message-ID: <319cceca0609251217s1c1091a7h60ea066e46311ce6@mail.gmail.com> Date: Mon, 25 Sep 2006 22:17:43 +0300 From: Maslan To: "tech@nano.net" In-Reply-To: <6.2.0.14.2.20060925123108.03038af0@nano.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <6.2.0.14.2.20060925123108.03038af0@nano.net> Cc: freebsd-hackers@freebsd.org Subject: Re: fsck X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Sep 2006 19:17:44 -0000 > I've got a /usr partition with some problems. During boot it fails and I'm > prompted to run fsck manually. I do so and when fsck has finished it asks > me to run it again, and again, and again...it seems to find the same errors > each time. It never seems to repair anything. It worked fine on errors it > found on the /var partition... I checked the man pages and didn't see > anything pertinent. How can I fix this partition? Have your tried to run fsck in single-user mode ???? -- I'm Searching For Perfection, So Even If U Need Portability U've To Use Assembly ;-) http://www.maslanlab.org http://libosdk.berlios.de From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 25 19:57:57 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 78B9816A403 for ; Mon, 25 Sep 2006 19:57:57 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id B699543D5D for ; Mon, 25 Sep 2006 19:57:56 +0000 (GMT) (envelope-from uspoerlein@gmail.com) Received: by nf-out-0910.google.com with SMTP id n29so24776nfc for ; Mon, 25 Sep 2006 12:57:55 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:date:from:to:subject:message-id:mail-followup-to:references:mime-version:content-type:content-disposition:in-reply-to; b=B3wVTNMyYQd/27dIJ6F7jzr0Hzp3PLhN5XW7Ll/L6F5n9eC+FMiJeniykYqDUl+8JBHhQ/8xfbqKjV8Z+vMYeDiRGD/i52v8CeYujeiESfEXSHtxZkr4dA1No99wmQSp2nBNhd9Y0Gc3jiGyvm8WIE/lABgZNLII6E6eleSuS6Q= Received: by 10.48.48.15 with SMTP id v15mr97699nfv; Mon, 25 Sep 2006 12:57:55 -0700 (PDT) Received: from roadrunner.q.local ( [85.180.155.61]) by mx.gmail.com with ESMTP id x27sm5748069nfb.2006.09.25.12.57.54; Mon, 25 Sep 2006 12:57:54 -0700 (PDT) Received: from roadrunner.q.local (localhost [127.0.0.1]) by roadrunner.q.local (8.13.8/8.13.6) with ESMTP id k8PJvp5C004496 for ; Mon, 25 Sep 2006 21:57:51 +0200 (CEST) (envelope-from uspoerlein@gmail.com) Received: (from q@localhost) by roadrunner.q.local (8.13.8/8.13.6/Submit) id k8MIiZZR002659 for freebsd-hackers@FreeBSD.ORG; Fri, 22 Sep 2006 20:44:35 +0200 (CEST) (envelope-from uspoerlein@gmail.com) Date: Fri, 22 Sep 2006 20:44:35 +0200 From: Ulrich Spoerlein To: freebsd-hackers@FreeBSD.ORG Message-ID: <20060922184435.GA1250@roadrunner.q.local> Mail-Followup-To: freebsd-hackers@FreeBSD.ORG References: <451140F8.9030500@centtech.com> <200609210831.k8L8VxvK007258@lurza.secnetix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200609210831.k8L8VxvK007258@lurza.secnetix.de> Cc: Subject: Re: numbers don't lie ... X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Sep 2006 19:57:57 -0000 Oliver Fromme wrote: > Eric Anderson wrote: > > Oliver Fromme wrote: > > > Reading /usr/src from a physical disk certainly requires > > > quite some I/O that takes more than zero time. > > > > But, in order to populate the ram disk, you must read /usr/src also from > > something, and that also takes time, which you should include in the > > full scope. > > But when you perform the buildworld several times (as you > should do when you're benchmarking properly), everything > is already in the RAM disk. If you instead rely on caching > but you don't have enough RAM to hold all of src + obj + > toolchain in RAM, then src (or at least parts of it) will > have to be read from the physical disk again upon each > buildworld. .. which makes no difference for the test case presented here. You're missing the point here: they benchmark with '-j8'. If you'd benchmark a -j1 build of md(4) vs. real disks, then you should get drastically different results (provided you start with a cold cache). But on these dual (quad?) CPU machines, with a -j8 build, 6 threads/processes are free to wait for disk I/O a very long time till they are finally scheduled. Thus, specifying high -jN values will mask any disk I/O latency (for reasonable combinations of CPUs and HDDs). Ulrich Spoerlein -- A: Yes. >Q: Are you sure? > >A: Because it reverses the logical flow of conversation. > >>Q: Why is top posting frowned upon? From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 25 20:41:24 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6CDC516A40F for ; Mon, 25 Sep 2006 20:41:24 +0000 (UTC) (envelope-from tech@nano.net) Received: from mail.smallweb.com (mail.smallweb.com [216.85.125.111]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4B09543D45 for ; Mon, 25 Sep 2006 20:41:18 +0000 (GMT) (envelope-from tech@nano.net) Received: from Sixpence.mail.smallweb.com (sixpence.nano.net [216.85.125.9]) by mail.smallweb.com (Rockliffe SMTPRA 5.3.11) with ESMTP id for ; Mon, 25 Sep 2006 14:49:13 -0600 Message-Id: <6.2.0.14.2.20060925142809.0300e3e0@nano.net> X-Mailer: QUALCOMM Windows Eudora Version 6.2.0.14 Date: Mon, 25 Sep 2006 14:41:18 -0600 To: freebsd-hackers@freebsd.org From: tech@nano.net In-Reply-To: <20060925190740.GI1154@turion.vk2pj.dyndns.org> References: <6.2.0.14.2.20060925123108.03038af0@nano.net> <20060925190740.GI1154@turion.vk2pj.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: Re: fsck X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Sep 2006 20:41:24 -0000 Hi Peter, The hard drive is in the fridge right now, in case it's a heat problem. It's FreeBSD version 4.x. It's getting hard read errors, and I'm using -y with fsck so it will continue on to the next error without prompting from me. The same thing happens whether I use the -y flag or not. It says that certain sectors are bad, moves on to the next bad sectors, and eventually says I need to rerun fsck. It's like "Groundhog Day", I get the same thing over and over and over... Nothing happened since the last boot, I was gzipping up the home folders to transfer to a new server (just in time I guess...) and it started getting really slowly. So I rebooted it from the command line and when it came back up it had problems. It has been restarted a few times in the past week and showed no errors at all before yesterday. It found the same type of errors on the /var partition and dealt with those without problems. So I'm wondering what the difference might be... The /var partition found errors, fixed them, and marked the partition as clean. Maybe I can mount a dirty partition..... I just need the data off it... At 01:07 PM 9/25/2006, you wrote: >On Mon, 2006-Sep-25 12:38:47 -0600, tech@nano.net wrote: > >I've got a /usr partition with some problems. During boot it fails and I'm > >prompted to run fsck manually. I do so and when fsck has finished it asks > >me to run it again, and again, and again...it seems to find the same errors > >each time. > >Can you give some more details please. >What version of FreeBSD is this? >What are the errors? >What options are you giving fsck? >What happened between the last time /usr fsck'd correctly and now? > >I don't have a script to re-create directories but it would be fairly >easy to write one. > >-- >Peter Jeremy From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 25 20:53:46 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 200DB16A416 for ; Mon, 25 Sep 2006 20:53:46 +0000 (UTC) (envelope-from rick@kiwi-computer.com) Received: from kiwi-computer.com (megan.kiwi-computer.com [63.224.10.3]) by mx1.FreeBSD.org (Postfix) with SMTP id 4CFF843D72 for ; Mon, 25 Sep 2006 20:53:41 +0000 (GMT) (envelope-from rick@kiwi-computer.com) Received: (qmail 2075 invoked by uid 2001); 25 Sep 2006 20:53:39 -0000 Date: Mon, 25 Sep 2006 15:53:39 -0500 From: "Rick C. Petty" To: tech@nano.net Message-ID: <20060925205339.GA2049@megan.kiwi-computer.com> References: <6.2.0.14.2.20060925123108.03038af0@nano.net> <20060925190740.GI1154@turion.vk2pj.dyndns.org> <6.2.0.14.2.20060925142809.0300e3e0@nano.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6.2.0.14.2.20060925142809.0300e3e0@nano.net> User-Agent: Mutt/1.4.2.1i Cc: freebsd-hackers@freebsd.org Subject: Re: fsck X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rick-freebsd@kiwi-computer.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Sep 2006 20:53:46 -0000 On Mon, Sep 25, 2006 at 02:41:18PM -0600, tech@nano.net wrote: > > Maybe I can mount a dirty partition..... I just need the data off it... Mount it read-only and get the data off it IMMEDIATELY. I wouldn't try fsck-ing on any disk with even a single read or write error. Fsck will fail if it can't find a real sector to allocate, and I don't think it deals well with bad sectors anyway. Point is: don't let it. "dd" the drive ASAP and cut your losses... -- Rick C. Petty From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 25 21:03:01 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5EC4816A40F for ; Mon, 25 Sep 2006 21:03:01 +0000 (UTC) (envelope-from tech@nano.net) Received: from mail.smallweb.com (mail.smallweb.com [216.85.125.111]) by mx1.FreeBSD.org (Postfix) with ESMTP id DDE5943D53 for ; Mon, 25 Sep 2006 21:03:00 +0000 (GMT) (envelope-from tech@nano.net) Received: from Sixpence.mail.smallweb.com (sixpence.nano.net [216.85.125.9]) by mail.smallweb.com (Rockliffe SMTPRA 5.3.11) with ESMTP id for ; Mon, 25 Sep 2006 15:10:55 -0600 Message-Id: <6.2.0.14.2.20060925150231.03029eb0@nano.net> X-Mailer: QUALCOMM Windows Eudora Version 6.2.0.14 Date: Mon, 25 Sep 2006 15:02:59 -0600 To: freebsd-hackers@freebsd.org From: tech@nano.net In-Reply-To: <20060925205339.GA2049@megan.kiwi-computer.com> References: <6.2.0.14.2.20060925123108.03038af0@nano.net> <20060925190740.GI1154@turion.vk2pj.dyndns.org> <6.2.0.14.2.20060925142809.0300e3e0@nano.net> <20060925205339.GA2049@megan.kiwi-computer.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: Re: fsck X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Sep 2006 21:03:01 -0000 Thanks.... At 02:53 PM 9/25/2006, you wrote: >On Mon, Sep 25, 2006 at 02:41:18PM -0600, tech@nano.net wrote: > > > > Maybe I can mount a dirty partition..... I just need the data off it... > >Mount it read-only and get the data off it IMMEDIATELY. I wouldn't try >fsck-ing on any disk with even a single read or write error. Fsck will >fail if it can't find a real sector to allocate, and I don't think it deals >well with bad sectors anyway. Point is: don't let it. "dd" the drive >ASAP and cut your losses... > >-- Rick C. Petty From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 25 21:16:44 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3481B16A403 for ; Mon, 25 Sep 2006 21:16:44 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (agora.rdrop.com [199.26.172.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF66343D4C for ; Mon, 25 Sep 2006 21:16:43 +0000 (GMT) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id k8PLFl7m070201 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Mon, 25 Sep 2006 14:15:47 -0700 (PDT) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id k8PLFlYM070198 for freebsd-hackers@freebsd.org; Mon, 25 Sep 2006 14:15:47 -0700 (PDT) Received: by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA14166; Mon, 25 Sep 06 14:09:47 PDT Date: Mon, 25 Sep 06 14:09:47 PDT From: perryh@pluto.rain.com (Perry Hutchison) Message-Id: <10609252109.AA14166@pluto.rain.com> To: freebsd-hackers@freebsd.org Subject: distinguishing inode block-list from symlink text X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Sep 2006 21:16:44 -0000 Can someone point me to a fairly detailed description of how softdep handles "rm", in particular how it determines whether a particular inode (e.g. a symlink) contains text instead of a list of block numbers? From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 26 01:36:49 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C440816A412 for ; Tue, 26 Sep 2006 01:36:49 +0000 (UTC) (envelope-from soralx@cydem.org) Received: from pd3mo3so.prod.shaw.ca (shawidc-mo1.cg.shawcable.net [24.71.223.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1FB1843D8B for ; Tue, 26 Sep 2006 01:36:38 +0000 (GMT) (envelope-from soralx@cydem.org) Received: from pd3mr2so.prod.shaw.ca (pd3mr2so-qfe3.prod.shaw.ca [10.0.141.178]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0J6600JPNF4C8M40@l-daemon> for freebsd-hackers@freebsd.org; Mon, 25 Sep 2006 19:36:12 -0600 (MDT) Received: from pn2ml2so.prod.shaw.ca ([10.0.121.146]) by pd3mr2so.prod.shaw.ca (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0J66002QNF4CSKL0@pd3mr2so.prod.shaw.ca> for freebsd-hackers@freebsd.org; Mon, 25 Sep 2006 19:36:12 -0600 (MDT) Received: from soralx.cydem.org ([24.87.27.3]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0J6600M3CF4CO0F0@l-daemon> for freebsd-hackers@freebsd.org; Mon, 25 Sep 2006 19:36:12 -0600 (MDT) Date: Mon, 25 Sep 2006 18:36:11 -0700 From: soralx@cydem.org In-reply-to: <20060925205339.GA2049@megan.kiwi-computer.com> To: freebsd-hackers@freebsd.org, rick-freebsd@kiwi-computer.com Message-id: <200609251836.11581.soralx@cydem.org> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7bit Content-disposition: inline References: <6.2.0.14.2.20060925123108.03038af0@nano.net> <6.2.0.14.2.20060925142809.0300e3e0@nano.net> <20060925205339.GA2049@megan.kiwi-computer.com> User-Agent: KMail/1.9.1 Cc: tech@nano.net Subject: Re: fsck X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Sep 2006 01:36:49 -0000 > > Maybe I can mount a dirty partition..... I just need the data off it... > Mount it read-only and get the data off it IMMEDIATELY. I wouldn't try > fsck-ing on any disk with even a single read or write error. Fsck will > fail if it can't find a real sector to allocate, and I don't think it deals > well with bad sectors anyway. Point is: don't let it. "dd" the drive > ASAP and cut your losses... also, just beware that the OS may panic when reading a corrupt FS (this happened to me at least once). umount all other slices. in case it panicks, use verbose cp (`cp -v`) to see which files are being copied, note those which cause panic, and skip them i would also suggest to dd the drive's contents, and then and then fool around with it for some time (in order of a week) to get the most data off of it. First, determine the cause of the failure (use smartmontools); if it's electronics, you'll see smth like: SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error [...] # 4 Short offline Completed: electrical failure 90% 13469 127 There's a good chance that the thing might heal itself somewhat (black magic!). One of the ATA drives I'm using now had this failure, and it persisted for a few days while I was subjecting the HDD to various stresses (heat/cold, vibration, intense workout, manufacturer's test program, etc). Then suddenly, after about a week, it started working, and still works! (of course, all the data was long rewritten million times :/) If the cause is a media defect, I don't believe there's any chance of recovering anymore data. If it failed because of a 'mild' head-crash, you'd want to be very careful with the drive, and make a copy ASAP; don't move it around too much. [SorAlx] ridin' VN1500-B2 From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 26 05:48:48 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 28B2016A417 for ; Tue, 26 Sep 2006 05:48:48 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7021843D5F for ; Tue, 26 Sep 2006 05:48:41 +0000 (GMT) (envelope-from marck@rinet.ru) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.13.8/8.13.6) with ESMTP id k8Q5md7O026613; Tue, 26 Sep 2006 09:48:39 +0400 (MSD) (envelope-from marck@rinet.ru) Date: Tue, 26 Sep 2006 09:48:39 +0400 (MSD) From: Dmitry Morozovsky To: Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= In-Reply-To: <86hcywrxkg.fsf@dwp.des.no> Message-ID: <20060926094720.Q25959@woozle.rinet.ru> References: <200609141232.k8ECWTXj045191@lurza.secnetix.de> <20060919160511.T33371@woozle.rinet.ru> <20060919173421.GA45928@xor.obsecurity.org> <20060920123940.W63482@woozle.rinet.ru> <86hcywrxkg.fsf@dwp.des.no> X-NCC-RegID: ru.rinet X-OpenPGP-Key-ID: 6B691B03 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (woozle.rinet.ru [0.0.0.0]); Tue, 26 Sep 2006 09:48:39 +0400 (MSD) Cc: freebsd-hackers@freebsd.org, Kris Kennaway Subject: Re: numbers don't lie ... X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Sep 2006 05:48:48 -0000 On Mon, 25 Sep 2006, Dag-Erling Sm?rgrav wrote: DS> > > > My experiments show that if you have enough memory to host radmdrive for DS> > > > /usr/src you'd better leave it for caching - there were no statistically DS> > > > meaningful performance difference, at least on machines with 1G+ RAM. DS> > > Really? My measurements show the opposite (on a system with 16GB of DS> > > RAM). DS> > My last test on amd64/dualcore with 4G of RAM and -j4 shows DS> > (buildworld+buildkernel): DS> > DS> > ==> /tmp/buildlog <== DS> > 1996.45 real 3032.94 user 624.83 sys DS> > Script done on Tue Sep 19 14:44:54 2006 DS> > DS> > ==> /tmp/buildlog.md <== DS> > 1957.45 real 3033.93 user 585.78 sys DS> > Script done on Tue Sep 19 15:20:42 2006 DS> > DS> > Second one was with 512M/4k/512 swap-backed md, the former with /usr/src on the DS> > gmirror'ed pair of SATAs. DS> DS> Seems to me that your own numbers contradict you. You saved about 40 DS> seconds (2%) by keeping /usr/src in a ram disk. Well, maybe I did used wrong wording (2% is statistically meaningful), but for me 2% is not worth all the efforts needed to organize ram disk infrastructure... Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------ From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 26 11:21:35 2006 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.ORG Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9F54616A407 for ; Tue, 26 Sep 2006 11:21:35 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id EB90F43D46 for ; Tue, 26 Sep 2006 11:21:34 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (tuxoxq@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id k8QBLRaA041908; Tue, 26 Sep 2006 13:21:33 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id k8QBLRSP041907; Tue, 26 Sep 2006 13:21:27 +0200 (CEST) (envelope-from olli) Date: Tue, 26 Sep 2006 13:21:27 +0200 (CEST) Message-Id: <200609261121.k8QBLRSP041907@lurza.secnetix.de> From: Oliver Fromme To: freebsd-hackers@FreeBSD.ORG, tech@nano.net In-Reply-To: <6.2.0.14.2.20060925123108.03038af0@nano.net> X-Newsgroups: list.freebsd-hackers User-Agent: tin/1.8.0-20051224 ("Ronay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Tue, 26 Sep 2006 13:21:33 +0200 (CEST) Cc: Subject: Re: fsck X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-hackers@FreeBSD.ORG, tech@nano.net List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Sep 2006 11:21:35 -0000 tech@nano.net wrote: > I've got a /usr partition with some problems. During boot it fails and I'm > prompted to run fsck manually. I do so and when fsck has finished it asks > me to run it again, and again, and again... If that happens, I would assume that the disk is dying. Do not try to fsck it, because it will probably make it worse. Instead, use "dd if=/dev... of=... conv=noerror,sync" to copy the disk to a safe place (i.e. other disk of same size or larger). Then run fsck there. > And now for something completely different.... If I can't get the /usr > partition to work is there any way to recreate the user directories from > the password file? The contents will be lost but nobody uses their folder > anyway, I just need all the /usr/home folders created... I could write a > script, but I thought I'd check first to see if something already exists....... That's trivial. In /bin/sh syntax: # cd /home # awk -F: '$3>999{print $1}' /etc/passwd | xargs mkdir # for i in *; do chown $i:$i $i; done That will create home directories for all users whose UID is greater than 999. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "C++ is the only current language making COBOL look good." -- Bertrand Meyer From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 26 11:31:19 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F062716A4E5 for ; Tue, 26 Sep 2006 11:31:19 +0000 (UTC) (envelope-from borjamar@sarenet.es) Received: from smtp2.sarenet.es (smtp2.sarenet.es [194.30.0.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8A47143D46 for ; Tue, 26 Sep 2006 11:31:09 +0000 (GMT) (envelope-from borjamar@sarenet.es) Received: from [127.0.0.1] (matahari.sarenet.es [192.148.167.18]) by smtp2.sarenet.es (Postfix) with ESMTP id 3E76B15E13; Tue, 26 Sep 2006 13:31:02 +0200 (CEST) In-Reply-To: <45180525.3060309@savvis.net> References: <7591D6A9-27EE-4ADE-AF09-84F8636ADD98@sarenet.es> <45180525.3060309@savvis.net> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <51C6D29F-F6AC-4C92-A633-4AD913BBA5B5@sarenet.es> Content-Transfer-Encoding: 7bit From: Borja Marcos Date: Tue, 26 Sep 2006 13:31:00 +0200 To: Maksim Yevmenkin X-Mailer: Apple Mail (2.752.2) Cc: hackers@freebsd.org Subject: Re: network stack problem in sparc64? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Sep 2006 11:31:20 -0000 On 25 Sep 2006, at 18:34, Maksim Yevmenkin wrote: > Borja Marcos wrote: >> earendil# sysctl net.inet.tcp|fgrep space >> net.inet.tcp.sendspace: 0 >> net.inet.tcp.recvspace: 0 >> earendil# sysctl net.inet.udp > > hmmm... how about this (untested) patch? > > -u_long tcp_sendspace = 1024*32; > +int tcp_sendspace = 1024*32; So it's just an integer size problem? I'm just compiling a kernel with the changes. I've had to change tcp_var.h and udp_var.h. I will try and report the results :) Are there many users of FreeBSD/sparc64? Changing the window size is not so esoteric, I guess someone might have tried it before... Borja. From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 26 11:57:00 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1F8CC16A412 for ; Tue, 26 Sep 2006 11:57:00 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail32.syd.optusnet.com.au (mail32.syd.optusnet.com.au [211.29.132.63]) by mx1.FreeBSD.org (Postfix) with ESMTP id B2B8543D78 for ; Tue, 26 Sep 2006 11:56:55 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail32.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k8QBupcu027561 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 26 Sep 2006 21:56:52 +1000 Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.8/8.13.8) with ESMTP id k8QBuph3001590; Tue, 26 Sep 2006 21:56:51 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.8/8.13.8/Submit) id k8QBupp6001589; Tue, 26 Sep 2006 21:56:51 +1000 (EST) (envelope-from peter) Date: Tue, 26 Sep 2006 21:56:51 +1000 From: Peter Jeremy To: tech@nano.net Message-ID: <20060926115651.GC952@turion.vk2pj.dyndns.org> References: <6.2.0.14.2.20060925123108.03038af0@nano.net> <20060925190740.GI1154@turion.vk2pj.dyndns.org> <6.2.0.14.2.20060925142809.0300e3e0@nano.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="IMjqdzrDRly81ofr" Content-Disposition: inline In-Reply-To: <6.2.0.14.2.20060925142809.0300e3e0@nano.net> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.12-2006-07-14 Cc: freebsd-hackers@freebsd.org Subject: Re: fsck X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Sep 2006 11:57:00 -0000 --IMjqdzrDRly81ofr Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, 2006-Sep-25 14:41:18 -0600, tech@nano.net wrote: >The hard drive is in the fridge right now, in case it's a heat problem.=20 >It's FreeBSD version 4.x. It's getting hard read errors, You may have an error in an important sector so fsck can't fix it. As an alternative to the dd or cp suggestions, I'd recommend dump: dump can handle unreadable sectors (though I'm not sure if FreeBSD's dump will tell you which file or inode the sectors belonged to). It's probably your best chance of getting the data off the disk. --=20 Peter Jeremy --IMjqdzrDRly81ofr Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFGRWD/opHv/APuIcRAhBiAKC1XHicvp7W+rYqwfgK2KI0XVp9SwCfSL6m nz+siSUa872toyUvEgKPDi4= =G9Mv -----END PGP SIGNATURE----- --IMjqdzrDRly81ofr-- From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 26 11:58:50 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CE20116A407 for ; Tue, 26 Sep 2006 11:58:50 +0000 (UTC) (envelope-from tech@nano.net) Received: from mail.smallweb.com (mail.smallweb.com [216.85.125.111]) by mx1.FreeBSD.org (Postfix) with ESMTP id 60AAC43D76 for ; Tue, 26 Sep 2006 11:58:45 +0000 (GMT) (envelope-from tech@nano.net) Received: from Sixpence.mail.smallweb.com (sixpence.nano.net [216.85.125.9]) by mail.smallweb.com (Rockliffe SMTPRA 5.3.11) with ESMTP id for ; Tue, 26 Sep 2006 06:06:42 -0600 Message-Id: <6.2.0.14.2.20060926055737.0302bd00@nano.net> X-Mailer: QUALCOMM Windows Eudora Version 6.2.0.14 Date: Tue, 26 Sep 2006 05:58:43 -0600 To: freebsd-hackers@FreeBSD.ORG From: tech@nano.net In-Reply-To: <200609261121.k8QBLRSP041907@lurza.secnetix.de> References: <6.2.0.14.2.20060925123108.03038af0@nano.net> <200609261121.k8QBLRSP041907@lurza.secnetix.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Cc: Subject: Re: fsck X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Sep 2006 11:58:50 -0000 Thanks! And thanks for the sh recommendation, that easier than what I was going to do... At 05:21 AM 9/26/2006, you wrote: >tech@nano.net wrote: > > I've got a /usr partition with some problems. During boot it fails and > I'm > > prompted to run fsck manually. I do so and when fsck has finished it asks > > me to run it again, and again, and again... > >If that happens, I would assume that the disk is dying. Do >not try to fsck it, because it will probably make it worse. >Instead, use "dd if=/dev... of=... conv=noerror,sync" to copy >the disk to a safe place (i.e. other disk of same size or >larger). Then run fsck there. > > > And now for something completely different.... If I can't get the /usr > > partition to work is there any way to recreate the user directories from > > the password file? The contents will be lost but nobody uses their folder > > anyway, I just need all the /usr/home folders created... I could write a > > script, but I thought I'd check first to see if something already > exists....... > >That's trivial. In /bin/sh syntax: > ># cd /home ># awk -F: '$3>999{print $1}' /etc/passwd | xargs mkdir ># for i in *; do chown $i:$i $i; done > >That will create home directories for all users whose UID >is greater than 999. > >Best regards > Oliver > > >-- >Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing >Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd >Any opinions expressed in this message may be personal to the author >and may not necessarily reflect the opinions of secnetix in any way. > >"C++ is the only current language making COBOL look good." > -- Bertrand Meyer From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 26 11:59:48 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 055C516A407 for ; Tue, 26 Sep 2006 11:59:48 +0000 (UTC) (envelope-from tech@nano.net) Received: from mail.smallweb.com (mail.smallweb.com [216.85.125.111]) by mx1.FreeBSD.org (Postfix) with ESMTP id B496C43D64 for ; Tue, 26 Sep 2006 11:59:37 +0000 (GMT) (envelope-from tech@nano.net) Received: from Sixpence.mail.smallweb.com (sixpence.nano.net [216.85.125.9]) by mail.smallweb.com (Rockliffe SMTPRA 5.3.11) with ESMTP id for ; Tue, 26 Sep 2006 06:07:35 -0600 Message-Id: <6.2.0.14.2.20060926055906.03034160@nano.net> X-Mailer: QUALCOMM Windows Eudora Version 6.2.0.14 Date: Tue, 26 Sep 2006 05:59:38 -0600 To: freebsd-hackers@FreeBSD.ORG From: tech@nano.net In-Reply-To: <20060926115651.GC952@turion.vk2pj.dyndns.org> References: <6.2.0.14.2.20060925123108.03038af0@nano.net> <20060925190740.GI1154@turion.vk2pj.dyndns.org> <6.2.0.14.2.20060925142809.0300e3e0@nano.net> <20060926115651.GC952@turion.vk2pj.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Cc: Subject: Re: fsck X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Sep 2006 11:59:48 -0000 Thanks again, I'll be trying all these things this morning. At 05:56 AM 9/26/2006, you wrote: >On Mon, 2006-Sep-25 14:41:18 -0600, tech@nano.net wrote: > >The hard drive is in the fridge right now, in case it's a heat problem. > >It's FreeBSD version 4.x. It's getting hard read errors, > >You may have an error in an important sector so fsck can't fix it. > >As an alternative to the dd or cp suggestions, I'd recommend dump: >dump can handle unreadable sectors (though I'm not sure if FreeBSD's >dump will tell you which file or inode the sectors belonged to). >It's probably your best chance of getting the data off the disk. > > >-- >Peter Jeremy From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 26 17:06:29 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BD02316A4E1 for ; Tue, 26 Sep 2006 17:06:29 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id C39F443DD7 for ; Tue, 26 Sep 2006 17:06:01 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.6/8.13.6) with ESMTP id k8QH5wSu049594; Tue, 26 Sep 2006 13:05:58 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Tue, 26 Sep 2006 12:16:31 -0400 User-Agent: KMail/1.9.1 References: <7591D6A9-27EE-4ADE-AF09-84F8636ADD98@sarenet.es> <45180525.3060309@savvis.net> In-Reply-To: <45180525.3060309@savvis.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200609261216.31760.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Tue, 26 Sep 2006 13:06:00 -0400 (EDT) X-Virus-Scanned: ClamAV 0.88.3/1946/Tue Sep 26 09:18:37 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: Borja Marcos Subject: Re: network stack problem in sparc64? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Sep 2006 17:06:29 -0000 On Monday 25 September 2006 12:34, Maksim Yevmenkin wrote: > Borja Marcos wrote: > > Hello, > > > > I saw this some time ago but always forgot to report it. > > > > I'm running a pair of machines with FreeBSD/sparc64 (various versions, > > one of them is running -STABLE now), and I've seen a problem with the > > network stack. > > > > Looking at buffer and window sizes, > > > > earendil# sysctl net.inet.tcp|fgrep space > > net.inet.tcp.sendspace: 0 > > net.inet.tcp.recvspace: 0 > > > > earendil# sysctl net.inet.udp > > net.inet.udp.checksum: 1 > > net.inet.udp.maxdgram: 0 > > net.inet.udp.recvspace: 0 > > > > When I try to modify them, it doesn't work at all. For example, trying > > to run nfcapd/nfsen in a sparc64 box, I get an error for a setsockopt() > > call > > > > earendil# /usr/local/etc/rc.d/nfsen start > > Starting nfsenStarting nfcpad: upstream1setsockopt(SO_RCVBUF,200000): > > Invalid argument > > Terminated due to errors. > > nfcapd exec error: exit: 255, signal: 0, coredump: 0 > > > > > > For x86 machines the values are correctly reported and they work as > > expected. > > > > I have been poking Google for this but I haven't seen any mention of this. > > hmmm... how about this (untested) patch? Probably better to use SYSCTL_ULONG() instead of SYSCTL_INT() and leave the variables as u_long. > --- tcp_usrreq.c.orig Fri Nov 4 12:26:14 2005 > +++ tcp_usrreq.c Mon Sep 25 09:31:42 2006 > @@ -1161,10 +1161,10 @@ > * sizes, respectively. These are obsolescent (this information should > * be set by the route). > */ > -u_long tcp_sendspace = 1024*32; > +int tcp_sendspace = 1024*32; > SYSCTL_INT(_net_inet_tcp, TCPCTL_SENDSPACE, sendspace, CTLFLAG_RW, > &tcp_sendspace , 0, "Maximum outgoing TCP datagram size"); > -u_long tcp_recvspace = 1024*64; > +int tcp_recvspace = 1024*64; > SYSCTL_INT(_net_inet_tcp, TCPCTL_RECVSPACE, recvspace, CTLFLAG_RW, > &tcp_recvspace , 0, "Maximum incoming TCP datagram size"); > > --- udp_usrreq.c.orig Wed Sep 13 11:19:26 2006 > +++ udp_usrreq.c Mon Sep 25 09:32:00 2006 > @@ -923,12 +923,12 @@ > return (error); > } > > -u_long udp_sendspace = 9216; /* really max datagram size */ > +int udp_sendspace = 9216; /* really max datagram size */ > /* 40 1K datagrams */ > SYSCTL_INT(_net_inet_udp, UDPCTL_MAXDGRAM, maxdgram, CTLFLAG_RW, > &udp_sendspace, 0, "Maximum outgoing UDP datagram size"); > > -u_long udp_recvspace = 40 * (1024 + > +int udp_recvspace = 40 * (1024 + > #ifdef INET6 > sizeof(struct sockaddr_in6) > #else > > thanks, > max > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > > -- John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 26 17:08:29 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 93B8B16A417; Tue, 26 Sep 2006 17:08:29 +0000 (UTC) (envelope-from maksim.yevmenkin@savvis.net) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E41A43DB7; Tue, 26 Sep 2006 17:07:53 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from localhost (localhost.localdomain [127.0.0.1]) by mailgate1b.savvis.net (Postfix) with ESMTP id 6F9723BE6D; Tue, 26 Sep 2006 12:07:52 -0500 (CDT) Received: from mailgate1b.savvis.net ([127.0.0.1]) by localhost (mailgate1b.savvis.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 22281-01-16; Tue, 26 Sep 2006 12:07:52 -0500 (CDT) Received: from [10.12.163.251] (unknown [10.12.163.251]) by mailgate1b.savvis.net (Postfix) with ESMTP id BFBBE3BE50; Tue, 26 Sep 2006 12:07:51 -0500 (CDT) Message-ID: <45195E64.1010302@savvis.net> Date: Tue, 26 Sep 2006 10:07:48 -0700 From: Maksim Yevmenkin User-Agent: Thunderbird 1.5.0.5 (X11/20060906) MIME-Version: 1.0 To: Borja Marcos References: <7591D6A9-27EE-4ADE-AF09-84F8636ADD98@sarenet.es> <45180525.3060309@savvis.net> In-Reply-To: <45180525.3060309@savvis.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at savvis.net Cc: hackers@freebsd.org Subject: Re: network stack problem in sparc64? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Sep 2006 17:08:29 -0000 Maksim Yevmenkin wrote: > Borja Marcos wrote: >> Hello, >> >> I saw this some time ago but always forgot to report it. >> >> I'm running a pair of machines with FreeBSD/sparc64 (various versions, >> one of them is running -STABLE now), and I've seen a problem with the >> network stack. >> >> Looking at buffer and window sizes, >> >> earendil# sysctl net.inet.tcp|fgrep space >> net.inet.tcp.sendspace: 0 >> net.inet.tcp.recvspace: 0 >> >> earendil# sysctl net.inet.udp >> net.inet.udp.checksum: 1 >> net.inet.udp.maxdgram: 0 >> net.inet.udp.recvspace: 0 >> >> When I try to modify them, it doesn't work at all. For example, trying >> to run nfcapd/nfsen in a sparc64 box, I get an error for a >> setsockopt() call >> >> earendil# /usr/local/etc/rc.d/nfsen start >> Starting nfsenStarting nfcpad: upstream1setsockopt(SO_RCVBUF,200000): >> Invalid argument >> Terminated due to errors. >> nfcapd exec error: exit: 255, signal: 0, coredump: 0 >> >> >> For x86 machines the values are correctly reported and they work as >> expected. >> >> I have been poking Google for this but I haven't seen any mention of >> this. > > hmmm... how about this (untested) patch? > > --- tcp_usrreq.c.orig Fri Nov 4 12:26:14 2005 > +++ tcp_usrreq.c Mon Sep 25 09:31:42 2006 > @@ -1161,10 +1161,10 @@ > * sizes, respectively. These are obsolescent (this information should > * be set by the route). > */ > -u_long tcp_sendspace = 1024*32; > +int tcp_sendspace = 1024*32; > SYSCTL_INT(_net_inet_tcp, TCPCTL_SENDSPACE, sendspace, CTLFLAG_RW, > &tcp_sendspace , 0, "Maximum outgoing TCP datagram size"); > -u_long tcp_recvspace = 1024*64; > +int tcp_recvspace = 1024*64; > SYSCTL_INT(_net_inet_tcp, TCPCTL_RECVSPACE, recvspace, CTLFLAG_RW, > &tcp_recvspace , 0, "Maximum incoming TCP datagram size"); > > --- udp_usrreq.c.orig Wed Sep 13 11:19:26 2006 > +++ udp_usrreq.c Mon Sep 25 09:32:00 2006 > @@ -923,12 +923,12 @@ > return (error); > } > > -u_long udp_sendspace = 9216; /* really max datagram size */ > +int udp_sendspace = 9216; /* really max datagram size */ > /* 40 1K datagrams */ > SYSCTL_INT(_net_inet_udp, UDPCTL_MAXDGRAM, maxdgram, CTLFLAG_RW, > &udp_sendspace, 0, "Maximum outgoing UDP datagram size"); > > -u_long udp_recvspace = 40 * (1024 + > +int udp_recvspace = 40 * (1024 + > #ifdef INET6 > sizeof(struct sockaddr_in6) > #else actually, it was fixed in -current long time ago, === Revision 1.128 / (download) - annotate - [select for diffs], Wed Dec 14 22:27:48 2005 UTC (9 months, 1 week ago) by mux Branch: MAIN Changes since 1.127: +2 -2 lines Diff to previous 1.127 (colored) Fix a bunch of SYSCTL_INT() that should have been SYSCTL_ULONG() to match the type of the variable they are exporting. Spotted by: Thomas Hurst MFC after: 3 days === i guess mfc did not happen in 3 days. thanks, max > > thanks, > max > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 27 09:00:39 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3E98E16A494 for ; Wed, 27 Sep 2006 09:00:39 +0000 (UTC) (envelope-from mux@freebsd.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 04E3D43D45 for ; Wed, 27 Sep 2006 09:00:38 +0000 (GMT) (envelope-from mux@freebsd.org) Received: by elvis.mu.org (Postfix, from userid 1920) id E17E01A3C1A; Wed, 27 Sep 2006 02:00:38 -0700 (PDT) Date: Wed, 27 Sep 2006 11:00:38 +0200 From: Maxime Henrion To: Maksim Yevmenkin Message-ID: <20060927090038.GC81610@elvis.mu.org> References: <7591D6A9-27EE-4ADE-AF09-84F8636ADD98@sarenet.es> <45180525.3060309@savvis.net> <45195E64.1010302@savvis.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45195E64.1010302@savvis.net> User-Agent: Mutt/1.4.2.2i Cc: hackers@freebsd.org, Borja Marcos Subject: Re: network stack problem in sparc64? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Sep 2006 09:00:39 -0000 Maksim Yevmenkin wrote: > Maksim Yevmenkin wrote: > >Borja Marcos wrote: > >>Hello, > >> > >>I saw this some time ago but always forgot to report it. > >> > >>I'm running a pair of machines with FreeBSD/sparc64 (various versions, > >>one of them is running -STABLE now), and I've seen a problem with the > >>network stack. > >> > >>Looking at buffer and window sizes, > >> > >>earendil# sysctl net.inet.tcp|fgrep space > >>net.inet.tcp.sendspace: 0 > >>net.inet.tcp.recvspace: 0 > >> > >>earendil# sysctl net.inet.udp > >>net.inet.udp.checksum: 1 > >>net.inet.udp.maxdgram: 0 > >>net.inet.udp.recvspace: 0 > >> > >>When I try to modify them, it doesn't work at all. For example, trying > >>to run nfcapd/nfsen in a sparc64 box, I get an error for a > >>setsockopt() call > >> > >>earendil# /usr/local/etc/rc.d/nfsen start > >>Starting nfsenStarting nfcpad: upstream1setsockopt(SO_RCVBUF,200000): > >>Invalid argument > >>Terminated due to errors. > >>nfcapd exec error: exit: 255, signal: 0, coredump: 0 > >> > >> > >>For x86 machines the values are correctly reported and they work as > >>expected. > >> > >>I have been poking Google for this but I haven't seen any mention of > >>this. > > > >hmmm... how about this (untested) patch? > > > >--- tcp_usrreq.c.orig Fri Nov 4 12:26:14 2005 > >+++ tcp_usrreq.c Mon Sep 25 09:31:42 2006 > >@@ -1161,10 +1161,10 @@ > > * sizes, respectively. These are obsolescent (this information should > > * be set by the route). > > */ > >-u_long tcp_sendspace = 1024*32; > >+int tcp_sendspace = 1024*32; > > SYSCTL_INT(_net_inet_tcp, TCPCTL_SENDSPACE, sendspace, CTLFLAG_RW, > > &tcp_sendspace , 0, "Maximum outgoing TCP datagram size"); > >-u_long tcp_recvspace = 1024*64; > >+int tcp_recvspace = 1024*64; > > SYSCTL_INT(_net_inet_tcp, TCPCTL_RECVSPACE, recvspace, CTLFLAG_RW, > > &tcp_recvspace , 0, "Maximum incoming TCP datagram size"); > > > >--- udp_usrreq.c.orig Wed Sep 13 11:19:26 2006 > >+++ udp_usrreq.c Mon Sep 25 09:32:00 2006 > >@@ -923,12 +923,12 @@ > > return (error); > > } > > > >-u_long udp_sendspace = 9216; /* really max datagram size */ > >+int udp_sendspace = 9216; /* really max datagram size */ > > /* 40 1K datagrams */ > > SYSCTL_INT(_net_inet_udp, UDPCTL_MAXDGRAM, maxdgram, CTLFLAG_RW, > > &udp_sendspace, 0, "Maximum outgoing UDP datagram size"); > > > >-u_long udp_recvspace = 40 * (1024 + > >+int udp_recvspace = 40 * (1024 + > > #ifdef INET6 > > sizeof(struct sockaddr_in6) > > #else > > > actually, it was fixed in -current long time ago, > > === > Revision 1.128 / (download) - annotate - [select for diffs], Wed Dec 14 > 22:27:48 2005 UTC (9 months, 1 week ago) by mux > Branch: MAIN > Changes since 1.127: +2 -2 lines > Diff to previous 1.127 (colored) > > Fix a bunch of SYSCTL_INT() that should have been SYSCTL_ULONG() to > match the type of the variable they are exporting. > > Spotted by: Thomas Hurst > MFC after: 3 days > === > > i guess mfc did not happen in 3 days. Oops! I'm terribly sorry about this. Unless there is an objection, I'll MFC those ASAP. Cheers, Maxime From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 27 12:23:26 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4A8F116A407; Wed, 27 Sep 2006 12:23:26 +0000 (UTC) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id 993A543D5C; Wed, 27 Sep 2006 12:23:25 +0000 (GMT) (envelope-from max@love2party.net) Received: from [88.64.177.224] (helo=amd64.laiers.local) by mrelayeu.kundenserver.de (node=mrelayeu1) with ESMTP (Nemesis), id 0MKwpI-1GSYRf3e6A-0004RA; Wed, 27 Sep 2006 14:23:24 +0200 From: Max Laier Organization: FreeBSD To: freebsd-hackers@freebsd.org Date: Wed, 27 Sep 2006 14:23:17 +0200 User-Agent: KMail/1.9.4 X-Face: ,,8R(x[kmU]tKN@>gtH1yQE4aslGdu+2]; R]*pL,U>^H?)gW@49@wdJ`H<%}*_BD U_or=\mOZf764&nYj=JYbR1PW0ud>|!~, , CPC.1-D$FG@0h3#'5"k{V]a~. X-Provags-ID: kundenserver.de abuse@kundenserver.de login:61c499deaeeba3ba5be80f48ecc83056 Cc: freebsd-current@freebsd.org Subject: Call for Status Reports: Oct 6 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: monthly@freebsd.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Sep 2006 12:23:26 -0000 --nextPart37427511.YMaSj71Kfd Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline All, it almost slipped my mind to remind you that it's that time again. We are= =20 collecting Status Reports for the third quarter of 2006. I know that=20 most of you are wrapped in the preparation for FreeBSD 6.2. It would be=20 great if you could still find some time to write about all the goodies=20 that where MFCed and newly appeared in CURRENT between June and now. We would also like to hear from our Google Summer of Code participants how= =20 their projects turned out - you may copy and paste or redirect to=20 your "official" documentation ;) Just let's make sure your work gets the=20 attention it deserves! Submissions are due by 6 October, 2006. Submission details can be found=20 on http://www.freebsd.org/news/status/ As always, this is by no means limited to FreeBSD committers, but a call=20 to report news and status about any FreeBSD related project. Looking forward to reading your reports. See you at EuroBSDCon 2006 in Milan: http://www.eurobsdcon.org/ =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart37427511.YMaSj71Kfd Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQBFGm06XyyEoT62BG0RApCBAJ0QEn7YGJmuqtPOzvevVjUa8pmjlwCbBzzz +a3P/mFrAijFVZkx0fezzFk= =u9Qo -----END PGP SIGNATURE----- --nextPart37427511.YMaSj71Kfd-- From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 27 22:31:20 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BECA316A403 for ; Wed, 27 Sep 2006 22:31:20 +0000 (UTC) (envelope-from dking@ketralnis.com) Received: from ketralnis.com (melchoir.ketralnis.com [68.183.67.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id A3C0D43D68 for ; Wed, 27 Sep 2006 22:31:08 +0000 (GMT) (envelope-from dking@ketralnis.com) Received: from [192.168.1.31] (pix.xythos.com [64.154.218.194]) (authenticated bits=0) by ketralnis.com (8.13.6/8.13.6) with ESMTP id k8RMV7eX090152 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO) for ; Wed, 27 Sep 2006 15:31:07 -0700 (PDT) (envelope-from dking@ketralnis.com) Mime-Version: 1.0 (Apple Message framework v752.2) In-Reply-To: <200609261121.k8QBLRSP041907@lurza.secnetix.de> References: <200609261121.k8QBLRSP041907@lurza.secnetix.de> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <43827BA9-D59C-4C5E-8727-2DF7AFE8F939@ketralnis.com> Content-Transfer-Encoding: 7bit From: David King Date: Wed, 27 Sep 2006 15:30:44 -0700 To: freebsd-hackers@freebsd.org X-Mailer: Apple Mail (2.752.2) Subject: Re: fsck X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Sep 2006 22:31:20 -0000 >> And now for something completely different.... If I can't get the / >> usr >> partition to work is there any way to recreate the user >> directories from >> the password file? The contents will be lost but nobody uses their >> folder >> anyway, I just need all the /usr/home folders created... I could >> write a >> script, but I thought I'd check first to see if something already >> exists....... > That's trivial. In /bin/sh syntax: > # cd /home > # awk -F: '$3>999{print $1}' /etc/passwd | xargs mkdir > # for i in *; do chown $i:$i $i; done It might help to copy the stuff out of /usr/share/skel, too, like this (untested): cd /home for user in `awk -F: '$3>999{print $1}' /etc/passwd`; do cp -r /usr/share/skel ./$user for dotfile in $user/dot.*; do mv $dotfile `echo $dotfile | sed 's#/dot\.#.#'` done chown -R $user:$user $user done Take a look at /usr/sbin/adduser to see how it does it > That will create home directories for all users whose UID > is greater than 999. > > Best regards > Oliver > > > -- > Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing > Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd > Any opinions expressed in this message may be personal to the author > and may not necessarily reflect the opinions of secnetix in any way. > > "C++ is the only current language making COBOL look good." > -- Bertrand Meyer > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers- > unsubscribe@freebsd.org" -- David King Computer Programmer Ketralnis Systems From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 29 19:40:22 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7638016A412 for ; Fri, 29 Sep 2006 19:40:22 +0000 (UTC) (envelope-from deathwolf@gmail.com) Received: from relay01.pair.com (relay01.pair.com [209.68.5.15]) by mx1.FreeBSD.org (Postfix) with SMTP id 9905E43D49 for ; Fri, 29 Sep 2006 19:40:21 +0000 (GMT) (envelope-from deathwolf@gmail.com) Received: (qmail 49424 invoked from network); 29 Sep 2006 19:40:20 -0000 Received: from unknown (HELO eugenie) (unknown) by unknown with SMTP; 29 Sep 2006 19:40:20 -0000 X-pair-Authenticated: 86.209.44.81 Date: Fri, 29 Sep 2006 21:40:21 +0200 From: Paul-Kenji Cahier X-Mailer: The Bat! (v3.80.06) Professional X-Priority: 3 (Normal) Message-ID: <52009783.20060929214021@F1-Photo.com> To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: VIA Sata Problem maybe? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Paul-Kenji Cahier List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Sep 2006 19:40:22 -0000 Hello, I am currently experiencing some technical problems with one of my remote servers running 6.1-RELEASE(#0: Sun May 7 04:32:43 UTC 2006 root@opus.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386) with the default kernel. Configuration is the following: http://83.149.102.206/lspci.txt The problem is basically the following: Every few days, the server crashes. Sometimes it reboots, sometimes it doesnt. In all cases, there's not a single trace of anything in logs(not even a single word in /var/log/messages). The problem usually worsens after it auto-reboots itself as it runs an fsck at the end of the boot time. That fsck runs, and most of the time it crashes again, causing a reboot or a complete freeze, then another reboot, etc. Once the system freezes, my only option is(since i dont have local access to the server) to remote reboot on a rescue os that allows me to set my rescue freebsd partition as main, and get a rescue freebsd. Once in, i just fsck the file system until it is marked clean and reboot. And everything goes fine... for a few days. Now what i tried was, after an unwanted reboot, to monitor the logs of fsck running to see what made it crash. Here is what i got from tail -f /var/log/messages(ad4s2f is the /usr partition that has most of the data): Sep 29 19:31:54 arcueid fsck: /dev/ad4s2f: INCORRECT BLOCK COUNT I=2615093 (20 should be 0) (CORRECTED) Sep 29 19:31:54 arcueid fsck: /dev/ad4s2f: INCORRECT BLOCK COUNT I=2615094 (20 should be 0) (CORRECTED) Sep 29 19:31:54 arcueid fsck: /dev/ad4s2f: INCORRECT BLOCK COUNT I=2615095 (20 should be 0) (CORRECTED) Sep 29 19:31:54 arcueid fsck: /dev/ad4s2f: INCORRECT BLOCK COUNT I=2615096 (20 should be 0) (CORRECTED) Sep 29 19:31:54 arcueid fsck: /dev/ad4s2f: INCORRECT BLOCK COUNT I=2615097 (20 should be 0) (CORRECTED) Sep 29 19:31:54 arcueid fsck: /dev/ad4s2f: INCORRECT BLOCK COUNT I=2615098 (20 should be 0) (CORRECTED) Sep 29 19:31:54 arcueid fsck: /dev/ad4s2f: INCORRECT BLOCK COUNT I=2615099 (20 should be 0) (CORRECTED) Sep 29 19:31:54 arcueid fsck: /dev/ad4s2f: INCORRECT BLOCK COUNT I=2615100 (16 should be 0) (CORRECTED) Sep 29 19:31:54 arcueid fsck: /dev/ad4s2f: INCORRECT BLOCK COUNT I=3674361 (12 should be 0) (CORRECTED) Sep 29 19:31:54 arcueid fsck: /dev/ad4s2f: INCORRECT BLOCK COUNT I=14994399 (4 should be 0) (CORRECTED) Sep 29 19:31:54 arcueid fsck: /dev/ad4s2f: INCORRECT BLOCK COUNT I=16016109 (6624 should be 320) (CORRECTED) Sep 29 19:31:54 arcueid fsck: /dev/ad4s2f: INCORRECT BLOCK COUNT I=16016110 (12 should be 0) (CORRECTED) Sep 29 19:31:54 arcueid fsck: /dev/ad4s2f: INCORRECT BLOCK COUNT I=16016111 (4352 should be 0) (CORRECTED) Sep 29 19:31:54 arcueid fsck: /dev/ad4s2f: INCORRECT BLOCK COUNT I=16016112 (8 should be 0) (CORRECTED) Sep 29 19:31:54 arcueid fsck: /dev/ad4s2f: UNREF FILE I=6 OWNER=root MODE=100400 Sep 29 19:31:54 arcueid fsck: /dev/ad4s2f: SIZE=151445575864 MTIME=Sep 29 19:02 2006 (CLEARED) Sep 29 19:31:54 arcueid fsck: /dev/ad4s2f: ALLOCATED FRAGS 431136-431167 MARKED FREE Sep 29 19:31:54 arcueid fsck: Sep 29 19:31:54 arcueid fsck: /dev/ad4s2f: UNEXPECTED SOFT UPDATE INCONSISTENCY; RUN fsck MANUALLY. And then the server went more or less haywire and crashed(no other input in /var/log/messages though) I also monitored the fsck process to see how it was running: <19:15:57> root@arcueid:~$ while (true); do echo `date` `ps aux | grep fsck | grep ad4`; sleep 2; done <...> Fri Sep 29 19:29:36 CEST 2006 root 777 0.7 1.8 19092 18612 ?? DN 7:11PM 0:21.07 fsck_ufs: /dev/ad4s2f p2 92% (fsck_ufs) Fri Sep 29 19:29:38 CEST 2006 root 777 0.6 1.8 19092 18612 ?? DN 7:11PM 0:21.09 fsck_ufs: /dev/ad4s2f p2 92% (fsck_ufs) Fri Sep 29 19:29:40 CEST 2006 root 777 0.6 1.8 19092 18612 ?? RN 7:11PM 0:21.12 fsck_ufs: /dev/ad4s2f p2 92% (fsck_ufs) Fri Sep 29 19:29:42 CEST 2006 root 777 0.6 1.8 19092 18612 ?? RN 7:11PM 0:21.14 fsck_ufs: /dev/ad4s2f p2 94% (fsck_ufs) Fri Sep 29 19:29:44 CEST 2006 root 777 0.6 1.8 19092 18612 ?? SN 7:11PM 0:21.17 fsck_ufs: /dev/ad4s2f p2 94% (fsck_ufs) Fri Sep 29 19:29:46 CEST 2006 root 777 0.6 1.8 19092 18612 ?? DN 7:11PM 0:21.19 fsck_ufs: /dev/ad4s2f p2 95% (fsck_ufs) Fri Sep 29 19:29:48 CEST 2006 root 777 0.6 1.8 19092 18612 ?? DN 7:11PM 0:21.21 fsck_ufs: /dev/ad4s2f p2 95% (fsck_ufs) Fri Sep 29 19:29:50 CEST 2006 root 777 0.6 1.8 19092 18612 ?? SN 7:11PM 0:21.25 fsck_ufs: /dev/ad4s2f p2 95% (fsck_ufs) Fri Sep 29 19:29:52 CEST 2006 root 777 0.5 1.8 19092 18612 ?? DN 7:11PM 0:21.29 fsck_ufs: /dev/ad4s2f p2 96% (fsck_ufs) Fri Sep 29 19:29:54 CEST 2006 root 777 0.8 1.8 19092 18612 ?? SN 7:11PM 0:21.35 fsck_ufs: /dev/ad4s2f p2 96% (fsck_ufs) Fri Sep 29 19:29:56 CEST 2006 root 777 0.8 1.8 19092 18612 ?? SN 7:11PM 0:21.38 fsck_ufs: /dev/ad4s2f p2 96% (fsck_ufs) Fri Sep 29 19:29:58 CEST 2006 root 777 0.8 1.8 19092 18612 ?? DN 7:11PM 0:21.40 fsck_ufs: /dev/ad4s2f p2 96% (fsck_ufs) Fri Sep 29 19:30:00 CEST 2006 root 777 0.7 1.8 19092 18612 ?? DN 7:11PM 0:21.43 fsck_ufs: /dev/ad4s2f p2 96% (fsck_ufs) Fri Sep 29 19:30:02 CEST 2006 root 777 0.7 1.8 19092 18612 ?? SN 7:11PM 0:21.47 fsck_ufs: /dev/ad4s2f p2 97% (fsck_ufs) Fri Sep 29 19:30:04 CEST 2006 root 777 0.6 1.8 19092 18612 ?? SN 7:11PM 0:21.49 fsck_ufs: /dev/ad4s2f p2 97% (fsck_ufs) Fri Sep 29 19:30:06 CEST 2006 root 777 0.5 1.8 19092 18612 ?? DN 7:11PM 0:21.51 fsck_ufs: /dev/ad4s2f p2 97% (fsck_ufs) Fri Sep 29 19:30:08 CEST 2006 root 777 0.4 1.8 19092 18612 ?? DN 7:11PM 0:21.53 fsck_ufs: /dev/ad4s2f p2 97% (fsck_ufs) Fri Sep 29 19:30:10 CEST 2006 root 777 0.6 1.8 19092 18612 ?? DN 7:11PM 0:21.57 fsck_ufs: /dev/ad4s2f p2 97% (fsck_ufs) Fri Sep 29 19:30:12 CEST 2006 root 777 0.7 1.8 19092 18612 ?? SN 7:11PM 0:21.59 fsck_ufs: /dev/ad4s2f p2 98% (fsck_ufs) Fri Sep 29 19:30:14 CEST 2006 root 777 0.6 1.8 19092 18612 ?? SN 7:11PM 0:21.59 fsck_ufs: /dev/ad4s2f p2 98% (fsck_ufs) Fri Sep 29 19:30:16 CEST 2006 root 777 0.5 1.8 19092 18612 ?? DN 7:11PM 0:21.61 fsck_ufs: /dev/ad4s2f p2 98% (fsck_ufs) Fri Sep 29 19:30:18 CEST 2006 root 777 0.4 1.8 19092 18612 ?? SN 7:11PM 0:21.62 fsck_ufs: /dev/ad4s2f p2 98% (fsck_ufs) Fri Sep 29 19:30:20 CEST 2006 root 777 0.4 1.8 19092 18612 ?? SN 7:11PM 0:21.63 fsck_ufs: /dev/ad4s2f p2 99% (fsck_ufs) Fri Sep 29 19:30:23 CEST 2006 root 777 0.3 1.8 19092 18612 ?? DN 7:11PM 0:21.64 fsck_ufs: /dev/ad4s2f p2 99% (fsck_ufs) Fri Sep 29 19:30:25 CEST 2006 root 777 0.2 1.8 19092 18612 ?? DN 7:11PM 0:21.66 fsck_ufs: /dev/ad4s2f p2 99% (fsck_ufs) Fri Sep 29 19:30:27 CEST 2006 root 777 0.1 1.8 19092 18612 ?? SN 7:11PM 0:21.68 fsck_ufs: /dev/ad4s2f p2 99% (fsck_ufs) Fri Sep 29 19:30:29 CEST 2006 root 777 0.0 1.8 19092 18612 ?? SN 7:11PM 0:21.70 fsck_ufs: /dev/ad4s2f p2 99% (fsck_ufs) Fri Sep 29 19:31:12 CEST 2006 root 777 0.0 1.8 19092 18724 ?? RN 7:11PM 0:22.17 fsck_ufs: /dev/ad4s2f p4 0% (fsck_ufs) Fri Sep 29 19:31:14 CEST 2006 root 777 0.9 1.8 19092 18748 ?? DN 7:11PM 0:22.34 fsck_ufs: /dev/ad4s2f p4 0% (fsck_ufs) Fri Sep 29 19:31:16 CEST 2006 root 777 0.9 1.8 19092 18748 ?? DN 7:11PM 0:22.35 fsck_ufs: /dev/ad4s2f p4 0% (fsck_ufs) Fri Sep 29 19:31:18 CEST 2006 root 777 0.7 1.8 19092 18748 ?? DN 7:11PM 0:22.37 fsck_ufs: /dev/ad4s2f p4 0% (fsck_ufs) Fri Sep 29 19:31:20 CEST 2006 root 777 0.7 1.8 19092 18748 ?? DN 7:11PM 0:22.40 fsck_ufs: /dev/ad4s2f p4 0% (fsck_ufs) Fri Sep 29 19:31:22 CEST 2006 root 777 0.6 1.8 19092 18748 ?? DN 7:11PM 0:22.40 fsck_ufs: /dev/ad4s2f p4 0% (fsck_ufs) Fri Sep 29 19:31:25 CEST 2006 root 777 0.5 1.8 19092 18748 ?? DN 7:11PM 0:22.42 fsck_ufs: /dev/ad4s2f p4 0% (fsck_ufs) Fri Sep 29 19:31:27 CEST 2006 root 777 0.5 1.8 19092 18748 ?? DN 7:11PM 0:22.45 fsck_ufs: /dev/ad4s2f p4 0% (fsck_ufs) Fri Sep 29 19:31:29 CEST 2006 root 777 0.4 1.8 19092 18748 ?? DN 7:11PM 0:22.46 fsck_ufs: /dev/ad4s2f p4 0% (fsck_ufs) Fri Sep 29 19:31:31 CEST 2006 root 777 0.4 1.8 19092 18748 ?? DN 7:11PM 0:22.48 fsck_ufs: /dev/ad4s2f p4 0% (fsck_ufs) Fri Sep 29 19:31:33 CEST 2006 root 777 0.4 1.8 19092 18748 ?? DN 7:11PM 0:22.50 fsck_ufs: /dev/ad4s2f p4 0% (fsck_ufs) Fri Sep 29 19:31:35 CEST 2006 root 777 0.3 1.8 19092 18748 ?? DN 7:11PM 0:22.51 fsck_ufs: /dev/ad4s2f p4 0% (fsck_ufs) Fri Sep 29 19:31:37 CEST 2006 root 777 0.2 1.8 19092 18748 ?? DN 7:11PM 0:22.53 fsck_ufs: /dev/ad4s2f p4 0% (fsck_ufs) Fri Sep 29 19:31:39 CEST 2006 root 777 0.1 1.8 19092 18748 ?? DN 7:11PM 0:22.55 fsck_ufs: /dev/ad4s2f p4 0% (fsck_ufs) Fri Sep 29 19:31:41 CEST 2006 root 777 0.2 1.8 19092 18748 ?? DN 7:11PM 0:22.57 fsck_ufs: /dev/ad4s2f p4 0% (fsck_ufs) Fri Sep 29 19:31:43 CEST 2006 root 777 0.1 1.8 19092 18748 ?? DN 7:11PM 0:22.57 fsck_ufs: /dev/ad4s2f p4 0% (fsck_ufs) Fri Sep 29 19:31:45 CEST 2006 root 777 0.0 1.8 19092 18748 ?? DN 7:11PM 0:22.58 fsck_ufs: /dev/ad4s2f p4 0% (fsck_ufs) Fri Sep 29 19:31:47 CEST 2006 root 777 0.0 1.8 19092 18748 ?? DN 7:11PM 0:22.59 fsck_ufs: /dev/ad4s2f p4 0% (fsck_ufs) Fri Sep 29 19:31:49 CEST 2006 root 777 0.0 1.8 19092 18748 ?? DN 7:11PM 0:22.60 fsck_ufs: /dev/ad4s2f p4 0% (fsck_ufs) Fri Sep 29 19:31:51 CEST 2006 root 777 0.0 1.8 19092 18748 ?? DN 7:11PM 0:22.61 fsck_ufs: /dev/ad4s2f p4 0% (fsck_ufs) Fri Sep 29 19:31:53 CEST 2006 root 777 0.0 1.8 19092 18748 ?? DN 7:11PM 0:22.61 fsck_ufs: /dev/ad4s2f p4 0% (fsck_ufs) Fri Sep 29 19:31:55 CEST 2006 Fri Sep 29 19:31:57 CEST 2006 Fri Sep 29 19:31:59 CEST 2006 Fri Sep 29 19:32:01 CEST 2006 Fri Sep 29 19:32:03 CEST 2006 Fri Sep 29 19:32:05 CEST 2006 Fri Sep 29 19:32:07 CEST 2006 Fri Sep 29 19:32:09 CEST 2006 Fri Sep 29 19:32:11 CEST 2006 Fri Sep 29 19:32:13 CEST 2006 Fri Sep 29 19:32:15 CEST 2006 Fri Sep 29 19:32:17 CEST 2006 Fri Sep 29 19:32:19 CEST 2006 Fri Sep 29 19:32:21 CEST 2006 Fri Sep 29 19:32:23 CEST 2006 Fri Sep 29 19:32:25 CEST 2006 As you can see, at the same time as softupdate reported a problem, the whole system wouldnt work anymore, process wouldnt display properly anymore either. RAM was extensively tested and is perfectly fine. The power supply unit seems to be running really fine too, with no particular events. The hard drive itself was tested extensively using both smart values and writing/reading from a linux setup and had not a single fault or alarming value. Another quite surprising event is the following: After a crash, i went into the rescue freebsd and as usual started an fsck. Result was: arcueid-rescue# fsck -y /dev/ad4s2f ** /dev/ad4s2f ** Last Mounted on /usr ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 1362084 files, 47944480 used, 23676944 free (1752392 frags, 2740569 blocks, 2.4% fragmentation) ***** FILE SYSTEM MARKED CLEAN ***** Just for the fun i ran it a second time just after: arcueid-rescue# fsck -y /dev/ad4s2f ** /dev/ad4s2f ** Last Mounted on /usr ** Phase 1 - Check Blocks and Sizes CANNOT READ BLK: 190083360 UNEXPECTED SOFT UPDATE INCONSISTENCY CONTINUE? yes THE FOLLOWING DISK SECTORS COULD NOT BE READ: 190083360, 190083361, 190083362, 190083363, 190083364, 190083365, 190083366, 190083367, 190083368, 190083369, 190083370, 190083371, 190083372, 190083373, 190083374, 190083375, 190083376, 190083377, 190083378, 190083379, 190083380, 190083381, 190083382, 190083383, 190083384, 190083385, 190083386, 190083387, 190083388, 190083389, 190083390, 190083391, INCORRECT BLOCK COUNT I=18375172 (640 should be 416) CORRECT? yes CANNOT READ BLK: 293557088 UNEXPECTED SOFT UPDATE INCONSISTENCY CONTINUE? yes THE FOLLOWING DISK SECTORS COULD NOT BE READ: 293557088, 293557089, 293557090, 293557091, 293557092, 293557093, 293557094, 293557095, 293557096, 293557097, 293557098, 293557099, 293557100, 293557101, 293557102, 293557103, 293557104, 293557105, 293557106, 293557107, 293557108, 293557109, 293557110, 293557111, 293557112, 293557113, 293557114, 293557115, 293557116, 293557117, 293557118, 293557119, CANNOT READ BLK: 190090784 UNEXPECTED SOFT UPDATE INCONSISTENCY CONTINUE? yes THE FOLLOWING DISK SECTORS COULD NOT BE READ: 190090784, 190090785, 190090786, 190090787, 190090788, 190090789, 190090790, 190090791, 190090792, 190090793, 190090794, 190090795, 190090796, 190090797, 190090798, 190090799, 190090800, 190090801, 190090802, 190090803, 190090804, 190090805, 190090806, 190090807, 190090808, 190090809, 190090810, 190090811, 190090812, 190090813, 190090814, 190090815, INCORRECT BLOCK COUNT I=18375174 (480 should be 416) CORRECT? yes CANNOT READ BLK: 190122624 UNEXPECTED SOFT UPDATE INCONSISTENCY CONTINUE? yes THE FOLLOWING DISK SECTORS COULD NOT BE READ: 190122624, 190122625, 190122626, 190122627, 190122628, 190122629, 190122630, 190122631, 190122632, 190122633, 190122634, 190122635, 190122636, 190122637, 190122638, 190122639, 190122640, 190122641, 190122642, 190122643, 190122644, 190122645, 190122646, 190122647, 190122648, 190122649, 190122650, 190122651, 190122652, 190122653, 190122654, 190122655, INCORRECT BLOCK COUNT I=18375178 (512 should be 416) CORRECT? yes CANNOT READ BLK: 190422528 UNEXPECTED SOFT UPDATE INCONSISTENCY CONTINUE? yes [etc] And then it crashed.... Again i did the sata tests numerous times and the drive seems perfectly healthy... So i have to think it might be driver related rather than hardware related. Any help would be appreciated, -- Best regards, Paul-Kenji From owner-freebsd-hackers@FreeBSD.ORG Sat Sep 30 22:22:16 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5B0CA16A403 for ; Sat, 30 Sep 2006 22:22:16 +0000 (UTC) (envelope-from deathwolf@gmail.com) Received: from relay03.pair.com (relay03.pair.com [209.68.5.17]) by mx1.FreeBSD.org (Postfix) with SMTP id C81F443D49 for ; Sat, 30 Sep 2006 22:22:15 +0000 (GMT) (envelope-from deathwolf@gmail.com) Received: (qmail 72099 invoked from network); 30 Sep 2006 22:22:13 -0000 Received: from unknown (HELO eugenie) (unknown) by unknown with SMTP; 30 Sep 2006 22:22:13 -0000 X-pair-Authenticated: 86.209.43.106 Date: Sun, 1 Oct 2006 00:22:14 +0200 From: Paul-Kenji Cahier X-Mailer: The Bat! (v3.80.06) Professional X-Priority: 3 (Normal) Message-ID: <189665893.20061001002214@F1-Photo.com> To: freebsd-hackers@freebsd.org In-Reply-To: <7528F5A9-4B4A-4FEC-9726-70BDCF31B631@foolishgames.com> References: <52009783.20060929214021@F1-Photo.com> <7528F5A9-4B4A-4FEC-9726-70BDCF31B631@foolishgames.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re[2]: VIA Sata Problem maybe? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Paul-Kenji Cahier List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Sep 2006 22:22:16 -0000 Hello, thanks for the reply. > You mentioned softupdates. Try disabling softupdates on the file > system. I've had to do this in the past with a sata raid 1 setup or > the system would reboot every few days. I tried that earlier, and it didnt help at all, i got a crash in the minutes after rebooting during fsck. > Also verify the "speed" of > the drives. I had a problem with freebsd 5.3 where it would set my > sata drives as udma33 which caused quite a few problems. How do i check the speed?(although i think it's not linked to that) You may > want to check if there are any updates in stable for the driver you > are using. 6.2 is close to release and while there are several > outstanding issues, it may improve your situation. where can i find a list of the drivers updates? I downloaded the latest HEAD kernel source, but from looking into the GENERIC configuration file, i didnt see anything for a VIA ATA chipset, or is there more than what is in the GENERIC file? Best Regards, Paul-Kenji Cahier >> Hello, >> I am currently experiencing some technical problems with one of my >> remote servers running 6.1-RELEASE(#0: Sun May 7 04:32:43 UTC >> 2006 root@opus.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC >> i386) with the default kernel. >> Configuration is the following: http://83.149.102.206/lspci.txt >> The problem is basically the following: >> Every few days, the server crashes. Sometimes it reboots, sometimes >> it doesnt. In all cases, there's not a single trace of anything in >> logs(not even a single word in /var/log/messages). >> The problem usually worsens after it auto-reboots itself as it runs >> an fsck at the end of the boot time. That fsck runs, and most of >> the time it crashes again, causing a reboot or a complete freeze, >> then another reboot, etc. Once the system freezes, my only option >> is(since i dont have local access to the server) to remote reboot >> on a rescue os that allows me to set my rescue freebsd partition as >> main, and get a rescue freebsd. Once in, i just fsck the file >> system until it is marked clean and reboot. And everything goes >> fine... >> for a few days. >> Now what i tried was, after an unwanted reboot, to monitor the logs >> of fsck running to see what made it crash. >> Here is what i got from tail -f /var/log/messages(ad4s2f is the / >> usr partition that has most of the data): >> Sep 29 19:31:54 arcueid fsck: /dev/ad4s2f: INCORRECT BLOCK COUNT >> I=2615093 (20 should be 0) (CORRECTED) >> Sep 29 19:31:54 arcueid fsck: /dev/ad4s2f: INCORRECT BLOCK COUNT >> I=2615094 (20 should be 0) (CORRECTED) >> Sep 29 19:31:54 arcueid fsck: /dev/ad4s2f: INCORRECT BLOCK COUNT >> I=2615095 (20 should be 0) (CORRECTED) >> Sep 29 19:31:54 arcueid fsck: /dev/ad4s2f: INCORRECT BLOCK COUNT >> I=2615096 (20 should be 0) (CORRECTED) >> Sep 29 19:31:54 arcueid fsck: /dev/ad4s2f: INCORRECT BLOCK COUNT >> I=2615097 (20 should be 0) (CORRECTED) >> Sep 29 19:31:54 arcueid fsck: /dev/ad4s2f: INCORRECT BLOCK COUNT >> I=2615098 (20 should be 0) (CORRECTED) >> Sep 29 19:31:54 arcueid fsck: /dev/ad4s2f: INCORRECT BLOCK COUNT >> I=2615099 (20 should be 0) (CORRECTED) >> Sep 29 19:31:54 arcueid fsck: /dev/ad4s2f: INCORRECT BLOCK COUNT >> I=2615100 (16 should be 0) (CORRECTED) >> Sep 29 19:31:54 arcueid fsck: /dev/ad4s2f: INCORRECT BLOCK COUNT >> I=3674361 (12 should be 0) (CORRECTED) >> Sep 29 19:31:54 arcueid fsck: /dev/ad4s2f: INCORRECT BLOCK COUNT >> I=14994399 (4 should be 0) (CORRECTED) >> Sep 29 19:31:54 arcueid fsck: /dev/ad4s2f: INCORRECT BLOCK COUNT >> I=16016109 (6624 should be 320) (CORRECTED) >> Sep 29 19:31:54 arcueid fsck: /dev/ad4s2f: INCORRECT BLOCK COUNT >> I=16016110 (12 should be 0) (CORRECTED) >> Sep 29 19:31:54 arcueid fsck: /dev/ad4s2f: INCORRECT BLOCK COUNT >> I=16016111 (4352 should be 0) (CORRECTED) >> Sep 29 19:31:54 arcueid fsck: /dev/ad4s2f: INCORRECT BLOCK COUNT >> I=16016112 (8 should be 0) (CORRECTED) >> Sep 29 19:31:54 arcueid fsck: /dev/ad4s2f: UNREF FILE I=6 >> OWNER=root MODE=100400 >> Sep 29 19:31:54 arcueid fsck: /dev/ad4s2f: SIZE=151445575864 >> MTIME=Sep 29 19:02 2006 (CLEARED) >> Sep 29 19:31:54 arcueid fsck: /dev/ad4s2f: ALLOCATED FRAGS >> 431136-431167 MARKED FREE >> Sep 29 19:31:54 arcueid fsck: >> Sep 29 19:31:54 arcueid fsck: /dev/ad4s2f: UNEXPECTED SOFT UPDATE >> INCONSISTENCY; RUN fsck MANUALLY. >> And then the server went more or less haywire and crashed(no other >> input in /var/log/messages though) >> I also monitored the fsck process to see how it was running: >> <19:15:57> root@arcueid:~$ while (true); do echo `date` `ps aux | >> grep fsck | grep ad4`; sleep 2; done >> <...> >> Fri Sep 29 19:29:36 CEST 2006 root 777 0.7 1.8 19092 18612 ?? DN >> 7:11PM 0:21.07 fsck_ufs: /dev/ad4s2f p2 92% (fsck_ufs) >> Fri Sep 29 19:29:38 CEST 2006 root 777 0.6 1.8 19092 18612 ?? DN >> 7:11PM 0:21.09 fsck_ufs: /dev/ad4s2f p2 92% (fsck_ufs) >> Fri Sep 29 19:29:40 CEST 2006 root 777 0.6 1.8 19092 18612 ?? RN >> 7:11PM 0:21.12 fsck_ufs: /dev/ad4s2f p2 92% (fsck_ufs) >> Fri Sep 29 19:29:42 CEST 2006 root 777 0.6 1.8 19092 18612 ?? RN >> 7:11PM 0:21.14 fsck_ufs: /dev/ad4s2f p2 94% (fsck_ufs) >> Fri Sep 29 19:29:44 CEST 2006 root 777 0.6 1.8 19092 18612 ?? SN >> 7:11PM 0:21.17 fsck_ufs: /dev/ad4s2f p2 94% (fsck_ufs) >> Fri Sep 29 19:29:46 CEST 2006 root 777 0.6 1.8 19092 18612 ?? DN >> 7:11PM 0:21.19 fsck_ufs: /dev/ad4s2f p2 95% (fsck_ufs) >> Fri Sep 29 19:29:48 CEST 2006 root 777 0.6 1.8 19092 18612 ?? DN >> 7:11PM 0:21.21 fsck_ufs: /dev/ad4s2f p2 95% (fsck_ufs) >> Fri Sep 29 19:29:50 CEST 2006 root 777 0.6 1.8 19092 18612 ?? SN >> 7:11PM 0:21.25 fsck_ufs: /dev/ad4s2f p2 95% (fsck_ufs) >> Fri Sep 29 19:29:52 CEST 2006 root 777 0.5 1.8 19092 18612 ?? DN >> 7:11PM 0:21.29 fsck_ufs: /dev/ad4s2f p2 96% (fsck_ufs) >> Fri Sep 29 19:29:54 CEST 2006 root 777 0.8 1.8 19092 18612 ?? SN >> 7:11PM 0:21.35 fsck_ufs: /dev/ad4s2f p2 96% (fsck_ufs) >> Fri Sep 29 19:29:56 CEST 2006 root 777 0.8 1.8 19092 18612 ?? SN >> 7:11PM 0:21.38 fsck_ufs: /dev/ad4s2f p2 96% (fsck_ufs) >> Fri Sep 29 19:29:58 CEST 2006 root 777 0.8 1.8 19092 18612 ?? DN >> 7:11PM 0:21.40 fsck_ufs: /dev/ad4s2f p2 96% (fsck_ufs) >> Fri Sep 29 19:30:00 CEST 2006 root 777 0.7 1.8 19092 18612 ?? DN >> 7:11PM 0:21.43 fsck_ufs: /dev/ad4s2f p2 96% (fsck_ufs) >> Fri Sep 29 19:30:02 CEST 2006 root 777 0.7 1.8 19092 18612 ?? SN >> 7:11PM 0:21.47 fsck_ufs: /dev/ad4s2f p2 97% (fsck_ufs) >> Fri Sep 29 19:30:04 CEST 2006 root 777 0.6 1.8 19092 18612 ?? SN >> 7:11PM 0:21.49 fsck_ufs: /dev/ad4s2f p2 97% (fsck_ufs) >> Fri Sep 29 19:30:06 CEST 2006 root 777 0.5 1.8 19092 18612 ?? DN >> 7:11PM 0:21.51 fsck_ufs: /dev/ad4s2f p2 97% (fsck_ufs) >> Fri Sep 29 19:30:08 CEST 2006 root 777 0.4 1.8 19092 18612 ?? DN >> 7:11PM 0:21.53 fsck_ufs: /dev/ad4s2f p2 97% (fsck_ufs) >> Fri Sep 29 19:30:10 CEST 2006 root 777 0.6 1.8 19092 18612 ?? DN >> 7:11PM 0:21.57 fsck_ufs: /dev/ad4s2f p2 97% (fsck_ufs) >> Fri Sep 29 19:30:12 CEST 2006 root 777 0.7 1.8 19092 18612 ?? SN >> 7:11PM 0:21.59 fsck_ufs: /dev/ad4s2f p2 98% (fsck_ufs) >> Fri Sep 29 19:30:14 CEST 2006 root 777 0.6 1.8 19092 18612 ?? SN >> 7:11PM 0:21.59 fsck_ufs: /dev/ad4s2f p2 98% (fsck_ufs) >> Fri Sep 29 19:30:16 CEST 2006 root 777 0.5 1.8 19092 18612 ?? DN >> 7:11PM 0:21.61 fsck_ufs: /dev/ad4s2f p2 98% (fsck_ufs) >> Fri Sep 29 19:30:18 CEST 2006 root 777 0.4 1.8 19092 18612 ?? SN >> 7:11PM 0:21.62 fsck_ufs: /dev/ad4s2f p2 98% (fsck_ufs) >> Fri Sep 29 19:30:20 CEST 2006 root 777 0.4 1.8 19092 18612 ?? SN >> 7:11PM 0:21.63 fsck_ufs: /dev/ad4s2f p2 99% (fsck_ufs) >> Fri Sep 29 19:30:23 CEST 2006 root 777 0.3 1.8 19092 18612 ?? DN >> 7:11PM 0:21.64 fsck_ufs: /dev/ad4s2f p2 99% (fsck_ufs) >> Fri Sep 29 19:30:25 CEST 2006 root 777 0.2 1.8 19092 18612 ?? DN >> 7:11PM 0:21.66 fsck_ufs: /dev/ad4s2f p2 99% (fsck_ufs) >> Fri Sep 29 19:30:27 CEST 2006 root 777 0.1 1.8 19092 18612 ?? SN >> 7:11PM 0:21.68 fsck_ufs: /dev/ad4s2f p2 99% (fsck_ufs) >> Fri Sep 29 19:30:29 CEST 2006 root 777 0.0 1.8 19092 18612 ?? SN >> 7:11PM 0:21.70 fsck_ufs: /dev/ad4s2f p2 99% (fsck_ufs) >> Fri Sep 29 19:31:12 CEST 2006 root 777 0.0 1.8 19092 18724 ?? RN >> 7:11PM 0:22.17 fsck_ufs: /dev/ad4s2f p4 0% (fsck_ufs) >> Fri Sep 29 19:31:14 CEST 2006 root 777 0.9 1.8 19092 18748 ?? DN >> 7:11PM 0:22.34 fsck_ufs: /dev/ad4s2f p4 0% (fsck_ufs) >> Fri Sep 29 19:31:16 CEST 2006 root 777 0.9 1.8 19092 18748 ?? DN >> 7:11PM 0:22.35 fsck_ufs: /dev/ad4s2f p4 0% (fsck_ufs) >> Fri Sep 29 19:31:18 CEST 2006 root 777 0.7 1.8 19092 18748 ?? DN >> 7:11PM 0:22.37 fsck_ufs: /dev/ad4s2f p4 0% (fsck_ufs) >> Fri Sep 29 19:31:20 CEST 2006 root 777 0.7 1.8 19092 18748 ?? DN >> 7:11PM 0:22.40 fsck_ufs: /dev/ad4s2f p4 0% (fsck_ufs) >> Fri Sep 29 19:31:22 CEST 2006 root 777 0.6 1.8 19092 18748 ?? DN >> 7:11PM 0:22.40 fsck_ufs: /dev/ad4s2f p4 0% (fsck_ufs) >> Fri Sep 29 19:31:25 CEST 2006 root 777 0.5 1.8 19092 18748 ?? DN >> 7:11PM 0:22.42 fsck_ufs: /dev/ad4s2f p4 0% (fsck_ufs) >> Fri Sep 29 19:31:27 CEST 2006 root 777 0.5 1.8 19092 18748 ?? DN >> 7:11PM 0:22.45 fsck_ufs: /dev/ad4s2f p4 0% (fsck_ufs) >> Fri Sep 29 19:31:29 CEST 2006 root 777 0.4 1.8 19092 18748 ?? DN >> 7:11PM 0:22.46 fsck_ufs: /dev/ad4s2f p4 0% (fsck_ufs) >> Fri Sep 29 19:31:31 CEST 2006 root 777 0.4 1.8 19092 18748 ?? DN >> 7:11PM 0:22.48 fsck_ufs: /dev/ad4s2f p4 0% (fsck_ufs) >> Fri Sep 29 19:31:33 CEST 2006 root 777 0.4 1.8 19092 18748 ?? DN >> 7:11PM 0:22.50 fsck_ufs: /dev/ad4s2f p4 0% (fsck_ufs) >> Fri Sep 29 19:31:35 CEST 2006 root 777 0.3 1.8 19092 18748 ?? DN >> 7:11PM 0:22.51 fsck_ufs: /dev/ad4s2f p4 0% (fsck_ufs) >> Fri Sep 29 19:31:37 CEST 2006 root 777 0.2 1.8 19092 18748 ?? DN >> 7:11PM 0:22.53 fsck_ufs: /dev/ad4s2f p4 0% (fsck_ufs) >> Fri Sep 29 19:31:39 CEST 2006 root 777 0.1 1.8 19092 18748 ?? DN >> 7:11PM 0:22.55 fsck_ufs: /dev/ad4s2f p4 0% (fsck_ufs) >> Fri Sep 29 19:31:41 CEST 2006 root 777 0.2 1.8 19092 18748 ?? DN >> 7:11PM 0:22.57 fsck_ufs: /dev/ad4s2f p4 0% (fsck_ufs) >> Fri Sep 29 19:31:43 CEST 2006 root 777 0.1 1.8 19092 18748 ?? DN >> 7:11PM 0:22.57 fsck_ufs: /dev/ad4s2f p4 0% (fsck_ufs) >> Fri Sep 29 19:31:45 CEST 2006 root 777 0.0 1.8 19092 18748 ?? DN >> 7:11PM 0:22.58 fsck_ufs: /dev/ad4s2f p4 0% (fsck_ufs) >> Fri Sep 29 19:31:47 CEST 2006 root 777 0.0 1.8 19092 18748 ?? DN >> 7:11PM 0:22.59 fsck_ufs: /dev/ad4s2f p4 0% (fsck_ufs) >> Fri Sep 29 19:31:49 CEST 2006 root 777 0.0 1.8 19092 18748 ?? DN >> 7:11PM 0:22.60 fsck_ufs: /dev/ad4s2f p4 0% (fsck_ufs) >> Fri Sep 29 19:31:51 CEST 2006 root 777 0.0 1.8 19092 18748 ?? DN >> 7:11PM 0:22.61 fsck_ufs: /dev/ad4s2f p4 0% (fsck_ufs) >> Fri Sep 29 19:31:53 CEST 2006 root 777 0.0 1.8 19092 18748 ?? DN >> 7:11PM 0:22.61 fsck_ufs: /dev/ad4s2f p4 0% (fsck_ufs) >> Fri Sep 29 19:31:55 CEST 2006 >> Fri Sep 29 19:31:57 CEST 2006 >> Fri Sep 29 19:31:59 CEST 2006 >> Fri Sep 29 19:32:01 CEST 2006 >> Fri Sep 29 19:32:03 CEST 2006 >> Fri Sep 29 19:32:05 CEST 2006 >> Fri Sep 29 19:32:07 CEST 2006 >> Fri Sep 29 19:32:09 CEST 2006 >> Fri Sep 29 19:32:11 CEST 2006 >> Fri Sep 29 19:32:13 CEST 2006 >> Fri Sep 29 19:32:15 CEST 2006 >> Fri Sep 29 19:32:17 CEST 2006 >> Fri Sep 29 19:32:19 CEST 2006 >> Fri Sep 29 19:32:21 CEST 2006 >> Fri Sep 29 19:32:23 CEST 2006 >> Fri Sep 29 19:32:25 CEST 2006 >> >> As you can see, at the same time as softupdate reported a problem, >> the whole system wouldnt work anymore, process wouldnt display >> properly anymore either. >> RAM was extensively tested and is perfectly fine. >> The power supply unit seems to be running really fine too, with no >> particular events. >> The hard drive itself was tested extensively using both smart >> values and writing/reading from a linux setup and had not a single >> fault or alarming value. >> Another quite surprising event is the following: >> After a crash, i went into the rescue freebsd and as usual started >> an fsck. Result was: >> arcueid-rescue# fsck -y /dev/ad4s2f >> ** /dev/ad4s2f >> ** Last Mounted on /usr >> ** Phase 1 - Check Blocks and Sizes >> ** Phase 2 - Check Pathnames >> ** Phase 3 - Check Connectivity >> ** Phase 4 - Check Reference Counts >> ** Phase 5 - Check Cyl groups >> 1362084 files, 47944480 used, 23676944 free (1752392 frags, 2740569 >> blocks, 2.4% fragmentation) >> ***** FILE SYSTEM MARKED CLEAN ***** >> Just for the fun i ran it a second time just after: >> arcueid-rescue# fsck -y /dev/ad4s2f >> ** /dev/ad4s2f >> ** Last Mounted on /usr >> ** Phase 1 - Check Blocks and Sizes >> CANNOT READ BLK: 190083360 >> UNEXPECTED SOFT UPDATE INCONSISTENCY >> CONTINUE? yes >> THE FOLLOWING DISK SECTORS COULD NOT BE READ: 190083360, 190083361, >> 190083362, 190083363, 190083364, 190083365, 190083366, 190083367, >> 190083368, 190083369, 190083370, 190083371, 190083372, 190083373, >> 190083374, 190083375, 190083376, 190083377, 190083378, 190083379, >> 190083380, 190083381, 190083382, 190083383, 190083384, 190083385, >> 190083386, 190083387, 190083388, 190083389, 190083390, 190083391, >> INCORRECT BLOCK COUNT I=18375172 (640 should be 416) >> CORRECT? yes >> CANNOT READ BLK: 293557088 >> UNEXPECTED SOFT UPDATE INCONSISTENCY >> CONTINUE? yes >> THE FOLLOWING DISK SECTORS COULD NOT BE READ: 293557088, 293557089, >> 293557090, 293557091, 293557092, 293557093, 293557094, 293557095, >> 293557096, 293557097, 293557098, 293557099, 293557100, 293557101, >> 293557102, 293557103, 293557104, 293557105, 293557106, 293557107, >> 293557108, 293557109, 293557110, 293557111, 293557112, 293557113, >> 293557114, 293557115, 293557116, 293557117, 293557118, 293557119, >> CANNOT READ BLK: 190090784 >> UNEXPECTED SOFT UPDATE INCONSISTENCY >> CONTINUE? yes >> THE FOLLOWING DISK SECTORS COULD NOT BE READ: 190090784, 190090785, >> 190090786, 190090787, 190090788, 190090789, 190090790, 190090791, >> 190090792, 190090793, 190090794, 190090795, 190090796, 190090797, >> 190090798, 190090799, 190090800, 190090801, 190090802, 190090803, >> 190090804, 190090805, 190090806, 190090807, 190090808, 190090809, >> 190090810, 190090811, 190090812, 190090813, 190090814, 190090815, >> INCORRECT BLOCK COUNT I=18375174 (480 should be 416) >> CORRECT? yes >> CANNOT READ BLK: 190122624 >> UNEXPECTED SOFT UPDATE INCONSISTENCY >> CONTINUE? yes >> THE FOLLOWING DISK SECTORS COULD NOT BE READ: 190122624, 190122625, >> 190122626, 190122627, 190122628, 190122629, 190122630, 190122631, >> 190122632, 190122633, 190122634, 190122635, 190122636, 190122637, >> 190122638, 190122639, 190122640, 190122641, 190122642, 190122643, >> 190122644, 190122645, 190122646, 190122647, 190122648, 190122649, >> 190122650, 190122651, 190122652, 190122653, 190122654, 190122655, >> INCORRECT BLOCK COUNT I=18375178 (512 should be 416) >> CORRECT? yes >> CANNOT READ BLK: 190422528 >> UNEXPECTED SOFT UPDATE INCONSISTENCY >> CONTINUE? yes >> [etc] >> And then it crashed.... >> Again i did the sata tests numerous times and the drive seems >> perfectly healthy... So i have to think it might be driver related >> rather than hardware related. >> Any help would be appreciated, >> -- >> Best regards, >> Paul-Kenji >> _______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to "freebsd-hackers- >> unsubscribe@freebsd.org" > Lucas Holt > Luke@FoolishGames.com > ________________________________________________________ > FoolishGames.com (Jewel Fan Site) > JustJournal.com (Free blogging) > FoolishGames.net (Enemy Territory site)