From owner-freebsd-stable@FreeBSD.ORG Sun Nov 16 08:22:49 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: FreeBSD-stable@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 24F9A1065680
for <FreeBSD-stable@FreeBSD.org>; Sun, 16 Nov 2008 08:22:49 +0000 (UTC)
(envelope-from rorya+freebsd.org@TrueStep.com)
Received: from Tserver.TrueStep.com (Tserver.TrueStep.com [64.253.96.188])
by mx1.freebsd.org (Postfix) with ESMTP id A470C8FC0A
for <FreeBSD-stable@FreeBSD.org>; Sun, 16 Nov 2008 08:22:48 +0000 (UTC)
(envelope-from rorya+freebsd.org@TrueStep.com)
Received: from Cypher.TrueStep (Cypher.TrueStep [10.101.1.8])
(authenticated bits=0)
by Tserver.TrueStep.com (8.14.3/8.14.3) with ESMTP id mAG8MdVw034854
(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
Sun, 16 Nov 2008 03:22:45 -0500 (EST)
(envelope-from rorya+freebsd.org@TrueStep.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=TrueStep.com;
s=default; t=1226823765; bh=0YjGTkXW3zdiI7BXxIPgTgDew0KOoE0R7hTb3jN
JaOs=; h=Cc:Message-Id:From:To:In-Reply-To:Content-Type:
Content-Transfer-Encoding:Mime-Version:Subject:Date:References;
b=lF7Yd6p7xCG8CrHT02HMgP1Q2/qIdn4SydvXv5zU6C8/DvgVPVYRL2rvhfTcigeT0
4UPXW7gqKhDxu08FWlPDAtOV0WAzE6pzAZrk9qJcNiUVlf5ykbp7CGohXsBMdDZB5Y4
0qpqsGJmsgczkP3Y2ezxxhfQw5w/QJJX+Tnu9Vw=
Message-Id: <9C64A87F-1359-4694-8238-6C4D4B025BE3@TrueStep.com>
From: Rory Arms <rorya+freebsd.org@TrueStep.com>
To: Ken Smith <kensmith@cse.buffalo.edu>
In-Reply-To: <1226078239.37011.37.camel@bauer.cse.buffalo.edu>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Sun, 16 Nov 2008 03:22:39 -0500
References: <9592E887-75F3-473F-9581-F9C22A9936A6@TrueStep.com>
<1226078239.37011.37.camel@bauer.cse.buffalo.edu>
X-Mailer: Apple Mail (2.929.2)
Cc: FreeBSD-stable@FreeBSD.org
Subject: Re: 6.4-RC2 crashes after a few minutes of uptime
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Nov 2008 08:22:49 -0000
On 2008-11-07, at 12:17 , Ken Smith wrote:
> On Fri, 2008-11-07 at 00:00 -0500, Rory Arms wrote:
>> Well, if I can assist with further debugging, let me know.
>
> The person who followed up with a list of things that *may* have made
> the problem go away mentioned one of the things was disabling powerd.
> Do you have that enable, and if yes would you mind disabling it to see
> if that's the culprit?
Ken,
Ok, guess something is amiss with the CD-ROM drive on this notebook,
as in GNOME, it flashes an icon of a CD on the desktop from time to
time, as if it has detected a disc in the drive. But of course there
is no disc in the drive. I believe it did the same with 6.3 though,
but as said before didn't ever panic due to this issue.
So, some anecdotal info, after running RC2 for a few days now. It
seems the pattern is that it seems to always panic a few minutes after
a first cold boot, but then seems to remain stable after the second
boot. Odd, as with 6.3 this didn't happen. So, I happened to catch a
panic while working in the syscons console after one of these cold
boots. As far as I can tell, the panic does have something to do with
the the CD-ROM drive, as right after I saw this message on the
console, it immediately paniced:
acd0: WARNING - PREVENT_ALLOW read data overrun 18>0
and then the panic is as follows:
kernel trap 12 with interrupts disabled
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x78
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc06d39b9
stack pointer = 0x28:0xca865c10
frame pointer = 0x28:0xca865c14
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags = resume, IOPL = 0
current process = 19 (swi6: task queue)
trap number = 12
panic: page fault
Uptime: 1h9m7s
Physical memory: 179MB
Dumping 43MB: 28 12
Dump complete
This is also the computer, as you may recall, that I can't ever get
kgdb(1) to open the core dump file. Note the uptime on that particular
boot was 1h because I pretty much let it sit idle after booting. So,
gdm loaded and then I switched to syscons, logged in, and then pretty
much let it idle, till it paniced.
Hope that helps,
- rory
From owner-freebsd-stable@FreeBSD.ORG Sun Nov 16 10:15:10 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id D50551065672;
Sun, 16 Nov 2008 10:15:10 +0000 (UTC)
(envelope-from bzeeb-lists@lists.zabbadoz.net)
Received: from mail.cksoft.de (mail.cksoft.de [62.111.66.27])
by mx1.freebsd.org (Postfix) with ESMTP id 88E6D8FC19;
Sun, 16 Nov 2008 10:15:10 +0000 (UTC)
(envelope-from bzeeb-lists@lists.zabbadoz.net)
Received: from localhost (amavis.str.cksoft.de [192.168.74.71])
by mail.cksoft.de (Postfix) with ESMTP id 2861A41C650;
Sun, 16 Nov 2008 11:15:08 +0100 (CET)
X-Virus-Scanned: amavisd-new at cksoft.de
Received: from mail.cksoft.de ([62.111.66.27])
by localhost (amavis.str.cksoft.de [192.168.74.71]) (amavisd-new,
port 10024)
with ESMTP id hw6Sj9eZNrJC; Sun, 16 Nov 2008 11:15:05 +0100 (CET)
Received: by mail.cksoft.de (Postfix, from userid 66)
id 8491341C65F; Sun, 16 Nov 2008 11:15:05 +0100 (CET)
Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net
[10.111.66.10])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(No client certificate requested)
by mail.int.zabbadoz.net (Postfix) with ESMTP id 21622444888;
Sun, 16 Nov 2008 10:10:37 +0000 (UTC)
Date: Sun, 16 Nov 2008 10:10:36 +0000 (UTC)
From: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>
X-X-Sender: bz@maildrop.int.zabbadoz.net
To: Lorenzo Perone <lopez.on.the.lists@yellowspace.net>
In-Reply-To: <2192B50F-16AE-4BC8-ACEC-6C5B99804DA0@yellowspace.net>
Message-ID: <20081116100529.Y61259@maildrop.int.zabbadoz.net>
References: <2192B50F-16AE-4BC8-ACEC-6C5B99804DA0@yellowspace.net>
X-OpenPGP-Key: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: freebsd-jail@freebsd.org, freebsd-stable@freebsd.org
Subject: Re: hangs for 7.1-PRE [was: problem possibly related to multi-ip
jail patch?]
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: freebsd-stable@freebsd.org
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Nov 2008 10:15:10 -0000
On Sun, 16 Nov 2008, Lorenzo Perone wrote:
Hi,
> I've been experiencing problems with one of the machines running FreeBSD
> 7.1-PRERELEASE #2: Thu Oct 16 20:23:09 CEST 2008 with the multi-ip patch
> bz_jail7-20080920-01-at150161.diff, and I'm wondering if it possibly related
> to the patch - in any case, any advice would be very welcome.
bottom line is that most of this looks less likely to be a jail
problem.
> It happens that mysql (tried both 4.0 and 5.1, in 2 separate jails), at some
> time stop responding to connections, and mysql gets stuck in sbwait state. It
> is only killable with kill -9 <pid>
Yeah, I had been seeing mysql hang or go to 99% CPU for years once in
a while; it's been more rare the last months. I have seen it in- and
outside of jails, with or without patches.
You could try to see if you can get backtraces of those processes.
> each of the two mysqlds is running in a jail on one private IP, serving
> connections to a webserver nearby - the latter having one public and one
> private IP, communicating with the other jail via the private network.
>
> I also experienced two complete system hangs (which must not be necessarily
> related to the mysql problem) both during a shutdown -r now. one was a panic,
> in another case the machine was still pingable but did not shut down
> completely. I could only reset it over the DRAC. here's a screenshot I made
> over the Dell RAC: http://lorenzo.yellowspace.net/stuck.png
Looking at your image I see more problems before the shutdown so this
as well is most likely not a jail problem.
> Since I'm also using zfs there and the kernel has been built with the DTRACE
> options.
>
> any advice (also about which more details that I should/could provide) would
> be very welcome...
I am Cc:ing the answer to stable@ and setting reply-to: to move the discussion there.
/bz
--
Bjoern A. Zeeb Stop bit received. Insert coin for new game.
From owner-freebsd-stable@FreeBSD.ORG Sun Nov 16 12:25:04 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: FreeBSD-stable@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id CDA4B10656B7
for <FreeBSD-stable@FreeBSD.org>; Sun, 16 Nov 2008 12:25:04 +0000 (UTC)
(envelope-from barbara.xxx1975@libero.it)
Received: from cp-out1.libero.it (cp-out1.libero.it [212.52.84.101])
by mx1.freebsd.org (Postfix) with ESMTP id 6344C8FC08
for <FreeBSD-stable@FreeBSD.org>; Sun, 16 Nov 2008 12:25:04 +0000 (UTC)
(envelope-from barbara.xxx1975@libero.it)
Received: from wmail2.libero.it (172.31.0.97) by cp-out1.libero.it (8.5.016.1)
id 49196160008D5517; Sun, 16 Nov 2008 13:24:42 +0100
Message-ID: <13170840.199821226838282753.JavaMail.defaultUser@defaultHost>
Date: Sun, 16 Nov 2008 13:24:42 +0100 (CET)
From: Barbara <barbara.xxx1975@libero.it>
To: <rorya+freebsd.org@TrueStep.com>, Ken Smith <kensmith@cse.buffalo.edu>
MIME-Version: 1.0
Content-Type: text/plain;charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-SenderIP: 87.1.198.170
Cc: FreeBSD-stable@FreeBSD.org
Subject: 6.4-RC2 crashes after a few minutes of uptime
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Barbara <barbara.xxx1975@libero.it>
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Nov 2008 12:25:04 -0000
>Ok, guess something is amiss with the CD-ROM drive on this notebook,
>as
in GNOME, it flashes an icon of a CD on the desktop from time to
>time, as if
it has detected a disc in the drive. But of course there
>is no disc in the
drive. I believe it did the same with 6.3 though,
>but as said before didn't
ever panic due to this issue.
>
>So, some anecdotal info, after running RC2 for
a few days now. It
>seems the pattern is that it seems to always panic a few
minutes after
>a first cold boot, but then seems to remain stable after the
second
>boot. Odd, as with 6.3 this didn't happen. So, I happened to catch
a
>panic while working in the syscons console after one of these cold
>boots. As far as I can tell, the panic does have something to do with
>the
the CD-ROM drive, as right after I saw this message on the
>console, it
immediately paniced:
>
>acd0: WARNING - PREVENT_ALLOW read data overrun 18>0
>
>and then the panic is as follows:
>
>kernel trap 12 with interrupts disabled
>
>Fatal trap 12: page fault while in kernel mode
>fault virtual address = 0x78
>fault code = supervisor read, page not present
>instruction pointer =
0x20:0xc06d39b9
>stack pointer = 0x28:0xca865c10
>frame pointer = 0x28:
0xca865c14
>code segment = base 0x0, limit 0xfffff, type 0x1b
> = DPL 0,
pres 1, def32 1, gran 1
>processor eflags = resume, IOPL = 0
>current process
= 19 (swi6: task queue)
>trap number = 12
>panic: page fault
>Uptime:
1h9m7s
>Physical memory: 179MB
>Dumping 43MB: 28 12
>Dump complete
Hi Rory,
did you see my replies or are you missing them for any reason?
Your panics and
some aspects about how they happens look like mine to me, look here:
http:
//lists.freebsd.org/pipermail/freebsd-stable/2008-October/045865.html
Unfortunately I got no answer about that and I've had no comment in the pr I've
filed http://www.freebsd.org/cgi/query-pr.cgi?pr=128076
I wonder if someone had
the time to look at it.
From owner-freebsd-stable@FreeBSD.ORG Sun Nov 16 21:21:49 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: FreeBSD-stable@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 4791A1065670
for <FreeBSD-stable@FreeBSD.org>; Sun, 16 Nov 2008 21:21:49 +0000 (UTC)
(envelope-from rorya+freebsd.org@TrueStep.com)
Received: from Tserver.TrueStep.com (Tserver.TrueStep.com [64.253.96.188])
by mx1.freebsd.org (Postfix) with ESMTP id E68258FC1F
for <FreeBSD-stable@FreeBSD.org>; Sun, 16 Nov 2008 21:21:48 +0000 (UTC)
(envelope-from rorya+freebsd.org@TrueStep.com)
Received: from Cypher.TrueStep (Cypher.TrueStep [10.101.1.8])
(authenticated bits=0)
by Tserver.TrueStep.com (8.14.3/8.14.3) with ESMTP id mAGLLdrD039831
(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
Sun, 16 Nov 2008 16:21:45 -0500 (EST)
(envelope-from rorya+freebsd.org@TrueStep.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=TrueStep.com;
s=default; t=1226870505; bh=QCTuOaD9xNWrSDwNQOnCch5bshHSrmq5XsYXNg4
iRY4=; h=Cc:Message-Id:From:To:In-Reply-To:Content-Type:
Content-Transfer-Encoding:Mime-Version:Subject:Date:References;
b=PFHuBfpgEacZDn4ZEtFY65cZyFrLznCiJY77ukD4J2+izgqz0gShGlEeskfwHFQCn
beSvbISNB3bIk+UVjJnDFtHBk8m5nwoHoJfK9TukJyZL69Ibbc7ICWEx1ADyXZQwXVV
ZYIKWy7fORiMqT83/N0iwH6JQEhZ899O0ihbdWI=
Message-Id: <369CC50A-9CF4-4F9B-8D22-153294B93532@TrueStep.com>
From: Rory Arms <rorya+freebsd.org@TrueStep.com>
To: Barbara <barbara.xxx1975@libero.it>
In-Reply-To: <13170840.199821226838282753.JavaMail.defaultUser@defaultHost>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Sun, 16 Nov 2008 16:21:38 -0500
References: <13170840.199821226838282753.JavaMail.defaultUser@defaultHost>
X-Mailer: Apple Mail (2.929.2)
Cc: Ken Smith <kensmith@cse.buffalo.edu>, FreeBSD-stable@FreeBSD.org
Subject: Re: 6.4-RC2 crashes after a few minutes of uptime
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Nov 2008 21:21:49 -0000
On 2008-11-16, at 7:24 , Barbara wrote:
>
>
>
>> Ok, guess something is amiss with the CD-ROM drive on this notebook,
>> as
> in GNOME, it flashes an icon of a CD on the desktop from time to
>> time, as if
> it has detected a disc in the drive. But of course there
>> is no disc in the
> drive. I believe it did the same with 6.3 though,
>> but as said before didn't
> ever panic due to this issue.
>>
>> So, some anecdotal info, after running RC2 for
> a few days now. It
>> seems the pattern is that it seems to always panic a few
> minutes after
>> a first cold boot, but then seems to remain stable after the
> second
>> boot. Odd, as with 6.3 this didn't happen. So, I happened to catch
> a
>> panic while working in the syscons console after one of these cold
>
>> boots. As far as I can tell, the panic does have something to do
>> with
>> the
> the CD-ROM drive, as right after I saw this message on the
>> console, it
> immediately paniced:
>>
>> acd0: WARNING - PREVENT_ALLOW read data overrun 18>0
>>
>
>> and then the panic is as follows:
>>
>> kernel trap 12 with interrupts disabled
>>
>
>> Fatal trap 12: page fault while in kernel mode
>> fault virtual address = 0x78
>
>> fault code = supervisor read, page not present
>> instruction pointer =
> 0x20:0xc06d39b9
>> stack pointer = 0x28:0xca865c10
>> frame pointer = 0x28:
> 0xca865c14
>> code segment = base 0x0, limit 0xfffff, type 0x1b
>> = DPL 0,
> pres 1, def32 1, gran 1
>> processor eflags = resume, IOPL = 0
>> current process
> = 19 (swi6: task queue)
>> trap number = 12
>> panic: page fault
>> Uptime:
> 1h9m7s
>> Physical memory: 179MB
>> Dumping 43MB: 28 12
>> Dump complete
>
> Hi Rory,
>
> did you see my replies or are you missing them for any reason?
Yes, I have seen your replies. I must have missed the PR you mentioned
last time, sorry.
>
>
> Your panics and
> some aspects about how they happens look like mine to me, look here:
> http:
> //lists.freebsd.org/pipermail/freebsd-stable/2008-October/045865.html
Yes, indeed. That looks very similar to the issue I'm running into
with 6.4-RC2 as well. Sounds like it might be a regression in ata(4).
At least you were able to open the core dump. Are you still able to
open core dumps with RC2?
>
>
>
> Unfortunately I got no answer about that and I've had no comment in
> the pr I've
> filed http://www.freebsd.org/cgi/query-pr.cgi?pr=128076
> I wonder if someone had
> the time to look at it.
>
From owner-freebsd-stable@FreeBSD.ORG Sun Nov 16 22:29:03 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: FreeBSD-stable@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id B44701065689
for <FreeBSD-stable@FreeBSD.org>; Sun, 16 Nov 2008 22:29:03 +0000 (UTC)
(envelope-from barbara.xxx1975@libero.it)
Received: from cp-out2.libero.it (cp-out2.libero.it [212.52.84.102])
by mx1.freebsd.org (Postfix) with ESMTP id 774298FC08
for <FreeBSD-stable@FreeBSD.org>; Sun, 16 Nov 2008 22:29:03 +0000 (UTC)
(envelope-from barbara.xxx1975@libero.it)
Received: from libero.it (192.168.17.15) by cp-out2.libero.it (8.5.016.1)
id 49197770008E9D9B; Sun, 16 Nov 2008 23:28:27 +0100
Date: Sun, 16 Nov 2008 23:28:27 +0100
Message-Id: <KAG6FF$FBDFC6EC6CA5FFC5B15B6F0EEE6746F7@libero.it>
MIME-Version: 1.0
X-Sensitivity: 3
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
From: "barbara" <barbara.xxx1975@libero.it>
To: "rorya+freebsd\.org" <rorya+freebsd.org@TrueStep.com>
X-XaM3-API-Version: 4.3 (R1) (B3pl25)
X-SenderIP: 87.1.198.170
Cc: kensmith <kensmith@cse.buffalo.edu>,
FreeBSD-stable <FreeBSD-stable@FreeBSD.org>
Subject: Re: 6.4-RC2 crashes after a few minutes of uptime
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Nov 2008 22:29:03 -0000
> > Hi Rory,
> >
> > did you see my replies or are you missing them for any reason?
>
> Yes, I have seen your replies. I must have missed the PR you mentioned =
> last time, sorry.
No problem!
> > Your panics and
> > some aspects about how they happens look like mine to me, look here:
> > http:
> > //lists.freebsd.org/pipermail/freebsd-stable/2008-October/045865.html=
>
> Yes, indeed. That looks very similar to the issue I'm running into
> with 6.4-RC2 as well. Sounds like it might be a regression in ata(4). =
> At least you were able to open the core dump. Are you still able to
> open core dumps with RC2?
>
I'm not sure. I'm running STABLE and I had no panics after the branch has=
changed to RC2. It seems that my panics are not frequent as yours.
Anyway my box freezed a couple of times after last newvers.sh and the sym=
ptoms looked like the same, with messages about acd0. I was able to ping =
it but it won't let me ssh in, like it was using all the cpus.
About kgdb...
I never used freebsd-update, so sorry if I'm saying something stupid, but=
could it be the case that the kernel has been built without debugging sy=
mbols or something like that? Does freebsd-update provide a kernel.debug?=
I've seen that you are not using shiny quad-core, but could you try build=
ing a kernel by yourself? I think that you could do it using a different,=
more powerful, freebsd box if you have it, or even on qemu. I could help=
if you wish.
From owner-freebsd-stable@FreeBSD.ORG Mon Nov 17 00:01:51 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 0618E1065673
for <freebsd-stable@freebsd.org>; Mon, 17 Nov 2008 00:01:51 +0000 (UTC)
(envelope-from p.christias@noc.ntua.gr)
Received: from achilles.noc.ntua.gr (achilles.noc.ntua.gr
[IPv6:2001:648:2000:de::210])
by mx1.freebsd.org (Postfix) with ESMTP id 6A61B8FC08
for <freebsd-stable@freebsd.org>; Mon, 17 Nov 2008 00:01:50 +0000 (UTC)
(envelope-from p.christias@noc.ntua.gr)
Received: from ajax.noc.ntua.gr (ajax6.noc.ntua.gr [IPv6:2001:648:2000:dc::1])
by achilles.noc.ntua.gr (8.14.3/8.14.3) with ESMTP id mAH01m0D080145
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
Mon, 17 Nov 2008 02:01:48 +0200 (EET)
(envelope-from p.christias@noc.ntua.gr)
Received: from ajax.noc.ntua.gr (localhost.noc.ntua.gr [127.0.0.1])
by ajax.noc.ntua.gr (8.13.8/8.13.8) with ESMTP id mAH01mMV052715
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
Mon, 17 Nov 2008 02:01:48 +0200 (EET)
(envelope-from p.christias@noc.ntua.gr)
Received: (from christia@localhost)
by ajax.noc.ntua.gr (8.13.8/8.13.8/Submit) id mAH01mol052714;
Mon, 17 Nov 2008 02:01:48 +0200 (EET)
(envelope-from p.christias@noc.ntua.gr)
X-Authentication-Warning: ajax.noc.ntua.gr: christia set sender to
p.christias@noc.ntua.gr using -f
Date: Mon, 17 Nov 2008 02:01:47 +0200
From: Panagiotis Christias <p.christias@noc.ntua.gr>
To: Claus Guttesen <kometen@gmail.com>
Message-ID: <20081117000147.GA52109@noc.ntua.gr>
References: <b41c75520811130322v578c0343qef57d4241f787206@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <b41c75520811130322v578c0343qef57d4241f787206@mail.gmail.com>
User-Agent: Mutt/1.5.16 (2007-06-09)
X-Virus-Scanned: ClamAV version 0.94,
clamav-milter version 0.94 on achilles.noc.ntua.gr
X-Virus-Status: Clean
Cc: FreeBSD Stable <freebsd-stable@freebsd.org>
Subject: Re: qlogic qle2462 hba and freebsd stable on a dl360 g5
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Nov 2008 00:01:51 -0000
On Thu, Nov 13, 2008 at 12:22:11PM +0100, Claus Guttesen wrote:
> Hi.
>
> I'm looking at a qlogic qle2462 hba for my dl360 g5. The thread
> http://www.mail-archive.com/freebsd-stable@freebsd.org/msg99497.html
> mentions a deadlock when system is loaded. Has this issue been
> resolved? Are there other PCI Express hba's which are known to work
> with freebsd stable and dl360 g5?
Hello,
no, the issue has not been resolved. The system still deadlocks
regardless the value of tag openings (even when set to the minimum
value of 2) and the filesystem gets corrupted or totally destroyed.
I am still looking for a solution and willing to do any tests.
Regards,
Panagiotis
--
Panagiotis J. Christias Network Management Center
P.Christias@noc.ntua.gr National Technical Univ. of Athens, GREECE
From owner-freebsd-stable@FreeBSD.ORG Mon Nov 17 00:02:29 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: FreeBSD-stable@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 6E6121065695
for <FreeBSD-stable@FreeBSD.org>; Mon, 17 Nov 2008 00:02:29 +0000 (UTC)
(envelope-from rorya+freebsd.org@TrueStep.com)
Received: from Tserver.TrueStep.com (Tserver.TrueStep.com [64.253.96.188])
by mx1.freebsd.org (Postfix) with ESMTP id 037198FC23
for <FreeBSD-stable@FreeBSD.org>; Mon, 17 Nov 2008 00:02:28 +0000 (UTC)
(envelope-from rorya+freebsd.org@TrueStep.com)
Received: from Cypher.TrueStep (Cypher.TrueStep [10.101.1.8])
(authenticated bits=0)
by Tserver.TrueStep.com (8.14.3/8.14.3) with ESMTP id mAH02Jjg040907
(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
Sun, 16 Nov 2008 19:02:25 -0500 (EST)
(envelope-from rorya+freebsd.org@TrueStep.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=TrueStep.com;
s=default; t=1226880145; bh=Su8IzqGamREsuHnjeB5XQJwzLSG/H+96WILUD3h
wDzE=; h=Cc:Message-Id:From:To:In-Reply-To:Content-Type:
Content-Transfer-Encoding:Mime-Version:Subject:Date:References;
b=SNorPDO7l4Pr/ovVMgYabB2RMXdCzav/fLKyNAWnd2ZQTFWYsiHX5FbWHHqnstRMq
5Tg1lCsKZVdYv0pcrC1X0qJReLvj+yEGu9XxYW5sceWvCN+bmuoI4a+K2FRRGXiwYPp
G7r3j22ynQsfrkfZHnWNse0BSBh2Uz/EmNsvK2I=
Message-Id: <ACD81AC3-512A-435F-91E6-73BBAC4443D6@TrueStep.com>
From: Rory Arms <rorya+freebsd.org@TrueStep.com>
To: barbara <barbara.xxx1975@libero.it>
In-Reply-To: <KAG6FF$FBDFC6EC6CA5FFC5B15B6F0EEE6746F7@libero.it>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Sun, 16 Nov 2008 19:02:19 -0500
References: <KAG6FF$FBDFC6EC6CA5FFC5B15B6F0EEE6746F7@libero.it>
X-Mailer: Apple Mail (2.929.2)
Cc: kensmith <kensmith@cse.buffalo.edu>,
FreeBSD-stable <FreeBSD-stable@FreeBSD.org>
Subject: Re: 6.4-RC2 crashes after a few minutes of uptime
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Nov 2008 00:02:29 -0000
On 2008-11-16, at 17:28 , barbara wrote:
>>> Hi Rory,
>>>
>>> did you see my replies or are you missing them for any reason?
>>
>> Yes, I have seen your replies. I must have missed the PR you
>> mentioned
>> last time, sorry.
>
> No problem!
>
>>> Your panics and
>>> some aspects about how they happens look like mine to me, look here:
>>> http:
>>> //lists.freebsd.org/pipermail/freebsd-stable/2008-October/
>>> 045865.html
>>
>> Yes, indeed. That looks very similar to the issue I'm running into
>> with 6.4-RC2 as well. Sounds like it might be a regression in ata(4).
>> At least you were able to open the core dump. Are you still able to
>> open core dumps with RC2?
>>
>
> I'm not sure. I'm running STABLE and I had no panics after the
> branch has changed to RC2. It seems that my panics are not frequent
> as yours.
> Anyway my box freezed a couple of times after last newvers.sh and
> the symptoms looked like the same, with messages about acd0. I was
> able to ping it but it won't let me ssh in, like it was using all
> the cpus.
>
> About kgdb...
> I never used freebsd-update, so sorry if I'm saying something
> stupid, but could it be the case that the kernel has been built
> without debugging symbols or something like that? Does freebsd-
> update provide a kernel.debug?
I haven't had to use a the kernel.debug file in the obj dir in a long
time. As far as I know, these days, the GENERIC kernel includes debug
symbols. And in cases when there aren't any debug symbols, that
shouldn't prevent kgdb from loading, I wouldn't think.
- rory
From owner-freebsd-stable@FreeBSD.ORG Mon Nov 17 00:45:21 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 391121065672
for <freebsd-stable@freebsd.org>; Mon, 17 Nov 2008 00:45:21 +0000 (UTC)
(envelope-from jrhett@netconsonance.com)
Received: from mail.netconsonance.com (mail.netconsonance.com [198.207.204.4])
by mx1.freebsd.org (Postfix) with ESMTP id 2210B8FC2B
for <freebsd-stable@freebsd.org>; Mon, 17 Nov 2008 00:45:21 +0000 (UTC)
(envelope-from jrhett@netconsonance.com)
Received: from [192.168.148.73] ([216.239.45.19]) (authenticated bits=0)
by mail.netconsonance.com (8.14.1/8.14.1) with ESMTP id mAH0jGYD095952;
Sun, 16 Nov 2008 16:45:17 -0800 (PST)
(envelope-from jrhett@netconsonance.com)
X-Virus-Scanned: amavisd-new at netconsonance.com
X-Spam-Flag: NO
X-Spam-Score: -1.44
X-Spam-Level:
X-Spam-Status: No, score=-1.44 tagged_above=-999 required=3.5
tests=[ALL_TRUSTED=-1.44]
Message-Id: <BC332C75-2E81-49E5-8D1C-166A0434525F@netconsonance.com>
From: Jo Rhett <jrhett@netconsonance.com>
To: Oliver Lehmann <lehmann@ans-netz.de>
In-Reply-To: <20081112204351.ccc51c2f.lehmann@ans-netz.de>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Sun, 16 Nov 2008 16:45:15 -0800
References: <20081029170728.be7cc7ab.lehmann@ans-netz.de>
<13394481-8FDC-4934-BB12-FA5BCB2D35CD@nevada.net.nz>
<20081112204351.ccc51c2f.lehmann@ans-netz.de>
X-Mailer: Apple Mail (2.929.2)
Cc: freebsd-stable@freebsd.org, Philip Murray <pmurray@nevada.net.nz>
Subject: Re: 3Ware 9000 series hangs under load
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Nov 2008 00:45:21 -0000
Philip Murray wrote:
> Anyway, I stopped running 3dmd (or 3dm2 I think it's called now) to
> monitor it, and the crashes went away. It's had hundreds of days
> uptime since.
We have never used 3dm2, and the 9500 units have been rock solid for us.
> I've never been game enough to try newer versions of 3dm, but a
> cronjob of tw_cli allows me to monitor it now without the lockups.
> Might not be your problem, but it's worth a shot if all else fails.
The driver logs all useful stuff, and the SEC logfile surfer does a
good job of notifying you quickly. I can send you an SEC
configuration for that if you want.
--
Jo Rhett
Net Consonance : consonant endings by net philanthropy, open source
and other randomness
From owner-freebsd-stable@FreeBSD.ORG Mon Nov 17 00:46:23 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 55AE4106564A
for <freebsd-stable@freebsd.org>; Mon, 17 Nov 2008 00:46:23 +0000 (UTC)
(envelope-from jrhett@netconsonance.com)
Received: from mail.netconsonance.com (mail.netconsonance.com [198.207.204.4])
by mx1.freebsd.org (Postfix) with ESMTP id 3CC0E8FC1B
for <freebsd-stable@freebsd.org>; Mon, 17 Nov 2008 00:46:23 +0000 (UTC)
(envelope-from jrhett@netconsonance.com)
Received: from [192.168.148.73] ([216.239.45.19]) (authenticated bits=0)
by mail.netconsonance.com (8.14.1/8.14.1) with ESMTP id mAH0jGYE095952;
Sun, 16 Nov 2008 16:46:18 -0800 (PST)
(envelope-from jrhett@netconsonance.com)
X-Virus-Scanned: amavisd-new at netconsonance.com
X-Spam-Flag: NO
X-Spam-Score: -0.04
X-Spam-Level:
X-Spam-Status: No, score=-0.04 tagged_above=-999 required=3.5
tests=[ALL_TRUSTED=-1.44, AWL=-1.400, DATE_IN_FUTURE_24_48=2.8]
Message-Id: <E0BD32FA-AF27-43CC-B84B-A47DF3AEBC49@netconsonance.com>
From: Jo Rhett <jrhett@netconsonance.com>
To: Philip Murray <pmurray@nevada.net.nz>
In-Reply-To: <95E9EA2C-C288-4F11-AD35-FE6AF6633A09@nevada.net.nz>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Sun, 16 Nov 2008 16:46:17 -0800
References: <20081029170728.be7cc7ab.lehmann@ans-netz.de>
<13394481-8FDC-4934-BB12-FA5BCB2D35CD@nevada.net.nz>
<20081112204351.ccc51c2f.lehmann@ans-netz.de>
<95E9EA2C-C288-4F11-AD35-FE6AF6633A09@nevada.net.nz>
X-Mailer: Apple Mail (2.929.2)
Cc: freebsd-stable@freebsd.org, Oliver Lehmann <lehmann@ans-netz.de>
Subject: Re: 3Ware 9000 series hangs under load
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Nov 2008 00:46:23 -0000
On Nov 12, 2008, at 12:37 PM, Philip Murray wrote:
> I just installed sysutils/tw_cli from ports, and it sets up some
> 'periodic' scripts for you. To be precise it puts 407.status-3ware-
> raid in /usr/local/etc/periodic/daily
Don't use that. It's a very old version of the code. Use the binary
version of tw_cli that matches the firmware on your controller.
--
Jo Rhett
Net Consonance : consonant endings by net philanthropy, open source
and other randomness
From owner-freebsd-stable@FreeBSD.ORG Mon Nov 17 01:13:23 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 8EDC11065670;
Mon, 17 Nov 2008 01:13:23 +0000 (UTC)
(envelope-from p.christias@noc.ntua.gr)
Received: from achilles.noc.ntua.gr (achilles.noc.ntua.gr
[IPv6:2001:648:2000:de::210])
by mx1.freebsd.org (Postfix) with ESMTP id F109D8FC17;
Mon, 17 Nov 2008 01:13:22 +0000 (UTC)
(envelope-from p.christias@noc.ntua.gr)
Received: from ajax.noc.ntua.gr (ajax6.noc.ntua.gr [IPv6:2001:648:2000:dc::1])
by achilles.noc.ntua.gr (8.14.3/8.14.3) with ESMTP id mAH1DIRJ013941
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
Mon, 17 Nov 2008 03:13:18 +0200 (EET)
(envelope-from p.christias@noc.ntua.gr)
Received: from ajax.noc.ntua.gr (localhost.noc.ntua.gr [127.0.0.1])
by ajax.noc.ntua.gr (8.13.8/8.13.8) with ESMTP id mAH1DHqN056431
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
Mon, 17 Nov 2008 03:13:17 +0200 (EET)
(envelope-from p.christias@noc.ntua.gr)
Received: (from christia@localhost)
by ajax.noc.ntua.gr (8.13.8/8.13.8/Submit) id mAH1DHVK056430;
Mon, 17 Nov 2008 03:13:17 +0200 (EET)
(envelope-from p.christias@noc.ntua.gr)
X-Authentication-Warning: ajax.noc.ntua.gr: christia set sender to
p.christias@noc.ntua.gr using -f
Date: Mon, 17 Nov 2008 03:13:17 +0200
From: Panagiotis Christias <p.christias@noc.ntua.gr>
To: Oleg Sharoiko <os@rsu.ru>
Message-ID: <20081117011317.GB52109@noc.ntua.gr>
References: <20081014222343.GA8706@noc.ntua.gr>
<1224049455.1277.44.camel@brain.cc.rsu.ru>
<20081015175453.GA3260@noc.ntua.gr>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20081015175453.GA3260@noc.ntua.gr>
User-Agent: Mutt/1.5.16 (2007-06-09)
X-Virus-Scanned: ClamAV version 0.94,
clamav-milter version 0.94 on achilles.noc.ntua.gr
X-Virus-Status: Clean
Cc: freebsd-scsi@freebsd.org, freebsd-stable@freebsd.org
Subject: Re: FreeBSD 7-STABLE, isp(4), QLE2462: panic & deadlocks
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Nov 2008 01:13:23 -0000
On Wed, Oct 15, 2008 at 08:54:53PM +0300, Panagiotis Christias wrote:
> On Wed, Oct 15, 2008 at 09:44:15AM +0400, Oleg Sharoiko wrote:
> > Hi!
> >
> > On Wed, 2008-10-15 at 01:23 +0300, Panagiotis Christias wrote:
> >
> > > However, when we connect them to the CX3-40, create and mount a new
> > > partition and then do something as simple as "tar -C /san -xf ports.tgz"
> > > the system panics and deadlocks. We have tried several FreeBSD versions
> > > (6.3 i386/adm64, 7.0 i386/adm64, 7.1 i386/adm64 and lastly 7-STABLE i386
> > > - we also tried the latest 8-CURRENT snapshot but it panicked too soon).
> > > The result is always the same; panic and deadlock.
> >
> > Try reducing the number of "tagged openings" with 'camcontrol tags' down
> > to 46. If it doesn't work try reducing it further to 2. Also be advised
> > that I've seen panics with geom_multipath in FreeBSD-7, unfortunately I
> > had no time to test it in -current.
>
>
> Hm.. that would probably explain the fact that I was unable to panic the
> system when I had set the hint.isp.0.debug="0x1F" in /boot/device.hints.
>
> Currently I am stress testing the server with the tagged openings set to
> 44 (first value tested). Until now there is no panic or deadlock. I am
> trying concurrent tar extractions and rsync copies. The filesystem looks
> ok till now according to fsck. I will let it write/copy/delete overnight
> and tomorrow I will try different tagged opening values.
>
> Thank you for the hint! I am wondering what is the performance penalty
> with decreased tagged openings. Also, is there anything else I could try
> in order to get more useful debug output? I have at least three servers
> that I could use for any kind of tests and I am willing to spend as much
> time I can get to help solving the problem.
>
> Finally, the only output in the logs is:
>
> Expensive timeout(9) function: 0xc06f4210(0xc67e1200) 0.059422635 s
> Expensive timeout(9) function: 0xc08d4fd0(0) 0.060676147 s
>
> I suppose that is related to the CAMDEBUG kernel config options.
For the record, I have done many tests using several stressing tools
in parallel, different FreeBSD versions (up to 7.1beta2), various
filesystem configurations (plain ufs2 with softupdates, ufs2 and
gjournal, zfs) and various tag openings values (down to 2).
Regardless of the configuration, the system deadlocks, panics or the
filesystem gets awfully corrupted within seconds, minutes or a few hours.
The only configuration that seems to work without problems(?) but with
a unacceptable *severe* performance penalty is when tag openings are set
to minimum value of 2 (that is more or less same as disabling tagged
command queueing at all).
All tests ran using a 500 GB RAID5 LUN on an EMC Clariion CX340:
da0 at isp0 bus 0 target 0 lun 0
da0: <DGC RAID 5 0326> Fixed Direct Access SCSI-4 device
da0: Serial Number CK200083100148
da0: 400.000MB/s transfers
da0: Command Queueing Enabled
da0: 512000MB (1048576000 512 byte sectors: 255H 63S/T 65270C)
Previously, a Sun StorEdge T3 was tested which worked flawlessly but
it had a 1 Gbps fibre channel interface, instead of a 4 Gbps that
Clariion has, was recognized as a SCSI-3 device and had 2 tags openings
(no surprise) by default:
da1 at isp1 bus 0 target 0 lun 0
da1: <SUN T300 0302> Fixed Direct Access SCSI-3 device
da1: 100.000MB/s transfers
da1: 241724MB (495050752 512 byte sectors: 255H 63S/T 30815C)
As I mentioned before, I am willing to spend time or/and provide
access to the system for testing and debugging.
Regards,
Panagiotis
--
Panagiotis J. Christias Network Management Center
P.Christias@noc.ntua.gr National Technical Univ. of Athens, GREECE
From owner-freebsd-stable@FreeBSD.ORG Mon Nov 17 02:29:53 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 2F3A11065673
for <freebsd-stable@freebsd.org>; Mon, 17 Nov 2008 02:29:53 +0000 (UTC)
(envelope-from hartzell@alerce.com)
Received: from merlin.alerce.com (merlin.alerce.com [64.62.142.94])
by mx1.freebsd.org (Postfix) with ESMTP id 1BDD78FC18
for <freebsd-stable@freebsd.org>; Mon, 17 Nov 2008 02:29:53 +0000 (UTC)
(envelope-from hartzell@alerce.com)
Received: from merlin.alerce.com (localhost [127.0.0.1])
by merlin.alerce.com (Postfix) with ESMTP id BDADD33C62;
Sun, 16 Nov 2008 18:29:52 -0800 (PST)
Received: from merlin.alerce.com (localhost [127.0.0.1])
by merlin.alerce.com (Postfix) with ESMTP id 3EB5633C5B;
Sun, 16 Nov 2008 18:29:51 -0800 (PST)
From: George Hartzell <hartzell@alerce.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <18720.55070.363778.698000@almost.alerce.com>
Date: Sun, 16 Nov 2008 18:29:50 -0800
To: hartzell@alerce.com
In-Reply-To: <18716.48723.452606.66518@almost.alerce.com>
References: <18716.48723.452606.66518@almost.alerce.com>
X-Mailer: VM 7.19 under Emacs 22.1.50.1
X-Virus-Scanned: ClamAV using ClamSMTP
Cc: freebsd-stable@freebsd.org
Subject: Re: problem moving gmirror between two machines.
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: hartzell@alerce.com
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Nov 2008 02:29:53 -0000
George Hartzell writes:
>
> I have an HP DL360 with a pair of 1TB seagate disks that's been
> running -STABLE with a ZFS root partition set up using the tools
> available here:
>
> http://yds.coolrat.org/zfsboot.shtml
>
> It's been working great. As part of trying to understand what's going
> on, I csup'ed to -RELENG earlier today and rebuilt/installed the
> kernel and world whilst running on the DL360, so everything should be
> current.
>
> I tried to move the disks into an HP DL320 G4 and it fails to boot
> because it can't find /dev/mirror/boot (which it wants to mount onto
> /strap and then parts get nullfs'ed onto /boot and /rescue). It gives
> me the opportunity to start a shell, and from that shell I can do a
> zfs mount -a and get all of the zfs filesystems mounted, but there's
> nothing in /dev/mirror. No gmirror status and list are silent.
>
> I can move the disks back into the older machine and they work fine.
>
> I've run fdisk -s ad4 and bsdlabel -A /dev/ad4s1a and diffed the
> output from the two machines and they're identical.
>
> I've booted with kern.geom.mirror.debug=2 and the DL320G4 tastes
> /dev/ad4s1a (along with everything else) but doesn't do anything with
> it.
>
> Any ideas?
>
[for the archives]
Solved. gmirror had been set up with -h specifying the device, and
although the newer server used the same device names for its disks
(ad[46]) it assigned them to different hot swap bays. Once I switched
the disks everything came up fine.
g.
From owner-freebsd-stable@FreeBSD.ORG Mon Nov 17 03:46:48 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 20CF21065689
for <freebsd-stable@freebsd.org>; Mon, 17 Nov 2008 03:46:48 +0000 (UTC)
(envelope-from cmdlnkid@gmail.com)
Received: from rn-out-0910.google.com (rn-out-0910.google.com [64.233.170.191])
by mx1.freebsd.org (Postfix) with ESMTP id C00168FC1E
for <freebsd-stable@freebsd.org>; Mon, 17 Nov 2008 03:46:47 +0000 (UTC)
(envelope-from cmdlnkid@gmail.com)
Received: by rn-out-0910.google.com with SMTP id j71so2331158rne.12
for <freebsd-stable@freebsd.org>; Sun, 16 Nov 2008 19:46:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:date:from:reply-to:to:cc
:subject:in-reply-to:message-id:references:user-agent:x-openpgp-key
:mime-version:content-type;
bh=/eT25LAT92xXVrLOvA9Io5a7LNiTfBFqCgwfIM6snkk=;
b=gpC2fp+qcJZL3D1grPfxTqe62hzk6mb3jyxnVIBaow2SMAiHTbZW4bzbXJIP6P4T0H
DdBhAvwpA10pojE5sJx2SoroE6hXSurbZNVMoAelvx6XGRxQUhHMKdo+Jo+h5/VEQj5j
dz7kbRFfdOucAVefay3F0Ak1kHrxIfpYm88nE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=date:from:reply-to:to:cc:subject:in-reply-to:message-id:references
:user-agent:x-openpgp-key:mime-version:content-type;
b=S/N3QNMf30liUhMXPTcZD0q/CLnwl0/WKeckKYScI2ZtKBHT8VKsd93GcD0laUc/oZ
KWRCCNg6jo4N4ZOTjtEHsbuCiZap7V8L/wFYApz3tnof9lKmI8fpztSr/w0ZG9LZcImS
pa0at88RF7V++NN+xd6tRDDkV4rd2sMaan7PY=
Received: by 10.90.98.13 with SMTP id v13mr2434406agb.28.1226891678587;
Sun, 16 Nov 2008 19:14:38 -0800 (PST)
Received: from ?192.168.1.50? (c-71-205-56-117.hsd1.mi.comcast.net
[71.205.56.117])
by mx.google.com with ESMTPS id 20sm2576183agb.38.2008.11.16.19.14.37
(version=TLSv1/SSLv3 cipher=RC4-MD5);
Sun, 16 Nov 2008 19:14:37 -0800 (PST)
Date: Sun, 16 Nov 2008 22:14:35 -0500
From: CmdLnKid <cmdlnkid@gmail.com>
To: George Hartzell <hartzell@alerce.com>
In-Reply-To: <18720.55070.363778.698000@almost.alerce.com>
Message-ID: <alpine.BSF.2.00.0811162208500.56550@qvzrafvba.5c.ybpny>
References: <18716.48723.452606.66518@almost.alerce.com>
<18720.55070.363778.698000@almost.alerce.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
X-OpenPGP-Key: 0xDFFDD218
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: freebsd-stable@freebsd.org
Subject: Re: problem moving gmirror between two machines.
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: CmdLnKid <cmdlnkid@gmail.com>
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Nov 2008 03:46:48 -0000
On Sun, 16 Nov 2008 21:29 -0000, hartzell wrote:
> George Hartzell writes:
> >
> > I have an HP DL360 with a pair of 1TB seagate disks that's been
> > running -STABLE with a ZFS root partition set up using the tools
> > available here:
> >
> > http://yds.coolrat.org/zfsboot.shtml
> >
> > It's been working great. As part of trying to understand what's going
> > on, I csup'ed to -RELENG earlier today and rebuilt/installed the
> > kernel and world whilst running on the DL360, so everything should be
> > current.
> >
> > I tried to move the disks into an HP DL320 G4 and it fails to boot
> > because it can't find /dev/mirror/boot (which it wants to mount onto
> > /strap and then parts get nullfs'ed onto /boot and /rescue). It gives
> > me the opportunity to start a shell, and from that shell I can do a
> > zfs mount -a and get all of the zfs filesystems mounted, but there's
> > nothing in /dev/mirror. No gmirror status and list are silent.
> >
> > I can move the disks back into the older machine and they work fine.
> >
> > I've run fdisk -s ad4 and bsdlabel -A /dev/ad4s1a and diffed the
> > output from the two machines and they're identical.
> >
> > I've booted with kern.geom.mirror.debug=2 and the DL320G4 tastes
> > /dev/ad4s1a (along with everything else) but doesn't do anything with
> > it.
> >
> > Any ideas?
> >
>
> [for the archives]
>
> Solved. gmirror had been set up with -h specifying the device, and
> although the newer server used the same device names for its disks
> (ad[46]) it assigned them to different hot swap bays. Once I switched
> the disks everything came up fine.
>
> g.
Wouldn't it be more feasible in this situation to just glabel the disks
and mount them from /dev/<fstype>/<label> instead. Might make your life
easier in the future for swapping disks.
Example:
/dev/ufs/tmp on /tmp (ufs, asynchronous, local, gjournal)
/dev/ufs/usr on /usr (ufs, local, soft-updates)
/dev/ufs/var on /var (ufs, local, soft-updates)
--
Sincerely, -- Jason H. ;; Networked Systems Engineering.
The Command Line Kid. ;; Multi-user Systems Advocate.
mailto:gmail.com!cmdlnkid ;; 1(616)403-XXXX / BSD Group.
- (2^(N-1))
From owner-freebsd-stable@FreeBSD.ORG Mon Nov 17 06:03:30 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 941031065673
for <freebsd-stable@freebsd.org>; Mon, 17 Nov 2008 06:03:30 +0000 (UTC)
(envelope-from mike@sentex.net)
Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18])
by mx1.freebsd.org (Postfix) with ESMTP id 59E458FC1A
for <freebsd-stable@freebsd.org>; Mon, 17 Nov 2008 06:03:30 +0000 (UTC)
(envelope-from mike@sentex.net)
Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18])
by smarthost1.sentex.ca (8.14.3/8.14.3) with ESMTP id mAH63Rlr087969;
Mon, 17 Nov 2008 01:03:27 -0500 (EST) (envelope-from mike@sentex.net)
Received: from mdt-xp.sentex.net (simeon.sentex.ca [192.168.43.27])
by lava.sentex.ca (8.13.8/8.13.3) with ESMTP id mAH63Q54011870
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
Mon, 17 Nov 2008 01:03:26 -0500 (EST) (envelope-from mike@sentex.net)
Message-Id: <200811170603.mAH63Q54011870@lava.sentex.ca>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 17 Nov 2008 01:03:24 -0500
To: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
From: Mike Tancsa <mike@sentex.net>
In-Reply-To: <73413.1226301391@critter.freebsd.dk>
References: <Your message of "Mon, 03 Nov 2008 20:43:53 EST."
<200811040143.mA41hjaa029665@lava.sentex.ca>
<73413.1226301391@critter.freebsd.dk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Scanned-By: MIMEDefang 2.64 on 64.7.153.18
Cc: freebsd-stable@freebsd.org
Subject: Re: fifo log problem
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Nov 2008 06:03:30 -0000
At 02:16 AM 11/10/2008, Poul-Henning Kamp wrote:
>In message <200811040143.mA41hjaa029665@lava.sentex.ca>, Mike Tancsa writes:
>
> >I tried changing the config so that there is only the fifo log being
> >written to and disabled newsyslog so that syslogd is not getting a
> >HUP signal. The strange thing is that reading from it gives
> >different results?!?
> >
> >Sometimes doing
> >[ps0278]# fifolog_reader all.fifo | wc
> >>From 0 Wed Dec 31 19:00:00 1969
> >To 1225760679 Mon Nov 3 20:04:39 2008
> >Read from 1d800
> > 59 413 3068
> >0[ps0278]#
> >
> >and a exactly for 1min it will show the correct results
> >
> >0[ps0278]# fifolog_reader all.fifo | wc
> >>From 0 Wed Dec 31 19:00:00 1969
> >To 1225760538 Mon Nov 3 20:02:18 2008
> >Read from 0
> > 10765 75995 556816
> >0[ps0278]#
>
>I could fear that you have two fifologs running at the same time,
>possibly as a result of syslogd doing something strange on sighup...
There is nothing really strange about the config. Any idea on how to resolve?
---Mike
From owner-freebsd-stable@FreeBSD.ORG Mon Nov 17 06:06:32 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 8FD991065670
for <freebsd-stable@freebsd.org>; Mon, 17 Nov 2008 06:06:32 +0000 (UTC)
(envelope-from lehmann@ans-netz.de)
Received: from avocado.salatschuessel.net (avocado.salatschuessel.net
[78.111.72.186]) by mx1.freebsd.org (Postfix) with SMTP id D56668FC0C
for <freebsd-stable@freebsd.org>; Mon, 17 Nov 2008 06:06:31 +0000 (UTC)
(envelope-from lehmann@ans-netz.de)
Received: (qmail 5492 invoked by uid 89); 17 Nov 2008 06:06:29 -0000
Received: from unknown (HELO kartoffel.salatschuessel.net) (78.111.72.187)
by avocado.salatschuessel.net with SMTP; 17 Nov 2008 06:06:29 -0000
Date: Mon, 17 Nov 2008 07:06:27 +0100
From: Oliver Lehmann <lehmann@ans-netz.de>
To: Jo Rhett <jrhett@netconsonance.com>
Message-Id: <20081117070627.a21086ef.lehmann@ans-netz.de>
In-Reply-To: <BC332C75-2E81-49E5-8D1C-166A0434525F@netconsonance.com>
References: <20081029170728.be7cc7ab.lehmann@ans-netz.de>
<13394481-8FDC-4934-BB12-FA5BCB2D35CD@nevada.net.nz>
<20081112204351.ccc51c2f.lehmann@ans-netz.de>
<BC332C75-2E81-49E5-8D1C-166A0434525F@netconsonance.com>
X-Mailer: Sylpheed 2.5.0 (GTK+ 2.12.11; amd64-portbld-freebsd7.0)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: freebsd-stable@freebsd.org, Philip Murray <pmurray@nevada.net.nz>
Subject: Re: 3Ware 9000 series hangs under load
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Nov 2008 06:06:32 -0000
Jo Rhett wrote:
> The driver logs all useful stuff, and the SEC logfile surfer does a
> good job of notifying you quickly. I can send you an SEC
> configuration for that if you want.
Hm - what is SEC?
--
Oliver Lehmann
http://www.pofo.de/
http://wishlist.ans-netz.de/
From owner-freebsd-stable@FreeBSD.ORG Mon Nov 17 14:11:27 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 0FE291065672;
Mon, 17 Nov 2008 14:11:27 +0000 (UTC)
(envelope-from sclark46@earthlink.net)
Received: from elasmtp-banded.atl.sa.earthlink.net
(elasmtp-banded.atl.sa.earthlink.net [209.86.89.70])
by mx1.freebsd.org (Postfix) with ESMTP id B5ABB8FC0A;
Mon, 17 Nov 2008 14:11:26 +0000 (UTC)
(envelope-from sclark46@earthlink.net)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net;
b=K/IjisuhXC0bPy20V76/JWEImHDJR6hkjHd8USrT91/8Bslsh48/GgLABnKlr7IU;
h=Received:Message-ID:Date:From:Reply-To:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [208.118.36.229] (helo=joker.seclark.com)
by elasmtp-banded.atl.sa.earthlink.net with esmtpsa
(TLSv1:AES256-SHA:256) (Exim 4.67)
(envelope-from <sclark46@earthlink.net>)
id 1L24p3-0008Hg-T3; Mon, 17 Nov 2008 09:11:26 -0500
Message-ID: <49217B8C.4020701@earthlink.net>
Date: Mon, 17 Nov 2008 09:11:24 -0500
From: Stephen Clark <sclark46@earthlink.net>
User-Agent: Thunderbird 2.0.0.16 (X11/20080723)
MIME-Version: 1.0
To: freebsd-net@freebsd.org
References: <491B2703.4080707@earthlink.net>
<491B31F7.30200@elischer.org> <491B4345.80106@earthlink.net>
<491B47D2.6010804@elischer.org> <491C2235.4090509@earthlink.net> <1226589468.1976.12.camel@wombat.2hip.net> <491C4EC2.2000802@earthlink.net>
<491D6CED.50006@earthlink.net> <491DC28E.80804@elischer.org> <1226688153.1719.23.camel@squirrel.corp.cox.com>
<20081115102746.K61259@maildrop.int.zabbadoz.net>
In-Reply-To: <20081115102746.K61259@maildrop.int.zabbadoz.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: a437fbc6971e80f61aa676d7e74259b7b3291a7d08dfec794af18fb7ee433dbef49ceb3c5a4d093f350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 208.118.36.229
Cc: FreeBSD Stable <freebsd-stable@freebsd.org>
Subject: Re: FreeBSD 6.3 gre and traceroute
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: sclark46@earthlink.net
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Nov 2008 14:11:27 -0000
Bjoern A. Zeeb wrote:
> On Fri, 14 Nov 2008, Robert Noland wrote:
>
> Hi,
>
>>>>> Also just using gre's without the
>>>>> underlying ipsec tunnels seems to
>>>>> work properly.
>
> The reason for this to my knowledge is:
> http://www.kame.net/dev/cvsweb2.cgi/kame/freebsd2/sys/netinet/ip_icmp.c#rev1.4
>
>
> or looking at recent freebsd code:
> http://fxr.watson.org/fxr/source/netinet/ip_icmp.c#L164
> Look for M_DECRYPTED.
>
> Now what happens in your case:
>
> you receive an IPSec ESP packet, which gets decryped, that sets
> M_DECRYPTED on the mbuf passes through various parts, gets up to gre,
> gets decapsulated is an IP packet (again) gets to ip_input, TTL
> expired, icmp_error and it's still the same mbuf that originally got
> the M_DECRYPTED set. Thus the packets is just freed and you never see
> anything.
>
> So thinking about this has nothing to do with gre (or gif for example
> as well) in first place. It's arguably that passing it on to another
> decapsulation the flag should be cleared when entering gre() for
> example.
>
> The other question of course is why we do not send the icmp error back
> even on plain ipsec? Is it because we could possibly leak information
> as it's not caught by the policy sending it back?
>
> /bz
>
Hi Bjoern,
Thanks for you insight. I see in the ip_icmp.c code what you are talking about.
Thanks,
Steve
--
"They that give up essential liberty to obtain temporary safety,
deserve neither liberty nor safety." (Ben Franklin)
"The course of history shows that as a government grows, liberty
decreases." (Thomas Jefferson)
From owner-freebsd-stable@FreeBSD.ORG Mon Nov 17 14:25:11 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id AA5AD106564A
for <freebsd-stable@freebsd.org>; Mon, 17 Nov 2008 14:25:11 +0000 (UTC)
(envelope-from jwb@homer.att.com)
Received: from mail161.messagelabs.com (mail161.messagelabs.com
[216.82.253.115])
by mx1.freebsd.org (Postfix) with ESMTP id 567328FC14
for <freebsd-stable@freebsd.org>; Mon, 17 Nov 2008 14:25:11 +0000 (UTC)
(envelope-from jwb@homer.att.com)
X-VirusChecked: Checked
X-Env-Sender: jwb@homer.att.com
X-Msg-Ref: server-15.tower-161.messagelabs.com!1226930227!10272359!1
X-StarScan-Version: 5.5.12.14.2; banners=-,-,-
X-Originating-IP: [144.160.20.54]
Received: (qmail 15792 invoked from network); 17 Nov 2008 13:57:08 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpi135.enaf.sfdc.sbc.com)
(144.160.20.54)
by server-15.tower-161.messagelabs.com with AES256-SHA encrypted SMTP;
17 Nov 2008 13:57:08 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1])
by mlpi135.enaf.sfdc.sbc.com (8.14.3/8.14.3) with ESMTP id
mAHDv7np015104; Mon, 17 Nov 2008 08:57:07 -0500
Received: from alph001.aldc.att.com (alph001.aldc.att.com [135.53.7.26])
by mlpi135.enaf.sfdc.sbc.com (8.14.3/8.14.3) with ESMTP id
mAHDv1Fr015037; Mon, 17 Nov 2008 08:57:01 -0500
Received: from aldc.att.com (localhost.localdomain [127.0.0.1])
by alph001.aldc.att.com (8.14.0/8.14.0) with ESMTP id mAHDv0iu009080;
Mon, 17 Nov 2008 08:57:01 -0500
Received: from ulysses.homer.att.com (ulysses.homer.att.com [135.205.193.8])
by alph001.aldc.att.com (8.14.0/8.14.0) with ESMTP id mAHDuudQ008990;
Mon, 17 Nov 2008 08:56:57 -0500
Received: from akiva.homer.att.com (akiva.homer.att.com [135.205.212.39])
by ulysses.homer.att.com (8.9.3/8.9.3) with ESMTP id IAA26038;
Mon, 17 Nov 2008 08:56:56 -0500 (EST)
Received: from akiva (localhost [127.0.0.1])
by akiva.homer.att.com (8.9.3/8.9.3) with ESMTP id IAA09494;
Mon, 17 Nov 2008 08:56:55 -0500 (EST)
Message-Id: <200811171356.IAA09494@akiva.homer.att.com>
X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.0.4
To: Peter Jeremy <peterjeremy@optushome.com.au>
In-reply-to: Your message of "Sun, 16 Nov 2008 09:46:04 +1100."
<20081115224604.GG51761@server.vk2pj.dyndns.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 17 Nov 2008 08:56:55 -0500
From: "J. W. Ballantine" <jwb@homer.att.com>
Cc: freebsd-stable@freebsd.org
Subject: Re: _nyssin undefined
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Nov 2008 14:25:11 -0000
I believe I typed/copied it correctly, but I could be wrong,
and it probably is a typo.
The problem started during the install of a new system build using
the Friday AM CVS bits, and I can't get on the system in any
mode.
Thanks
Jim
---------- In Response to your message -------------
> Date: Sun, 16 Nov 2008 09:46:04 +1100
> To: "J. W. Ballantine" <jwb@homer.att.com>
> From: Peter Jeremy <peterjeremy@optushome.com.au>
> Subject: Re: _nyssin undefined
>
>
> --zbGR4y+acU1DwHSi
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
> Content-Transfer-Encoding: quoted-printable
>
> On 2008-Nov-15 12:55:12 -0500, "J. W. Ballantine" <jwb@homer.att.com> wrote:
> >Yesterday AM, 11/14, I cvs'ed the 7-stable sources and did a
> >system build/install. Now all I get is:
> > /lib/ld-elf.so.1: /lib/libc.so.7: Undefined symbol _nyssin.
>
> I don't recognize and can't find that symbol in my (older) 7-STABLE
> sources so I'm not sure what might have triggered it. However,
> I don't have ld-elf.so.1 in /lib - it's in /libexec. Is that a
> typo on your part?
>
> At what point do you get that error? Can you get to a single user
> mode shell?
>
> The previous ld-elf.so.1 is saved as /libexec/ld-elf.so.1.old - you
> can use tools in /rescue to rename it (you will need to use chflags to
> clear the schg flag on /libexec/ld-elf.so.1 before you can overwrite
> it). Unfortunately, there's no backup of /lib/libc.so.7 so if that's
> the problem, you will need to recover it from backups or a live
> filesystem CD.
>
> --=20
> Peter Jeremy
> Please excuse any delays as the result of my ISP's inability to implement
> an MTA that is either RFC2821-compliant or matches their claimed behaviour.
>
> --zbGR4y+acU1DwHSi
> Content-Type: application/pgp-signature
> Content-Disposition: inline
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.9 (FreeBSD)
>
> iEYEARECAAYFAkkfUSwACgkQ/opHv/APuIcgQwCgueEy72NP0szOaz8Gl8AkFUAg
> 42EAoLpg2TCwP0HCZLlEon3cCfs+daew
> =zk8S
> -----END PGP SIGNATURE-----
>
> --zbGR4y+acU1DwHSi--
>
From owner-freebsd-stable@FreeBSD.ORG Mon Nov 17 16:30:19 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id EE6B11065673
for <freebsd-stable@freebsd.org>; Mon, 17 Nov 2008 16:30:19 +0000 (UTC)
(envelope-from pjd@garage.freebsd.pl)
Received: from mail.garage.freebsd.pl (chello087206045082.chello.pl
[87.206.45.82]) by mx1.freebsd.org (Postfix) with ESMTP id 420738FC16
for <freebsd-stable@freebsd.org>; Mon, 17 Nov 2008 16:30:19 +0000 (UTC)
(envelope-from pjd@garage.freebsd.pl)
Received: by mail.garage.freebsd.pl (Postfix, from userid 65534)
id 8BC1B4569A; Mon, 17 Nov 2008 16:58:44 +0100 (CET)
Received: from localhost (ghf58.internetdsl.tpnet.pl [83.12.187.58])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(No client certificate requested)
by mail.garage.freebsd.pl (Postfix) with ESMTP id 481EF45684;
Mon, 17 Nov 2008 16:58:38 +0100 (CET)
Date: Mon, 17 Nov 2008 16:58:35 +0100
From: Pawel Jakub Dawidek <pjd@FreeBSD.org>
To: d@delphij.net
Message-ID: <20081117155835.GC2101@garage.freebsd.pl>
References: <491CE71F.2020208@delphij.net> <491CE835.4050504@delphij.net>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="OROCMA9jn6tkzFBc"
Content-Disposition: inline
In-Reply-To: <491CE835.4050504@delphij.net>
User-Agent: Mutt/1.4.2.3i
X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc
X-OS: FreeBSD 8.0-CURRENT i386
X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on
mail.garage.freebsd.pl
X-Spam-Level:
X-Spam-Status: No, score=-5.9 required=3.0 tests=ALL_TRUSTED,BAYES_00
autolearn=ham version=3.0.4
Cc: FreeBSD Stable <freebsd-stable@freebsd.org>,
Quake Lee <quakelee@geekcn.org>
Subject: Re: ZFS crashes on heavy threaded environment
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Nov 2008 16:30:20 -0000
--OROCMA9jn6tkzFBc
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Thu, Nov 13, 2008 at 06:53:41PM -0800, Xin LI wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>=20
> Xin LI wrote:
> > Hi, Pawel,
> >=20
> > We can still reproduce the ZFS crash (threading+heavy I/O load) on a
> > fresh 7.1-STABLE build, in a few minutes:
> >=20
> > /usr/local/bin/iozone -M -e -+u -T -t 128 -S 4096 -L 64 -r 4k -s 30g -i
> > 0 -i 1 -i 2 -i 8 -+p 70 -C
> >=20
> > I have included a backtrace output from my colleague who has his hands
> > on the test environment. Should there is more information necessary
> > please let us know and we wish to provide help on this.
>=20
> Further datapoint. The system used to run with untuned loader.conf, and
> my colleague just reported that with the following loader.conf, the
> problem can be triggered sooner:
>=20
> vm.kmem_size_max=3D838860800
> vm.kmem_size_scale=3D"2"
>=20
> The system is running FreeBSD/amd64 7.1-PRERELEASE equipped with 8GB of
> RAM with GENERIC kernel.
With new ZFS I get:
Memory allocation failed:: Cannot allocate memory
Is this expected?
--=20
Pawel Jakub Dawidek http://www.wheel.pl
pjd@FreeBSD.org http://www.FreeBSD.org
FreeBSD committer Am I Evil? Yes, I Am!
--OROCMA9jn6tkzFBc
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4 (FreeBSD)
iD8DBQFJIZSqForvXbEpPzQRAkT1AKDD/4FH7jqvcB6+FA1CoZorlaB2BQCfeVVl
kMfwjVaTgb3KWzXzPKlVcG4=
=1bhB
-----END PGP SIGNATURE-----
--OROCMA9jn6tkzFBc--
From owner-freebsd-stable@FreeBSD.ORG Mon Nov 17 16:47:25 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 137E61065670
for <freebsd-stable@freebsd.org>; Mon, 17 Nov 2008 16:47:25 +0000 (UTC)
(envelope-from asossi@dotcom.ts.it)
Received: from mail.dotcom.ts.it (89-96-242-204.ip14.fastwebnet.it
[89.96.242.204]) by mx1.freebsd.org (Postfix) with SMTP id 7436A8FC08
for <freebsd-stable@freebsd.org>; Mon, 17 Nov 2008 16:47:24 +0000 (UTC)
(envelope-from asossi@dotcom.ts.it)
Received: (qmail 18410 invoked by uid 89); 17 Nov 2008 16:20:42 -0000
Received: by simscan 1.1.0 ppid: 18385, pid: 18401, t: 0.8744s scanners:none
X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on web.dotcom.ts.it
X-Spam-Level:
X-Spam-Status: No, hits=-4.1 required=3.0 tests=ALL_TRUSTED,AWL,BAYES_00
autolearn=ham version=3.2.3
Received: from unknown (HELO ?192.168.0.2?) (asossi@dotcom.ts.it@192.168.254.3)
by test.dotcom.ts.it with SMTP; 17 Nov 2008 16:20:41 -0000
Message-ID: <49219959.8040209@dotcom.ts.it>
Date: Mon, 17 Nov 2008 17:18:33 +0100
From: Sossi Andrej <asossi@dotcom.ts.it>
Organization: DotCom Information technology
User-Agent: Thunderbird 2.0.0.17 (X11/20080914)
MIME-Version: 1.0
To: freebsd-stable@freebsd.org
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: swap_pager: indefinite wait
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Nov 2008 16:47:25 -0000
Hello,
I manage a www (apache), database (postgresql) and e-mail (qmail) with
about 100 Internet domains.
We recently purchased a DELL MD3000i server with data access through
ISCSI protocol.
I installed a new server with FreeBSD 7.0 compiled kernel with ISCSI
(v. 2.1) and SCHED_ULE scheduler.
The server's local disk configuration is:
512 MB /
1024 MB SWAP
254 MB / var
2048MB / var/ qmail
512 MB /tmp
~ 70 GB /usr
The apache data (/usr/local/www), postgre (/usr/local/pgsql) and qmail
(/usr/local/vpopmail) are instead on the partition on ISCSI. After
installing all the necessary softwares I tested the machine as mail
server for a one domain and everything worked fine for 2-3 days.
I wanted to test the correct functioning of qmail and of the
reading/writing on ISCSI. On the end of testing I decided to transfer
all of data (www, DB and e-mail) on the FreeBSD 7.0. I compressed all
the data on the original server (on tar.gz format). I transferred them
on the new server and started to decompress the files. Www data have
been decompressed correctly on the ISCSI disk. But while the messages
were being decompressed (~80GB of tar.gz) and all the DB were being
restored, the server crashed.
The error shown was:
swap_pager: indefinite wait buffer: bufobj: 0, blkno: 31, size: 4096
This message repeated every 30 seconds.
While restarting with the single user mode I checked there wasn't any
message after the crash in /var/log/messages.
I think 1GB of swap should be enough, since with this configuration on
FreeBSD 5.5 everything worked for over 270 days without reboot.
The local disks are 2 of ~80GB in RAID 1 (mirror) with Gmirror
before installing FreeBSD I tested the 2 disks with the badblocks
software on Slackware which didn't find any r/w error.
Can somebody help me understand why the system crashed this way or how
to avoid future crash?
It's a production server and I can't afford an out-of-service or data loss.
Thank you very much and kind regards.
--
Sossi Andrej
-------------------------
DotCom Information technology
Via Biancospino, 9
34151 - Opicina (TS)
Italy
tel: +39 040 2158191
fax: +39 040 0641954
E-mail: asossi@dotcom.ts.it
----------------------------
Ai sensi del D.lgs n. 196 del 30.06.03 (Codice Privacy) si precisa che
le informazioni contenute in questo messaggio sono riservate e ad uso
esclusivo del destinatario. Qualora il messaggio in parola Le fosse
pervenuto per errore, La preghiamo di eliminarlo senza copiarlo e di non
inoltrarlo a terzi, dandocene gentilmente comunicazione. Grazie
This message, for the D.lgs n. 196 / 30.06.03 (Privacy Code), may
contain confidential and/or privileged information. If you are not the
addressee or authorized to receive this for the addressee, you must not
use, copy, disclose or take any action based on this message or any
information herein. If you have received this message in error, please
advise the sender immediately by reply e-mail and delete this message.
Thank you for your cooperation.
From owner-freebsd-stable@FreeBSD.ORG Mon Nov 17 17:17:58 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id C8206106564A
for <freebsd-stable@freebsd.org>; Mon, 17 Nov 2008 17:17:58 +0000 (UTC)
(envelope-from asossi@dotcom.ts.it)
Received: from mail.dotcom.ts.it (89-96-242-204.ip14.fastwebnet.it
[89.96.242.204]) by mx1.freebsd.org (Postfix) with SMTP id 346608FC12
for <freebsd-stable@freebsd.org>; Mon, 17 Nov 2008 17:17:57 +0000 (UTC)
(envelope-from asossi@dotcom.ts.it)
Received: (qmail 24212 invoked by uid 89); 17 Nov 2008 17:17:57 -0000
Received: by simscan 1.1.0 ppid: 24193, pid: 24206, t: 0.7607s scanners:none
X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on web.dotcom.ts.it
X-Spam-Level:
X-Spam-Status: No, hits=-4.1 required=3.0 tests=ALL_TRUSTED,AWL,BAYES_00
autolearn=ham version=3.2.3
Received: from unknown (HELO ?192.168.0.2?) (asossi@dotcom.ts.it@192.168.254.3)
by test.dotcom.ts.it with SMTP; 17 Nov 2008 17:17:56 -0000
Message-ID: <4921A6C5.6000107@dotcom.ts.it>
Date: Mon, 17 Nov 2008 18:15:49 +0100
From: Sossi Andrej <asossi@dotcom.ts.it>
Organization: DotCom Information technology
User-Agent: Thunderbird 2.0.0.17 (X11/20080914)
MIME-Version: 1.0
To: "Paul B. Mahol" <onemda@gmail.com>
References: <49219959.8040209@dotcom.ts.it>
<3a142e750811170859o226d3d91r45ac4106821e6fae@mail.gmail.com>
In-Reply-To: <3a142e750811170859o226d3d91r45ac4106821e6fae@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: freebsd-stable@freebsd.org
Subject: Re: swap_pager: indefinite wait
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Nov 2008 17:17:59 -0000
Paul B. Mahol wrote:
> On 11/17/08, Sossi Andrej <asossi@dotcom.ts.it> wrote:
>
>> Hello,
>> I manage a www (apache), database (postgresql) and e-mail (qmail) with
>> about 100 Internet domains.
>> We recently purchased a DELL MD3000i server with data access through
>> ISCSI protocol.
>> I installed a new server with FreeBSD 7.0 compiled kernel with ISCSI
>> (v. 2.1) and SCHED_ULE scheduler.
>> The server's local disk configuration is:
>> 512 MB /
>> 1024 MB SWAP
>> 254 MB / var
>> 2048MB / var/ qmail
>> 512 MB /tmp
>> ~ 70 GB /usr
>>
>> The apache data (/usr/local/www), postgre (/usr/local/pgsql) and qmail
>> (/usr/local/vpopmail) are instead on the partition on ISCSI. After
>> installing all the necessary softwares I tested the machine as mail
>> server for a one domain and everything worked fine for 2-3 days.
>> I wanted to test the correct functioning of qmail and of the
>> reading/writing on ISCSI. On the end of testing I decided to transfer
>> all of data (www, DB and e-mail) on the FreeBSD 7.0. I compressed all
>> the data on the original server (on tar.gz format). I transferred them
>> on the new server and started to decompress the files. Www data have
>> been decompressed correctly on the ISCSI disk. But while the messages
>> were being decompressed (~80GB of tar.gz) and all the DB were being
>> restored, the server crashed.
>>
>
> Which application were used for decompression?
>
I use this command:
tar -xvzf filename.tar.gz (for file decompression as root)
and
psql -f filename.sql postgres (for restore all databases)
>> The error shown was:
>>
>> swap_pager: indefinite wait buffer: bufobj: 0, blkno: 31, size: 4096
>>
>
> I believe this can happen any time when to much of swap partition is used.
> If this sort of thing happens often, review memory management of application(s)
> that is causing such scenario, if that is application fault - you have
> two choices:
> get more RAM (this may not always help) or use another application.
> Increasing swap partition will not help much ....
>
During decompression i sometimes monitor the system with command top and
I don't see the system use swap at all, but I didn't monitor constantly.
If the problem is caused by tar, what choices do i have to transport
files from original server to another quickly?
>> This message repeated every 30 seconds.
>> While restarting with the single user mode I checked there wasn't any
>> message after the crash in /var/log/messages.
>>
>> I think 1GB of swap should be enough, since with this configuration on
>> FreeBSD 5.5 everything worked for over 270 days without reboot.
>> The local disks are 2 of ~80GB in RAID 1 (mirror) with Gmirror
>> before installing FreeBSD I tested the 2 disks with the badblocks
>> software on Slackware which didn't find any r/w error.
>>
>> Can somebody help me understand why the system crashed this way or how
>> to avoid future crash?
>> It's a production server and I can't afford an out-of-service or data loss.
>>
>> Thank you very much and kind regards
Thank for your reply.
--
Sossi Andrej
-------------------------
DotCom Information technology
Via Biancospino, 9
34151 - Opicina (TS)
Italy
tel: +39 040 2158191
fax: +39 040 0641954
E-mail: asossi@dotcom.ts.it
----------------------------
Ai sensi del D.lgs n. 196 del 30.06.03 (Codice Privacy) si precisa che le informazioni contenute in questo messaggio sono riservate e ad uso esclusivo del destinatario. Qualora il messaggio in parola Le fosse pervenuto per errore, La preghiamo di eliminarlo senza copiarlo e di non inoltrarlo a terzi, dandocene gentilmente comunicazione. Grazie
This message, for the D.lgs n. 196 / 30.06.03 (Privacy Code), may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation.
From owner-freebsd-stable@FreeBSD.ORG Mon Nov 17 17:26:23 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id D86851065672
for <freebsd-stable@freebsd.org>; Mon, 17 Nov 2008 17:26:23 +0000 (UTC)
(envelope-from jdc@koitsu.dyndns.org)
Received: from QMTA10.emeryville.ca.mail.comcast.net
(qmta10.emeryville.ca.mail.comcast.net [76.96.30.17])
by mx1.freebsd.org (Postfix) with ESMTP id BC0B08FC14
for <freebsd-stable@freebsd.org>; Mon, 17 Nov 2008 17:26:23 +0000 (UTC)
(envelope-from jdc@koitsu.dyndns.org)
Received: from OMTA11.emeryville.ca.mail.comcast.net ([76.96.30.36])
by QMTA10.emeryville.ca.mail.comcast.net with comcast
id gG6z1a0010mlR8UAAHSPqm; Mon, 17 Nov 2008 17:26:23 +0000
Received: from koitsu.dyndns.org ([69.181.141.110])
by OMTA11.emeryville.ca.mail.comcast.net with comcast
id gHSN1a00M2P6wsM8XHSN18; Mon, 17 Nov 2008 17:26:23 +0000
X-Authority-Analysis: v=1.0 c=1 a=6I5d2MoRAAAA:8 a=QycZ5dHgAAAA:8
a=vcCQquSeVj8nnLyQ8RsA:9 a=fzz0aSQosRoeDjjIRVsA:7
a=-6aY_ejPScliUKX8HGRiG1n6kSoA:4 a=EoioJ0NPDVgA:10 a=LY0hPdMaydYA:10
Received: by icarus.home.lan (Postfix, from userid 1000)
id 60FD933C36; Mon, 17 Nov 2008 09:26:22 -0800 (PST)
Date: Mon, 17 Nov 2008 09:26:22 -0800
From: Jeremy Chadwick <koitsu@FreeBSD.org>
To: Sossi Andrej <asossi@dotcom.ts.it>
Message-ID: <20081117172622.GA34962@icarus.home.lan>
References: <49219959.8040209@dotcom.ts.it>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <49219959.8040209@dotcom.ts.it>
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: freebsd-stable@freebsd.org
Subject: Re: swap_pager: indefinite wait
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Nov 2008 17:26:23 -0000
On Mon, Nov 17, 2008 at 05:18:33PM +0100, Sossi Andrej wrote:
> Hello,
> I manage a www (apache), database (postgresql) and e-mail (qmail) with
> about 100 Internet domains.
> We recently purchased a DELL MD3000i server with data access through
> ISCSI protocol.
> I installed a new server with FreeBSD 7.0 compiled kernel with ISCSI
> (v. 2.1) and SCHED_ULE scheduler.
> The server's local disk configuration is:
> 512 MB /
> 1024 MB SWAP
> 254 MB / var
> 2048MB / var/ qmail
> 512 MB /tmp
> ~ 70 GB /usr
>
> The apache data (/usr/local/www), postgre (/usr/local/pgsql) and qmail
> (/usr/local/vpopmail) are instead on the partition on ISCSI. After
> installing all the necessary softwares I tested the machine as mail
> server for a one domain and everything worked fine for 2-3 days.
> I wanted to test the correct functioning of qmail and of the
> reading/writing on ISCSI. On the end of testing I decided to transfer
> all of data (www, DB and e-mail) on the FreeBSD 7.0. I compressed all
> the data on the original server (on tar.gz format). I transferred them
> on the new server and started to decompress the files. Www data have
> been decompressed correctly on the ISCSI disk. But while the messages
> were being decompressed (~80GB of tar.gz) and all the DB were being
> restored, the server crashed.
> The error shown was:
>
> swap_pager: indefinite wait buffer: bufobj: 0, blkno: 31, size: 4096
>
> This message repeated every 30 seconds.
Is this of any help?
http://lists.freebsd.org/pipermail/freebsd-scsi/2008-February/003383.html
http://lists.freebsd.org/pipermail/freebsd-scsi/2008-February/003387.html
--
| Jeremy Chadwick jdc at parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |
From owner-freebsd-stable@FreeBSD.ORG Mon Nov 17 17:27:36 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id CE6151065677
for <freebsd-stable@freebsd.org>; Mon, 17 Nov 2008 17:27:36 +0000 (UTC)
(envelope-from onemda@gmail.com)
Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.28])
by mx1.freebsd.org (Postfix) with ESMTP id 7E3EF8FC08
for <freebsd-stable@freebsd.org>; Mon, 17 Nov 2008 17:27:36 +0000 (UTC)
(envelope-from onemda@gmail.com)
Received: by yw-out-2324.google.com with SMTP id 9so1043208ywe.13
for <freebsd-stable@freebsd.org>; Mon, 17 Nov 2008 09:27:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:message-id:date:from:to
:subject:cc:in-reply-to:mime-version:content-type
:content-transfer-encoding:content-disposition:references;
bh=BdPSxSQKWr4jk6wppbrj4bXZzLcXvBUdHHtN+U8m4OY=;
b=mjqQpO8bGvk2REnJfMZuPCcqFxjjuPutMp47sQHNhv5NO+qF+kSSH1LJaejf3BGIDv
1o2mv1IQEK8qYouvjkFKDn7eoM5xLLzzs6ylXuTlU2aMxfJSeqNnVgm2oyTromB/E6HA
EGMNmeNhZDwopCTJleT2fPZUVOHhv/YtPDy9I=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
:content-type:content-transfer-encoding:content-disposition
:references;
b=r3erb6gSX49CqiGl8FQq62hWfeicLVW4lVNJOdpuJM2DPotpLBiuAREsk1bTqV6hQg
lMj8WvQlfg1vkL81lsLnTY27PsOnSRvCaRnNLc6hr45MnSK+ibeK8VOOfazFaZ3PnMGn
P4v1hb03hCJYCxeWgl1uuTT4Wj+5P+iZI3d50=
Received: by 10.65.59.11 with SMTP id m11mr3904295qbk.90.1226941140704;
Mon, 17 Nov 2008 08:59:00 -0800 (PST)
Received: by 10.65.216.9 with HTTP; Mon, 17 Nov 2008 08:59:00 -0800 (PST)
Message-ID: <3a142e750811170859o226d3d91r45ac4106821e6fae@mail.gmail.com>
Date: Mon, 17 Nov 2008 17:59:00 +0100
From: "Paul B. Mahol" <onemda@gmail.com>
To: "Sossi Andrej" <asossi@dotcom.ts.it>
In-Reply-To: <49219959.8040209@dotcom.ts.it>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <49219959.8040209@dotcom.ts.it>
Cc: freebsd-stable@freebsd.org
Subject: Re: swap_pager: indefinite wait
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Nov 2008 17:27:37 -0000
On 11/17/08, Sossi Andrej <asossi@dotcom.ts.it> wrote:
> Hello,
> I manage a www (apache), database (postgresql) and e-mail (qmail) with
> about 100 Internet domains.
> We recently purchased a DELL MD3000i server with data access through
> ISCSI protocol.
> I installed a new server with FreeBSD 7.0 compiled kernel with ISCSI
> (v. 2.1) and SCHED_ULE scheduler.
> The server's local disk configuration is:
> 512 MB /
> 1024 MB SWAP
> 254 MB / var
> 2048MB / var/ qmail
> 512 MB /tmp
> ~ 70 GB /usr
>
> The apache data (/usr/local/www), postgre (/usr/local/pgsql) and qmail
> (/usr/local/vpopmail) are instead on the partition on ISCSI. After
> installing all the necessary softwares I tested the machine as mail
> server for a one domain and everything worked fine for 2-3 days.
> I wanted to test the correct functioning of qmail and of the
> reading/writing on ISCSI. On the end of testing I decided to transfer
> all of data (www, DB and e-mail) on the FreeBSD 7.0. I compressed all
> the data on the original server (on tar.gz format). I transferred them
> on the new server and started to decompress the files. Www data have
> been decompressed correctly on the ISCSI disk. But while the messages
> were being decompressed (~80GB of tar.gz) and all the DB were being
> restored, the server crashed.
Which application were used for decompression?
> The error shown was:
>
> swap_pager: indefinite wait buffer: bufobj: 0, blkno: 31, size: 4096
I believe this can happen any time when to much of swap partition is used.
If this sort of thing happens often, review memory management of application(s)
that is causing such scenario, if that is application fault - you have
two choices:
get more RAM (this may not always help) or use another application.
Increasing swap partition will not help much ....
> This message repeated every 30 seconds.
> While restarting with the single user mode I checked there wasn't any
> message after the crash in /var/log/messages.
>
> I think 1GB of swap should be enough, since with this configuration on
> FreeBSD 5.5 everything worked for over 270 days without reboot.
> The local disks are 2 of ~80GB in RAID 1 (mirror) with Gmirror
> before installing FreeBSD I tested the 2 disks with the badblocks
> software on Slackware which didn't find any r/w error.
>
> Can somebody help me understand why the system crashed this way or how
> to avoid future crash?
> It's a production server and I can't afford an out-of-service or data loss.
>
> Thank you very much and kind regards.
>
> --
> Sossi Andrej
> -------------------------
> DotCom Information technology
>
> Via Biancospino, 9
> 34151 - Opicina (TS)
> Italy
>
> tel: +39 040 2158191
> fax: +39 040 0641954
> E-mail: asossi@dotcom.ts.it
> ----------------------------
>
> Ai sensi del D.lgs n. 196 del 30.06.03 (Codice Privacy) si precisa che
> le informazioni contenute in questo messaggio sono riservate e ad uso
> esclusivo del destinatario. Qualora il messaggio in parola Le fosse
> pervenuto per errore, La preghiamo di eliminarlo senza copiarlo e di non
> inoltrarlo a terzi, dandocene gentilmente comunicazione. Grazie
>
> This message, for the D.lgs n. 196 / 30.06.03 (Privacy Code), may
> contain confidential and/or privileged information. If you are not the
> addressee or authorized to receive this for the addressee, you must not
> use, copy, disclose or take any action based on this message or any
> information herein. If you have received this message in error, please
> advise the sender immediately by reply e-mail and delete this message.
> Thank you for your cooperation.
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
>
From owner-freebsd-stable@FreeBSD.ORG Mon Nov 17 17:44:56 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 6A252106564A
for <freebsd-stable@freebsd.org>; Mon, 17 Nov 2008 17:44:56 +0000 (UTC)
(envelope-from hartzell@alerce.com)
Received: from merlin.alerce.com (merlin.alerce.com [64.62.142.94])
by mx1.freebsd.org (Postfix) with ESMTP id E02CE8FC14
for <freebsd-stable@freebsd.org>; Mon, 17 Nov 2008 17:44:55 +0000 (UTC)
(envelope-from hartzell@alerce.com)
Received: from merlin.alerce.com (localhost [127.0.0.1])
by merlin.alerce.com (Postfix) with ESMTP id 0523633C62;
Mon, 17 Nov 2008 09:44:55 -0800 (PST)
Received: from merlin.alerce.com (localhost [127.0.0.1])
by merlin.alerce.com (Postfix) with ESMTP id 9F73433C5B;
Mon, 17 Nov 2008 09:44:54 -0800 (PST)
From: George Hartzell <hartzell@alerce.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <18721.44437.401689.422651@almost.alerce.com>
Date: Mon, 17 Nov 2008 09:44:53 -0800
To: CmdLnKid <cmdlnkid@gmail.com>
In-Reply-To: <alpine.BSF.2.00.0811162208500.56550@qvzrafvba.5c.ybpny>
References: <18716.48723.452606.66518@almost.alerce.com>
<18720.55070.363778.698000@almost.alerce.com>
<alpine.BSF.2.00.0811162208500.56550@qvzrafvba.5c.ybpny>
X-Mailer: VM 7.19 under Emacs 22.1.50.1
X-Virus-Scanned: ClamAV using ClamSMTP
Cc: freebsd-stable@freebsd.org, George Hartzell <hartzell@alerce.com>
Subject: Re: problem moving gmirror between two machines.
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: hartzell@alerce.com
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Nov 2008 17:44:56 -0000
CmdLnKid writes:
> On Sun, 16 Nov 2008 21:29 -0000, hartzell wrote:
>
> > George Hartzell writes:
> > >
> > > I have an HP DL360 with a pair of 1TB seagate disks that's been
> > > running -STABLE with a ZFS root partition set up using the tools
> > > available here:
> > >
> > > http://yds.coolrat.org/zfsboot.shtml
> > >
> > > It's been working great. As part of trying to understand what's going
> > > on, I csup'ed to -RELENG earlier today and rebuilt/installed the
> > > kernel and world whilst running on the DL360, so everything should be
> > > current.
> > >
> > > I tried to move the disks into an HP DL320 G4 and it fails to boot
> > > because it can't find /dev/mirror/boot (which it wants to mount onto
> > > /strap and then parts get nullfs'ed onto /boot and /rescue). It gives
> > > me the opportunity to start a shell, and from that shell I can do a
> > > zfs mount -a and get all of the zfs filesystems mounted, but there's
> > > nothing in /dev/mirror. No gmirror status and list are silent.
> > >
> > > I can move the disks back into the older machine and they work fine.
> > >
> > > I've run fdisk -s ad4 and bsdlabel -A /dev/ad4s1a and diffed the
> > > output from the two machines and they're identical.
> > >
> > > I've booted with kern.geom.mirror.debug=2 and the DL320G4 tastes
> > > /dev/ad4s1a (along with everything else) but doesn't do anything with
> > > it.
> > >
> > > Any ideas?
> > >
> >
> > [for the archives]
> >
> > Solved. gmirror had been set up with -h specifying the device, and
> > although the newer server used the same device names for its disks
> > (ad[46]) it assigned them to different hot swap bays. Once I switched
> > the disks everything came up fine.
> >
> > g.
>
> Wouldn't it be more feasible in this situation to just glabel the disks
> and mount them from /dev/<fstype>/<label> instead. Might make your life
> easier in the future for swapping disks.
>
> Example:
> /dev/ufs/tmp on /tmp (ufs, asynchronous, local, gjournal)
> /dev/ufs/usr on /usr (ufs, local, soft-updates)
> /dev/ufs/var on /var (ufs, local, soft-updates)
Yep, something like that would definitely be an improvement, but the
situation's a bit different. The failure was caused by trying to
mount /dev/mirror/boot on /strap (Yarema's naming choice), since
gmirror couldn't assemble /dev/ad[46]s1a into the mirror there *was*
no /dev/mirror/boot. I think one could build a mirror using -h and
glabeled devices, alternately I'm almost certain that just not using
-h would have results in gmirror finding the slices regardless of the
device number they got.
I set this system up as an experiment to play with zfs on a root
filesystem, and in it's most recent configuration used a set of
scripts by Yarema, found here:
http://yds.coolrat.org/zfsboot.shtml
When I asked Pawel about the gmirror funny business (at meetBSD over
the weekend) he asked me if the mirror had been set up with -h and I
had to sheepishly confess that I didn't know, since I'd just run
Yarema's stuff.
None of my dual-disk boot from gmirror'ed disks systems (based on
Ralf's approach, http://people.freebsd.org/~rse/mirror/) use -h and
I'd completely forgotten about it.
Having posted the question as a "mystery", I just thought it'd be
worth posting the outcome.
g.
From owner-freebsd-stable@FreeBSD.ORG Mon Nov 17 17:57:00 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id F071C106564A
for <freebsd-stable@freebsd.org>; Mon, 17 Nov 2008 17:57:00 +0000 (UTC)
(envelope-from peterjeremy@optushome.com.au)
Received: from mail36.syd.optusnet.com.au (mail36.syd.optusnet.com.au
[211.29.133.76])
by mx1.freebsd.org (Postfix) with ESMTP id 681DE8FC2A
for <freebsd-stable@freebsd.org>; Mon, 17 Nov 2008 17:57:00 +0000 (UTC)
(envelope-from peterjeremy@optushome.com.au)
Received: from server.vk2pj.dyndns.org
(c122-106-215-175.belrs3.nsw.optusnet.com.au [122.106.215.175])
by mail36.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id
mAHHukTP018520
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
Tue, 18 Nov 2008 04:56:48 +1100
X-Bogosity: Ham, spamicity=0.000000
Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1])
by server.vk2pj.dyndns.org (8.14.3/8.14.3) with ESMTP id mAHHukDI024306;
Tue, 18 Nov 2008 04:56:46 +1100 (EST)
(envelope-from peter@server.vk2pj.dyndns.org)
Received: (from peter@localhost)
by server.vk2pj.dyndns.org (8.14.3/8.14.3/Submit) id mAHHujXB024305;
Tue, 18 Nov 2008 04:56:45 +1100 (EST) (envelope-from peter)
Date: Tue, 18 Nov 2008 04:56:45 +1100
From: Peter Jeremy <peterjeremy@optushome.com.au>
To: "J. W. Ballantine" <jwb@homer.att.com>
Message-ID: <20081117175645.GN51761@server.vk2pj.dyndns.org>
References: <20081115224604.GG51761@server.vk2pj.dyndns.org>
<200811171356.IAA09494@akiva.homer.att.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="lHGcFxmlz1yfXmOs"
Content-Disposition: inline
In-Reply-To: <200811171356.IAA09494@akiva.homer.att.com>
X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: freebsd-stable@freebsd.org
Subject: Re: _nyssin undefined
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Nov 2008 17:57:01 -0000
--lHGcFxmlz1yfXmOs
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On 2008-Nov-17 08:56:55 -0500, "J. W. Ballantine" <jwb@homer.att.com> wrote:
>The problem started during the install of a new system build using
>the Friday AM CVS bits, and I can't get on the system in any
>mode.
If you try to boot to single-user, do you get the "enter shell pathname"
prompt? If so, does specifying "/rescue/sh" give you a shell?
--=20
Peter Jeremy
Please excuse any delays as the result of my ISP's inability to implement
an MTA that is either RFC2821-compliant or matches their claimed behaviour.
--lHGcFxmlz1yfXmOs
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (FreeBSD)
iEYEARECAAYFAkkhsF0ACgkQ/opHv/APuIcTzgCfUSZeYDAiiuQFZS4DH7Jc5CtV
t74An2s0lsq0r41mRUH4uF45Mn19K5K1
=ZJAR
-----END PGP SIGNATURE-----
--lHGcFxmlz1yfXmOs--
From owner-freebsd-stable@FreeBSD.ORG Mon Nov 17 19:27:32 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 03B481065673
for <freebsd-stable@freebsd.org>; Mon, 17 Nov 2008 19:27:32 +0000 (UTC)
(envelope-from prvs=120731b379=killing@multiplay.co.uk)
Received: from mail1.multiplay.co.uk (core6.multiplay.co.uk [85.236.96.23])
by mx1.freebsd.org (Postfix) with ESMTP id 84B6B8FC13
for <freebsd-stable@freebsd.org>; Mon, 17 Nov 2008 19:27:31 +0000 (UTC)
(envelope-from prvs=120731b379=killing@multiplay.co.uk)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=multiplay.co.uk;
s=Multiplay; t=1226949134; x=1227553934; q=dns/txt; h=Received:
Message-ID:From:To:Subject:Date:MIME-Version:Content-Type:
Content-Transfer-Encoding; bh=f6JFTuKIje2HCJhZz2HEQr0TSdugCN6j+9
l7lhoX2uI=; b=B9z33szGnE56m40efjoLgx50OnlMHiW56TlmSp2nkE0MeQ2aHG
adQFOeCUjupJzeZWOKYKyjUaNzKxu1zVyh9FlwF67MOpoaPtokJoHvahVC/X5IyH
BJkBwQxtmHlV4MJTuvdV83MWD1Y874lsG50kZ0VY4k0uSP2tKwuul6uUQ=
X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on
mail1.multiplay.co.uk
X-Spam-Level:
X-Spam-Status: No, score=-14.7 required=6.0 tests=BAYES_00, FORGED_MUA_OUTLOOK,
USER_IN_WHITELIST,USER_IN_WHITELIST_TO autolearn=ham version=3.1.8
Received: from r2d2 by mail1.multiplay.co.uk (MDaemon PRO v9.6.6)
with ESMTP id md50006556818.msg
for <freebsd-stable@freebsd.org>; Mon, 17 Nov 2008 19:12:12 +0000
X-Authenticated-Sender: Killing@multiplay.co.uk
X-MDRemoteIP: 213.123.247.160
X-Return-Path: prvs=120731b379=killing@multiplay.co.uk
X-Envelope-From: killing@multiplay.co.uk
X-MDaemon-Deliver-To: freebsd-stable@freebsd.org
Message-ID: <89DE4FDF67DC40AE88477897DF4CD0E7@multiplay.co.uk>
From: "Steven Hartland" <killing@multiplay.co.uk>
To: <freebsd-stable@freebsd.org>
Date: Mon, 17 Nov 2008 19:11:50 -0000
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5512
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Spam-Processed: mail1.multiplay.co.uk, Mon, 17 Nov 2008 19:12:14 +0000
X-MDAV-Processed: mail1.multiplay.co.uk, Mon, 17 Nov 2008 19:12:14 +0000
Subject: Possible regression in ifconfig under7.0 - removes valid default
route
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Nov 2008 19:27:32 -0000
I believe there "may be" a regression in the behaviour of ifconfig or
possibly just something I've never experienced before.
Basically when changing the IP of one of our machines, it suddenly
became inaccessible. After some investigation it turned out the machine
was inaccessible from anything other than the local VLAN and continued
diagnostics determined that the process of changing the IP had also
removed the default route.
This was clearly unexpected behaviour as the new IP was on the same
VLAN as the old IP and hence no routing table updates should be
required.
I don't have any older machines to test this on but I believe we have
done this procedure in the past without any such issues so wanted to
raise it here to see if anyone else has had experience with it.
Even if this isn't a regression it may well be something worth fixing
as its quite unexpected behaviour which could render a machine totally
inaccessible.
Regards
Steve
================================================
This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it.
In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337
or return the E.mail to postmaster@multiplay.co.uk.
From owner-freebsd-stable@FreeBSD.ORG Mon Nov 17 20:02:53 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 5E0FD1065670
for <freebsd-stable@freebsd.org>; Mon, 17 Nov 2008 20:02:53 +0000 (UTC)
(envelope-from jdc@koitsu.dyndns.org)
Received: from QMTA09.westchester.pa.mail.comcast.net
(qmta09.westchester.pa.mail.comcast.net [76.96.62.96])
by mx1.freebsd.org (Postfix) with ESMTP id E9A488FC18
for <freebsd-stable@freebsd.org>; Mon, 17 Nov 2008 20:02:52 +0000 (UTC)
(envelope-from jdc@koitsu.dyndns.org)
Received: from OMTA11.westchester.pa.mail.comcast.net ([76.96.62.36])
by QMTA09.westchester.pa.mail.comcast.net with comcast
id gJuS1a00D0mv7h059L2sJz; Mon, 17 Nov 2008 20:02:52 +0000
Received: from koitsu.dyndns.org ([69.181.141.110])
by OMTA11.westchester.pa.mail.comcast.net with comcast
id gL2r1a0022P6wsM3XL2ro0; Mon, 17 Nov 2008 20:02:52 +0000
X-Authority-Analysis: v=1.0 c=1 a=KxjOStg9nI0A:10 a=ta0Jkjhx-mIA:10
a=QycZ5dHgAAAA:8 a=lAaB-bto0OL5IMqRhA0A:9 a=TtTIlnhxIKH-XV7i6RoA:7
a=4wF9NWMi8qYGwvObpkiDGVl-MGUA:4 a=EoioJ0NPDVgA:10 a=LY0hPdMaydYA:10
Received: by icarus.home.lan (Postfix, from userid 1000)
id DA52A33C36; Mon, 17 Nov 2008 12:02:50 -0800 (PST)
Date: Mon, 17 Nov 2008 12:02:50 -0800
From: Jeremy Chadwick <koitsu@FreeBSD.org>
To: Steven Hartland <killing@multiplay.co.uk>
Message-ID: <20081117200250.GA38619@icarus.home.lan>
References: <89DE4FDF67DC40AE88477897DF4CD0E7@multiplay.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <89DE4FDF67DC40AE88477897DF4CD0E7@multiplay.co.uk>
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: freebsd-stable@freebsd.org
Subject: Re: Possible regression in ifconfig under7.0 - removes valid
default route
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Nov 2008 20:02:53 -0000
On Mon, Nov 17, 2008 at 07:11:50PM -0000, Steven Hartland wrote:
> I believe there "may be" a regression in the behaviour of ifconfig or
> possibly just something I've never experienced before.
>
> Basically when changing the IP of one of our machines, it suddenly
> became inaccessible. After some investigation it turned out the machine
> was inaccessible from anything other than the local VLAN and continued
> diagnostics determined that the process of changing the IP had also
> removed the default route.
>
> This was clearly unexpected behaviour as the new IP was on the same
> VLAN as the old IP and hence no routing table updates should be
> required.
>
> I don't have any older machines to test this on but I believe we have
> done this procedure in the past without any such issues so wanted to
> raise it here to see if anyone else has had experience with it.
>
> Even if this isn't a regression it may well be something worth fixing
> as its quite unexpected behaviour which could render a machine totally
> inaccessible.
I can try to reproduce this if you'd like, on a VMware session.
One case where the default route could be (I haven't checked) removed:
some NIC drivers in the past, when changing the "primary IP" (first IP
shown in ifconfig for an interface), would actually bring down the
entire interface (e.g. ifconfig XXX down) then back up again a second or
two later. dmesg on your machine would be able to confirm whether or
not this is happening.
--
| Jeremy Chadwick jdc at parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |
From owner-freebsd-stable@FreeBSD.ORG Mon Nov 17 20:47:33 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id BA827106567A
for <freebsd-stable@freebsd.org>; Mon, 17 Nov 2008 20:47:33 +0000 (UTC)
(envelope-from prvs=120731b379=killing@multiplay.co.uk)
Received: from mail1.multiplay.co.uk (core6.multiplay.co.uk [85.236.96.23])
by mx1.freebsd.org (Postfix) with ESMTP id 1B7FB8FC0A
for <freebsd-stable@freebsd.org>; Mon, 17 Nov 2008 20:47:32 +0000 (UTC)
(envelope-from prvs=120731b379=killing@multiplay.co.uk)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=multiplay.co.uk;
s=Multiplay; t=1226954802; x=1227559602; q=dns/txt; h=Received:
Message-ID:From:To:Cc:References:Subject:Date:MIME-Version:
Content-Type:Content-Transfer-Encoding; bh=BaucXge3D22Y34ZdMmUNQ
zj9CptKnzMb9vW8ssI+mC4=; b=bp4Z9vGSTa8u7B/r7u72HkV7vmdV5FLPtaJW8
6wWySf70qdz/FCO6VrMAUM6pzlYbpHu7zh45v0pItWNVrh2vU76cRxDaYITbZlS0
KGIH96Qpf4Bna8hbKID4lwkaUN438tUTK6C1xWn90pLkYRdtpnxQPP+sTgvf+biV
7w+TKQ=
X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on
mail1.multiplay.co.uk
X-Spam-Level:
X-Spam-Status: No, score=-14.7 required=6.0 tests=BAYES_00, FORGED_MUA_OUTLOOK,
USER_IN_WHITELIST,USER_IN_WHITELIST_TO autolearn=ham version=3.1.8
Received: from r2d2 by mail1.multiplay.co.uk (MDaemon PRO v9.6.6)
with ESMTP id md50006557183.msg; Mon, 17 Nov 2008 20:46:39 +0000
X-Authenticated-Sender: Killing@multiplay.co.uk
X-MDRemoteIP: 213.123.247.160
X-Return-Path: prvs=120731b379=killing@multiplay.co.uk
X-Envelope-From: killing@multiplay.co.uk
Message-ID: <4E2AB11167C143D6948D2BEEDBCA8512@multiplay.co.uk>
From: "Steven Hartland" <killing@multiplay.co.uk>
To: "Jeremy Chadwick" <koitsu@FreeBSD.org>
References: <89DE4FDF67DC40AE88477897DF4CD0E7@multiplay.co.uk>
<20081117200250.GA38619@icarus.home.lan>
Date: Mon, 17 Nov 2008 20:45:43 -0000
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5512
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Spam-Processed: mail1.multiplay.co.uk, Mon, 17 Nov 2008 20:46:41 +0000
X-MDAV-Processed: mail1.multiplay.co.uk, Mon, 17 Nov 2008 20:46:42 +0000
Cc: freebsd-stable@freebsd.org
Subject: Re: Possible regression in ifconfig under7.0 - removes validdefault
route
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Nov 2008 20:47:33 -0000
----- Original Message -----
From: "Jeremy Chadwick" <koitsu@FreeBSD.org>
> I can try to reproduce this if you'd like, on a VMware session.
>
> One case where the default route could be (I haven't checked) removed:
> some NIC drivers in the past, when changing the "primary IP" (first IP
> shown in ifconfig for an interface), would actually bring down the
> entire interface (e.g. ifconfig XXX down) then back up again a second or
> two later. dmesg on your machine would be able to confirm whether or
> not this is happening.
Thanks Jeremy, no such down up here is show so I believe this is not
the case, here anyway. The interface in question was em0 details:-
em0: <Intel(R) PRO/1000 Network Connection Version - 6.7.3> port 0xd400-0xd43f mem 0xfea60000-0xfea7ffff,0xfea40000-0xfea5ffff irq
23 at device 8.0 on pci1
em0: Ethernet address: 00:30:48:71:b6:b7
em0: [FILTER]
FreeBSD test 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb 24 19:59:52 UTC 2008
root@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386
Would be most interested in the results of you vm test if you would
be so kind.
Regards
Steve
================================================
This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it.
In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337
or return the E.mail to postmaster@multiplay.co.uk.
From owner-freebsd-stable@FreeBSD.ORG Mon Nov 17 21:01:42 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 86731106564A;
Mon, 17 Nov 2008 21:01:42 +0000 (UTC)
(envelope-from sclark46@earthlink.net)
Received: from elasmtp-mealy.atl.sa.earthlink.net
(elasmtp-mealy.atl.sa.earthlink.net [209.86.89.69])
by mx1.freebsd.org (Postfix) with ESMTP id 36D808FC16;
Mon, 17 Nov 2008 21:01:42 +0000 (UTC)
(envelope-from sclark46@earthlink.net)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net;
b=FNJ5vk4XIVeNYvYpQUUPqV46qfDtBhnzzipdntxDLwsrxiwWsWPpZ4xf4iYXgfNw;
h=Received:Message-ID:Date:From:Reply-To:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [208.118.36.229] (helo=joker.seclark.com)
by elasmtp-mealy.atl.sa.earthlink.net with esmtpsa
(TLSv1:AES256-SHA:256) (Exim 4.67)
(envelope-from <sclark46@earthlink.net>)
id 1L2BE5-0007Kp-GD; Mon, 17 Nov 2008 16:01:41 -0500
Message-ID: <4921DBB4.4060505@earthlink.net>
Date: Mon, 17 Nov 2008 16:01:40 -0500
From: Stephen Clark <sclark46@earthlink.net>
User-Agent: Thunderbird 2.0.0.16 (X11/20080723)
MIME-Version: 1.0
To: freebsd-net@freebsd.org
References: <491B2703.4080707@earthlink.net>
<491B31F7.30200@elischer.org> <491B4345.80106@earthlink.net>
<491B47D2.6010804@elischer.org> <491C2235.4090509@earthlink.net> <1226589468.1976.12.camel@wombat.2hip.net> <491C4EC2.2000802@earthlink.net>
<491D6CED.50006@earthlink.net> <491DC28E.80804@elischer.org> <1226688153.1719.23.camel@squirrel.corp.cox.com>
<20081115102746.K61259@maildrop.int.zabbadoz.net>
In-Reply-To: <20081115102746.K61259@maildrop.int.zabbadoz.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: a437fbc6971e80f61aa676d7e74259b7b3291a7d08dfec797040dbfe5ded6009d701fad992715179350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 208.118.36.229
Cc: FreeBSD Stable <freebsd-stable@freebsd.org>
Subject: Re: FreeBSD 6.3 gre and traceroute
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: sclark46@earthlink.net
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Nov 2008 21:01:42 -0000
Bjoern A. Zeeb wrote:
> On Fri, 14 Nov 2008, Robert Noland wrote:
>
> Hi,
>
>>>>> Also just using gre's without the
>>>>> underlying ipsec tunnels seems to
>>>>> work properly.
>
> The reason for this to my knowledge is:
> http://www.kame.net/dev/cvsweb2.cgi/kame/freebsd2/sys/netinet/ip_icmp.c#rev1.4
>
>
> or looking at recent freebsd code:
> http://fxr.watson.org/fxr/source/netinet/ip_icmp.c#L164
> Look for M_DECRYPTED.
>
> Now what happens in your case:
>
> you receive an IPSec ESP packet, which gets decryped, that sets
> M_DECRYPTED on the mbuf passes through various parts, gets up to gre,
> gets decapsulated is an IP packet (again) gets to ip_input, TTL
> expired, icmp_error and it's still the same mbuf that originally got
> the M_DECRYPTED set. Thus the packets is just freed and you never see
> anything.
>
> So thinking about this has nothing to do with gre (or gif for example
> as well) in first place. It's arguably that passing it on to another
> decapsulation the flag should be cleared when entering gre() for
> example.
>
> The other question of course is why we do not send the icmp error back
> even on plain ipsec? Is it because we could possibly leak information
> as it's not caught by the policy sending it back?
>
> /bz
>
Update:
Adding this code in ip_icmp.c makes the traceroute work.
case IPPROTO_GRE:
hlen += sizeof(struct gre_h);
+ m->m_flags &= ~(M_DECRYPTED);
Steve
--
"They that give up essential liberty to obtain temporary safety,
deserve neither liberty nor safety." (Ben Franklin)
"The course of history shows that as a government grows, liberty
decreases." (Thomas Jefferson)
From owner-freebsd-stable@FreeBSD.ORG Mon Nov 17 21:11:58 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 83E981065670
for <freebsd-stable@freebsd.org>; Mon, 17 Nov 2008 21:11:58 +0000 (UTC)
(envelope-from jdc@koitsu.dyndns.org)
Received: from QMTA04.emeryville.ca.mail.comcast.net
(qmta04.emeryville.ca.mail.comcast.net [76.96.30.40])
by mx1.freebsd.org (Postfix) with ESMTP id 1DE1C8FC0C
for <freebsd-stable@freebsd.org>; Mon, 17 Nov 2008 21:11:56 +0000 (UTC)
(envelope-from jdc@koitsu.dyndns.org)
Received: from OMTA02.emeryville.ca.mail.comcast.net ([76.96.30.19])
by QMTA04.emeryville.ca.mail.comcast.net with comcast
id gG6z1a05D0QkzPwA4MBuss; Mon, 17 Nov 2008 21:11:54 +0000
Received: from koitsu.dyndns.org ([69.181.141.110])
by OMTA02.emeryville.ca.mail.comcast.net with comcast
id gMBs1a00C2P6wsM8NMBsk5; Mon, 17 Nov 2008 21:11:53 +0000
X-Authority-Analysis: ??
Received: by icarus.home.lan (Postfix, from userid 1000)
id 8CD3033C36; Mon, 17 Nov 2008 13:11:53 -0800 (PST)
Date: Mon, 17 Nov 2008 13:11:53 -0800
From: Jeremy Chadwick <koitsu@FreeBSD.org>
To: Steven Hartland <killing@multiplay.co.uk>
Message-ID: <20081117211153.GA39851@icarus.home.lan>
References: <89DE4FDF67DC40AE88477897DF4CD0E7@multiplay.co.uk>
<20081117200250.GA38619@icarus.home.lan>
<4E2AB11167C143D6948D2BEEDBCA8512@multiplay.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4E2AB11167C143D6948D2BEEDBCA8512@multiplay.co.uk>
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: freebsd-stable@freebsd.org
Subject: Re: Possible regression in ifconfig under7.0 - removes
validdefault route
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Nov 2008 21:11:58 -0000
On Mon, Nov 17, 2008 at 08:45:43PM -0000, Steven Hartland wrote:
> ----- Original Message ----- From: "Jeremy Chadwick" <koitsu@FreeBSD.org>
>> I can try to reproduce this if you'd like, on a VMware session.
>>
>> One case where the default route could be (I haven't checked) removed:
>> some NIC drivers in the past, when changing the "primary IP" (first IP
>> shown in ifconfig for an interface), would actually bring down the
>> entire interface (e.g. ifconfig XXX down) then back up again a second or
>> two later. dmesg on your machine would be able to confirm whether or
>> not this is happening.
>
>
> Thanks Jeremy, no such down up here is show so I believe this is not
> the case, here anyway. The interface in question was em0 details:-
> em0: <Intel(R) PRO/1000 Network Connection Version - 6.7.3> port
> 0xd400-0xd43f mem 0xfea60000-0xfea7ffff,0xfea40000-0xfea5ffff irq 23 at
> device 8.0 on pci1
> em0: Ethernet address: 00:30:48:71:b6:b7
> em0: [FILTER]
>
> FreeBSD test 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb 24 19:59:52 UTC
> 2008 root@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386
>
> Would be most interested in the results of you vm test if you would
> be so kind.
No problem. I'm testing on VMware Workstation 6.5.0 build 118116,
RELENG_7 amd64 (world/kernel dated 2008/10/23).
rc.conf (showing DHCP is not in use):
ifconfig_em0="inet 192.168.1.190 netmask 255.255.255.0"
defaultrouter="192.168.1.1"
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=9b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM>
ether 00:0c:29:0a:c9:37
inet 192.168.1.190 netmask 0xffffff00 broadcast 192.168.1.255
media: Ethernet autoselect (1000baseTX <full-duplex>)
status: active
Destination Gateway Flags Refs Use Netif Expire
default 192.168.1.1 UGS 0 0 em0
127.0.0.1 127.0.0.1 UH 0 0 lo0
192.168.1.0/24 link#1 UC 0 0 em0
192.168.1.1 link#1 UHLW 2 0 em0
192.168.1.51 00:30:48:d2:22:d0 UHLW 2 50 em0 1107
Command executed: ifconfig em0 inet 10.0.0.1 netmask 255.0.0.0
Aftermath:
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=9b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM>
ether 00:0c:29:0a:c9:37
inet 10.0.0.1 netmask 0xff000000 broadcast 10.255.255.255
media: Ethernet autoselect (1000baseTX <full-duplex>)
status: active
Destination Gateway Flags Refs Use Netif Expire
10.0.0.0/8 link#1 UC 0 0 em0
127.0.0.1 127.0.0.1 UH 0 0 lo0
Command executed: route add default 10.0.0.128
Aftermath:
Destination Gateway Flags Refs Use Netif Expire
default 10.0.0.128 UGS 0 0 em0
10.0.0.0/8 link#1 UC 0 0 em0
10.0.0.128 link#1 UHLW 2 0 em0
127.0.0.1 127.0.0.1 UH 0 0 lo0
Command executed: ifconfig em0 inet 10.10.10.10 netmask 255.0.0.0
Aftermath:
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=9b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM>
ether 00:0c:29:0a:c9:37
inet 10.10.10.10 netmask 0xff000000 broadcast 10.255.255.255
media: Ethernet autoselect (1000baseTX <full-duplex>)
status: active
Destination Gateway Flags Refs Use Netif Expire
10.0.0.0/8 link#1 UC 0 0 em0
127.0.0.1 127.0.0.1 UH 0 0 lo0
Summary: confirmed. Above two tests show that even if changing the IP
to something else within the same network block, the default route is
removed and not put back.
This is pretty major, if you ask me.
--
| Jeremy Chadwick jdc at parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |
From owner-freebsd-stable@FreeBSD.ORG Mon Nov 17 21:39:04 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 326411065677
for <freebsd-stable@freebsd.org>; Mon, 17 Nov 2008 21:39:04 +0000 (UTC)
(envelope-from jrhett@netconsonance.com)
Received: from mail.netconsonance.com (mail.netconsonance.com [198.207.204.4])
by mx1.freebsd.org (Postfix) with ESMTP id 156DD8FC20
for <freebsd-stable@freebsd.org>; Mon, 17 Nov 2008 21:39:03 +0000 (UTC)
(envelope-from jrhett@netconsonance.com)
Received: from [10.66.240.106] (public-wireless.sv.svcolo.com [64.13.135.30])
(authenticated bits=0)
by mail.netconsonance.com (8.14.1/8.14.1) with ESMTP id mAHLcwA2067504;
Mon, 17 Nov 2008 13:38:58 -0800 (PST)
(envelope-from jrhett@netconsonance.com)
X-Virus-Scanned: amavisd-new at netconsonance.com
X-Spam-Flag: NO
X-Spam-Score: -1.048
X-Spam-Level:
X-Spam-Status: No, score=-1.048 tagged_above=-999 required=3.5
tests=[ALL_TRUSTED=-1.44, AWL=0.392]
Message-Id: <8E74A88B-8E7F-4D80-9DD3-972DACA427F2@netconsonance.com>
From: Jo Rhett <jrhett@netconsonance.com>
To: Oliver Lehmann <lehmann@ans-netz.de>
In-Reply-To: <20081117070627.a21086ef.lehmann@ans-netz.de>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Mon, 17 Nov 2008 13:38:53 -0800
References: <20081029170728.be7cc7ab.lehmann@ans-netz.de>
<13394481-8FDC-4934-BB12-FA5BCB2D35CD@nevada.net.nz>
<20081112204351.ccc51c2f.lehmann@ans-netz.de>
<BC332C75-2E81-49E5-8D1C-166A0434525F@netconsonance.com>
<20081117070627.a21086ef.lehmann@ans-netz.de>
X-Mailer: Apple Mail (2.929.2)
Cc: freebsd-stable@freebsd.org, Philip Murray <pmurray@nevada.net.nz>
Subject: Re: 3Ware 9000 series hangs under load
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Nov 2008 21:39:04 -0000
> Jo Rhett wrote:
>> The driver logs all useful stuff, and the SEC logfile surfer does a
>> good job of notifying you quickly. I can send you an SEC
>> configuration for that if you want.
On Nov 16, 2008, at 10:06 PM, Oliver Lehmann wrote:
> Hm - what is SEC?
Simple Event Correlator
http://kodu.neti.ee/~risto/sec/
and
/usr/ports/sysutils/sec
Best damn logsurger evar! *giggle*
--
Jo Rhett
Net Consonance : consonant endings by net philanthropy, open source
and other randomness
From owner-freebsd-stable@FreeBSD.ORG Mon Nov 17 21:41:03 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id D15FD1065672
for <freebsd-stable@freebsd.org>; Mon, 17 Nov 2008 21:41:03 +0000 (UTC)
(envelope-from jrhett@netconsonance.com)
Received: from mail.netconsonance.com (mail.netconsonance.com [198.207.204.4])
by mx1.freebsd.org (Postfix) with ESMTP id 9D2DA8FC14
for <freebsd-stable@freebsd.org>; Mon, 17 Nov 2008 21:41:03 +0000 (UTC)
(envelope-from jrhett@netconsonance.com)
Received: from [10.66.240.106] (public-wireless.sv.svcolo.com [64.13.135.30])
(authenticated bits=0)
by mail.netconsonance.com (8.14.1/8.14.1) with ESMTP id mAHLf1J3067556;
Mon, 17 Nov 2008 13:41:01 -0800 (PST)
(envelope-from jrhett@netconsonance.com)
X-Virus-Scanned: amavisd-new at netconsonance.com
X-Spam-Flag: NO
X-Spam-Score: -1.05
X-Spam-Level:
X-Spam-Status: No, score=-1.05 tagged_above=-999 required=3.5
tests=[ALL_TRUSTED=-1.44, AWL=0.390]
From: Jo Rhett <jrhett@netconsonance.com>
To: Steven Hartland <killing@multiplay.co.uk>
In-Reply-To: <89DE4FDF67DC40AE88477897DF4CD0E7@multiplay.co.uk>
X-Priority: 3
References: <89DE4FDF67DC40AE88477897DF4CD0E7@multiplay.co.uk>
Message-Id: <188BDB85-46C0-41AA-B270-DA03BBD4CFF2@netconsonance.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Mon, 17 Nov 2008 13:40:55 -0800
X-Mailer: Apple Mail (2.929.2)
Cc: freebsd-stable@freebsd.org
Subject: Re: Possible regression in ifconfig under7.0 - removes valid
default route
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Nov 2008 21:41:03 -0000
This is a bug in my mind, but it's not a regression. FreeBSD has done
this for at least 10 years now. If you are changing the IP of an
interface, you *must* do a semicolon chained command to a route add
default. It's been true for as long as I can remember.
On Nov 17, 2008, at 11:11 AM, Steven Hartland wrote:
> I believe there "may be" a regression in the behaviour of ifconfig or
> possibly just something I've never experienced before.
>
> Basically when changing the IP of one of our machines, it suddenly
> became inaccessible. After some investigation it turned out the
> machine
> was inaccessible from anything other than the local VLAN and continued
> diagnostics determined that the process of changing the IP had also
> removed the default route.
>
> This was clearly unexpected behaviour as the new IP was on the same
> VLAN as the old IP and hence no routing table updates should be
> required.
>
> I don't have any older machines to test this on but I believe we have
> done this procedure in the past without any such issues so wanted to
> raise it here to see if anyone else has had experience with it.
>
> Even if this isn't a regression it may well be something worth fixing
> as its quite unexpected behaviour which could render a machine totally
> inaccessible.
>
> Regards
> Steve
>
> ================================================
> This e.mail is private and confidential between Multiplay (UK) Ltd.
> and the person or entity to whom it is addressed. In the event of
> misdirection, the recipient is prohibited from using, copying,
> printing or otherwise disseminating it or any information contained
> in it.
> In the event of misdirection, illegible or incomplete transmission
> please telephone +44 845 868 1337
> or return the E.mail to postmaster@multiplay.co.uk.
>
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org
> "
--
Jo Rhett
Net Consonance : consonant endings by net philanthropy, open source
and other randomness
From owner-freebsd-stable@FreeBSD.ORG Mon Nov 17 22:12:35 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 1C334106564A
for <freebsd-stable@freebsd.org>; Mon, 17 Nov 2008 22:12:35 +0000 (UTC)
(envelope-from prvs=120731b379=killing@multiplay.co.uk)
Received: from mail1.multiplay.co.uk (core6.multiplay.co.uk [85.236.96.23])
by mx1.freebsd.org (Postfix) with ESMTP id 95DD58FC18
for <freebsd-stable@freebsd.org>; Mon, 17 Nov 2008 22:12:34 +0000 (UTC)
(envelope-from prvs=120731b379=killing@multiplay.co.uk)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=multiplay.co.uk;
s=Multiplay; t=1226959718; x=1227564518; q=dns/txt; h=Received:
Message-ID:From:To:Cc:References:Subject:Date:MIME-Version:
Content-Type:Content-Transfer-Encoding; bh=/QZ/FtPHcKheqcM8ltzF7
ROgqMPnVaVULXbFEFHxMx8=; b=emz1XEJN6ATFj8lJUslv/4+P65pt/PtYHyEOA
yk/tZkYg9djyCt614lH/mjEKTtegt6h6qa8/F4qEj9K2Sye//HgB27Q9lYAse+pV
AGO86KxQ+EdqF4u8pWRy1pCfro6pJLyOA5Xp9fCeMCGBy/iE4tdt6TA2U7gZXGeL
2zTJtE=
X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on
mail1.multiplay.co.uk
X-Spam-Level:
X-Spam-Status: No, score=-14.7 required=6.0 tests=BAYES_00, FORGED_MUA_OUTLOOK,
USER_IN_WHITELIST,USER_IN_WHITELIST_TO autolearn=ham version=3.1.8
Received: from r2d2 by mail1.multiplay.co.uk (MDaemon PRO v9.6.6)
with ESMTP id md50006557512.msg
for <freebsd-stable@freebsd.org>; Mon, 17 Nov 2008 22:08:36 +0000
X-Authenticated-Sender: Killing@multiplay.co.uk
X-MDRemoteIP: 213.123.247.160
X-Return-Path: prvs=120731b379=killing@multiplay.co.uk
X-Envelope-From: killing@multiplay.co.uk
X-MDaemon-Deliver-To: freebsd-stable@freebsd.org
Message-ID: <5FD58BCD6B4C409DA7E7C30150FB10C7@multiplay.co.uk>
From: "Steven Hartland" <killing@multiplay.co.uk>
To: "Jo Rhett" <jrhett@netconsonance.com>
References: <89DE4FDF67DC40AE88477897DF4CD0E7@multiplay.co.uk>
<188BDB85-46C0-41AA-B270-DA03BBD4CFF2@netconsonance.com>
Date: Mon, 17 Nov 2008 22:08:32 -0000
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
reply-type=response
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5512
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Spam-Processed: mail1.multiplay.co.uk, Mon, 17 Nov 2008 22:08:36 +0000
X-MDAV-Processed: mail1.multiplay.co.uk, Mon, 17 Nov 2008 22:08:38 +0000
Cc: freebsd-stable@freebsd.org
Subject: Re: Possible regression in ifconfig under7.0 - removes validdefault
route
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Nov 2008 22:12:35 -0000
Thanks for the confirmation on that its not a regression Jo. It really
is a nasty little bug so I'll raise a PR for it, hopefully someone
with the power will then fix it :)
Regards
Steve
----- Original Message -----
From: "Jo Rhett" <jrhett@netconsonance.com>
> This is a bug in my mind, but it's not a regression. FreeBSD has done
> this for at least 10 years now. If you are changing the IP of an
> interface, you *must* do a semicolon chained command to a route add
> default. It's been true for as long as I can remember.
================================================
This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it.
In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337
or return the E.mail to postmaster@multiplay.co.uk.
From owner-freebsd-stable@FreeBSD.ORG Mon Nov 17 22:23:46 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 794A91065700;
Mon, 17 Nov 2008 22:23:46 +0000 (UTC)
(envelope-from lists@pingle.org)
Received: from willow.pingle.org (willow.pingle.org [68.76.213.30])
by mx1.freebsd.org (Postfix) with ESMTP id 440528FC08;
Mon, 17 Nov 2008 22:23:46 +0000 (UTC)
(envelope-from lists@pingle.org)
Received: from localhost (unknown [127.0.0.1])
by willow.pingle.org (Postfix) with ESMTP id 2112811458;
Mon, 17 Nov 2008 17:03:46 -0500 (EST)
X-Virus-Scanned: amavisd-new at pingle.org
Received: from willow.pingle.org ([127.0.0.1])
by localhost (willow.pingle.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id vIIXtyT8IqkJ; Mon, 17 Nov 2008 17:03:44 -0500 (EST)
Received: from [127.0.0.1] (hpcw.hpcisp.com [68.76.213.13])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(No client certificate requested) (Authenticated sender: jim)
by willow.pingle.org (Postfix) with ESMTPSA id B704B11455;
Mon, 17 Nov 2008 17:03:41 -0500 (EST)
Message-ID: <4921EA3D.4010409@pingle.org>
Date: Mon, 17 Nov 2008 17:03:41 -0500
From: Jim Pingle <lists@pingle.org>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Jeremy Chadwick <koitsu@FreeBSD.org>
References: <89DE4FDF67DC40AE88477897DF4CD0E7@multiplay.co.uk> <20081117200250.GA38619@icarus.home.lan> <4E2AB11167C143D6948D2BEEDBCA8512@multiplay.co.uk>
<20081117211153.GA39851@icarus.home.lan>
In-Reply-To: <20081117211153.GA39851@icarus.home.lan>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: freebsd-stable@freebsd.org, Steven Hartland <killing@multiplay.co.uk>
Subject: Re: Possible regression in ifconfig under7.0 - removes validdefault
route
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Nov 2008 22:23:46 -0000
Jeremy Chadwick wrote:
> Summary: confirmed. Above two tests show that even if changing the IP
> to something else within the same network block, the default route is
> removed and not put back.
>
> This is pretty major, if you ask me.
I've encountered similar issues before, and typically just added ";
/etc/rc.d/routing restart" or "&& /etc/rc.d/routing restart" after the
ifconfig statement just to be safe.
Typically I had adjusted rc.conf, then used "/etc/rc.d/netif restart;
/etc/rc.d/routing restart"
Jim
From owner-freebsd-stable@FreeBSD.ORG Mon Nov 17 23:03:02 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 757DA1065672
for <freebsd-stable@freebsd.org>; Mon, 17 Nov 2008 23:03:02 +0000 (UTC)
(envelope-from sthaug@nethelp.no)
Received: from bizet.nethelp.no (bizet.nethelp.no [195.1.209.33])
by mx1.freebsd.org (Postfix) with SMTP id ADCFD8FC0C
for <freebsd-stable@freebsd.org>; Mon, 17 Nov 2008 23:03:01 +0000 (UTC)
(envelope-from sthaug@nethelp.no)
Received: (qmail 99560 invoked from network); 17 Nov 2008 22:36:19 -0000
Received: from bizet.nethelp.no (HELO localhost) (195.1.209.33)
by bizet.nethelp.no with SMTP; 17 Nov 2008 22:36:19 -0000
Date: Mon, 17 Nov 2008 23:36:19 +0100 (CET)
Message-Id: <20081117.233619.85395429.sthaug@nethelp.no>
To: killing@multiplay.co.uk
From: sthaug@nethelp.no
In-Reply-To: <5FD58BCD6B4C409DA7E7C30150FB10C7@multiplay.co.uk>
References: <89DE4FDF67DC40AE88477897DF4CD0E7@multiplay.co.uk>
<188BDB85-46C0-41AA-B270-DA03BBD4CFF2@netconsonance.com>
<5FD58BCD6B4C409DA7E7C30150FB10C7@multiplay.co.uk>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: jrhett@netconsonance.com, freebsd-stable@freebsd.org
Subject: Re: Possible regression in ifconfig under7.0 - removes
validdefault route
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Nov 2008 23:03:02 -0000
> Thanks for the confirmation on that its not a regression Jo. It really
> is a nasty little bug so I'll raise a PR for it, hopefully someone
> with the power will then fix it :)
This leads to the question - what do people *want* with respect to
static routes? I know what *I* want: The static route behavior that
Cisco, Juniper and other big router vendors have, i.e.
- A configured static route exists in the routing table as long as
the nexthop IP address is valid. If the nexthop becomes invalid (for
instance if you lose link on an Ethernet interface), the static
route is also removed from the routing table.
- But (and here's the big difference) - *if the nexthop comes back*,
for instance because your Ethernet interface gets link again, the
configured static route is inserted into the routing table again.
Note that with this behavior, changing the IP address of an interface
would not result in the default route being deleted, as long as the
nexthop for the default route remained valid.
Oh yeah, since we're in wishful thinking mode, I want interface
descriptions too...
Steinar Haug, Nethelp consulting, sthaug@nethelp.no
From owner-freebsd-stable@FreeBSD.ORG Tue Nov 18 08:12:00 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 40E301065673
for <freebsd-stable@freebsd.org>; Tue, 18 Nov 2008 08:12:00 +0000 (UTC)
(envelope-from peterjeremy@optushome.com.au)
Received: from mail16.syd.optusnet.com.au (mail16.syd.optusnet.com.au
[211.29.132.197])
by mx1.freebsd.org (Postfix) with ESMTP id C73DE8FC12
for <freebsd-stable@freebsd.org>; Tue, 18 Nov 2008 08:11:59 +0000 (UTC)
(envelope-from peterjeremy@optushome.com.au)
Received: from server.vk2pj.dyndns.org
(c122-106-215-175.belrs3.nsw.optusnet.com.au [122.106.215.175])
by mail16.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id
mAI8Bsal013581
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
Tue, 18 Nov 2008 19:11:56 +1100
X-Bogosity: Ham, spamicity=0.000000
Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1])
by server.vk2pj.dyndns.org (8.14.3/8.14.3) with ESMTP id mAI8BrvF061838;
Tue, 18 Nov 2008 19:11:53 +1100 (EST)
(envelope-from peter@server.vk2pj.dyndns.org)
Received: (from peter@localhost)
by server.vk2pj.dyndns.org (8.14.3/8.14.3/Submit) id mAI8Br4x061834;
Tue, 18 Nov 2008 19:11:53 +1100 (EST) (envelope-from peter)
Date: Tue, 18 Nov 2008 19:11:53 +1100
From: Peter Jeremy <peterjeremy@optushome.com.au>
To: sthaug@nethelp.no
Message-ID: <20081118081153.GQ51761@server.vk2pj.dyndns.org>
References: <89DE4FDF67DC40AE88477897DF4CD0E7@multiplay.co.uk>
<188BDB85-46C0-41AA-B270-DA03BBD4CFF2@netconsonance.com>
<5FD58BCD6B4C409DA7E7C30150FB10C7@multiplay.co.uk>
<20081117.233619.85395429.sthaug@nethelp.no>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="sT9gWZPUZYhvPS56"
Content-Disposition: inline
In-Reply-To: <20081117.233619.85395429.sthaug@nethelp.no>
X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: freebsd-stable@freebsd.org
Subject: Re: Possible regression in ifconfig under7.0 - removes
validdefault route
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Nov 2008 08:12:00 -0000
--sT9gWZPUZYhvPS56
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On 2008-Nov-17 23:36:19 +0100, sthaug@nethelp.no wrote:
>Oh yeah, since we're in wishful thinking mode, I want interface
>descriptions too...
Have you looked at the 'name' and 'group' keywords in ifconfig(8)?
If this isn't what you want, please expand on your wish.
--=20
Peter Jeremy
Please excuse any delays as the result of my ISP's inability to implement
an MTA that is either RFC2821-compliant or matches their claimed behaviour.
--sT9gWZPUZYhvPS56
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (FreeBSD)
iEYEARECAAYFAkkieMkACgkQ/opHv/APuIdsrQCfQwaS8YHjEblAltPCPUiIKsrc
p08AmwekMjo6/bqw+PsylDzjzvmyY9G+
=AdCr
-----END PGP SIGNATURE-----
--sT9gWZPUZYhvPS56--
From owner-freebsd-stable@FreeBSD.ORG Tue Nov 18 09:20:52 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 08E4E106568B;
Tue, 18 Nov 2008 09:20:51 +0000 (UTC)
(envelope-from quakelee@geekcn.org)
Received: from tarsier.delphij.net (delphij-pt.tunnel.tserv2.fmt.ipv6.he.net
[IPv6:2001:470:1f03:2c9::2])
by mx1.freebsd.org (Postfix) with ESMTP id A76FB8FC0C;
Tue, 18 Nov 2008 09:20:50 +0000 (UTC)
(envelope-from quakelee@geekcn.org)
Received: from tarsier.geekcn.org (tarsier.geekcn.org [211.166.10.233])
(using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits))
(No client certificate requested)
by tarsier.delphij.net (Postfix) with ESMTPS id CA3A12844E;
Tue, 18 Nov 2008 17:20:49 +0800 (CST)
Received: from localhost (tarsier.geekcn.org [211.166.10.233])
by tarsier.geekcn.org (Postfix) with ESMTP id 82555EC68C9;
Tue, 18 Nov 2008 17:20:49 +0800 (CST)
X-Virus-Scanned: amavisd-new at geekcn.org
Received: from tarsier.geekcn.org ([211.166.10.233])
by localhost (mail.geekcn.org [211.166.10.233]) (amavisd-new,
port 10024)
with ESMTP id Zk37FIA3ashY; Tue, 18 Nov 2008 17:20:44 +0800 (CST)
Received: from qld630 (unknown [222.131.116.4])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(No client certificate requested)
by tarsier.geekcn.org (Postfix) with ESMTPSA id 20C04EC68C6;
Tue, 18 Nov 2008 17:20:44 +0800 (CST)
DomainKey-Signature: a=rsa-sha1; s=default; d=geekcn.org; c=nofws; q=dns;
h=date:to:subject:from:organization:cc:content-type:
mime-version:references:content-transfer-encoding:message-id:in-reply-to:user-agent;
b=NACDwVvDzZm7E8sfCXFq2rUcHprEa0JR6x2gPQ/pAd5VoZ4a3HX+0B1VNd3vX5EG8
vsxIFBjMo7sgaDauNUY9A==
Date: Tue, 18 Nov 2008 17:20:43 +0800
To: "Pawel Jakub Dawidek" <pjd@freebsd.org>, d@delphij.net
From: "Chao Shin" <quakelee@geekcn.org>
Organization: GeekCN
Content-Type: text/plain; format=flowed; delsp=yes; charset=utf-8
MIME-Version: 1.0
References: <491CE71F.2020208@delphij.net> <491CE835.4050504@delphij.net>
<20081117155835.GC2101@garage.freebsd.pl>
Content-Transfer-Encoding: 8bit
Message-ID: <op.uks5krn2hnq548@qld630>
In-Reply-To: <20081117155835.GC2101@garage.freebsd.pl>
User-Agent: Opera Mail/9.62 (Win32)
Cc: FreeBSD Stable <freebsd-stable@freebsd.org>
Subject: Re: ZFS crashes on heavy threaded environment
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Nov 2008 09:20:52 -0000
On Mon, 17 Nov 2008 23:58:35 +0800，Pawel Jakub Dawidek <pjd@freebsd.org>
wrote:
> On Thu, Nov 13, 2008 at 06:53:41PM -0800, Xin LI wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Xin LI wrote:
>> > Hi, Pawel,
>> >
>> > We can still reproduce the ZFS crash (threading+heavy I/O load) on a
>> > fresh 7.1-STABLE build, in a few minutes:
>> >
>> > /usr/local/bin/iozone -M -e -+u -T -t 128 -S 4096 -L 64 -r 4k -s 30g
>> -i
>> > 0 -i 1 -i 2 -i 8 -+p 70 -C
>> >
>> > I have included a backtrace output from my colleague who has his hands
>> > on the test environment. Should there is more information necessary
>> > please let us know and we wish to provide help on this.
>>
>> Further datapoint. The system used to run with untuned loader.conf, and
>> my colleague just reported that with the following loader.conf, the
>> problem can be triggered sooner:
>>
>> vm.kmem_size_max=838860800
>> vm.kmem_size_scale="2"
>>
>> The system is running FreeBSD/amd64 7.1-PRERELEASE equipped with 8GB of
>> RAM with GENERIC kernel.
>
> With new ZFS I get:
>
> Memory allocation failed:: Cannot allocate memory
>
> Is this expected?
>
At first, Congratulations to you, thanks to your works, well done!
I used this command on a FreeBSD 7.1-PRERELEASE amd64 box with 8GB mem,
isn't got output like that, but kernel panic.
Maybe you should lower the threads and file size, for example:
/usr/local/bin/iozone -M -e -+u -T -t 64 -S 4096 -L 64 -r 4k -s 2g -i 0 -i
1 -i 2 -i 8 -+p 70 -C
Actually, we had used this command to test a 8-current with zfs v12 patch
on July, there is no more panic. So we hope
zfs v13 can MFC as soon as possible, because we really need it now.
--
The Power to Serve
From owner-freebsd-stable@FreeBSD.ORG Tue Nov 18 09:34:27 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id B9F7F106564A
for <freebsd-stable@freebsd.org>; Tue, 18 Nov 2008 09:34:27 +0000 (UTC)
(envelope-from sthaug@nethelp.no)
Received: from bizet.nethelp.no (bizet.nethelp.no [195.1.209.33])
by mx1.freebsd.org (Postfix) with SMTP id 031E08FC1A
for <freebsd-stable@freebsd.org>; Tue, 18 Nov 2008 09:34:26 +0000 (UTC)
(envelope-from sthaug@nethelp.no)
Received: (qmail 44310 invoked from network); 18 Nov 2008 09:34:24 -0000
Received: from bizet.nethelp.no (HELO localhost) (195.1.209.33)
by bizet.nethelp.no with SMTP; 18 Nov 2008 09:34:24 -0000
Date: Tue, 18 Nov 2008 10:34:24 +0100 (CET)
Message-Id: <20081118.103424.74710091.sthaug@nethelp.no>
To: peterjeremy@optushome.com.au
From: sthaug@nethelp.no
In-Reply-To: <20081118081153.GQ51761@server.vk2pj.dyndns.org>
References: <5FD58BCD6B4C409DA7E7C30150FB10C7@multiplay.co.uk>
<20081117.233619.85395429.sthaug@nethelp.no>
<20081118081153.GQ51761@server.vk2pj.dyndns.org>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: freebsd-stable@freebsd.org
Subject: Re: Possible regression in ifconfig under7.0 - removes
validdefault route
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Nov 2008 09:34:27 -0000
> >Oh yeah, since we're in wishful thinking mode, I want interface
> >descriptions too...
>
> Have you looked at the 'name' and 'group' keywords in ifconfig(8)?
> If this isn't what you want, please expand on your wish.
It is not what I want.
On routers, switches and lots of other boxes from most vendors you can
associate a description string with each interface - where interface
can be a physical port, or for instance a VLAN based interface. This
description string is useful to document things like
- what is the box at the other end of the cable connected to this port
- what is the port at the other end of the cable connected to this port
- what is the circuit id for the circuit this port is connected to
- what is this port used for
etc. Typical example, from one of our switches (Cisco syntax):
interface GigabitEthernet0/12
description TO: fs1.td ID: BTN-11510092 TXT: gi1/0/7 EoSDH 50 Mbps
switchport trunk allowed vlan 123,770,1024,1500,1504,1528,1536
showing the first three points I mentioned above.
Such a description string is can normally be retrieved using SNMP.
Steinar Haug, Nethelp consulting, sthaug@nethelp.no
From owner-freebsd-stable@FreeBSD.ORG Tue Nov 18 10:12:54 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 6F25C1065675;
Tue, 18 Nov 2008 10:12:54 +0000 (UTC)
(envelope-from prvs=1208040d95=killing@multiplay.co.uk)
Received: from mail1.multiplay.co.uk (core6.multiplay.co.uk [85.236.96.23])
by mx1.freebsd.org (Postfix) with ESMTP id C5F6E8FC14;
Tue, 18 Nov 2008 10:12:53 +0000 (UTC)
(envelope-from prvs=1208040d95=killing@multiplay.co.uk)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=multiplay.co.uk;
s=Multiplay; t=1227001978; x=1227606778; q=dns/txt; h=Received:
Message-ID:From:To:Cc:References:Subject:Date:MIME-Version:
Content-Type:Content-Transfer-Encoding; bh=kZk4iecLGZaSNY0Z8Dy3Y
XLOj5AopBHm7jdZaWLd5V4=; b=hOOqCnqbRN/RtYUYoT+vKhUpiSrrViVhVMEKk
WHU1pFjSevbgiAg/eTeJHQCw3akkOlHj1+g7clPDIQnDsVhdHu+qtddNAwCqh4nB
YEfVK4OE9TzyLhMGrgRgSYHbNUnAcIFq9gUHQ080QQKKW4GJ2a0HcdYdzgzPl00F
1TSVTw=
X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on
mail1.multiplay.co.uk
X-Spam-Level:
X-Spam-Status: No, score=-14.7 required=6.0 tests=BAYES_00, FORGED_MUA_OUTLOOK,
USER_IN_WHITELIST,USER_IN_WHITELIST_TO autolearn=ham version=3.1.8
Received: from r2d2 by mail1.multiplay.co.uk (MDaemon PRO v9.6.6)
with ESMTP id md50006559279.msg; Tue, 18 Nov 2008 09:52:57 +0000
X-Authenticated-Sender: Killing@multiplay.co.uk
X-MDRemoteIP: 213.123.247.160
X-Return-Path: prvs=1208040d95=killing@multiplay.co.uk
X-Envelope-From: killing@multiplay.co.uk
Message-ID: <579A727AE73F4E4780156C9C43258677@multiplay.co.uk>
From: "Steven Hartland" <killing@multiplay.co.uk>
To: "Jeremy Chadwick" <koitsu@FreeBSD.org>
References: <89DE4FDF67DC40AE88477897DF4CD0E7@multiplay.co.uk>
<20081117200250.GA38619@icarus.home.lan>
<4E2AB11167C143D6948D2BEEDBCA8512@multiplay.co.uk>
<20081117211153.GA39851@icarus.home.lan>
Date: Tue, 18 Nov 2008 09:52:51 -0000
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5512
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Spam-Processed: mail1.multiplay.co.uk, Tue, 18 Nov 2008 09:52:57 +0000
X-MDAV-Processed: mail1.multiplay.co.uk, Tue, 18 Nov 2008 09:52:58 +0000
Cc: freebsd-stable@freebsd.org
Subject: Re: Possible regression in ifconfig under7.0 - removesvaliddefault
route
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Nov 2008 10:12:54 -0000
This has now been raised as PR:
http://www.freebsd.org/cgi/query-pr.cgi?pr=128954
Regards
Steve
----- Original Message -----
From: "Jeremy Chadwick" <koitsu@FreeBSD.org>
> On Mon, Nov 17, 2008 at 08:45:43PM -0000, Steven Hartland wrote:
>> ----- Original Message ----- From: "Jeremy Chadwick" <koitsu@FreeBSD.org>
>>> I can try to reproduce this if you'd like, on a VMware session.
>>>
>>> One case where the default route could be (I haven't checked) removed:
>>> some NIC drivers in the past, when changing the "primary IP" (first IP
>>> shown in ifconfig for an interface), would actually bring down the
>>> entire interface (e.g. ifconfig XXX down) then back up again a second or
>>> two later. dmesg on your machine would be able to confirm whether or
>>> not this is happening.
>>
>>
>> Thanks Jeremy, no such down up here is show so I believe this is not
>> the case, here anyway. The interface in question was em0 details:-
>> em0: <Intel(R) PRO/1000 Network Connection Version - 6.7.3> port
>> 0xd400-0xd43f mem 0xfea60000-0xfea7ffff,0xfea40000-0xfea5ffff irq 23 at
>> device 8.0 on pci1
>> em0: Ethernet address: 00:30:48:71:b6:b7
>> em0: [FILTER]
>>
>> FreeBSD test 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb 24 19:59:52 UTC
>> 2008 root@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386
>>
>> Would be most interested in the results of you vm test if you would
>> be so kind.
>
> No problem. I'm testing on VMware Workstation 6.5.0 build 118116,
> RELENG_7 amd64 (world/kernel dated 2008/10/23).
>
>
> rc.conf (showing DHCP is not in use):
>
> ifconfig_em0="inet 192.168.1.190 netmask 255.255.255.0"
> defaultrouter="192.168.1.1"
>
> em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
> options=9b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM>
> ether 00:0c:29:0a:c9:37
> inet 192.168.1.190 netmask 0xffffff00 broadcast 192.168.1.255
> media: Ethernet autoselect (1000baseTX <full-duplex>)
> status: active
>
> Destination Gateway Flags Refs Use Netif Expire
> default 192.168.1.1 UGS 0 0 em0
> 127.0.0.1 127.0.0.1 UH 0 0 lo0
> 192.168.1.0/24 link#1 UC 0 0 em0
> 192.168.1.1 link#1 UHLW 2 0 em0
> 192.168.1.51 00:30:48:d2:22:d0 UHLW 2 50 em0 1107
>
>
> Command executed: ifconfig em0 inet 10.0.0.1 netmask 255.0.0.0
> Aftermath:
>
> em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
> options=9b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM>
> ether 00:0c:29:0a:c9:37
> inet 10.0.0.1 netmask 0xff000000 broadcast 10.255.255.255
> media: Ethernet autoselect (1000baseTX <full-duplex>)
> status: active
>
> Destination Gateway Flags Refs Use Netif Expire
> 10.0.0.0/8 link#1 UC 0 0 em0
> 127.0.0.1 127.0.0.1 UH 0 0 lo0
>
>
> Command executed: route add default 10.0.0.128
> Aftermath:
>
> Destination Gateway Flags Refs Use Netif Expire
> default 10.0.0.128 UGS 0 0 em0
> 10.0.0.0/8 link#1 UC 0 0 em0
> 10.0.0.128 link#1 UHLW 2 0 em0
> 127.0.0.1 127.0.0.1 UH 0 0 lo0
>
> Command executed: ifconfig em0 inet 10.10.10.10 netmask 255.0.0.0
> Aftermath:
>
> em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
> options=9b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM>
> ether 00:0c:29:0a:c9:37
> inet 10.10.10.10 netmask 0xff000000 broadcast 10.255.255.255
> media: Ethernet autoselect (1000baseTX <full-duplex>)
> status: active
>
> Destination Gateway Flags Refs Use Netif Expire
> 10.0.0.0/8 link#1 UC 0 0 em0
> 127.0.0.1 127.0.0.1 UH 0 0 lo0
>
>
> Summary: confirmed. Above two tests show that even if changing the IP
> to something else within the same network block, the default route is
> removed and not put back.
>
> This is pretty major, if you ask me.
================================================
This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it.
In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337
or return the E.mail to postmaster@multiplay.co.uk.
From owner-freebsd-stable@FreeBSD.ORG Tue Nov 18 11:52:25 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 85B7E106568E
for <freebsd-stable@freebsd.org>; Tue, 18 Nov 2008 11:52:25 +0000 (UTC)
(envelope-from cpghost@cordula.ws)
Received: from fw.farid-hajji.net (fw.farid-hajji.net [213.146.115.42])
by mx1.freebsd.org (Postfix) with ESMTP id 195678FC24
for <freebsd-stable@freebsd.org>; Tue, 18 Nov 2008 11:52:25 +0000 (UTC)
(envelope-from cpghost@cordula.ws)
Received: from phenom.cordula.ws (phenom [192.168.254.60])
by fw.farid-hajji.net (Postfix) with ESMTP id F22E83616A;
Tue, 18 Nov 2008 12:33:25 +0100 (CET)
Date: Tue, 18 Nov 2008 12:38:11 +0100
From: cpghost <cpghost@cordula.ws>
To: freebsd-stable@freebsd.org
Message-ID: <20081118113811.GB1136@phenom.cordula.ws>
References: <5FD58BCD6B4C409DA7E7C30150FB10C7@multiplay.co.uk>
<20081117.233619.85395429.sthaug@nethelp.no>
<20081118081153.GQ51761@server.vk2pj.dyndns.org>
<20081118.103424.74710091.sthaug@nethelp.no>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20081118.103424.74710091.sthaug@nethelp.no>
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: sthaug@nethelp.no
Subject: ifconfig(8) interface description field
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Nov 2008 11:52:25 -0000
On Tue, Nov 18, 2008 at 10:34:24AM +0100, sthaug@nethelp.no wrote:
> > >Oh yeah, since we're in wishful thinking mode, I want interface
> > >descriptions too...
> >
> > Have you looked at the 'name' and 'group' keywords in ifconfig(8)?
> > If this isn't what you want, please expand on your wish.
>
> It is not what I want.
>
> On routers, switches and lots of other boxes from most vendors you can
> associate a description string with each interface - where interface
> can be a physical port, or for instance a VLAN based interface. This
> description string is useful to document things like
>
> - what is the box at the other end of the cable connected to this port
> - what is the port at the other end of the cable connected to this port
> - what is the circuit id for the circuit this port is connected to
> - what is this port used for
>
> etc. Typical example, from one of our switches (Cisco syntax):
>
> interface GigabitEthernet0/12
> description TO: fs1.td ID: BTN-11510092 TXT: gi1/0/7 EoSDH 50 Mbps
> switchport trunk allowed vlan 123,770,1024,1500,1504,1528,1536
>
> showing the first three points I mentioned above.
>
> Such a description string is can normally be retrieved using SNMP.
Yes, that's a very useful addition. I'm administering a lot of Cisco
boxes, and this desc field has been extremely useful over the years.
Maybe an ifi_desc field could be added to:
/usr/src/sys/net/if.h:struct if_data
and some glue so that ifconfig(8) can read and write to it?
How long should this field be at most?
> Steinar Haug, Nethelp consulting, sthaug@nethelp.no
-cpghost.
--
Cordula's Web. http://www.cordula.ws/
From owner-freebsd-stable@FreeBSD.ORG Tue Nov 18 12:10:07 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 97CC01065673
for <freebsd-stable@freebsd.org>; Tue, 18 Nov 2008 12:10:07 +0000 (UTC)
(envelope-from bzeeb-lists@lists.zabbadoz.net)
Received: from mail.cksoft.de (mail.cksoft.de [62.111.66.27])
by mx1.freebsd.org (Postfix) with ESMTP id 4F8E28FC23
for <freebsd-stable@freebsd.org>; Tue, 18 Nov 2008 12:10:07 +0000 (UTC)
(envelope-from bzeeb-lists@lists.zabbadoz.net)
Received: from localhost (amavis.str.cksoft.de [192.168.74.71])
by mail.cksoft.de (Postfix) with ESMTP id 5973741C64A;
Tue, 18 Nov 2008 13:10:06 +0100 (CET)
X-Virus-Scanned: amavisd-new at cksoft.de
Received: from mail.cksoft.de ([62.111.66.27])
by localhost (amavis.str.cksoft.de [192.168.74.71]) (amavisd-new,
port 10024)
with ESMTP id LnAOqYv9RjQp; Tue, 18 Nov 2008 13:10:05 +0100 (CET)
Received: by mail.cksoft.de (Postfix, from userid 66)
id AF04D41C5EB; Tue, 18 Nov 2008 13:10:05 +0100 (CET)
Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net
[10.111.66.10])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(No client certificate requested)
by mail.int.zabbadoz.net (Postfix) with ESMTP id 55341444888;
Tue, 18 Nov 2008 12:07:32 +0000 (UTC)
Date: Tue, 18 Nov 2008 12:07:32 +0000 (UTC)
From: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>
X-X-Sender: bz@maildrop.int.zabbadoz.net
To: cpghost <cpghost@cordula.ws>
In-Reply-To: <20081118113811.GB1136@phenom.cordula.ws>
Message-ID: <20081118120244.U61259@maildrop.int.zabbadoz.net>
References: <5FD58BCD6B4C409DA7E7C30150FB10C7@multiplay.co.uk>
<20081117.233619.85395429.sthaug@nethelp.no>
<20081118081153.GQ51761@server.vk2pj.dyndns.org>
<20081118.103424.74710091.sthaug@nethelp.no>
<20081118113811.GB1136@phenom.cordula.ws>
X-OpenPGP-Key: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: freebsd-stable@freebsd.org, sthaug@nethelp.no
Subject: Re: ifconfig(8) interface description field
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Nov 2008 12:10:07 -0000
On Tue, 18 Nov 2008, cpghost wrote:
> On Tue, Nov 18, 2008 at 10:34:24AM +0100, sthaug@nethelp.no wrote:
>>>> Oh yeah, since we're in wishful thinking mode, I want interface
>>>> descriptions too...
>>>
>>> Have you looked at the 'name' and 'group' keywords in ifconfig(8)?
>>> If this isn't what you want, please expand on your wish.
>>
>> It is not what I want.
>>
>> On routers, switches and lots of other boxes from most vendors you can
>> associate a description string with each interface - where interface
>> can be a physical port, or for instance a VLAN based interface. This
>> description string is useful to document things like
>>
>> - what is the box at the other end of the cable connected to this port
>> - what is the port at the other end of the cable connected to this port
>> - what is the circuit id for the circuit this port is connected to
>> - what is this port used for
>>
>> etc. Typical example, from one of our switches (Cisco syntax):
>>
>> interface GigabitEthernet0/12
>> description TO: fs1.td ID: BTN-11510092 TXT: gi1/0/7 EoSDH 50 Mbps
>> switchport trunk allowed vlan 123,770,1024,1500,1504,1528,1536
>>
>> showing the first three points I mentioned above.
>>
>> Such a description string is can normally be retrieved using SNMP.
>
> Yes, that's a very useful addition. I'm administering a lot of Cisco
> boxes, and this desc field has been extremely useful over the years.
>
> Maybe an ifi_desc field could be added to:
>
> /usr/src/sys/net/if.h:struct if_data
>
> and some glue so that ifconfig(8) can read and write to it?
> How long should this field be at most?
This is nothing the really belongs in the kernel.
Add an "interface" to set/get the information per interface (index,
name, ...) and store the actual data in a file maybe.
Make the format extensible to store other meta data that
people may want to think along with it in the future.
After all you want the information to be peristent over a reboot so
you have to write it out somehow anyway.
Just my 0.02CAD
/bz
--
Bjoern A. Zeeb Stop bit received. Insert coin for new game.
From owner-freebsd-stable@FreeBSD.ORG Tue Nov 18 12:48:15 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 6865D1065670
for <freebsd-stable@FreeBSD.org>; Tue, 18 Nov 2008 12:48:15 +0000 (UTC)
(envelope-from gavin@FreeBSD.org)
Received: from mail-gw2.york.ac.uk (mail-gw2.york.ac.uk [144.32.128.247])
by mx1.freebsd.org (Postfix) with ESMTP id DC3F98FC1B
for <freebsd-stable@FreeBSD.org>; Tue, 18 Nov 2008 12:48:14 +0000 (UTC)
(envelope-from gavin@FreeBSD.org)
Received: from mail-gw7.york.ac.uk (mail-gw7.york.ac.uk [144.32.129.30])
by mail-gw2.york.ac.uk (8.13.6/8.13.6) with ESMTP id mAICm7Vl013063;
Tue, 18 Nov 2008 12:48:07 GMT
Received: from buffy-128.york.ac.uk ([144.32.128.160] helo=buffy.york.ac.uk)
by mail-gw7.york.ac.uk with esmtps (TLSv1:AES256-SHA:256) (Exim 4.68)
(envelope-from <gavin@FreeBSD.org>)
id 1L2Pzz-00074B-E0; Tue, 18 Nov 2008 12:48:07 +0000
Received: from buffy.york.ac.uk (localhost [127.0.0.1])
by buffy.york.ac.uk (8.14.2/8.14.2) with ESMTP id mAICm7eG024867;
Tue, 18 Nov 2008 12:48:07 GMT (envelope-from gavin@FreeBSD.org)
Received: (from ga9@localhost)
by buffy.york.ac.uk (8.14.2/8.14.2/Submit) id mAICm6GA024866;
Tue, 18 Nov 2008 12:48:06 GMT (envelope-from gavin@FreeBSD.org)
X-Authentication-Warning: buffy.york.ac.uk: ga9 set sender to
gavin@FreeBSD.org using -f
From: Gavin Atkinson <gavin@FreeBSD.org>
To: cpghost <cpghost@cordula.ws>
In-Reply-To: <20081118113811.GB1136@phenom.cordula.ws>
References: <5FD58BCD6B4C409DA7E7C30150FB10C7@multiplay.co.uk>
<20081117.233619.85395429.sthaug@nethelp.no>
<20081118081153.GQ51761@server.vk2pj.dyndns.org>
<20081118.103424.74710091.sthaug@nethelp.no>
<20081118113811.GB1136@phenom.cordula.ws>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Date: Tue, 18 Nov 2008 12:48:06 +0000
Message-Id: <1227012486.23755.20.camel@buffy.york.ac.uk>
Mime-Version: 1.0
X-Mailer: Evolution 2.22.2 FreeBSD GNOME Team Port
X-York-MailScanner: Found to be clean
X-York-MailScanner-From: gavin@freebsd.org
Cc: freebsd-stable@FreeBSD.org, sthaug@nethelp.no
Subject: Re: ifconfig(8) interface description field
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Nov 2008 12:48:15 -0000
On Tue, 2008-11-18 at 12:38 +0100, cpghost wrote:
> On Tue, Nov 18, 2008 at 10:34:24AM +0100, sthaug@nethelp.no wrote:
> > > >Oh yeah, since we're in wishful thinking mode, I want interface
> > > >descriptions too...
> > >
> > > Have you looked at the 'name' and 'group' keywords in ifconfig(8)?
> > > If this isn't what you want, please expand on your wish.
> >
> > It is not what I want.
> >
> > On routers, switches and lots of other boxes from most vendors you can
> > associate a description string with each interface - where interface
> > can be a physical port, or for instance a VLAN based interface. This
> > description string is useful to document things like
> >
> > - what is the box at the other end of the cable connected to this port
> > - what is the port at the other end of the cable connected to this port
> > - what is the circuit id for the circuit this port is connected to
> > - what is this port used for
> >
> > etc. Typical example, from one of our switches (Cisco syntax):
> >
> > interface GigabitEthernet0/12
> > description TO: fs1.td ID: BTN-11510092 TXT: gi1/0/7 EoSDH 50 Mbps
> > switchport trunk allowed vlan 123,770,1024,1500,1504,1528,1536
> >
> > showing the first three points I mentioned above.
> >
> > Such a description string is can normally be retrieved using SNMP.
>
> Yes, that's a very useful addition. I'm administering a lot of Cisco
> boxes, and this desc field has been extremely useful over the years.
>
> Maybe an ifi_desc field could be added to:
>
> /usr/src/sys/net/if.h:struct if_data
>
> and some glue so that ifconfig(8) can read and write to it?
> How long should this field be at most?
Patches already existfor one method of implementing this, see PR
kern/83622.
Gavin
From owner-freebsd-stable@FreeBSD.ORG Tue Nov 18 13:08:22 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 887551065672
for <freebsd-stable@FreeBSD.org>; Tue, 18 Nov 2008 13:08:22 +0000 (UTC)
(envelope-from cpghost@cordula.ws)
Received: from fw.farid-hajji.net (fw.farid-hajji.net [213.146.115.42])
by mx1.freebsd.org (Postfix) with ESMTP id E625E8FC08
for <freebsd-stable@FreeBSD.org>; Tue, 18 Nov 2008 13:08:21 +0000 (UTC)
(envelope-from cpghost@cordula.ws)
Received: from phenom.cordula.ws (phenom [192.168.254.60])
by fw.farid-hajji.net (Postfix) with ESMTP id E389535F35;
Tue, 18 Nov 2008 14:05:09 +0100 (CET)
Date: Tue, 18 Nov 2008 14:09:55 +0100
From: cpghost <cpghost@cordula.ws>
To: Gavin Atkinson <gavin@FreeBSD.org>
Message-ID: <20081118130955.GA958@phenom.cordula.ws>
References: <5FD58BCD6B4C409DA7E7C30150FB10C7@multiplay.co.uk>
<20081117.233619.85395429.sthaug@nethelp.no>
<20081118081153.GQ51761@server.vk2pj.dyndns.org>
<20081118.103424.74710091.sthaug@nethelp.no>
<20081118113811.GB1136@phenom.cordula.ws>
<1227012486.23755.20.camel@buffy.york.ac.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1227012486.23755.20.camel@buffy.york.ac.uk>
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: freebsd-stable@FreeBSD.org, sthaug@nethelp.no
Subject: Re: ifconfig(8) interface description field
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Nov 2008 13:08:22 -0000
On Tue, Nov 18, 2008 at 12:48:06PM +0000, Gavin Atkinson wrote:
> On Tue, 2008-11-18 at 12:38 +0100, cpghost wrote:
> > On Tue, Nov 18, 2008 at 10:34:24AM +0100, sthaug@nethelp.no wrote:
> > > > >Oh yeah, since we're in wishful thinking mode, I want interface
> > > > >descriptions too...
> > > >
> > > > Have you looked at the 'name' and 'group' keywords in ifconfig(8)?
> > > > If this isn't what you want, please expand on your wish.
> > >
> > > It is not what I want.
> > >
> > > On routers, switches and lots of other boxes from most vendors you can
> > > associate a description string with each interface - where interface
> > > can be a physical port, or for instance a VLAN based interface. This
> > > description string is useful to document things like
> > >
> > > - what is the box at the other end of the cable connected to this port
> > > - what is the port at the other end of the cable connected to this port
> > > - what is the circuit id for the circuit this port is connected to
> > > - what is this port used for
> > >
> > > etc. Typical example, from one of our switches (Cisco syntax):
> > >
> > > interface GigabitEthernet0/12
> > > description TO: fs1.td ID: BTN-11510092 TXT: gi1/0/7 EoSDH 50 Mbps
> > > switchport trunk allowed vlan 123,770,1024,1500,1504,1528,1536
> > >
> > > showing the first three points I mentioned above.
> > >
> > > Such a description string is can normally be retrieved using SNMP.
> >
> > Yes, that's a very useful addition. I'm administering a lot of Cisco
> > boxes, and this desc field has been extremely useful over the years.
> >
> > Maybe an ifi_desc field could be added to:
> >
> > /usr/src/sys/net/if.h:struct if_data
> >
> > and some glue so that ifconfig(8) can read and write to it?
> > How long should this field be at most?
>
> Patches already existfor one method of implementing this, see PR
> kern/83622.
>
> Gavin
Ah yes, that was exactly what I was thinking of!
Thank you for the hint!
-cpghost.
--
Cordula's Web. http://www.cordula.ws/
From owner-freebsd-stable@FreeBSD.ORG Tue Nov 18 13:21:31 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id CA98E1065673
for <freebsd-stable@freebsd.org>; Tue, 18 Nov 2008 13:21:31 +0000 (UTC)
(envelope-from cpghost@cordula.ws)
Received: from fw.farid-hajji.net (fw.farid-hajji.net [213.146.115.42])
by mx1.freebsd.org (Postfix) with ESMTP id 01D4E8FC17
for <freebsd-stable@freebsd.org>; Tue, 18 Nov 2008 13:21:30 +0000 (UTC)
(envelope-from cpghost@cordula.ws)
Received: from phenom.cordula.ws (phenom [192.168.254.60])
by fw.farid-hajji.net (Postfix) with ESMTP id 02F3D36171;
Tue, 18 Nov 2008 14:18:19 +0100 (CET)
Date: Tue, 18 Nov 2008 14:23:05 +0100
From: cpghost <cpghost@cordula.ws>
To: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>
Message-ID: <20081118132305.GB958@phenom.cordula.ws>
References: <5FD58BCD6B4C409DA7E7C30150FB10C7@multiplay.co.uk>
<20081117.233619.85395429.sthaug@nethelp.no>
<20081118081153.GQ51761@server.vk2pj.dyndns.org>
<20081118.103424.74710091.sthaug@nethelp.no>
<20081118113811.GB1136@phenom.cordula.ws>
<20081118120244.U61259@maildrop.int.zabbadoz.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20081118120244.U61259@maildrop.int.zabbadoz.net>
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: freebsd-stable@freebsd.org, sthaug@nethelp.no
Subject: Re: ifconfig(8) interface description field
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Nov 2008 13:21:32 -0000
On Tue, Nov 18, 2008 at 12:07:32PM +0000, Bjoern A. Zeeb wrote:
> On Tue, 18 Nov 2008, cpghost wrote:
>
> > On Tue, Nov 18, 2008 at 10:34:24AM +0100, sthaug@nethelp.no wrote:
> >>>> Oh yeah, since we're in wishful thinking mode, I want interface
> >>>> descriptions too...
> >>>
> >>> Have you looked at the 'name' and 'group' keywords in ifconfig(8)?
> >>> If this isn't what you want, please expand on your wish.
> >>
> >> It is not what I want.
> >>
> >> On routers, switches and lots of other boxes from most vendors you can
> >> associate a description string with each interface - where interface
> >> can be a physical port, or for instance a VLAN based interface. This
> >> description string is useful to document things like
> >>
> >> - what is the box at the other end of the cable connected to this port
> >> - what is the port at the other end of the cable connected to this port
> >> - what is the circuit id for the circuit this port is connected to
> >> - what is this port used for
> >>
> >> etc. Typical example, from one of our switches (Cisco syntax):
> >>
> >> interface GigabitEthernet0/12
> >> description TO: fs1.td ID: BTN-11510092 TXT: gi1/0/7 EoSDH 50 Mbps
> >> switchport trunk allowed vlan 123,770,1024,1500,1504,1528,1536
> >>
> >> showing the first three points I mentioned above.
> >>
> >> Such a description string is can normally be retrieved using SNMP.
> >
> > Yes, that's a very useful addition. I'm administering a lot of Cisco
> > boxes, and this desc field has been extremely useful over the years.
> >
> > Maybe an ifi_desc field could be added to:
> >
> > /usr/src/sys/net/if.h:struct if_data
> >
> > and some glue so that ifconfig(8) can read and write to it?
> > How long should this field be at most?
>
> This is nothing the really belongs in the kernel.
>
> Add an "interface" to set/get the information per interface (index,
> name, ...) and store the actual data in a file maybe.
> Make the format extensible to store other meta data that
> people may want to think along with it in the future.
>
> After all you want the information to be peristent over a reboot so
> you have to write it out somehow anyway.
Yes, but some interfaces are created on-the-fly, and you never
know in advance which name they'll get (think of tunN, ngN etc...).
If those interfaces are meant to be queried frequently (every few
minutes or so) by an snmpd, wouldn't it be more inefficient to check
an external file than get the meta data from the kernel?
Some network management apps could also decide to use the description
field as a repository for more dynamic data; data that could be queried
by applications running on the hosts. Here too, would'nt it be more
efficient if descr. were in-kernel?
For persistence, an /etc/rc.d script could always set the static
interface descriptions via ifconfig calls any way it likes, including
reading those definitions from a config file. Everything else will
probably be set remotely via the network management software, which
itself has its own persistence store (usually a database).
> Just my 0.02CAD
>
> /bz
>
> --
> Bjoern A. Zeeb Stop bit received. Insert coin for new game.
-cpghost.
--
Cordula's Web. http://www.cordula.ws/
From owner-freebsd-stable@FreeBSD.ORG Tue Nov 18 13:40:56 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 242A8106564A
for <freebsd-stable@freebsd.org>; Tue, 18 Nov 2008 13:40:55 +0000 (UTC)
(envelope-from cpghost@cordula.ws)
Received: from fw.farid-hajji.net (fw.farid-hajji.net [213.146.115.42])
by mx1.freebsd.org (Postfix) with ESMTP id 1871F8FC14
for <freebsd-stable@freebsd.org>; Tue, 18 Nov 2008 13:40:55 +0000 (UTC)
(envelope-from cpghost@cordula.ws)
Received: from phenom.cordula.ws (phenom [192.168.254.60])
by fw.farid-hajji.net (Postfix) with ESMTP id A740A35F35;
Tue, 18 Nov 2008 14:37:43 +0100 (CET)
Date: Tue, 18 Nov 2008 14:42:28 +0100
From: cpghost <cpghost@cordula.ws>
To: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>,
freebsd-stable@freebsd.org, sthaug@nethelp.no
Message-ID: <20081118134228.GC958@phenom.cordula.ws>
References: <5FD58BCD6B4C409DA7E7C30150FB10C7@multiplay.co.uk>
<20081117.233619.85395429.sthaug@nethelp.no>
<20081118081153.GQ51761@server.vk2pj.dyndns.org>
<20081118.103424.74710091.sthaug@nethelp.no>
<20081118113811.GB1136@phenom.cordula.ws>
<20081118120244.U61259@maildrop.int.zabbadoz.net>
<20081118132305.GB958@phenom.cordula.ws>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20081118132305.GB958@phenom.cordula.ws>
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc:
Subject: Re: ifconfig(8) interface description field
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Nov 2008 13:40:56 -0000
On Tue, Nov 18, 2008 at 02:23:05PM +0100, cpghost wrote:
> On Tue, Nov 18, 2008 at 12:07:32PM +0000, Bjoern A. Zeeb wrote:
> > On Tue, 18 Nov 2008, cpghost wrote:
> >
> > > On Tue, Nov 18, 2008 at 10:34:24AM +0100, sthaug@nethelp.no wrote:
> > >>>> Oh yeah, since we're in wishful thinking mode, I want interface
> > >>>> descriptions too...
> > >>>
> > >>> Have you looked at the 'name' and 'group' keywords in ifconfig(8)?
> > >>> If this isn't what you want, please expand on your wish.
> > >>
> > >> It is not what I want.
> > >>
> > >> On routers, switches and lots of other boxes from most vendors you can
> > >> associate a description string with each interface - where interface
> > >> can be a physical port, or for instance a VLAN based interface. This
> > >> description string is useful to document things like
> > >>
> > >> - what is the box at the other end of the cable connected to this port
> > >> - what is the port at the other end of the cable connected to this port
> > >> - what is the circuit id for the circuit this port is connected to
> > >> - what is this port used for
> > >>
> > >> etc. Typical example, from one of our switches (Cisco syntax):
> > >>
> > >> interface GigabitEthernet0/12
> > >> description TO: fs1.td ID: BTN-11510092 TXT: gi1/0/7 EoSDH 50 Mbps
> > >> switchport trunk allowed vlan 123,770,1024,1500,1504,1528,1536
> > >>
> > >> showing the first three points I mentioned above.
> > >>
> > >> Such a description string is can normally be retrieved using SNMP.
> > >
> > > Yes, that's a very useful addition. I'm administering a lot of Cisco
> > > boxes, and this desc field has been extremely useful over the years.
> > >
> > > Maybe an ifi_desc field could be added to:
> > >
> > > /usr/src/sys/net/if.h:struct if_data
> > >
> > > and some glue so that ifconfig(8) can read and write to it?
> > > How long should this field be at most?
> >
> > This is nothing the really belongs in the kernel.
> >
> > Add an "interface" to set/get the information per interface (index,
> > name, ...) and store the actual data in a file maybe.
> > Make the format extensible to store other meta data that
> > people may want to think along with it in the future.
> >
> > After all you want the information to be peristent over a reboot so
> > you have to write it out somehow anyway.
>
> Yes, but some interfaces are created on-the-fly, and you never
> know in advance which name they'll get (think of tunN, ngN etc...).
>
> If those interfaces are meant to be queried frequently (every few
> minutes or so) by an snmpd, wouldn't it be more inefficient to check
> an external file than get the meta data from the kernel?
>
> Some network management apps could also decide to use the description
> field as a repository for more dynamic data; data that could be queried
> by applications running on the hosts. Here too, would'nt it be more
> efficient if descr. were in-kernel?
>
> For persistence, an /etc/rc.d script could always set the static
> interface descriptions via ifconfig calls any way it likes, including
> reading those definitions from a config file. Everything else will
> probably be set remotely via the network management software, which
> itself has its own persistence store (usually a database).
Another reason you want to avoid using a file for this: what about
appliances that run as dedicated routers and boot from a flash-based
read-only filesystem? How would you change the interface description
(remotely or on the console) if you can't write to a file?
> > Bjoern A. Zeeb Stop bit received. Insert coin for new game.
-cpghost.
--
Cordula's Web. http://www.cordula.ws/
From owner-freebsd-stable@FreeBSD.ORG Tue Nov 18 14:00:07 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id B4289106567A
for <freebsd-stable@freebsd.org>; Tue, 18 Nov 2008 14:00:07 +0000 (UTC)
(envelope-from bzeeb-lists@lists.zabbadoz.net)
Received: from mail.cksoft.de (mail.cksoft.de [62.111.66.27])
by mx1.freebsd.org (Postfix) with ESMTP id 575EE8FC1B
for <freebsd-stable@freebsd.org>; Tue, 18 Nov 2008 14:00:07 +0000 (UTC)
(envelope-from bzeeb-lists@lists.zabbadoz.net)
Received: from localhost (amavis.str.cksoft.de [192.168.74.71])
by mail.cksoft.de (Postfix) with ESMTP id 17FCD41C65F;
Tue, 18 Nov 2008 15:00:06 +0100 (CET)
X-Virus-Scanned: amavisd-new at cksoft.de
Received: from mail.cksoft.de ([62.111.66.27])
by localhost (amavis.str.cksoft.de [192.168.74.71]) (amavisd-new,
port 10024)
with ESMTP id JWqjRJ8+Epeh; Tue, 18 Nov 2008 15:00:05 +0100 (CET)
Received: by mail.cksoft.de (Postfix, from userid 66)
id 7D63941C65E; Tue, 18 Nov 2008 15:00:05 +0100 (CET)
Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net
[10.111.66.10])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(No client certificate requested)
by mail.int.zabbadoz.net (Postfix) with ESMTP id 0954D444888;
Tue, 18 Nov 2008 13:58:10 +0000 (UTC)
Date: Tue, 18 Nov 2008 13:58:09 +0000 (UTC)
From: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>
X-X-Sender: bz@maildrop.int.zabbadoz.net
To: cpghost <cpghost@cordula.ws>
In-Reply-To: <20081118134228.GC958@phenom.cordula.ws>
Message-ID: <20081118135622.L61259@maildrop.int.zabbadoz.net>
References: <5FD58BCD6B4C409DA7E7C30150FB10C7@multiplay.co.uk>
<20081117.233619.85395429.sthaug@nethelp.no>
<20081118081153.GQ51761@server.vk2pj.dyndns.org>
<20081118.103424.74710091.sthaug@nethelp.no>
<20081118113811.GB1136@phenom.cordula.ws>
<20081118120244.U61259@maildrop.int.zabbadoz.net>
<20081118132305.GB958@phenom.cordula.ws>
<20081118134228.GC958@phenom.cordula.ws>
X-OpenPGP-Key: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: freebsd-stable@freebsd.org, sthaug@nethelp.no
Subject: Re: ifconfig(8) interface description field
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Nov 2008 14:00:07 -0000
On Tue, 18 Nov 2008, cpghost wrote:
Hi,
> On Tue, Nov 18, 2008 at 02:23:05PM +0100, cpghost wrote:
>> On Tue, Nov 18, 2008 at 12:07:32PM +0000, Bjoern A. Zeeb wrote:
>>> On Tue, 18 Nov 2008, cpghost wrote:
>>>
>>>> On Tue, Nov 18, 2008 at 10:34:24AM +0100, sthaug@nethelp.no wrote:
>>>>>>> Oh yeah, since we're in wishful thinking mode, I want interface
>>>>>>> descriptions too...
>>>>>>
>>>>>> Have you looked at the 'name' and 'group' keywords in ifconfig(8)?
>>>>>> If this isn't what you want, please expand on your wish.
>>>>>
>>>>> It is not what I want.
>>>>>
>>>>> On routers, switches and lots of other boxes from most vendors you can
>>>>> associate a description string with each interface - where interface
>>>>> can be a physical port, or for instance a VLAN based interface. This
>>>>> description string is useful to document things like
>>>>>
>>>>> - what is the box at the other end of the cable connected to this port
>>>>> - what is the port at the other end of the cable connected to this port
>>>>> - what is the circuit id for the circuit this port is connected to
>>>>> - what is this port used for
>>>>>
>>>>> etc. Typical example, from one of our switches (Cisco syntax):
>>>>>
>>>>> interface GigabitEthernet0/12
>>>>> description TO: fs1.td ID: BTN-11510092 TXT: gi1/0/7 EoSDH 50 Mbps
>>>>> switchport trunk allowed vlan 123,770,1024,1500,1504,1528,1536
>>>>>
>>>>> showing the first three points I mentioned above.
>>>>>
>>>>> Such a description string is can normally be retrieved using SNMP.
>>>>
>>>> Yes, that's a very useful addition. I'm administering a lot of Cisco
>>>> boxes, and this desc field has been extremely useful over the years.
>>>>
>>>> Maybe an ifi_desc field could be added to:
>>>>
>>>> /usr/src/sys/net/if.h:struct if_data
>>>>
>>>> and some glue so that ifconfig(8) can read and write to it?
>>>> How long should this field be at most?
>>>
>>> This is nothing the really belongs in the kernel.
>>>
>>> Add an "interface" to set/get the information per interface (index,
>>> name, ...) and store the actual data in a file maybe.
>>> Make the format extensible to store other meta data that
>>> people may want to think along with it in the future.
>>>
>>> After all you want the information to be peristent over a reboot so
>>> you have to write it out somehow anyway.
>>
>> Yes, but some interfaces are created on-the-fly, and you never
>> know in advance which name they'll get (think of tunN, ngN etc...).
>>
>> If those interfaces are meant to be queried frequently (every few
>> minutes or so) by an snmpd, wouldn't it be more inefficient to check
>> an external file than get the meta data from the kernel?
>>
>> Some network management apps could also decide to use the description
>> field as a repository for more dynamic data; data that could be queried
>> by applications running on the hosts. Here too, would'nt it be more
>> efficient if descr. were in-kernel?
>>
>> For persistence, an /etc/rc.d script could always set the static
>> interface descriptions via ifconfig calls any way it likes, including
>> reading those definitions from a config file. Everything else will
>> probably be set remotely via the network management software, which
>> itself has its own persistence store (usually a database).
>
> Another reason you want to avoid using a file for this: what about
> appliances that run as dedicated routers and boot from a flash-based
> read-only filesystem? How would you change the interface description
> (remotely or on the console) if you can't write to a file?
So how would you make it persistent across a reboot if you cannot write
it anywhere?
Regards,
Bjoern
--
Bjoern A. Zeeb Stop bit received. Insert coin for new game.
From owner-freebsd-stable@FreeBSD.ORG Tue Nov 18 15:02:58 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 54A9810656DB
for <freebsd-stable@freebsd.org>; Tue, 18 Nov 2008 15:02:58 +0000 (UTC)
(envelope-from igor.lyapin@gmail.com)
Received: from mail-qy0-f18.google.com (mail-qy0-f18.google.com
[209.85.221.18])
by mx1.freebsd.org (Postfix) with ESMTP id BB8D78FC1F
for <freebsd-stable@freebsd.org>; Tue, 18 Nov 2008 15:02:57 +0000 (UTC)
(envelope-from igor.lyapin@gmail.com)
Received: by qyk11 with SMTP id 11so929066qyk.19
for <freebsd-stable@freebsd.org>; Tue, 18 Nov 2008 07:02:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:message-id:date:from:to
:subject:mime-version:content-type;
bh=VnGJ1m/nSdpZVyRY+Jq0fqrodp01K5TCbQditfDTjDw=;
b=FyFi+GjM8dzlMkavpcYiTYjICT5oteU0DcdpG3P/JGjh4/bmgFtUw2AqaO4O/qrBcM
QD9jxNPrxtaXobzPPEzAoxhyzyNHHWQjwPm8WdOm0aD5OehOxLZurPlnsEC2eI6nEWfV
fiBuxhQwU4kz8QlbYOkdVeTDCY9p7dpE4G4Wg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=message-id:date:from:to:subject:mime-version:content-type;
b=dFTLgWTFNyapc7jQx6ntOQfWSNQepS03Wk1pPNZR+5jxa1jnY+YuE085pj8jiiXLHU
h8rxYQx7TJdyngAb1TDBkzgw2eQEICSQegLNjPhmXQTPnJVfQ9BdyVjezuBYZiCoOmUk
iUGXV0bGJtOtphTIbvmCYhfTFpVdIZKlFwPiI=
Received: by 10.215.66.8 with SMTP id t8mr3886352qak.160.1227019055140;
Tue, 18 Nov 2008 06:37:35 -0800 (PST)
Received: by 10.214.43.11 with HTTP; Tue, 18 Nov 2008 06:37:35 -0800 (PST)
Message-ID: <fd2a4c1f0811180637m6ee44d4fv4cf97d18e322ca5a@mail.gmail.com>
Date: Tue, 18 Nov 2008 17:37:35 +0300
From: "Igor Lyapin" <igor.lyapin@gmail.com>
To: freebsd-stable@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
Subject: High system in %system load .
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Nov 2008 15:02:58 -0000
Hello
Got strange problem with high system "%system load" and very slow user level
programs (apache+php+mysql) behavior
gstat shows 1.5-4% hard disk busy load but system shows about 20-30% load
while user load is max 5%.
vmstat shows from 2 to 35 process in "b" state.
Now use 7.0-RELEASE-p5 , but the same problem was with 7.0-RELEASE.
And have no idea what to do with this.
-------------------------------------------------------------------
#uname -a
FreeBSD i.x00.net 7.0-RELEASE-p5 FreeBSD 7.0-RELEASE-p5 #0: Mon Nov 10
19:49:07 MSK 2008 root@i.x00.net:/usr/obj/usr/src/sys/KERNEL-4BSD amd64
-------------------------------------------------------------------
#top
last pid: 47964; load averages: 1.26, 1.62, 1.75 up
0+19:17:13 17:11:06
287 processes: 10 running, 277 sleeping
CPU states: 2.2% user, 0.0% nice, 28.3% system, 0.2% interrupt, 69.3%
idle
Mem: 1286M Active, 1729M Inact, 478M Wired, 131M Cache, 214M Buf, 302M Free
Swap: 8192M Total, 8192M Free
-------------------------------------------------------------------
#vmstat 5
procs memory page disks faults cpu
r b w avm fre flt re pi po fr sr ad4 ad6 in sy cs us
sy id
1 24 0 4357672 419648 10598 1 0 0 10648 34 0 0 558 25212 9072
6 15 80
1 29 0 4365116 414892 3060 0 0 0 2780 0 0 0 975 12270 11501
3 29 68
1 25 0 4392488 408596 14142 0 0 0 13903 0 0 0 526 16696 10389
6 30 64
-------------------------------------------------------------------
#ps ax | grep " [DLW] "
45585 ?? D 0:04.68 /usr/local/sbin/httpd
45975 ?? D 0:04.92 /usr/local/sbin/httpd
45981 ?? D 0:29.91 /usr/local/sbin/httpd
45995 ?? D 0:23.99 /usr/local/sbin/httpd
46019 ?? D 0:26.76 /usr/local/sbin/httpd
46160 ?? D 0:18.89 /usr/local/sbin/httpd
46287 ?? D 0:19.88 /usr/local/sbin/httpd
46303 ?? D 0:05.14 /usr/local/sbin/httpd
46307 ?? D 0:29.15 /usr/local/sbin/httpd
46398 ?? D 0:09.18 /usr/local/sbin/httpd
46617 ?? D 0:02.00 /usr/local/sbin/httpd
46767 ?? D 0:05.26 /usr/local/sbin/httpd
46771 ?? D 0:02.07 /usr/local/sbin/httpd
46803 ?? D 0:30.51 /usr/local/sbin/httpd
46807 ?? D 0:01.34 /usr/local/sbin/httpd
46889 ?? D 0:01.35 /usr/local/sbin/httpd
47659 ?? D 0:01.54 /usr/local/sbin/httpd
47711 ?? D 0:00.92 /usr/local/sbin/httpd
47849 ?? D 0:01.00 /usr/local/sbin/httpd
47877 ?? D 0:00.40 /usr/local/sbin/httpd
-------------------------------------------------------------------
#dmesg
All buffers synced.
Copyright (c) 1992-2008 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 7.0-RELEASE-p5 #0: Mon Nov 10 19:49:07 MSK 2008
root@i.x00.net:/usr/obj/usr/src/sys/KERNEL-4BSD
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz (2400.10-MHz K8-class
CPU)
Origin = "GenuineIntel" Id = 0x6fb Stepping = 11
Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
Features2=0xe3bd<SSE3,RSVD2,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM>
AMD Features=0x20100800<SYSCALL,NX,LM>
AMD Features2=0x1<LAHF>
Cores per package: 4
usable memory = 4283449344 (4085 MB)
avail memory = 4134977536 (3943 MB)
ACPI APIC Table: <022108 APIC2247>
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
cpu0 (BSP): APIC ID: 0
cpu1 (AP): APIC ID: 1
cpu2 (AP): APIC ID: 2
cpu3 (AP): APIC ID: 3
ioapic0 <Version 2.0> irqs 0-23 on motherboard
kbd1 at kbdmux0
hptrr: HPT RocketRAID controller driver v1.1 (Nov 10 2008 19:48:39)
acpi0: <022108 RSDT2247> on motherboard
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
acpi0: reservation of 0, a0000 (3) failed
acpi0: reservation of 100000, eff00000 (3) failed
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
cpu0: <ACPI CPU> on acpi0
est0: <Enhanced SpeedStep Frequency Control> on cpu0
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 928092806000928
device_attach: est0 attach returned 6
p4tcc0: <CPU Frequency Thermal Control> on cpu0
cpu1: <ACPI CPU> on acpi0
est1: <Enhanced SpeedStep Frequency Control> on cpu1
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 928092806000928
device_attach: est1 attach returned 6
p4tcc1: <CPU Frequency Thermal Control> on cpu1
cpu2: <ACPI CPU> on acpi0
est2: <Enhanced SpeedStep Frequency Control> on cpu2
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 928092806000928
device_attach: est2 attach returned 6
p4tcc2: <CPU Frequency Thermal Control> on cpu2
cpu3: <ACPI CPU> on acpi0
est3: <Enhanced SpeedStep Frequency Control> on cpu3
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 928092806000928
device_attach: est3 attach returned 6
p4tcc3: <CPU Frequency Thermal Control> on cpu3
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pcib1: <ACPI PCI-PCI bridge> irq 16 at device 1.0 on pci0
pci5: <ACPI PCI bus> on pcib1
pcib2: <ACPI PCI-PCI bridge> irq 16 at device 28.0 on pci0
pci2: <ACPI PCI bus> on pcib2
pcib3: <ACPI PCI-PCI bridge> irq 16 at device 28.4 on pci0
pci3: <ACPI PCI bus> on pcib3
bge0: <Broadcom NetXtreme Gigabit Ethernet Controller, ASIC rev. 0x4201> mem
0xfeaf0000-0xfeafffff irq 16 at device 0.0 on pci3
miibus0: <MII bus> on bge0
brgphy0: <BCM5750 10/100/1000baseTX PHY> PHY 1 on miibus0
brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,
1000baseT-FDX, auto
bge0: Ethernet address: 00:1f:c6:48:c8:9b
bge0: [ITHREAD]
pcib4: <ACPI PCI-PCI bridge> irq 17 at device 28.5 on pci0
pci4: <ACPI PCI bus> on pcib4
bge1: <Broadcom NetXtreme Gigabit Ethernet Controller, ASIC rev. 0x4201> mem
0xfebf0000-0xfebfffff irq 17 at device 0.0 on pci4
miibus1: <MII bus> on bge1
brgphy1: <BCM5750 10/100/1000baseTX PHY> PHY 1 on miibus1
brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,
1000baseT-FDX, auto
bge1: Ethernet address: 00:1f:c6:48:ca:b7
bge1: [ITHREAD]
pcib5: <ACPI PCI-PCI bridge> at device 30.0 on pci0
pci1: <ACPI PCI bus> on pcib5
vgapci0: <VGA-compatible display> port 0xec00-0xec7f mem
0xf8000000-0xfbffffff,0xfe9c0000-0xfe9fffff at device 4.0 on pci1
isab0: <PCI-ISA bridge> at device 31.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel ICH7 UDMA100 controller> port
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 31.1 on pci0
ata0: <ATA channel 0> on atapci0
ata0: [ITHREAD]
ata1: <ATA channel 1> on atapci0
ata1: [ITHREAD]
atapci1: <Intel ICH7 SATA300 controller> port
0xdc00-0xdc07,0xd880-0xd883,0xd800-0xd807,0xd480-0xd483,0xd400-0xd40f mem
0xfe8ffc00-0xfe8fffff irq 19 at device 31.2 on pci0
atapci1: [ITHREAD]
atapci1: AHCI called from vendor specific driver
atapci1: AHCI Version 01.10 controller with 4 ports detected
ata2: <ATA channel 0> on atapci1
ata2: [ITHREAD]
ata3: <ATA channel 1> on atapci1
ata3: [ITHREAD]
ata4: <ATA channel 2> on atapci1
ata4: [ITHREAD]
ata5: <ATA channel 3> on atapci1
ata5: [ITHREAD]
pci0: <serial bus, SMBus> at device 31.3 (no driver attached)
acpi_button0: <Power Button> on acpi0
orm0: <ISA Option ROM> at iomem 0xc0000-0xc7fff on isa0
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
atkbd0: [ITHREAD]
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sio0: configured irq 4 not in bitmap of probed irqs 0
sio0: port may not be enabled
sio0: configured irq 4 not in bitmap of probed irqs 0
sio0: port may not be enabled
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 8250 or not responding
sio0: [FILTER]
sio1: configured irq 3 not in bitmap of probed irqs 0
sio1: port may not be enabled
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
Timecounters tick every 1.000 msec
ipfw2 (+ipv6) initialized, divert loadable, rule-based forwarding disabled,
default to accept, logging limited to 5 packets/entry by default
hptrr: no controller detected.
acd0: DVDR <MATSHITADVD-RAM UJ-860S/1.00> at ata0-master UDMA33
ad4: 476940MB <Seagate ST3500320NS SN05> at ata2-master SATA300
ad6: 476940MB <Seagate ST3500320NS SN05> at ata3-master SATA300
ad10: 476940MB <Seagate ST3500320NS SN05> at ata5-master SATA300
ar0: 476937MB <Intel MatrixRAID RAID1> status: READY
ar0: disk0 READY (master) using ad4 at ata2-master
ar0: disk1 READY (mirror) using ad6 at ata3-master
SMP: AP CPU #1 Launched!
SMP: AP CPU #3 Launched!
SMP: AP CPU #2 Launched!
Trying to mount root from ufs:/dev/ar0s1a
bge0: link state changed to UP
-------------------------------------------------------------------
cat ./KERNEL-4BSD | grep -v "^#"
cpu HAMMER
ident KERNEL-4BSD
options SCHED_4BSD # 4BSD scheduler
options PREEMPTION # Enable kernel thread preemption
options INET # InterNETworking
options INET6 # IPv6 communications protocols
options SCTP # Stream Control Transmission
Protocol
options FFS # Berkeley Fast Filesystem
options SOFTUPDATES # Enable FFS soft updates support
options UFS_ACL # Support for access control lists
options UFS_DIRHASH # Improve performance on big
directories
options UFS_GJOURNAL # Enable gjournal-based UFS
journaling
options MD_ROOT # MD is a potential root device
options MSDOSFS # MSDOS Filesystem
options CD9660 # ISO 9660 Filesystem
options PROCFS # Process filesystem (requires
PSEUDOFS)
options PSEUDOFS # Pseudo-filesystem framework
options GEOM_PART_GPT # GUID Partition Tables.
options GEOM_LABEL # Provides labelization
options COMPAT_43TTY # BSD 4.3 TTY compat [KEEP THIS!]
options COMPAT_IA32 # Compatible with i386 binaries
options COMPAT_FREEBSD4 # Compatible with FreeBSD4
options COMPAT_FREEBSD5 # Compatible with FreeBSD5
options COMPAT_FREEBSD6 # Compatible with FreeBSD6
options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI
options KTRACE # ktrace(1) support
options SYSVSHM # SYSV-style shared memory
options SYSVMSG # SYSV-style message queues
options SYSVSEM # SYSV-style semaphores
options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time
extensions
options KBD_INSTALL_CDEV # install a CDEV entry in /dev
options ADAPTIVE_GIANT # Giant mutex is adaptive.
options STOP_NMI # Stop CPUS using NMI instead of IPI
options AUDIT # Security event auditing
options SMP # Symmetric MultiProcessor Kernel
options IPFIREWALL
options IPFIREWALL_VERBOSE
options IPFIREWALL_VERBOSE_LIMIT=5
options IPFIREWALL_DEFAULT_TO_ACCEPT
options QUOTA
device cpufreq
device acpi
device pci
device fdc
device ata
device atadisk # ATA disk drives
device ataraid # ATA RAID drives
device atapicd # ATAPI CDROM drives
options ATA_STATIC_ID # Static device numbering
device ahc # AHA2940 and onboard AIC7xxx devices
options AHC_REG_PRETTY_PRINT # Print register bitfields in debug
# output. Adds ~128k to driver.
device ahd # AHA39320/29320 and onboard AIC79xx devices
options AHD_REG_PRETTY_PRINT # Print register bitfields in debug
# output. Adds ~215k to driver.
device amd # AMD 53C974 (Tekram DC-390(T))
device hptiop # Highpoint RocketRaid 3xxx series
device isp # Qlogic family
device mpt # LSI-Logic MPT-Fusion
device sym # NCR/Symbios Logic (newer chipsets + those
of `ncr')
device trm # Tekram DC395U/UW/F DC315U adapters
device adv # Advansys SCSI adapters
device adw # Advansys wide SCSI adapters
device aic # Adaptec 15[012]x SCSI adapters,
AIC-6[23]60.
device bt # Buslogic/Mylex MultiMaster SCSI adapters
device scbus # SCSI bus (required for SCSI)
device ch # SCSI media changers
device da # Direct Access (disks)
device sa # Sequential Access (tape etc)
device cd # CD
device pass # Passthrough device (direct SCSI access)
device ses # SCSI Environmental Services (and SAF-TE)
device amr # AMI MegaRAID
device arcmsr # Areca SATA II RAID
device ciss # Compaq Smart RAID 5*
device dpt # DPT Smartcache III, IV - See NOTES for
options
device hptmv # Highpoint RocketRAID 182x
device hptrr # Highpoint RocketRAID 17xx, 22xx, 23xx,
25xx
device iir # Intel Integrated RAID
device ips # IBM (Adaptec) ServeRAID
device mly # Mylex AcceleRAID/eXtremeRAID
device twa # 3ware 9000 series PATA/SATA RAID
device aac # Adaptec FSA RAID
device aacp # SCSI passthrough for aac (requires CAM)
device ida # Compaq Smart RAID
device mfi # LSI MegaRAID SAS
device mlx # Mylex DAC960 family
device twe # 3ware ATA RAID
device atkbdc # AT keyboard controller
device atkbd # AT keyboard
device psm # PS/2 mouse
device kbdmux # keyboard multiplexer
device vga # VGA video card driver
device splash # Splash screen and screen saver support
device sc
device agp # support several AGP chipsets
device sio # 8250, 16[45]50 based serial ports
device uart # Generic UART driver
device de # DEC/Intel DC21x4x (``Tulip'')
device em # Intel PRO/1000 adapter Gigabit Ethernet
Card
device ixgb # Intel PRO/10GbE Ethernet Card
device le # AMD Am7900 LANCE and Am79C9xx PCnet
device txp # 3Com 3cR990 (``Typhoon'')
device vx # 3Com 3c590, 3c595 (``Vortex'')
device miibus # MII bus support
device bce # Broadcom BCM5706/BCM5708 Gigabit Ethernet
device bfe # Broadcom BCM440x 10/100 Ethernet
device bge # Broadcom BCM570xx Gigabit Ethernet
device dc # DEC/Intel 21143 and various workalikes
device fxp # Intel EtherExpress PRO/100B (82557, 82558)
device lge # Level 1 LXT1001 gigabit Ethernet
device msk # Marvell/SysKonnect Yukon II Gigabit
Ethernet
device nfe # nVidia nForce MCP on-board Ethernet
device nge # NatSemi DP83820 gigabit Ethernet
device pcn # AMD Am79C97x PCI 10/100 (precedence over
'le')
device re # RealTek 8139C+/8169/8169S/8110S
device rl # RealTek 8129/8139
device sf # Adaptec AIC-6915 (``Starfire'')
device sis # Silicon Integrated Systems SiS 900/SiS
7016
device sk # SysKonnect SK-984x & SK-982x gigabit
Ethernet
device ste # Sundance ST201 (D-Link DFE-550TX)
device ti # Alteon Networks Tigon I/II gigabit
Ethernet
device tl # Texas Instruments ThunderLAN
device tx # SMC EtherPower II (83c170 ``EPIC'')
device vge # VIA VT612x gigabit Ethernet
device vr # VIA Rhine, Rhine II
device wb # Winbond W89C840F
device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'')
device loop # Network loopback
device random # Entropy device
device ether # Ethernet support
device sl # Kernel SLIP
device ppp # Kernel PPP
device tun # Packet tunnel.
device pty # Pseudo-ttys (telnet etc)
device md # Memory "disks"
device gif # IPv6 and IPv4 tunneling
device faith # IPv6-to-IPv4 relaying (translation)
device firmware # firmware assist module
device bpf # Berkeley packet filter
device uhci # UHCI PCI->USB interface
device ohci # OHCI PCI->USB interface
device ehci # EHCI PCI->USB interface (USB 2.0)
device usb # USB Bus (required)
device ugen # Generic
device uhid # "Human Interface Devices"
device ukbd # Keyboard
device umass # Disks/Mass storage - Requires scbus and da
device ums # Mouse
--
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited. If you received
this in error, please contact the sender and delete the material from any
computer.
From owner-freebsd-stable@FreeBSD.ORG Tue Nov 18 15:29:53 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 2ADF31065675
for <freebsd-stable@freebsd.org>; Tue, 18 Nov 2008 15:29:53 +0000 (UTC)
(envelope-from freebsd-stable@m.gmane.org)
Received: from ciao.gmane.org (main.gmane.org [80.91.229.2])
by mx1.freebsd.org (Postfix) with ESMTP id 9852B8FC13
for <freebsd-stable@freebsd.org>; Tue, 18 Nov 2008 15:29:52 +0000 (UTC)
(envelope-from freebsd-stable@m.gmane.org)
Received: from list by ciao.gmane.org with local (Exim 4.43)
id 1L2SWT-0001ch-VK
for freebsd-stable@freebsd.org; Tue, 18 Nov 2008 15:29:49 +0000
Received: from lara.cc.fer.hr ([161.53.72.113])
by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
id 1AlnuQ-0007hv-00
for <freebsd-stable@freebsd.org>; Tue, 18 Nov 2008 15:29:49 +0000
Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian))
id 1AlnuQ-0007hv-00
for <freebsd-stable@freebsd.org>; Tue, 18 Nov 2008 15:29:49 +0000
X-Injected-Via-Gmane: http://gmane.org/
To: freebsd-stable@freebsd.org
From: Ivan Voras <ivoras@freebsd.org>
Date: Tue, 18 Nov 2008 16:30:18 +0100
Lines: 36
Message-ID: <gfun0o$lvq$1@ger.gmane.org>
References: <fd2a4c1f0811180637m6ee44d4fv4cf97d18e322ca5a@mail.gmail.com>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature";
boundary="------------enig75F956B6F39BDC226C434BB8"
X-Complaints-To: usenet@ger.gmane.org
X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr
User-Agent: Thunderbird 2.0.0.17 (X11/20080925)
In-Reply-To: <fd2a4c1f0811180637m6ee44d4fv4cf97d18e322ca5a@mail.gmail.com>
X-Enigmail-Version: 0.95.0
Sender: news <news@ger.gmane.org>
Subject: Re: High system in %system load .
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Nov 2008 15:29:53 -0000
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig75F956B6F39BDC226C434BB8
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Igor Lyapin wrote:
> Hello
> Got strange problem with high system "%system load" and very slow user =
level
> programs (apache+php+mysql) behavior
> gstat shows 1.5-4% hard disk busy load but system shows about 20-30% lo=
ad
> while user load is max 5%.
> vmstat shows from 2 to 35 process in "b" state.
> Now use 7.0-RELEASE-p5 , but the same problem was with 7.0-RELEASE.
> And have no idea what to do with this.
Where is the system busy? For start, try to collect information about
what are your processes doing - for example from top(1).
--------------enig75F956B6F39BDC226C434BB8
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFJIt+KldnAQVacBcgRAsY+AJ48hXvq1KGSyedw411ENgzgNhkargCbBI3G
2Udwh2E0I+fgVP45rZIBAfM=
=QNp+
-----END PGP SIGNATURE-----
--------------enig75F956B6F39BDC226C434BB8--
From owner-freebsd-stable@FreeBSD.ORG Tue Nov 18 17:04:42 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 786BE1065675
for <freebsd-stable@freebsd.org>; Tue, 18 Nov 2008 17:04:42 +0000 (UTC)
(envelope-from igor.lyapin@gmail.com)
Received: from mail-qy0-f18.google.com (mail-qy0-f18.google.com
[209.85.221.18])
by mx1.freebsd.org (Postfix) with ESMTP id 187298FC18
for <freebsd-stable@freebsd.org>; Tue, 18 Nov 2008 17:04:41 +0000 (UTC)
(envelope-from igor.lyapin@gmail.com)
Received: by qyk11 with SMTP id 11so985422qyk.19
for <freebsd-stable@freebsd.org>; Tue, 18 Nov 2008 09:04:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:message-id:date:from:to
:subject:in-reply-to:mime-version:content-type:references;
bh=Y09JFiJbiiRziMk7sZdUcOCPVUX8riu+lTCP3nIpWbQ=;
b=exC1GgxQoI9bmVfWIIZUZFifuGUAYkPZLatDZq6APh24pbpfnwtp5Pd9DO0NPnyQs0
8g1m7SD3kcVy+UFmdDKrr+G79RfDXldOWFsjvvxjffm+e9K27dtzcM2akOvPeaLKy+Fw
OeVB3zCuVBF4noYq26BD+EGnioWI4O2ZvlEVY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=message-id:date:from:to:subject:in-reply-to:mime-version
:content-type:references;
b=UGa5ZRX9OdzFTgQuPQWAMj/OPjhZx1klqsznj/Qzr7VKVfXQo5MV8zyz2WjjXtZBmh
k38s5CzxvoUTSwMYTUT3HSy7BrYnz1NpGvYMEpmMEOadIrsNM6JXJJYrbjs/ig584DJO
3tc9tr3a6wvaHfgUkV4G47bN7xnOctbBsQCm0=
Received: by 10.214.149.15 with SMTP id w15mr139733qad.94.1227027881496;
Tue, 18 Nov 2008 09:04:41 -0800 (PST)
Received: by 10.214.43.11 with HTTP; Tue, 18 Nov 2008 09:04:41 -0800 (PST)
Message-ID: <fd2a4c1f0811180904k396dff47m43d537a07ae87579@mail.gmail.com>
Date: Tue, 18 Nov 2008 20:04:41 +0300
From: "Igor Lyapin" <igor.lyapin@gmail.com>
To: freebsd-stable@freebsd.org
In-Reply-To: <gfun0o$lvq$1@ger.gmane.org>
MIME-Version: 1.0
References: <fd2a4c1f0811180637m6ee44d4fv4cf97d18e322ca5a@mail.gmail.com>
<gfun0o$lvq$1@ger.gmane.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
Subject: Re: High system in %system load .
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Nov 2008 17:04:42 -0000
I already sent # top head in my first mail
that's all non idle top process
last pid: 56920; load averages: 2.90, 2.25, 1.72 up
0+22:10:12 20:04:05
210 processes: 2 running, 207 sleeping, 1 zombie
CPU states: 8.3% user, 0.0% nice, 32.5% system, 0.3% interrupt, 58.9%
idle
Mem: 1268M Active, 1904M Inact, 479M Wired, 154M Cache, 214M Buf, 125M Free
Swap: 8192M Total, 8192M Free
PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU
COMMAND
55546 www 1 -4 0 198M 24912K ufs 1 0:25 29.39% httpd
55986 www 1 -4 0 198M 23228K ufs 2 0:08 21.39% httpd
56030 www 1 -4 0 199M 23400K ufs 1 0:05 11.23% httpd
56033 www 1 96 0 198M 23760K select 0 0:31 5.86% httpd
55134 www 1 -4 0 199M 29864K ufs 1 0:19 5.37% httpd
711 mysql 26 96 0 1545M 641M ucond 1 165:53 5.08%
mysqld
56001 www 1 4 0 198M 24060K accept 0 0:31 3.76% httpd
55928 www 1 96 0 198M 24184K select 0 0:31 2.29% httpd
56070 www 1 -4 0 199M 25620K ufs 2 0:02 2.20% httpd
56020 www 1 -4 0 198M 20684K ufs 1 0:22 2.15% httpd
55970 www 1 97 0 198M 23996K select 0 0:01 1.51% httpd
55898 www 1 96 0 199M 25724K select 0 0:02 1.46% httpd
56009 www 1 4 0 199M 26564K accept 1 0:03 1.32% httpd
56058 www 1 96 0 199M 25040K select 2 0:01 1.27% httpd
56914 www 1 96 0 198M 20720K select 0 0:00 1.24% httpd
56912 www 1 96 0 198M 20688K select 0 0:00 1.15% httpd
56149 www 1 96 0 199M 25204K select 0 0:01 1.12% httpd
56918 www 1 96 0 198M 20692K select 0 0:00 1.12% httpd
55901 www 1 4 0 199M 25176K accept 0 0:02 1.07% httpd
56018 www 1 4 0 199M 25680K accept 3 0:02 0.93% httpd
56073 www 1 4 0 199M 24960K accept 1 0:02 0.93% httpd
56880 www 1 4 0 198M 20720K accept 2 0:00 0.89% httpd
56671 www 1 4 0 198M 20708K accept 0 0:01 0.79% httpd
55979 www 1 4 0 199M 24176K accept 2 0:03 0.78% httpd
55843 www 1 96 0 199M 27756K select 2 0:01 0.78% httpd
55779 www 1 96 0 199M 27420K select 0 0:03 0.73% httpd
56881 www 1 4 0 198M 22300K accept 0 0:01 0.69% httpd
55933 www 1 4 0 199M 24952K accept 0 0:02 0.68% httpd
55926 www 1 96 0 199M 26324K select 1 0:02 0.68% httpd
55969 www 1 4 0 199M 25128K accept 0 0:02 0.68% httpd
56892 www 1 96 0 199M 24084K select 3 0:01 0.67% httpd
56907 www 1 96 0 198M 20692K select 3 0:00 0.65% httpd
56874 www 1 96 0 199M 23300K select 1 0:01 0.64% httpd
56125 www 1 96 0 199M 24004K select 0 0:02 0.63% httpd
On Tue, Nov 18, 2008 at 6:30 PM, Ivan Voras <ivoras@freebsd.org> wrote:
> Igor Lyapin wrote:
> > Hello
> > Got strange problem with high system "%system load" and very slow user
> level
> > programs (apache+php+mysql) behavior
> > gstat shows 1.5-4% hard disk busy load but system shows about 20-30% load
> > while user load is max 5%.
> > vmstat shows from 2 to 35 process in "b" state.
> > Now use 7.0-RELEASE-p5 , but the same problem was with 7.0-RELEASE.
> > And have no idea what to do with this.
>
> Where is the system busy? For start, try to collect information about
> what are your processes doing - for example from top(1).
>
>
From owner-freebsd-stable@FreeBSD.ORG Tue Nov 18 17:06:57 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id AE6981065673
for <freebsd-stable@freebsd.org>; Tue, 18 Nov 2008 17:06:57 +0000 (UTC)
(envelope-from cpghost@cordula.ws)
Received: from fw.farid-hajji.net (fw.farid-hajji.net [213.146.115.42])
by mx1.freebsd.org (Postfix) with ESMTP id D6D0F8FC1A
for <freebsd-stable@freebsd.org>; Tue, 18 Nov 2008 17:06:56 +0000 (UTC)
(envelope-from cpghost@cordula.ws)
Received: from phenom.cordula.ws (phenom [192.168.254.60])
by fw.farid-hajji.net (Postfix) with ESMTP id 9A28235E2E;
Tue, 18 Nov 2008 18:03:45 +0100 (CET)
Date: Tue, 18 Nov 2008 18:08:31 +0100
From: cpghost <cpghost@cordula.ws>
To: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>
Message-ID: <20081118170831.GA2264@phenom.cordula.ws>
References: <5FD58BCD6B4C409DA7E7C30150FB10C7@multiplay.co.uk>
<20081117.233619.85395429.sthaug@nethelp.no>
<20081118081153.GQ51761@server.vk2pj.dyndns.org>
<20081118.103424.74710091.sthaug@nethelp.no>
<20081118113811.GB1136@phenom.cordula.ws>
<20081118120244.U61259@maildrop.int.zabbadoz.net>
<20081118132305.GB958@phenom.cordula.ws>
<20081118134228.GC958@phenom.cordula.ws>
<20081118135622.L61259@maildrop.int.zabbadoz.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20081118135622.L61259@maildrop.int.zabbadoz.net>
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: freebsd-stable@freebsd.org, sthaug@nethelp.no
Subject: Re: ifconfig(8) interface description field
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Nov 2008 17:06:57 -0000
On Tue, Nov 18, 2008 at 01:58:09PM +0000, Bjoern A. Zeeb wrote:
> >> Some network management apps could also decide to use the description
> >> field as a repository for more dynamic data; data that could be queried
> >> by applications running on the hosts. Here too, would'nt it be more
> >> efficient if descr. were in-kernel?
> >>
> >> For persistence, an /etc/rc.d script could always set the static
> >> interface descriptions via ifconfig calls any way it likes, including
> >> reading those definitions from a config file. Everything else will
> >> probably be set remotely via the network management software, which
> >> itself has its own persistence store (usually a database).
> >
> > Another reason you want to avoid using a file for this: what about
> > appliances that run as dedicated routers and boot from a flash-based
> > read-only filesystem? How would you change the interface description
> > (remotely or on the console) if you can't write to a file?
>
> So how would you make it persistent across a reboot if you cannot write
> it anywhere?
This would be done remotely by the network management system (NMS) The
NMS will notice that the node rebooted, and will send to its snmpd the
description of its interfaces. snmpd runs on the node, and will call
an ifconfig ioctl to store this description in kernel memory. From
then on, you could ssh to the box, and look around by calling
ifconfig(8) manually: you'all immediately know what each interface is
intended for. If you have hundreds of nodes, you'll appreciate the
convenience!
The presistence occurs at the NMS site: it is merely mirrored onto the
nodes.
So why store this on the nodes at all, as it is redundant and already
persistently available in the NMS?
Well, in practice, NMS can and do break down every now and then for
all kinds of reasons (database problems, server problems, network
problems to the NMS server, ...). But a NOC can't afford to wait for
the NMS be available again to reconfigure some important nodes on a
backbone.
Even when the NMS is down, you'll still have to manually ifconfig(8)
some interfaces on crucial backbone nodes. When the NMS is available
again, it will poll all the snmpd of its managed hosts, and will
update its own database if things changed in the mean time on the
nodes. That's the easiest way to synchronize the NMS database back
with the manual changes at the nodes that occured while the NMS was
down.
(Sure, there's a little time window where information can be lost:
that's just after the manual ifconfig(8) and the polling of the
snmpd by the NMS. But, hey, if THIS happened, you could still use
some logfile (script(1)?) of your manual changes to catch this.
The normal workflow is to manage at the NMS and to push the data
to the nodes, the reverse workflow is for emergencies only.)
The point I'm trying to make, is that diskless systems, or systems
with read-only filesystems should still be configurable, remotely and
manually; and the configuration data (in this case it's the
description strings of its interfaces) will have to be stored in
memory.
For something as trivial as description strings, kernel memory seems
like a good idea. If user memory is preferred and absolutely needed,
one could always write an ifconfigd daemon and store it there; but
*that* seems like overkill for such a simple change.
> Bjoern A. Zeeb Stop bit received. Insert coin for new game.
-cpghost.
--
Cordula's Web. http://www.cordula.ws/
From owner-freebsd-stable@FreeBSD.ORG Tue Nov 18 17:53:07 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 309851065675
for <freebsd-stable@freebsd.org>; Tue, 18 Nov 2008 17:53:07 +0000 (UTC)
(envelope-from jdc@koitsu.dyndns.org)
Received: from QMTA08.emeryville.ca.mail.comcast.net
(qmta08.emeryville.ca.mail.comcast.net [76.96.30.80])
by mx1.freebsd.org (Postfix) with ESMTP id 009488FC16
for <freebsd-stable@freebsd.org>; Tue, 18 Nov 2008 17:53:04 +0000 (UTC)
(envelope-from jdc@koitsu.dyndns.org)
Received: from OMTA08.emeryville.ca.mail.comcast.net ([76.96.30.12])
by QMTA08.emeryville.ca.mail.comcast.net with comcast
id geAx1a0030FhH24A8ht48V; Tue, 18 Nov 2008 17:53:04 +0000
Received: from koitsu.dyndns.org ([69.181.141.110])
by OMTA08.emeryville.ca.mail.comcast.net with comcast
id ght31a00R2P6wsM8Uht4Mz; Tue, 18 Nov 2008 17:53:04 +0000
X-Authority-Analysis: v=1.0 c=1 a=6fuZhc4rEvsA:10 a=QycZ5dHgAAAA:8
a=CgHnNpHRzfLQiBv6M5YA:9 a=RknhzwHGqi6nS8WZ2VAA:7
a=MJSs6dGhlf_5UPKnXAlXtAei14AA:4 a=EoioJ0NPDVgA:10 a=LY0hPdMaydYA:10
Received: by icarus.home.lan (Postfix, from userid 1000)
id 87A7133C37; Tue, 18 Nov 2008 09:53:03 -0800 (PST)
Date: Tue, 18 Nov 2008 09:53:03 -0800
From: Jeremy Chadwick <koitsu@FreeBSD.org>
To: Igor Lyapin <igor.lyapin@gmail.com>
Message-ID: <20081118175303.GA64181@icarus.home.lan>
References: <fd2a4c1f0811180637m6ee44d4fv4cf97d18e322ca5a@mail.gmail.com>
<gfun0o$lvq$1@ger.gmane.org>
<fd2a4c1f0811180904k396dff47m43d537a07ae87579@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <fd2a4c1f0811180904k396dff47m43d537a07ae87579@mail.gmail.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: freebsd-stable@freebsd.org
Subject: Re: High system in %system load .
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Nov 2008 17:53:07 -0000
On Tue, Nov 18, 2008 at 08:04:41PM +0300, Igor Lyapin wrote:
> I already sent # top head in my first mail
> that's all non idle top process
>
> last pid: 56920; load averages: 2.90, 2.25, 1.72 up
> 0+22:10:12 20:04:05
> 210 processes: 2 running, 207 sleeping, 1 zombie
> CPU states: 8.3% user, 0.0% nice, 32.5% system, 0.3% interrupt, 58.9%
> idle
> Mem: 1268M Active, 1904M Inact, 479M Wired, 154M Cache, 214M Buf, 125M Free
> Swap: 8192M Total, 8192M Free
>
> PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU
> COMMAND
> 55546 www 1 -4 0 198M 24912K ufs 1 0:25 29.39% httpd
> 55986 www 1 -4 0 198M 23228K ufs 2 0:08 21.39% httpd
> 56030 www 1 -4 0 199M 23400K ufs 1 0:05 11.23% httpd
> 56033 www 1 96 0 198M 23760K select 0 0:31 5.86% httpd
> 55134 www 1 -4 0 199M 29864K ufs 1 0:19 5.37% httpd
> 711 mysql 26 96 0 1545M 641M ucond 1 165:53 5.08%
> mysqld
> 56001 www 1 4 0 198M 24060K accept 0 0:31 3.76% httpd
> 55928 www 1 96 0 198M 24184K select 0 0:31 2.29% httpd
> 56070 www 1 -4 0 199M 25620K ufs 2 0:02 2.20% httpd
> 56020 www 1 -4 0 198M 20684K ufs 1 0:22 2.15% httpd
> 55970 www 1 97 0 198M 23996K select 0 0:01 1.51% httpd
> 55898 www 1 96 0 199M 25724K select 0 0:02 1.46% httpd
> 56009 www 1 4 0 199M 26564K accept 1 0:03 1.32% httpd
> 56058 www 1 96 0 199M 25040K select 2 0:01 1.27% httpd
> 56914 www 1 96 0 198M 20720K select 0 0:00 1.24% httpd
> 56912 www 1 96 0 198M 20688K select 0 0:00 1.15% httpd
> 56149 www 1 96 0 199M 25204K select 0 0:01 1.12% httpd
> 56918 www 1 96 0 198M 20692K select 0 0:00 1.12% httpd
> 55901 www 1 4 0 199M 25176K accept 0 0:02 1.07% httpd
> 56018 www 1 4 0 199M 25680K accept 3 0:02 0.93% httpd
> 56073 www 1 4 0 199M 24960K accept 1 0:02 0.93% httpd
> 56880 www 1 4 0 198M 20720K accept 2 0:00 0.89% httpd
> 56671 www 1 4 0 198M 20708K accept 0 0:01 0.79% httpd
> 55979 www 1 4 0 199M 24176K accept 2 0:03 0.78% httpd
> 55843 www 1 96 0 199M 27756K select 2 0:01 0.78% httpd
> 55779 www 1 96 0 199M 27420K select 0 0:03 0.73% httpd
> 56881 www 1 4 0 198M 22300K accept 0 0:01 0.69% httpd
> 55933 www 1 4 0 199M 24952K accept 0 0:02 0.68% httpd
> 55926 www 1 96 0 199M 26324K select 1 0:02 0.68% httpd
> 55969 www 1 4 0 199M 25128K accept 0 0:02 0.68% httpd
> 56892 www 1 96 0 199M 24084K select 3 0:01 0.67% httpd
> 56907 www 1 96 0 198M 20692K select 3 0:00 0.65% httpd
> 56874 www 1 96 0 199M 23300K select 1 0:01 0.64% httpd
> 56125 www 1 96 0 199M 24004K select 0 0:02 0.63% httpd
What version of Apache is this, and exactly what options did you build
it with?
--
| Jeremy Chadwick jdc at parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |
From owner-freebsd-stable@FreeBSD.ORG Tue Nov 18 18:43:01 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 61319106564A;
Tue, 18 Nov 2008 18:43:01 +0000 (UTC)
(envelope-from lopez.on.the.lists@yellowspace.net)
Received: from mail.yellowspace.net (mail.yellowspace.net [80.190.200.164])
by mx1.freebsd.org (Postfix) with ESMTP id D0C388FC13;
Tue, 18 Nov 2008 18:43:00 +0000 (UTC)
(envelope-from lopez.on.the.lists@yellowspace.net)
Received: from [192.168.178.21] ([85.181.143.201])
(AUTH: CRAM-MD5 lopez.on.the.lists@yellowspace.net, TLS: TLSv1/SSLv3,
128bits, AES128-SHA)
by mail.yellowspace.net with esmtp; Tue, 18 Nov 2008 19:42:58 +0100
id 0035E94F.0000000049230CB2.00012CED
Message-Id: <7BA53082-577E-4DF2-8E2A-025942C11C0A@yellowspace.net>
From: Lorenzo Perone <lopez.on.the.lists@yellowspace.net>
To: Chao Shin <quakelee@geekcn.org>
In-Reply-To: <op.uks5krn2hnq548@qld630>
Content-Type: text/plain; charset=UTF-8; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Tue, 18 Nov 2008 19:42:56 +0100
References: <491CE71F.2020208@delphij.net> <491CE835.4050504@delphij.net>
<20081117155835.GC2101@garage.freebsd.pl>
<op.uks5krn2hnq548@qld630>
X-Mailer: Apple Mail (2.929.2)
Cc: d@delphij.net, Pawel Jakub Dawidek <pjd@freebsd.org>,
FreeBSD Stable <freebsd-stable@freebsd.org>
Subject: Re: ZFS crashes on heavy threaded environment
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Nov 2008 18:43:01 -0000
For what's worth it, I have similar problems on a comparable system =20
(amd64/8GB,
7.1-PRERELEASE #3: Sun Nov 16 13:39:43), which I wouldn't call
heavilly threaded yet (as there is only one mysql51 running,
and courier-mta/imap, max 15 users now).
Perhaps worth a note: Bjoern's multi-IP jail patches are applied on
this system.
The setup is so that one zfs filesystem is mounted into a jail handling
only mail (and for that: just the root of the mail files), and a =20
script on
the main host rotates snapshots hourly (making a new one, and
destroying the oldest).
After about 8-24 hours of production:
- mysqld is stuck in sbwait state;
- messages start filling up with
kernel: vm_thread_new: kstack allocation failed
- almost any attempt to fork a process fails with
Cannot allocate memory.
No panic so far, at least since I've introduced =20
vfs.zfs.prefetch_disable=3D"1".
Before that, I experienced several panics upon shutdown.
If I still have an open shell, I can send around some -TERMs and
-KILLs and halfway get back control; after that, if I zfs umount -a
kernel memory usage drastically drops down, and I can resume
the services. However, not for long. After about 1-2 hrs of production
it starts whining again in the messages about kstack allocation failed,
and soon thereafter it all repeats. Only rebooting gives back another
12-24hrs of operation.
What I've tracked down so far:
- zfs destroy'ing old snapshots definitively makes those failures
pop up earlier
- I've been collecting some data shortly around the memory
problems, which I post below.
Since this is a production machine (I know, I shoudn't - but hey,
you made us lick blood and now we ended up wanting more! So,
yes, I confirm, you definitively _are_ evil! ;)), I'm almost
ready to move that back to UFS.
But if it can be useful for debugging, I would be willing to set up a =20=
zabbix
agent or such to track whichever values could be useful over time for =20=
a day or two.
If on the other hand these bugs (leaks, or whatever) are likely to
be solved in the recent commit, I'll just move back to UFS until
they're ported to -STABLE.
Here follows some data about memory usage (strangely, I never
saw this even halfway reaching 1.5 GB, but it's really almost
voodoo to me so I leave the analysis up to others):
TEXT=3D`kldstat | tr a-f A-F | awk 'BEGIN {print "ibase=3D16"}; NR > 1 =20=
{print $4}' | bc | awk '{a+=3D$1}; END {print a}'`
DATA=3D`vmstat -m | sed 's/K//' | awk '{a+=3D$3}; END {print a*1024}'`
TOTAL=3D`echo $DATA $TEXT | awk '{print $1+$2}'`
TEXT=3D13102280, 12.4953 MB
DATA=3D470022144, 448.248 MB
TOTAL=3D483124424, 460.743 MB
vmstat -m | grep vnodes
kern.maxvnodes: 100000
kern.minvnodes: 25000
vfs.freevnodes: 2380
vfs.wantfreevnodes: 25000
vfs.numvnodes: 43982
As said, the box has 8 GB of RAM, the following loader.conf,
and at the time of the lockups there were about 5GB free
userland memory available.
my loader.conf:
vm.kmem_size=3D"1536M"
vm.kmem_size_max=3D"1536M"
vfs.zfs.arc_min=3D"512M"
vfs.zfs.arc_max=3D"768M"
vfs.zfs.prefetch_disable=3D"1"
as for the filesystem, I only changed the recordsize and
the mountpoint, the rest is default:
[horkheimer:lopez] root# zfs get all hkpool/mail
NAME PROPERTY VALUE SOURCE
hkpool/mail type filesystem -
hkpool/mail creation Fri Oct 31 13:28 2008 -
hkpool/mail used 5.50G -
hkpool/mail available 386G -
hkpool/mail referenced 4.33G -
hkpool/mail compressratio 1.05x -
hkpool/mail mounted yes -
hkpool/mail quota none default
hkpool/mail reservation none default
hkpool/mail recordsize 4K local
hkpool/mail mountpoint /jails/mail/mail local
hkpool/mail sharenfs off default
hkpool/mail checksum on default
hkpool/mail compression on local
hkpool/mail atime on default
hkpool/mail devices on default
hkpool/mail exec on default
hkpool/mail setuid on default
hkpool/mail readonly off default
hkpool/mail jailed off local
hkpool/mail snapdir hidden default
hkpool/mail aclmode groupmask default
hkpool/mail aclinherit secure default
hkpool/mail canmount on default
hkpool/mail shareiscsi off default
hkpool/mail xattr off temporary
hkpool/mail copies 1 default
the pool is using a partition on a hardware RAID1:
[horkheimer:lopez] root# zpool status
pool: hkpool
state: ONLINE
scrub: none requested
config:
NAME STATE READ WRITE CKSUM
hkpool ONLINE 0 0 0
da0s1f ONLINE 0 0 0
Regards and thanx a lot for bringing on zfs,
Lorenzo
On 18.11.2008, at 10:20, Chao Shin wrote:
> On Mon, 17 Nov 2008 23:58:35 +0800=EF=BC=8CPawel Jakub Dawidek =
<pjd@freebsd.o=20
> rg> wrote:
>
>> On Thu, Nov 13, 2008 at 06:53:41PM -0800, Xin LI wrote:
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>>
>>> Xin LI wrote:
>>> > Hi, Pawel,
>>> >
>>> > We can still reproduce the ZFS crash (threading+heavy I/O load) =20=
>>> on a
>>> > fresh 7.1-STABLE build, in a few minutes:
>>> >
>>> > /usr/local/bin/iozone -M -e -+u -T -t 128 -S 4096 -L 64 -r 4k -s =20=
>>> 30g -i
>>> > 0 -i 1 -i 2 -i 8 -+p 70 -C
>>> >
>>> > I have included a backtrace output from my colleague who has his =20=
>>> hands
>>> > on the test environment. Should there is more information =20
>>> necessary
>>> > please let us know and we wish to provide help on this.
>>>
>>> Further datapoint. The system used to run with untuned =20
>>> loader.conf, and
>>> my colleague just reported that with the following loader.conf, the
>>> problem can be triggered sooner:
>>>
>>> vm.kmem_size_max=3D838860800
>>> vm.kmem_size_scale=3D"2"
>>>
>>> The system is running FreeBSD/amd64 7.1-PRERELEASE equipped with =20
>>> 8GB of
>>> RAM with GENERIC kernel.
>>
>> With new ZFS I get:
>>
>> Memory allocation failed:: Cannot allocate memory
>>
>> Is this expected?
>>
>
> At first, Congratulations to you, thanks to your works, well done!
>
> I used this command on a FreeBSD 7.1-PRERELEASE amd64 box with 8GB =20
> mem, isn't got output like that, but kernel panic.
> Maybe you should lower the threads and file size, for example:
>
> /usr/local/bin/iozone -M -e -+u -T -t 64 -S 4096 -L 64 -r 4k -s 2g -=20=
> i 0 -i 1 -i 2 -i 8 -+p 70 -C
>
> Actually, we had used this command to test a 8-current with zfs v12 =20=
> patch on July, there is no more panic. So we hope
> zfs v13 can MFC as soon as possible, because we really need it now.
> --=20
> The Power to Serve
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to =
"freebsd-stable-unsubscribe@freebsd.org=20
> "
From owner-freebsd-stable@FreeBSD.ORG Tue Nov 18 19:33:04 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 63F991065670
for <freebsd-stable@freebsd.org>; Tue, 18 Nov 2008 19:33:04 +0000 (UTC)
(envelope-from igor.lyapin@gmail.com)
Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.26])
by mx1.freebsd.org (Postfix) with ESMTP id 0D6388FC14
for <freebsd-stable@freebsd.org>; Tue, 18 Nov 2008 19:33:03 +0000 (UTC)
(envelope-from igor.lyapin@gmail.com)
Received: by qw-out-2122.google.com with SMTP id 9so1738087qwb.7
for <freebsd-stable@freebsd.org>; Tue, 18 Nov 2008 11:33:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:message-id:date:from:to
:subject:cc:in-reply-to:mime-version:content-type:references;
bh=4UmVtm5YRlJ/VAeqQ2N8o08zMC8X4mwlGcTXZXr7uY8=;
b=P4BTz+zPSbrIvaK6qbl/u+xH6AEObpK1eD/ufHMZoa7sb1emvlqo5Q+zZjARCWKA6q
MEaD8GPCgFsuc3fuyaVIUNaknq0r8Cd45gFbssBtxRaKL+xa06RpPdlMJSalx9t2GImA
TRp/2aRM2QPKe7438lLgjUcEAmLhBVNipXxh4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
:content-type:references;
b=oGnQowJ8fl6lZfbHgg/5uGNRORBKA14bJwO8flWStxj1hC5UJpOtVkUYoztKTyhP77
a4afqh7iDGxGtHTHSFv83YMJM81wl7SoA/qO6yAkkSLImREyp8tvnLAA8H+K4QUwrR3f
6ZRM7jrak10o8f6Itl13dPSUREydEFXVh2XkI=
Received: by 10.215.13.6 with SMTP id q6mr392169qai.37.1227036782990;
Tue, 18 Nov 2008 11:33:02 -0800 (PST)
Received: by 10.214.43.11 with HTTP; Tue, 18 Nov 2008 11:33:02 -0800 (PST)
Message-ID: <fd2a4c1f0811181133u72ecef4ep83375fe512bc843f@mail.gmail.com>
Date: Tue, 18 Nov 2008 22:33:02 +0300
From: "Igor Lyapin" <igor.lyapin@gmail.com>
To: "Jeremy Chadwick" <koitsu@freebsd.org>
In-Reply-To: <20081118175303.GA64181@icarus.home.lan>
MIME-Version: 1.0
References: <fd2a4c1f0811180637m6ee44d4fv4cf97d18e322ca5a@mail.gmail.com>
<gfun0o$lvq$1@ger.gmane.org>
<fd2a4c1f0811180904k396dff47m43d537a07ae87579@mail.gmail.com>
<20081118175303.GA64181@icarus.home.lan>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
Cc: freebsd-stable@freebsd.org
Subject: Re: High system in %system load .
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Nov 2008 19:33:04 -0000
# apachectl -V
Server version: Apache/2.2.9 (FreeBSD)
Server built: Oct 17 2008 13:31:54
Server's Module Magic Number: 20051115:15
Server loaded: APR 1.3.0, APR-Util 1.3.0
Compiled using: APR 1.3.0, APR-Util 1.3.0
Architecture: 64-bit
Server MPM: Prefork
threaded: no
forked: yes (variable process count)
Server compiled with....
-D APACHE_MPM_DIR="server/mpm/prefork"
-D APR_HAS_SENDFILE
-D APR_HAS_MMAP
-D APR_HAVE_IPV6 (IPv4-mapped addresses enabled)
-D APR_USE_FLOCK_SERIALIZE
-D APR_USE_PTHREAD_SERIALIZE
-D SINGLE_LISTEN_UNSERIALIZED_ACCEPT
-D APR_HAS_OTHER_CHILD
-D AP_HAVE_RELIABLE_PIPED_LOGS
-D DYNAMIC_MODULE_LIMIT=128
-D HTTPD_ROOT="/usr/local"
-D SUEXEC_BIN="/usr/local/bin/suexec"
-D DEFAULT_PIDLOG="/var/run/httpd.pid"
-D DEFAULT_SCOREBOARD="/var/run/apache_runtime_status"
-D DEFAULT_LOCKFILE="/var/run/accept.lock"
-D DEFAULT_ERRORLOG="/var/log/httpd-error.log"
-D AP_TYPES_CONFIG_FILE="etc/apache22/mime.types"
-D SERVER_CONFIG_FILE="etc/apache22/httpd.conf"
On Tue, Nov 18, 2008 at 8:53 PM, Jeremy Chadwick <koitsu@freebsd.org> wrote:
> On Tue, Nov 18, 2008 at 08:04:41PM +0300, Igor Lyapin wrote:
> > I already sent # top head in my first mail
> > that's all non idle top process
> >
> > last pid: 56920; load averages: 2.90, 2.25, 1.72 up
> > 0+22:10:12 20:04:05
> > 210 processes: 2 running, 207 sleeping, 1 zombie
> > CPU states: 8.3% user, 0.0% nice, 32.5% system, 0.3% interrupt, 58.9%
> > idle
> > Mem: 1268M Active, 1904M Inact, 479M Wired, 154M Cache, 214M Buf, 125M
> Free
> > Swap: 8192M Total, 8192M Free
> >
> > PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU
> > COMMAND
> > 55546 www 1 -4 0 198M 24912K ufs 1 0:25 29.39%
> httpd
> > 55986 www 1 -4 0 198M 23228K ufs 2 0:08 21.39%
> httpd
> > 56030 www 1 -4 0 199M 23400K ufs 1 0:05 11.23%
> httpd
> > 56033 www 1 96 0 198M 23760K select 0 0:31 5.86%
> httpd
> > 55134 www 1 -4 0 199M 29864K ufs 1 0:19 5.37%
> httpd
> > 711 mysql 26 96 0 1545M 641M ucond 1 165:53 5.08%
> > mysqld
> > 56001 www 1 4 0 198M 24060K accept 0 0:31 3.76%
> httpd
> > 55928 www 1 96 0 198M 24184K select 0 0:31 2.29%
> httpd
> > 56070 www 1 -4 0 199M 25620K ufs 2 0:02 2.20%
> httpd
> > 56020 www 1 -4 0 198M 20684K ufs 1 0:22 2.15%
> httpd
> > 55970 www 1 97 0 198M 23996K select 0 0:01 1.51%
> httpd
> > 55898 www 1 96 0 199M 25724K select 0 0:02 1.46%
> httpd
> > 56009 www 1 4 0 199M 26564K accept 1 0:03 1.32%
> httpd
> > 56058 www 1 96 0 199M 25040K select 2 0:01 1.27%
> httpd
> > 56914 www 1 96 0 198M 20720K select 0 0:00 1.24%
> httpd
> > 56912 www 1 96 0 198M 20688K select 0 0:00 1.15%
> httpd
> > 56149 www 1 96 0 199M 25204K select 0 0:01 1.12%
> httpd
> > 56918 www 1 96 0 198M 20692K select 0 0:00 1.12%
> httpd
> > 55901 www 1 4 0 199M 25176K accept 0 0:02 1.07%
> httpd
> > 56018 www 1 4 0 199M 25680K accept 3 0:02 0.93%
> httpd
> > 56073 www 1 4 0 199M 24960K accept 1 0:02 0.93%
> httpd
> > 56880 www 1 4 0 198M 20720K accept 2 0:00 0.89%
> httpd
> > 56671 www 1 4 0 198M 20708K accept 0 0:01 0.79%
> httpd
> > 55979 www 1 4 0 199M 24176K accept 2 0:03 0.78%
> httpd
> > 55843 www 1 96 0 199M 27756K select 2 0:01 0.78%
> httpd
> > 55779 www 1 96 0 199M 27420K select 0 0:03 0.73%
> httpd
> > 56881 www 1 4 0 198M 22300K accept 0 0:01 0.69%
> httpd
> > 55933 www 1 4 0 199M 24952K accept 0 0:02 0.68%
> httpd
> > 55926 www 1 96 0 199M 26324K select 1 0:02 0.68%
> httpd
> > 55969 www 1 4 0 199M 25128K accept 0 0:02 0.68%
> httpd
> > 56892 www 1 96 0 199M 24084K select 3 0:01 0.67%
> httpd
> > 56907 www 1 96 0 198M 20692K select 3 0:00 0.65%
> httpd
> > 56874 www 1 96 0 199M 23300K select 1 0:01 0.64%
> httpd
> > 56125 www 1 96 0 199M 24004K select 0 0:02 0.63%
> httpd
>
> What version of Apache is this, and exactly what options did you build
> it with?
>
> --
> | Jeremy Chadwick jdc at parodius.com |
> | Parodius Networking http://www.parodius.com/ |
> | UNIX Systems Administrator Mountain View, CA, USA |
> | Making life hard for others since 1977. PGP: 4BD6C0CB |
>
>
--
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited. If you received
this in error, please contact the sender and delete the material from any
computer.
From owner-freebsd-stable@FreeBSD.ORG Tue Nov 18 21:30:40 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id EA7611065673
for <stable@freebsd.org>; Tue, 18 Nov 2008 21:30:40 +0000 (UTC)
(envelope-from dudu.meyer@gmail.com)
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.172])
by mx1.freebsd.org (Postfix) with ESMTP id C00818FC1D
for <stable@freebsd.org>; Tue, 18 Nov 2008 21:30:40 +0000 (UTC)
(envelope-from dudu.meyer@gmail.com)
Received: by wf-out-1314.google.com with SMTP id 24so3230971wfg.7
for <stable@freebsd.org>; Tue, 18 Nov 2008 13:30:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:message-id:date:from:to
:subject:mime-version:content-type:content-transfer-encoding
:content-disposition;
bh=pfheWpyScQYNfECQr5JoN/hJbX4OX6Dka1vH5rxKYqg=;
b=NfNAA9IpoRI6HU4DfikBmf7IFa8c+I2R08+n3wwWvE+9a7hhSiGHSvjd8Qf5w3itZB
WB3tpc11a6H/jffZD8+olNZVEGDurvNk5IdMhsDNsicCGvt9IyJBZLSRQm9kHOEBNY1F
d5f6kn++oni16rQgnvfaUQZDTj5hCeiccmJVc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=message-id:date:from:to:subject:mime-version:content-type
:content-transfer-encoding:content-disposition;
b=ZBWOTHeUZmMtGQfQW2iMkohxyZuQLCTldBTWonV67u+JUWI0Fpmf7h1mPLabmVjK27
YBrmzWCQbisBsyXuUL1koWxJ8bpHzPdKL3g1nSSJFPAuzvugCUEPIufUPiKqBgrQ9iV5
XYIqL1y13CwJZF1GBUqxLcDMhNYoVlrHDQtjA=
Received: by 10.143.43.7 with SMTP id v7mr132933wfj.192.1227043839841;
Tue, 18 Nov 2008 13:30:39 -0800 (PST)
Received: by 10.142.229.10 with HTTP; Tue, 18 Nov 2008 13:30:39 -0800 (PST)
Message-ID: <d3ea75b30811181330o61fd850du440d9db0790bf1af@mail.gmail.com>
Date: Tue, 18 Nov 2008 19:30:39 -0200
From: "Eduardo Meyer" <dudu.meyer@gmail.com>
To: stable@freebsd.org, questions@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc:
Subject: tcpdump(1) filter by date
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Nov 2008 21:30:41 -0000
Hello,
I have a kind big tcpdump file, which has data from the last week. I
want to dump information based on date. Can I do it without generating
a full output and later parse the headers?
Say, I want to filter by date in the <expression> filter and not with
tcpdump -r dumpfile | awk '{<some-black-magic-here}'
Because sometimes I want o search the full packet content (-vvv, -XX,
-T, ...) by date, and as its a huge file, dumpling everthing and
parsing it later on run-time wound consume too much memory (its a
couple of GBs file).
Thank you all, but I could not find a "date" keyword for filtering expression.
However, counting by packets sequence would also fit my needs because
the need is to, say, "analyse until a certain point" and later
"continue analysing from where I stopped", so, lets say
tcpdump -r dumpfile -c 10000
Would allow me to read the first 10000 packets from the dumpfile.
Later I would need to keep doing my job from packet 10001 to 20000.
The "date" question is because I can check the precise epoch timestamp
of the last packet I have read and later, ask tcpdump to print -c
<count> number of packets starting from the epoch-formatted date I
have paused my work later.
Sometimes I will also need this for pflog files, so, I would
appreciate any tips to do this with tcpdump custom files or pflog
generated files if there is anything would fit for one situation but
not for another.
Thank you all in advance.
--
===========
Eduardo Meyer
pessoal: dudu.meyer@gmail.com
profissional: ddm.farmaciap@saude.gov.br
From owner-freebsd-stable@FreeBSD.ORG Tue Nov 18 21:41:06 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id AB30A1065674
for <stable@freebsd.org>; Tue, 18 Nov 2008 21:41:06 +0000 (UTC)
(envelope-from david@catwhisker.org)
Received: from bunrab.catwhisker.org
(adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122])
by mx1.freebsd.org (Postfix) with ESMTP id 78D0F8FC13
for <stable@freebsd.org>; Tue, 18 Nov 2008 21:41:06 +0000 (UTC)
(envelope-from david@catwhisker.org)
Received: from bunrab.catwhisker.org (localhost [127.0.0.1])
by bunrab.catwhisker.org (8.13.3/8.13.3) with ESMTP id mAILf5UM015347;
Tue, 18 Nov 2008 13:41:05 -0800 (PST)
(envelope-from david@bunrab.catwhisker.org)
Received: (from david@localhost)
by bunrab.catwhisker.org (8.13.3/8.13.1/Submit) id mAILf5Wf015346;
Tue, 18 Nov 2008 13:41:05 -0800 (PST) (envelope-from david)
Date: Tue, 18 Nov 2008 13:41:05 -0800
From: David Wolfskill <david@catwhisker.org>
To: Eduardo Meyer <dudu.meyer@gmail.com>
Message-ID: <20081118214105.GL83287@bunrab.catwhisker.org>
Mail-Followup-To: David Wolfskill <david@catwhisker.org>,
Eduardo Meyer <dudu.meyer@gmail.com>, stable@freebsd.org
References: <d3ea75b30811181330o61fd850du440d9db0790bf1af@mail.gmail.com>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="GD0jJf8rm+K0B4Sk"
Content-Disposition: inline
In-Reply-To: <d3ea75b30811181330o61fd850du440d9db0790bf1af@mail.gmail.com>
User-Agent: Mutt/1.4.2.1i
Cc: stable@freebsd.org
Subject: Re: tcpdump(1) filter by date
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Nov 2008 21:41:06 -0000
--GD0jJf8rm+K0B4Sk
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
[Cross-post to -questions elided, since I saw the message on -stable,
and I'd like to discourage gratuitous cross-posting. dhw]
On Tue, Nov 18, 2008 at 07:30:39PM -0200, Eduardo Meyer wrote:
> Hello,
>=20
> I have a kind big tcpdump file, which has data from the last week. I
> want to dump information based on date. Can I do it without generating
> a full output and later parse the headers?
See the port net/tcpslice.
Here's an excerpt from its man page:
DESCRIPTION
Tcpslice is a program for extracting portions of packet-trace fi=
les
generated using tcpdump(l)'s -w flag. It can also be used to me=
rge
together several such files, as discussed below.
=2E..
There are a number of ways to specify times. The first is using U=
nix
timestamps of the form sssssssss.uuuuuu (this is the format specif=
ied
by tcpdump's -tt flag). For example, 654321098.7654 specifies 38 s=
ec-
onds and 765,400 microseconds after 8:51PM PDT, Sept. 25, 1990.
> ...
Peace,
david
--=20
David H. Wolfskill david@catwhisker.org
Depriving a girl or boy of an opportunity for education is evil.
See http://www.catwhisker.org/~david/publickey.gpg for my public key.
--GD0jJf8rm+K0B4Sk
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (FreeBSD)
iEYEARECAAYFAkkjNnAACgkQmprOCmdXAD1wiQCdGdBu3145Hm09q14bxjd5Wz0e
d2AAn1m+ljS+GyUYKSG3wBIjnhUGcLX7
=rVbH
-----END PGP SIGNATURE-----
--GD0jJf8rm+K0B4Sk--
From owner-freebsd-stable@FreeBSD.ORG Tue Nov 18 22:40:45 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id CE01B1065679
for <stable@freebsd.org>; Tue, 18 Nov 2008 22:40:45 +0000 (UTC)
(envelope-from crapsh@monkeybrains.net)
Received: from ape.monkeybrains.net (mail.monkeybrains.net [208.69.40.9])
by mx1.freebsd.org (Postfix) with ESMTP id B70298FC08
for <stable@freebsd.org>; Tue, 18 Nov 2008 22:40:45 +0000 (UTC)
(envelope-from crapsh@monkeybrains.net)
Received: from [192.168.2.105] (adsl-76-203-175-18.dsl.pltn13.sbcglobal.net
[76.203.175.18]) (authenticated bits=0)
by ape.monkeybrains.net (8.14.1/8.14.1) with ESMTP id mAIMKfpM011169
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
for <stable@freebsd.org>; Tue, 18 Nov 2008 14:20:42 -0800 (PST)
(envelope-from crapsh@monkeybrains.net)
Message-ID: <49233FE0.3000805@monkeybrains.net>
Date: Tue, 18 Nov 2008 14:21:20 -0800
From: Rudy <crapsh@monkeybrains.net>
User-Agent: Thunderbird 2.0.0.17 (X11/20080925)
MIME-Version: 1.0
To: stable@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV version 0.94,
clamav-milter version 0.94 on pita.monkeybrains.net
X-Virus-Status: Clean
Cc:
Subject: "df" locked up after upgrade to FreeBSD 7.1-PRERELEASE
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Nov 2008 22:40:45 -0000
Has anyone see the 'df' command just hang after an upgrade?
From another terminal, I saw df in the 'D' state when running ps.
I tried 'df &' in my new terminal, and that too just hung out in the
background.
typing 'reboot' fixed the problem. =)
This box had been up for a while, no problems. The only thing I changed
was a 7.0 to 7.1 upgrade.
(Haven't rebuilt all the ports to match the new OS, yet....)
> uname -v
FreeBSD 7.1-PRERELEASE #0: Thu Nov 13 19:14:42 PST 2008
root@example.monkeybrains.net:/usr/obj/usr/src/sys/MONKEY
(MONKEY is pretty close to generic, just some ethernet and scsi stuff
left out)
> kldstat
Id Refs Address Size Name
1 7 0xc0400000 4d39fc kernel
2 1 0xc08d4000 164e8 geom_mirror.ko
3 1 0xc3e93000 9000 if_bridge.ko
4 1 0xc3e9c000 6000 bridgestp.ko
5 1 0xc3f78000 5000 if_tap.ko
6 1 0xc3fdd000 3000 daemon_saver.ko
> df -h
Filesystem Size Used Avail Capacity Mounted on
/dev/ad4s1a 248M 213M 14M 94% /
devfs 1.0K 1.0K 0B 100% /dev
procfs 4.0K 4.0K 0B 100% /proc
/dev/mirror/gm0s1d 989M 200M 710M 22% /var
/dev/mirror/gm0s1e 496M 1.7M 454M 0% /tmp
/dev/ad4s1f 2.9G 1.4G 1.3G 52% /usr
/dev/mirror/gm0s1g 268G 105G 142G 42% /data
/dev/ad4s1h 180G 391M 166G 0% /data2
devfs 1.0K 1.0K 0B 100% /var/named/dev
- Rudy
From owner-freebsd-stable@FreeBSD.ORG Tue Nov 18 22:59:36 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id E07D91065670
for <stable@freebsd.org>; Tue, 18 Nov 2008 22:59:36 +0000 (UTC)
(envelope-from jille@quis.cx)
Received: from istud.quis.cx (ip83-113-174-82.adsl2.static.versatel.nl
[82.174.113.83])
by mx1.freebsd.org (Postfix) with ESMTP id 95D638FC18
for <stable@freebsd.org>; Tue, 18 Nov 2008 22:59:36 +0000 (UTC)
(envelope-from jille@quis.cx)
Received: from [192.168.1.4] (ille [192.168.1.4])
by istud.quis.cx (Postfix) with ESMTP id B6AF85C19;
Tue, 18 Nov 2008 23:44:11 +0100 (CET)
Message-ID: <4923453A.5070206@quis.cx>
Date: Tue, 18 Nov 2008 23:44:10 +0100
From: Jille Timmermans <jille@quis.cx>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Rudy <crapsh@monkeybrains.net>
References: <49233FE0.3000805@monkeybrains.net>
In-Reply-To: <49233FE0.3000805@monkeybrains.net>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: stable@freebsd.org
Subject: Re: "df" locked up after upgrade to FreeBSD 7.1-PRERELEASE
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Nov 2008 22:59:37 -0000
Are there 'broken' (lost connection without being umounted) NFS mounts
by any chance ?
That would cause df to wait for eternity (or till the host comes back up).
-- Jille
Rudy schreef:
>
> Has anyone see the 'df' command just hang after an upgrade?
> From another terminal, I saw df in the 'D' state when running ps.
>
> I tried 'df &' in my new terminal, and that too just hung out in the
> background.
> typing 'reboot' fixed the problem. =)
>
> This box had been up for a while, no problems. The only thing I changed
> was a 7.0 to 7.1 upgrade.
> (Haven't rebuilt all the ports to match the new OS, yet....)
>
>> uname -v
> FreeBSD 7.1-PRERELEASE #0: Thu Nov 13 19:14:42 PST 2008
> root@example.monkeybrains.net:/usr/obj/usr/src/sys/MONKEY
> (MONKEY is pretty close to generic, just some ethernet and scsi stuff
> left out)
>
>> kldstat
> Id Refs Address Size Name
> 1 7 0xc0400000 4d39fc kernel
> 2 1 0xc08d4000 164e8 geom_mirror.ko
> 3 1 0xc3e93000 9000 if_bridge.ko
> 4 1 0xc3e9c000 6000 bridgestp.ko
> 5 1 0xc3f78000 5000 if_tap.ko
> 6 1 0xc3fdd000 3000 daemon_saver.ko
>
>> df -h
> Filesystem Size Used Avail Capacity Mounted on
> /dev/ad4s1a 248M 213M 14M 94% /
> devfs 1.0K 1.0K 0B 100% /dev
> procfs 4.0K 4.0K 0B 100% /proc
> /dev/mirror/gm0s1d 989M 200M 710M 22% /var
> /dev/mirror/gm0s1e 496M 1.7M 454M 0% /tmp
> /dev/ad4s1f 2.9G 1.4G 1.3G 52% /usr
> /dev/mirror/gm0s1g 268G 105G 142G 42% /data
> /dev/ad4s1h 180G 391M 166G 0% /data2
> devfs 1.0K 1.0K 0B 100% /var/named/dev
>
>
>
> - Rudy
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
From owner-freebsd-stable@FreeBSD.ORG Tue Nov 18 23:15:00 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id B96B0106567D
for <stable@freebsd.org>; Tue, 18 Nov 2008 23:15:00 +0000 (UTC)
(envelope-from crapsh@monkeybrains.net)
Received: from ape.monkeybrains.net (mail.monkeybrains.net [208.69.40.9])
by mx1.freebsd.org (Postfix) with ESMTP id 9FDB08FC08
for <stable@freebsd.org>; Tue, 18 Nov 2008 23:15:00 +0000 (UTC)
(envelope-from crapsh@monkeybrains.net)
Received: from [192.168.2.105] (adsl-76-203-175-18.dsl.pltn13.sbcglobal.net
[76.203.175.18]) (authenticated bits=0)
by ape.monkeybrains.net (8.14.1/8.14.1) with ESMTP id mAINEGZw019491
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
Tue, 18 Nov 2008 15:14:17 -0800 (PST)
(envelope-from crapsh@monkeybrains.net)
Message-ID: <49234C6F.7070000@monkeybrains.net>
Date: Tue, 18 Nov 2008 15:14:55 -0800
From: Rudy <crapsh@monkeybrains.net>
User-Agent: Thunderbird 2.0.0.17 (X11/20080925)
MIME-Version: 1.0
To: Jille Timmermans <jille@quis.cx>
References: <49233FE0.3000805@monkeybrains.net> <4923453A.5070206@quis.cx>
In-Reply-To: <4923453A.5070206@quis.cx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV version 0.94,
clamav-milter version 0.94 on pita.monkeybrains.net
X-Virus-Status: Clean
Cc: stable@freebsd.org
Subject: Re: "df" locked up after upgrade to FreeBSD 7.1-PRERELEASE
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Nov 2008 23:15:00 -0000
Jille Timmermans wrote:
> Are there 'broken' (lost connection without being umounted) NFS mounts
> by any chance ?
> That would cause df to wait for eternity (or till the host comes back up).
>
Doh! I have the FreeBSD source on one server and mount over NFS for
builds. I thought I'd already rebooted into the new kernel thus
unmounting /usr/src, but I must have remounted (maybe when I ran
mergemaster (or something!))!!!
Thanks,
Rudy
From owner-freebsd-stable@FreeBSD.ORG Tue Nov 18 23:18:42 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 083B31065678
for <stable@freebsd.org>; Tue, 18 Nov 2008 23:18:42 +0000 (UTC)
(envelope-from subhro.kar@gmail.com)
Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.182])
by mx1.freebsd.org (Postfix) with ESMTP id CD0C08FC16
for <stable@freebsd.org>; Tue, 18 Nov 2008 23:18:41 +0000 (UTC)
(envelope-from subhro.kar@gmail.com)
Received: by wa-out-1112.google.com with SMTP id m34so1703326wag.27
for <stable@freebsd.org>; Tue, 18 Nov 2008 15:18:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:message-id:date:from:to
:subject:in-reply-to:mime-version:content-type
:content-transfer-encoding:content-disposition:references;
bh=UAwMXbB5Ifkgz2fReqFJvhpTubN2DirdqSZ9ICFKOjI=;
b=MRXByLrerEs3llEMZZyMh92VSQ6WB+MP5uAiHcydeoNiiw8ex+2rT4EZQ82/0lQZWR
yMprXZxe82j8Q119fPIFLEDGXh/FhGGFuJ6LiO44Q8jly5M6CuIWUOGi0K05ygO1K4J+
rqLW9COW+UgZgcrhWNQxVTILGMcxCvexQDH4c=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=message-id:date:from:to:subject:in-reply-to:mime-version
:content-type:content-transfer-encoding:content-disposition
:references;
b=Uzj3ZwAPhJ1sL2y/1CPd6iY1oh7A0hjSWWP+zWaY/hB8+V600lylGQXBD4XogEIdBm
Ged/1pwougiPzaE//YgUVSnwN1j/u6NVZ5faYt6uIS67Nd3m2XBMbSTVtwuHJ2GGjbiO
3U+W9LnCnpWk4sA6kCIqRQ6wwaQxEBJnadlis=
Received: by 10.115.89.1 with SMTP id r1mr236754wal.84.1227048513087;
Tue, 18 Nov 2008 14:48:33 -0800 (PST)
Received: by 10.114.15.4 with HTTP; Tue, 18 Nov 2008 14:48:33 -0800 (PST)
Message-ID: <b2807d040811181448l51ed79ei4aa38fa0aab84982@mail.gmail.com>
Date: Wed, 19 Nov 2008 04:18:33 +0530
From: Subhro <subhro.kar@gmail.com>
To: Rudy <crapsh@monkeybrains.net>, stable@freebsd.org
In-Reply-To: <49233FE0.3000805@monkeybrains.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <49233FE0.3000805@monkeybrains.net>
Cc:
Subject: Re: "df" locked up after upgrade to FreeBSD 7.1-PRERELEASE
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Nov 2008 23:18:42 -0000
Is there anything NFS related to the box? If yes, then it could be
because of some hung mounts.
Thanks
Subhro
On 11/19/08, Rudy <crapsh@monkeybrains.net> wrote:
>
> Has anyone see the 'df' command just hang after an upgrade?
> From another terminal, I saw df in the 'D' state when running ps.
>
> I tried 'df &' in my new terminal, and that too just hung out in the
> background.
> typing 'reboot' fixed the problem. =)
>
> This box had been up for a while, no problems. The only thing I changed
> was a 7.0 to 7.1 upgrade.
> (Haven't rebuilt all the ports to match the new OS, yet....)
>
> > uname -v
> FreeBSD 7.1-PRERELEASE #0: Thu Nov 13 19:14:42 PST 2008
> root@example.monkeybrains.net:/usr/obj/usr/src/sys/MONKEY
> (MONKEY is pretty close to generic, just some ethernet and scsi stuff
> left out)
>
> > kldstat
> Id Refs Address Size Name
> 1 7 0xc0400000 4d39fc kernel
> 2 1 0xc08d4000 164e8 geom_mirror.ko
> 3 1 0xc3e93000 9000 if_bridge.ko
> 4 1 0xc3e9c000 6000 bridgestp.ko
> 5 1 0xc3f78000 5000 if_tap.ko
> 6 1 0xc3fdd000 3000 daemon_saver.ko
>
> > df -h
> Filesystem Size Used Avail Capacity Mounted on
> /dev/ad4s1a 248M 213M 14M 94% /
> devfs 1.0K 1.0K 0B 100% /dev
> procfs 4.0K 4.0K 0B 100% /proc
> /dev/mirror/gm0s1d 989M 200M 710M 22% /var
> /dev/mirror/gm0s1e 496M 1.7M 454M 0% /tmp
> /dev/ad4s1f 2.9G 1.4G 1.3G 52% /usr
> /dev/mirror/gm0s1g 268G 105G 142G 42% /data
> /dev/ad4s1h 180G 391M 166G 0% /data2
> devfs 1.0K 1.0K 0B 100% /var/named/dev
>
>
>
> - Rudy
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
>
--
Subhro Kar
Software Engineer
Dynamic Digital Technologies Pvt. Ltd.
EPY-3, Sector: V
Salt Lake City
700091
India
From owner-freebsd-stable@FreeBSD.ORG Tue Nov 18 23:38:23 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id C9BF01065674
for <freebsd-stable@freebsd.org>; Tue, 18 Nov 2008 23:38:23 +0000 (UTC)
(envelope-from nakal@web.de)
Received: from fmmailgate02.web.de (fmmailgate02.web.de [217.72.192.227])
by mx1.freebsd.org (Postfix) with ESMTP id 575C38FC13
for <freebsd-stable@freebsd.org>; Tue, 18 Nov 2008 23:38:23 +0000 (UTC)
(envelope-from nakal@web.de)
Received: from smtp07.web.de (fmsmtp07.dlan.cinetic.de [172.20.5.215])
by fmmailgate02.web.de (Postfix) with ESMTP id 49426F6D1FCF
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 00:38:22 +0100 (CET)
Received: from [217.236.6.209] (helo=zelda.local)
by smtp07.web.de with asmtp (TLSv1:AES256-SHA:256)
(WEB.DE 4.109 #226) id 1L2a9F-0000nP-00
for freebsd-stable@freebsd.org; Wed, 19 Nov 2008 00:38:22 +0100
Date: Wed, 19 Nov 2008 00:38:20 +0100
From: Martin <nakal@web.de>
To: freebsd-stable@freebsd.org
Message-ID: <20081119003820.2bea8117@zelda.local>
X-Mailer: Claws Mail 3.6.0 (GTK+ 2.12.11; amd64-portbld-freebsd7.1)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: nakal@web.de
X-Sender: nakal@web.de
X-Provags-ID: V01U2FsdGVkX180OOKDkvHAfebWCEDlbj5i4S+o1yfChs17Wnes
AsdU+CrNzRlO9wLX6pZ15NQ799ZP/CphoR98MMdsr0iR+JHhIj zBpAw1qyo=
Subject: syslogd starting earlier network scripts
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Nov 2008 23:38:23 -0000
Hi,
I have a weird situation here on 7-PRERELEASE since a longer time. When
I enable IPv6, syslogd tries to start before the network is being
initialised and I get the following output:
Mounting local file systems:.
hw.snd.default_unit: 0 -> 1
Setting hostname: zelda.local.
Creating and/or trimming log files:.
Starting syslogd.
Nov 18 16:01:27 syslogd: bind: Can't assign requested address
Nov 18 16:01:27 syslogd: bind: Can't assign requested address
syslogd: child pid 226 exited with return code 1
Checking for core dump on /dev/ad0s1b.eli...
savecore: error reading last dump header at offset 8589930496
in /dev/ad0s1b.eli : Invalid argument
savecore: no dumps found
Initial amd64 initialization:.
Additional ABI support: linux.
re0: link state changed to DOWN
re0: no link ....re0: link state changed to UP
got link
re0: link state changed to DOWN
DHCPREQUEST on re0 to 255.255.255.255 port 67
re0: link state changed to UP
DHCPACK from 192.168.0.1
re0: link state changed to DOWN
re0: link state changed to UP
bound to 192.168.0.12 -- renewal in 180000 seconds.
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4
inet 127.0.0.1 netmask 0xff000000
re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu
1500
options=389b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_UCAST ,WOL_MCAST,WOL_MAGIC>
ether xxxxxxxxxxxxxx
inet6 xxxxxxxxxxxxx%re0 prefixlen 64 scopeid 0x1
inet 192.168.0.12 netmask 0xffffff00 broadcast 192.168.0.255
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
Starting pflog.
pflog0: promiscuous mode enabled
Enabling pf.
[...]
At the moment, I'm using a workaround and start syslogd once again
in /etc/rc.local.
Here my rc.conf:
pf_enable="YES"
pflog_enable="YES"
pflog_logfile="/var/log/pflog"
hostname="xxxxxxxxxxxxxx"
defaultrouter="192.168.0.1"
ipv6_enable="YES"
ipv6_defaultrouter="xxxxxxxxxxxxxxxxx"
ipv6_ifconfig_re0="xxxxxxxxxxxxxxxxxx"
nfs_client_enable="YES"
ifconfig_re0="DHCP"
amd_enable="YES"
amd_flags="-d xxxxxxxxxx -a /.amd_mnt -l syslog /net /etc/amd.map"
keymap="german.iso"
keyrate="fast"
font8x14="iso15-8x14"
font8x16="iso15-8x16"
font8x8="iso15-8x8"
gdm_enable="YES"
hald_enable="YES"
cupsd_enable="YES"
dbus_enable="YES"
linux_enable="YES"
moused_ums0_enable="YES"
ntpd_enable="YES"
ntpd_config="/etc/ntp.conf"
polkitd_enable="YES"
smartd_enable="YES"
sshd_enable="YES"
hcsecd_enable="YES"
sdpd_enable="YES"
geli_devices="ad0s1g"
dumpdev="/dev/ad0s1b.eli"
bsdstats_enable="YES"
Is it a bug in the rc start script sequence or wrong configuration?
--
Martin
From owner-freebsd-stable@FreeBSD.ORG Tue Nov 18 23:18:37 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 8ABF91065796
for <stable@freebsd.org>; Tue, 18 Nov 2008 23:18:37 +0000 (UTC)
(envelope-from rameshayyagari@yahoo.com)
Received: from n27.bullet.mail.mud.yahoo.com (n27.bullet.mail.mud.yahoo.com
[68.142.206.222])
by mx1.freebsd.org (Postfix) with SMTP id 461D58FC13
for <stable@freebsd.org>; Tue, 18 Nov 2008 23:18:37 +0000 (UTC)
(envelope-from rameshayyagari@yahoo.com)
Received: from [209.191.108.96] by n27.bullet.mail.mud.yahoo.com with NNFMP;
18 Nov 2008 23:05:12 -0000
Received: from [68.142.201.243] by t3.bullet.mud.yahoo.com with NNFMP;
18 Nov 2008 23:05:12 -0000
Received: from [127.0.0.1] by omp404.mail.mud.yahoo.com with NNFMP;
18 Nov 2008 23:05:12 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 877493.81486.bm@omp404.mail.mud.yahoo.com
Received: (qmail 37171 invoked by uid 60001); 18 Nov 2008 23:05:12 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Message-ID;
b=oEKKDL5D7bxA3nTAbn4a76wg06fFgJzMfl74uPtp+wEOKMz3wF33AAeVnGQNIaqJ1wGu2ZdwZbxglbTc5frvMYAlGOIE6xVek83peLaGo5IIKqkStXL5HAS0TWYKEGt2rQHd7qBCcWpjG//rqULw1etF33fJ0cUNKGAU8ChzeMQ=;
X-YMail-OSG: dLKHbyMVM1kv10TLwnQEVKOjtVEsVFKMasmichOdRghr1lFQ8eJm46DkKX_vCiuxOSvJ3lwKPaTL2qwD5Iq8CzdLWsVLqmzgqgMxKTytZq.03AerN8Gg7.pudoPwbGKsldiInXA-
Received: from [168.61.10.145] by web111109.mail.gq1.yahoo.com via HTTP;
Tue, 18 Nov 2008 15:05:12 PST
X-Mailer: YahooMailRC/1155.32 YahooMailWebService/0.7.260.1
Date: Tue, 18 Nov 2008 15:05:12 -0800 (PST)
From: Ramesh Ayyagari <rameshayyagari@yahoo.com>
To: stable@freebsd.org
MIME-Version: 1.0
Message-ID: <436595.20263.qm@web111109.mail.gq1.yahoo.com>
X-Mailman-Approved-At: Wed, 19 Nov 2008 00:59:57 +0000
Content-Type: text/plain; charset=us-ascii
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
Cc:
Subject: What would be the appropriate value for kern.maxfiles
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Nov 2008 23:18:37 -0000
Hello All,
I have my client system running FreeBSD 6.3-RELEASE-p1 with 4 GB of RAM. This morning i have the following errors popping up on the console log -
postfix/qmgr[94057]: fatal: socket: Too many open files
Googling for this error, I found this is someway related to the kernel parameter kern.maxflies and increasing this value can have errors go away. The present value of this parameter is 24000. I also found this also depends of the RAM we have on the system.
what would the appropriate value for kern.maxfiles for a system having 2GB RAM, a system having 4 GB and a system having 16GB of RAM. Please help
-Ram
From owner-freebsd-stable@FreeBSD.ORG Wed Nov 19 03:14:06 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 440D51065670
for <stable@freebsd.org>; Wed, 19 Nov 2008 03:14:06 +0000 (UTC)
(envelope-from glen.j.barber@gmail.com)
Received: from mu-out-0910.google.com (mu-out-0910.google.com [209.85.134.186])
by mx1.freebsd.org (Postfix) with ESMTP id BD2298FC0C
for <stable@freebsd.org>; Wed, 19 Nov 2008 03:14:05 +0000 (UTC)
(envelope-from glen.j.barber@gmail.com)
Received: by mu-out-0910.google.com with SMTP id i2so3362880mue.3
for <stable@freebsd.org>; Tue, 18 Nov 2008 19:14:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:message-id:date:from:to
:subject:cc:in-reply-to:mime-version:content-type
:content-transfer-encoding:content-disposition:references;
bh=A4allmXErerdjXWkIssoakNqXVFR+IPDyz6GAJO6TFY=;
b=EbAOq0M50nn2wU5sAGRMzp75LgrcsTOwcOPPg8ZdPFZvTQtxbEhhK52PBFPs2Q+VEq
KH9MxRDq3yvNEISWZVWIGpo4b3kDr7ALqN4fP4TES7lyoos1CKhPAwkXwUnYIX21n/FV
BNmJ7eYOu9MRGbyn+M+VGm9yrruScsvBmNCbg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
:content-type:content-transfer-encoding:content-disposition
:references;
b=egSOa1ZeweC7S7fvcT+OYFy2MrQ5V4uFNMyR/IxJk3oMSov+wSbtNXQRGLp7V76CnH
BWbuih6FQVEcXJWz+GrjLu5Y2YmjvKTIrkqwIh3rPg5zHlBxkvLK5tMexVmCVtEK2kI9
bb23iwxZR1xNJ8ZOsi+pzS3eNVNTKa/c8Hkzs=
Received: by 10.103.160.10 with SMTP id m10mr203575muo.50.1227062636439;
Tue, 18 Nov 2008 18:43:56 -0800 (PST)
Received: by 10.103.169.16 with HTTP; Tue, 18 Nov 2008 18:43:56 -0800 (PST)
Message-ID: <4ad871310811181843v14e57474t8441b465dcb1ec99@mail.gmail.com>
Date: Tue, 18 Nov 2008 21:43:56 -0500
From: "Glen Barber" <glen.j.barber@gmail.com>
To: "Ramesh Ayyagari" <rameshayyagari@yahoo.com>
In-Reply-To: <436595.20263.qm@web111109.mail.gq1.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <436595.20263.qm@web111109.mail.gq1.yahoo.com>
Cc: stable@freebsd.org
Subject: Re: What would be the appropriate value for kern.maxfiles
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Nov 2008 03:14:06 -0000
On Tue, Nov 18, 2008 at 6:05 PM, Ramesh Ayyagari
<rameshayyagari@yahoo.com> wrote:
> Hello All,
>
> I have my client system running FreeBSD 6.3-RELEASE-p1 with 4 GB of RAM. This morning i have the following errors popping up on the console log -
>
> postfix/qmgr[94057]: fatal: socket: Too many open files
>
> Googling for this error, I found this is someway related to the kernel parameter kern.maxflies and increasing this value can have errors go away. The present value of this parameter is 24000. I also found this also depends of the RAM we have on the system.
>
> what would the appropriate value for kern.maxfiles for a system having 2GB RAM, a system having 4 GB and a system having 16GB of RAM. Please help
>
The Xorg meta-package recommends 'kern.maxfiles="25000"' for a desktop
system. This is a situation where it really depends on what you're
using your system for.
HTH
--
Glen Barber
570.328.0318
"If you have any trouble sounding condescending, find a Unix user to
show you how it's done."
--Scott Adams
From owner-freebsd-stable@FreeBSD.ORG Wed Nov 19 03:54:21 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@FreeBSD.ORG
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 791F9106564A
for <freebsd-stable@FreeBSD.ORG>; Wed, 19 Nov 2008 03:54:21 +0000 (UTC)
(envelope-from ganbold@micom.mng.net)
Received: from publicd.ub.mng.net (publicd.ub.mng.net [202.179.0.88])
by mx1.freebsd.org (Postfix) with ESMTP id 2859A8FC12
for <freebsd-stable@FreeBSD.ORG>; Wed, 19 Nov 2008 03:54:21 +0000 (UTC)
(envelope-from ganbold@micom.mng.net)
Received: from [202.179.0.164] (helo=daemon.micom.mng.net)
by publicd.ub.mng.net with esmtpa (Exim 4.69 (FreeBSD))
(envelope-from <ganbold@micom.mng.net>) id 1L2NGI-000IU2-EZ
for freebsd-stable@FreeBSD.ORG; Tue, 18 Nov 2008 17:52:46 +0800
Message-ID: <4922906D.4060805@micom.mng.net>
Date: Tue, 18 Nov 2008 17:52:45 +0800
From: Ganbold <ganbold@micom.mng.net>
User-Agent: Thunderbird 2.0.0.12 (X11/20080415)
MIME-Version: 1.0
To: freebsd-stable@FreeBSD.ORG
X-Enigmail-Version: 0.95.6
OpenPGP: id=78F6425E
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc:
Subject: shutdown -p now crashes
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Nov 2008 03:54:21 -0000
Hi,
Few hours ago I have updated my machine to latest RELENG_7.
daemon% uname -an
FreeBSD daemon.micom.mng.net 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #6:
Tue Nov 18 02:05:57 ULAT 2008
tsgan@daemon.micom.mng.net:/usr/obj/usr/src/sys/GDAEMON i386
daemon%
When I try to issue command shutdown -p now, system paniced.
...
(kgdb) where
#0 doadump () at pcpu.h:196
#1 0xc062ba67 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418
#2 0xc062bd72 in panic (fmt=Variable "fmt" is not available.
) at /usr/src/sys/kern/kern_shutdown.c:574
#3 0xc06ab8b3 in vput (vp=0xc3d11ac8) at /usr/src/sys/kern/vfs_subr.c:2202
#4 0xc06a69e6 in dounmount (mp=0xc3e59b30, flags=524288, td=0xc3b31d20)
at /usr/src/sys/kern/vfs_mount.c:1288
#5 0xc06aa493 in vfs_unmountall () at /usr/src/sys/kern/vfs_subr.c:2939
#6 0xc062b7f4 in boot (howto=16392) at
/usr/src/sys/kern/kern_shutdown.c:400
#7 0xc062bc17 in reboot (td=0xc3b31d20, uap=0xeef55cfc) at
/usr/src/sys/kern/kern_shutdown.c:172
#8 0xc08171f5 in syscall (frame=0xeef55d38) at
/usr/src/sys/i386/i386/trap.c:1090
#9 0xc07fd710 in Xint0x80_syscall () at
/usr/src/sys/i386/i386/exception.s:255
#10 0x00000033 in ?? ()
(kgdb)
...
Is this known issue?
thanks,
Ganbold
--
Yeah, but you're taking the universe out of context.
From owner-freebsd-stable@FreeBSD.ORG Wed Nov 19 05:03:09 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id C57771065672
for <stable@freebsd.org>; Wed, 19 Nov 2008 05:03:09 +0000 (UTC)
(envelope-from zbeeble@gmail.com)
Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.30])
by mx1.freebsd.org (Postfix) with ESMTP id 71D558FC17
for <stable@freebsd.org>; Wed, 19 Nov 2008 05:03:09 +0000 (UTC)
(envelope-from zbeeble@gmail.com)
Received: by yx-out-2324.google.com with SMTP id 8so1381580yxb.13
for <stable@freebsd.org>; Tue, 18 Nov 2008 21:03:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:message-id:date:from:to
:subject:in-reply-to:mime-version:content-type:references;
bh=zGLnX5xiC1KmB0hpFSvO2mRuoxaeUy4IsLiFNZSYdN4=;
b=C86USf1wbcx1RfM/SML/VmmQzBk6UxMu/xQZziTFvHYXyzkdfvFPKATIzziqowgluB
MUspt11cbQEKTy911pKRbGfQixRYw9Kqaiyv7DTubc/SHvCYwiArpmu4/BkFhRyquD1G
+8wEBRwn2k5kPXAy4OInZ6WrFAj4oq2RPhX3g=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=message-id:date:from:to:subject:in-reply-to:mime-version
:content-type:references;
b=WhlipF9JCnLlhOL7CsB4/S2RFZzVkoUcxoSCs33yLihmH1/k3dspA1I3xo5aA0rShy
paPETYcUzweN58qQFzl4QMyiRcgMwJbDlCDPGy7a3wX1bIAoQSfkzXyN+DzqGW/7ddKP
Tkg042tQ4zaBpISi1jV4ZdMrx0+uWy9Qtl3G0=
Received: by 10.151.108.3 with SMTP id k3mr1271070ybm.235.1227069750494;
Tue, 18 Nov 2008 20:42:30 -0800 (PST)
Received: by 10.151.72.7 with HTTP; Tue, 18 Nov 2008 20:42:30 -0800 (PST)
Message-ID: <5f67a8c40811182042n50555d5fqb873efcb9b0343d7@mail.gmail.com>
Date: Tue, 18 Nov 2008 23:42:30 -0500
From: "Zaphod Beeblebrox" <zbeeble@gmail.com>
To: "David Wolfskill" <david@catwhisker.org>,
"Eduardo Meyer" <dudu.meyer@gmail.com>, stable@freebsd.org
In-Reply-To: <20081118214105.GL83287@bunrab.catwhisker.org>
MIME-Version: 1.0
References: <d3ea75b30811181330o61fd850du440d9db0790bf1af@mail.gmail.com>
<20081118214105.GL83287@bunrab.catwhisker.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
Cc:
Subject: Re: tcpdump(1) filter by date
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Nov 2008 05:03:09 -0000
I don't know whether or not this has been fixed, but I found that I had to
recompile tcpslice and/or tcpdump to deal with files larger than 4 gig (or
maybe 2 gig). I suppose it's a better situation than wireshark. After a
few million packets, it falls over because it makes the widgets in the
scroller window for every packet in the file that's visible with the current
filter. The memory from these widgets gets big fast. On a 64 bit machine
... you can analyze a larger file --- and suck down a lot of swap... but on
a 32 bit machine, you run out of address space quickly.
On Tue, Nov 18, 2008 at 4:41 PM, David Wolfskill <david@catwhisker.org>wrote:
> [Cross-post to -questions elided, since I saw the message on -stable,
> and I'd like to discourage gratuitous cross-posting. dhw]
>
> On Tue, Nov 18, 2008 at 07:30:39PM -0200, Eduardo Meyer wrote:
> > Hello,
> >
> > I have a kind big tcpdump file, which has data from the last week. I
> > want to dump information based on date. Can I do it without generating
> > a full output and later parse the headers?
>
> See the port net/tcpslice.
>
> Here's an excerpt from its man page:
>
> DESCRIPTION
> Tcpslice is a program for extracting portions of packet-trace
> files
> generated using tcpdump(l)'s -w flag. It can also be used to
> merge
> together several such files, as discussed below.
> ...
> There are a number of ways to specify times. The first is using
> Unix
> timestamps of the form sssssssss.uuuuuu (this is the format
> specified
> by tcpdump's -tt flag). For example, 654321098.7654 specifies 38
> sec-
> onds and 765,400 microseconds after 8:51PM PDT, Sept. 25, 1990.
>
> > ...
>
> Peace,
> david
> --
> David H. Wolfskill david@catwhisker.org
> Depriving a girl or boy of an opportunity for education is evil.
>
> See http://www.catwhisker.org/~david/publickey.gpg<http://www.catwhisker.org/%7Edavid/publickey.gpg>for my public key.
>
From owner-freebsd-stable@FreeBSD.ORG Wed Nov 19 07:07:44 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 58757106564A
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 07:07:44 +0000 (UTC)
(envelope-from nakal@web.de)
Received: from fmmailgate01.web.de (fmmailgate01.web.de [217.72.192.221])
by mx1.freebsd.org (Postfix) with ESMTP id 15F578FC17
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 07:07:44 +0000 (UTC)
(envelope-from nakal@web.de)
Received: from smtp08.web.de (fmsmtp08.dlan.cinetic.de [172.20.5.216])
by fmmailgate01.web.de (Postfix) with ESMTP id A19D8F9B2A8C
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 08:07:42 +0100 (CET)
Received: from [217.236.30.212] (helo=zelda.local)
by smtp08.web.de with asmtp (TLSv1:AES256-SHA:256)
(WEB.DE 4.109 #226) id 1L2hA6-0004Cj-00
for freebsd-stable@freebsd.org; Wed, 19 Nov 2008 08:07:42 +0100
Date: Wed, 19 Nov 2008 08:07:41 +0100
From: Martin <nakal@web.de>
To: freebsd-stable@freebsd.org
Message-ID: <20081119080741.6197009a@zelda.local>
In-Reply-To: <20081119003820.2bea8117@zelda.local>
References: <20081119003820.2bea8117@zelda.local>
X-Mailer: Claws Mail 3.6.0 (GTK+ 2.12.11; amd64-portbld-freebsd7.1)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: nakal@web.de
X-Sender: nakal@web.de
X-Provags-ID: V01U2FsdGVkX1/+zo+AHeRJCCd4gBdLxtLUMR4AmJvq7N0P3bXj
wkjGHK5TqK3nO5HmfHonLZ0ZxzU+UFBtBls+nn0oz1GymyR4Oi 1q7lM7wBk=
Subject: Re: syslogd starting earlier than network scripts
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Nov 2008 07:07:44 -0000
Hi,
I've made a mistake in the subject line. Sorry.
--
Martin
From owner-freebsd-stable@FreeBSD.ORG Wed Nov 19 08:29:12 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 0D2D2106564A
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 08:29:12 +0000 (UTC)
(envelope-from kamikaze@bsdforen.de)
Received: from mail.bsdforen.de (bsdforen.de [212.204.60.79])
by mx1.freebsd.org (Postfix) with ESMTP id C12E58FC13
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 08:29:11 +0000 (UTC)
(envelope-from kamikaze@bsdforen.de)
Received: from mobileKamikaze.norad (vpn-cl-165-217.rz.uni-karlsruhe.de
[141.3.165.217])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(No client certificate requested)
by mail.bsdforen.de (Postfix) with ESMTP id A85328A00D1
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 09:05:51 +0100 (CET)
Message-ID: <4923C8D4.2000109@bsdforen.de>
Date: Wed, 19 Nov 2008 09:05:40 +0100
From: Dominic Fandrey <kamikaze@bsdforen.de>
User-Agent: Thunderbird 2.0.0.17 (X11/20080927)
MIME-Version: 1.0
To: freebsd-stable@freebsd.org
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: u3g and ubsa
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Nov 2008 08:29:12 -0000
I have recently been pointed to the u3g driver and gave it a try,
because UBSA works very unreliable for me.
- In combination with PF-NAT I get kernel panics under high load.
- I have to hack some buffer sizes in the driver to get the full
3G speed.
- Often my USB-3G stick is not detected, sometimes I spent several
minutes plugging it in and out until it is detected.
- It doesn't let me use the card reader in the stick.
The u3g driver has NONE of these problems. Everything just works
for me.
So obviously I would like to have u3g in stable and chose for
myself or even take support for devices out of ubsa that work
better with u3g.
From owner-freebsd-stable@FreeBSD.ORG Wed Nov 19 08:54:58 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 829CE106564A
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 08:54:58 +0000 (UTC)
(envelope-from admin@kkip.pl)
Received: from mainframe.kkip.pl (kkip.pl [87.105.164.78])
by mx1.freebsd.org (Postfix) with ESMTP id 2DF8F8FC13
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 08:54:58 +0000 (UTC)
(envelope-from admin@kkip.pl)
Received: from admin.admin.lan.kkip.pl ([10.66.3.254])
by mainframe.kkip.pl with esmtpsa (TLSv1:AES256-SHA:256)
(Exim 4.69 (FreeBSD)) (envelope-from <admin@kkip.pl>)
id 1L2ipq-0007eA-Qp
for freebsd-stable@freebsd.org; Wed, 19 Nov 2008 09:54:57 +0100
Message-ID: <4923D460.5020900@kkip.pl>
Date: Wed, 19 Nov 2008 09:54:56 +0100
From: Bartosz Stec <admin@kkip.pl>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: FreeBSD Stable <freebsd-stable@freebsd.org>
References: <20081109174303.GA5146@ourbrains.org> <20081109184349.GG51239@server.vk2pj.dyndns.org> <4920D879.3070806@jrv.org>
<20081117050441.GA16855@ourbrains.org> <20081118175210.GA3753@hyperion.scode.org> <20081119001742.GA21835@ourbrains.org>
<49235D86.4050106@modulus.org> <86bpwcp1d8.fsf@ds4.des.no>
In-Reply-To: <86bpwcp1d8.fsf@ds4.des.no>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Authenticated-User: admin@kkip.pl
X-Authenticator: plain
X-Sender-Verify: SUCCEEDED (sender exists & accepts mail)
X-Spam-Score: -8.9
X-Spam-Score-Int: -88
X-Exim-Version: 4.69 (build at 01-Nov-2008 10:39:57)
X-Date: 2008-11-19 09:54:57
X-Connected-IP: 10.66.3.254:1749
X-Message-Linecount: 45
X-Body-Linecount: 32
X-Message-Size: 1530
X-Body-Size: 774
X-Received-Count: 1
X-Recipient-Count: 1
X-Local-Recipient-Count: 1
X-Local-Recipient-Defer-Count: 0
X-Local-Recipient-Fail-Count: 0
Subject: Re: Will XFS be adopted
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Nov 2008 08:54:58 -0000
Dag-Erling Smørgrav pisze:
> Andrew Snow <andrew@modulus.org> writes:
>
>> [...] I would wait until it has been considered stable and moved into
>> the 7-STABLE tree before deploying a production server.
>>
>
> ZFS has been in 7 for over a year.
>
> DES
>
Yes, it's in STABLE, however zfs module says:
This module (opensolaris) contains code covered by the
Common Development and Distribution License (CDDL)
see http://opensolaris.org/os/licensing/opensolaris_license/
*WARNING: ZFS is considered to be an experimental feature in FreeBSD.*
So ZFS in 7.X should not be considered as STABLE for now.
--
Bartosz Stec
AUXILIA Spółka z o.o.
ul. Wałbrzyska 43/2
52-314 Wrocław
tel. (71) 79 99 760 w. 69
GSM: 662171775
E-Mail: admin@kkip.pl
From owner-freebsd-stable@FreeBSD.ORG Wed Nov 19 09:04:12 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id D4AD71065670
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 09:04:12 +0000 (UTC)
(envelope-from igor.lyapin@gmail.com)
Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.24])
by mx1.freebsd.org (Postfix) with ESMTP id 3EC308FC1A
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 09:04:11 +0000 (UTC)
(envelope-from igor.lyapin@gmail.com)
Received: by qw-out-2122.google.com with SMTP id 9so1787312qwb.7
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 01:04:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:message-id:date:from:to
:subject:cc:in-reply-to:mime-version:content-type:references;
bh=AVbI2L2ig8C3Xc7CoWxSa584EoSjjP9OGbRmVNHpqMY=;
b=k3fXlsEdvgeaFJ3mN4zZvQDfo8mz5fPKq7kIgG22PjAdm61z8+aBewlKu8NdH+xodn
tTyUUm/aaIp+bRFBfebGJn3gYvkI0PWVE2QxazdKPwqKk2Yo7i+8ZiEBPqZZdsE++RKG
P6cdSJ6XY8Y8nJeV6BGuOOPSjEhPG51poHFZs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
:content-type:references;
b=qcfp/TIcoF9iqdPw8n+iJ94fet3X1kx4HwtepgjjcUMBNsv4ehNRDYKd1r4y9T6Wa0
RS/Tp7e0wANmhcg5SSCpV2kdrEqPRC7xOTpmX1pVCibctu5Hte8JG/k0PcZBsdEqe18B
8tbKvsnIcMtv7pfrtGCXA8a25HzGZ9I8G02hM=
Received: by 10.215.101.10 with SMTP id d10mr848972qam.225.1227085450384;
Wed, 19 Nov 2008 01:04:10 -0800 (PST)
Received: by 10.214.43.11 with HTTP; Wed, 19 Nov 2008 01:04:10 -0800 (PST)
Message-ID: <fd2a4c1f0811190104k60e3288w9a77e1a78d51ad6c@mail.gmail.com>
Date: Wed, 19 Nov 2008 12:04:10 +0300
From: "Igor Lyapin" <igor.lyapin@gmail.com>
To: "Tomas Randa" <randa@blueboard.cz>
In-Reply-To: <4923D17A.6070209@blueboard.cz>
MIME-Version: 1.0
References: <fd2a4c1f0811180637m6ee44d4fv4cf97d18e322ca5a@mail.gmail.com>
<49234CFF.4010207@blueboard.cz>
<fd2a4c1f0811182137n5c5ac427x15975b3c43038917@mail.gmail.com>
<4923D17A.6070209@blueboard.cz>
Content-Type: text/plain; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
Cc: freebsd-stable@freebsd.org
Subject: Re: High system in %system load .
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Nov 2008 09:04:12 -0000
I have only one CPU: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
(2400.10-MHz K8-class CPU)
Origin =3D "GenuineIntel" Id =3D 0x6fb Stepping =3D 11
Features=3D0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,
This is from systat -v and this behavior is not the same as yours, CSW
during problems could be from normal 8k -11k CSW some time rise to 57k for =
a
1-2 sec but system load ~30% in system and 10-20 process in block state
process.
---------------------------------------------------------------------------=
------------------------
3 users Load 1.45 1.95 1.77 Nov 19 11:58
Mem:KB REAL VIRTUAL VN PAGER SWAP
PAGER
Tot Share Tot Share Free in out in
out
Act 1363876 17076 4175592 31032 273076 count
All 1412996 20628 8683036 74448 pages
Proc: Interrupts
r p d s w Csw Trp Sys Int Sof Flt 44 cow 9096 total
1 19 251 14k 13k 29k 1100 272 12k 12707 zfod ata0
irq14
ozfod 210
atapci1 19
29.5%Sys 0.6%Intr 5.1%User 0.0%Nice 64.8%Idle %ozfod 2012 cpu0:
time
| | | | | | | | | | | daefr 890 bge0
256
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D>>> =
353 prcfr 2012 cpu1:
time
162 dtbuf 12807 totfr 1986 cpu3:
time
Namei Name-cache Dir-cache 100000 desvn react 1986 cpu2:
time
Calls hits % hits % 80638 numvn pdwak
99564 99060 99 308 0 25001 frevn pdpgs
intrn
Disks ad4 ad6 ad10 ar0 505820 wire
KB/t 0.00 0.00 0.00 12.46 1359456 act
tps 0 0 0 53 1880952 inact
MB/s 0.00 0.00 0.00 0.65 115104 cache
%busy 0 0 0 7 157972 free
---------------------------------------------------------------------------=
--------
On Wed, Nov 19, 2008 at 11:42 AM, Tomas Randa <randa@blueboard.cz> wrote:
> I think that ULE from 7.0 is not good enough...
> My problem was at 2x quad xeon (total 8 CPUS), where sometime system load
> increased to number 100-150 (normal was 1-4). When I look at systat -v,
> there was many CSW (about 300k, instead od 10k at normal).
> I tried many things -
>
> move from i386 to amd64 - same behaviour
> upgrade from 7.0 to 7.1BETA1 - better behaviour, but another problems..
> when I switched from ULE to 4BSD, situation get worse.
> So I tried remove one CPU and it helps!...
> My opinion is, that FeeBSD scheduler in some situations (apache/php) do
> some cycle, which rapidly increase CSW.
>
> Try to look at CSW, when your problem occurs and write me a message
>
> Regards
>
> Tom=E1=9A Randa, Hosting Blueboard.cz
> ----------------------------------
> Jabber: ares@jabber.cz
> ICQ: 100956181
> Tel: +420 245 008 678
> GSM: +420 775 086 575
>
>
>
>
>
> Igor Lyapin wrote:
>
>> On Wed, Nov 19, 2008 at 2:17 AM, Tomas Randa - Hosting Blueboard CZ <
>> tomas@blueboard.cz> wrote:
>>
>>
>>
>>> Hello,
>>>
>>> I have similar problem... what HW are you using? Some quad core xeon? O=
ne
>>> or two CPUS?
>>> I think it is scheduler based problem. Try to look at systat -v and wat=
ch
>>> CSW value at normal state and then if problem occurs..
>>>
>>>
>>
>> Context switches do not rise and in problem and normal state is about
>> 8000-
>> 12000
>>
>>
>>
>>> Are you using 4BSD, aren`t you? Did you try ULE?
>>>
>>>
>>
>> I try ULE and 4BSD problem steel exists.
>>
>>
>>
>>
>>
>>> Send dmesg...
>>>
>>>
>>
>> #dmesg
>> All buffers synced.
>> Copyright (c) 1992-2008 The FreeBSD Project.
>> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
>> The Regents of the University of California. All rights reserved.
>> FreeBSD is a registered trademark of The FreeBSD Foundation.
>> FreeBSD 7.0-RELEASE-p5 #0: Mon Nov 10 19:49:07 MSK 2008
>> root@i.x00.net:/usr/obj/usr/
>>
>>
>>> src/sys/KERNEL-4BSD
>>> Timecounter "i8254" frequency 1193182 Hz quality 0
>>> CPU: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz (2400.10-MHz
>>> K8-class
>>> CPU)
>>> Origin =3D "GenuineIntel" Id =3D 0x6fb Stepping =3D 11
>>>
>>>
>>>
>>> Features=3D0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,=
PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
>>> Features2=3D0xe3bd<SSE3,RSVD2,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,P=
DCM>
>>> AMD Features=3D0x20100800<SYSCALL,NX,LM>
>>> AMD Features2=3D0x1<LAHF>
>>> Cores per package: 4
>>> usable memory =3D 4283449344 (4085 MB)
>>> avail memory =3D 4134977536 (3943 MB)
>>> ACPI APIC Table: <022108 APIC2247>
>>> FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
>>> cpu0 (BSP): APIC ID: 0
>>> cpu1 (AP): APIC ID: 1
>>> cpu2 (AP): APIC ID: 2
>>> cpu3 (AP): APIC ID: 3
>>> ioapic0 <Version 2.0> irqs 0-23 on motherboard
>>> kbd1 at kbdmux0
>>> hptrr: HPT RocketRAID controller driver v1.1 (Nov 10 2008 19:48:39)
>>> acpi0: <022108 RSDT2247> on motherboard
>>> acpi0: [ITHREAD]
>>> acpi0: Power Button (fixed)
>>> acpi0: reservation of 0, a0000 (3) failed
>>> acpi0: reservation of 100000, eff00000 (3) failed
>>> Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
>>> acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
>>> cpu0: <ACPI CPU> on acpi0
>>> est0: <Enhanced SpeedStep Frequency Control> on cpu0
>>> est: CPU supports Enhanced Speedstep, but is not recognized.
>>> est: cpu_vendor GenuineIntel, msr 928092806000928
>>> device_attach: est0 attach returned 6
>>> p4tcc0: <CPU Frequency Thermal Control> on cpu0
>>> cpu1: <ACPI CPU> on acpi0
>>> est1: <Enhanced SpeedStep Frequency Control> on cpu1
>>> est: CPU supports Enhanced Speedstep, but is not recognized.
>>> est: cpu_vendor GenuineIntel, msr 928092806000928
>>> device_attach: est1 attach returned 6
>>> p4tcc1: <CPU Frequency Thermal Control> on cpu1
>>> cpu2: <ACPI CPU> on acpi0
>>> est2: <Enhanced SpeedStep Frequency Control> on cpu2
>>> est: CPU supports Enhanced Speedstep, but is not recognized.
>>> est: cpu_vendor GenuineIntel, msr 928092806000928
>>> device_attach: est2 attach returned 6
>>> p4tcc2: <CPU Frequency Thermal Control> on cpu2
>>> cpu3: <ACPI CPU> on acpi0
>>> est3: <Enhanced SpeedStep Frequency Control> on cpu3
>>> est: CPU supports Enhanced Speedstep, but is not recognized.
>>> est: cpu_vendor GenuineIntel, msr 928092806000928
>>> device_attach: est3 attach returned 6
>>> p4tcc3: <CPU Frequency Thermal Control> on cpu3
>>> pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
>>> pci0: <ACPI PCI bus> on pcib0
>>> pcib1: <ACPI PCI-PCI bridge> irq 16 at device 1.0 on pci0
>>> pci5: <ACPI PCI bus> on pcib1
>>> pcib2: <ACPI PCI-PCI bridge> irq 16 at device 28.0 on pci0
>>> pci2: <ACPI PCI bus> on pcib2
>>> pcib3: <ACPI PCI-PCI bridge> irq 16 at device 28.4 on pci0
>>> pci3: <ACPI PCI bus> on pcib3
>>> bge0: <Broadcom NetXtreme Gigabit Ethernet Controller, ASIC rev. 0x4201=
>
>>> mem
>>> 0xfeaf0000-0xfeafffff irq 16 at device 0.0 on pci3
>>> miibus0: <MII bus> on bge0
>>> brgphy0: <BCM5750 10/100/1000baseTX PHY> PHY 1 on miibus0
>>> brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,
>>> 1000baseT-FDX, auto
>>> bge0: Ethernet address: 00:1f:c6:48:c8:9b
>>> bge0: [ITHREAD]
>>> pcib4: <ACPI PCI-PCI bridge> irq 17 at device 28.5 on pci0
>>> pci4: <ACPI PCI bus> on pcib4
>>> bge1: <Broadcom NetXtreme Gigabit Ethernet Controller, ASIC rev. 0x4201=
>
>>> mem
>>> 0xfebf0000-0xfebfffff irq 17 at device 0.0 on pci4
>>> miibus1: <MII bus> on bge1
>>> brgphy1: <BCM5750 10/100/1000baseTX PHY> PHY 1 on miibus1
>>> brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,
>>> 1000baseT-FDX, auto
>>> bge1: Ethernet address: 00:1f:c6:48:ca:b7
>>> bge1: [ITHREAD]
>>> pcib5: <ACPI PCI-PCI bridge> at device 30.0 on pci0
>>> pci1: <ACPI PCI bus> on pcib5
>>> vgapci0: <VGA-compatible display> port 0xec00-0xec7f mem
>>> 0xf8000000-0xfbffffff,0xfe9c0000-0xfe9fffff at device 4.0 on pci1
>>> isab0: <PCI-ISA bridge> at device 31.0 on pci0
>>> isa0: <ISA bus> on isab0
>>> atapci0: <Intel ICH7 UDMA100 controller> port
>>> 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 31.1 on pci=
0
>>> ata0: <ATA channel 0> on atapci0
>>> ata0: [ITHREAD]
>>> ata1: <ATA channel 1> on atapci0
>>> ata1: [ITHREAD]
>>> atapci1: <Intel ICH7 SATA300 controller> port
>>> 0xdc00-0xdc07,0xd880-0xd883,0xd800-0xd807,0xd480-0xd483,0xd400-0xd40f m=
em
>>> 0xfe8ffc00-0xfe8fffff irq 19 at device 31.2 on pci0
>>> atapci1: [ITHREAD]
>>> atapci1: AHCI called from vendor specific driver
>>> atapci1: AHCI Version 01.10 controller with 4 ports detected
>>> ata2: <ATA channel 0> on atapci1
>>> ata2: [ITHREAD]
>>> ata3: <ATA channel 1> on atapci1
>>> ata3: [ITHREAD]
>>> ata4: <ATA channel 2> on atapci1
>>> ata4: [ITHREAD]
>>> ata5: <ATA channel 3> on atapci1
>>> ata5: [ITHREAD]
>>> pci0: <serial bus, SMBus> at device 31.3 (no driver attached)
>>> acpi_button0: <Power Button> on acpi0
>>> orm0: <ISA Option ROM> at iomem 0xc0000-0xc7fff on isa0
>>> atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
>>> atkbd0: <AT Keyboard> irq 1 on atkbdc0
>>> kbd0 at atkbd0
>>> atkbd0: [GIANT-LOCKED]
>>> atkbd0: [ITHREAD]
>>> sc0: <System console> at flags 0x100 on isa0
>>> sc0: VGA <16 virtual consoles, flags=3D0x300>
>>> sio0: configured irq 4 not in bitmap of probed irqs 0
>>> sio0: port may not be enabled
>>> sio0: configured irq 4 not in bitmap of probed irqs 0
>>> sio0: port may not be enabled
>>> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
>>> sio0: type 8250 or not responding
>>> sio0: [FILTER]
>>> sio1: configured irq 3 not in bitmap of probed irqs 0
>>> sio1: port may not be enabled
>>> vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on is=
a0
>>> Timecounters tick every 1.000 msec
>>> ipfw2 (+ipv6) initialized, divert loadable, rule-based forwarding
>>> disabled,
>>> default to accept, logging limited to 5 packets/entry by default
>>> hptrr: no controller detected.
>>> acd0: DVDR <MATSHITADVD-RAM UJ-860S/1.00> at ata0-master UDMA33
>>> ad4: 476940MB <Seagate ST3500320NS SN05> at ata2-master SATA300
>>> ad6: 476940MB <Seagate ST3500320NS SN05> at ata3-master SATA300
>>> ad10: 476940MB <Seagate ST3500320NS SN05> at ata5-master SATA300
>>> ar0: 476937MB <Intel MatrixRAID RAID1> status: READY
>>> ar0: disk0 READY (master) using ad4 at ata2-master
>>> ar0: disk1 READY (mirror) using ad6 at ata3-master
>>> SMP: AP CPU #1 Launched!
>>> SMP: AP CPU #3 Launched!
>>> SMP: AP CPU #2 Launched!
>>> Trying to mount root from ufs:/dev/ar0s1a
>>> bge0: link state changed to UP
>>>
>>>
>>>
>>
>>
>>
>>> Tomas Randa
>>>
>>>
>>> Igor Lyapin wrote:
>>>
>>>
>>>
>>>> Hello
>>>> Got strange problem with high system "%system load" and very slow user
>>>> level
>>>> programs (apache+php+mysql) behavior
>>>> gstat shows 1.5-4% hard disk busy load but system shows about 20-30%
>>>> load
>>>> while user load is max 5%.
>>>> vmstat shows from 2 to 35 process in "b" state.
>>>> Now use 7.0-RELEASE-p5 , but the same problem was with 7.0-RELEASE.
>>>> And have no idea what to do with this.
>>>>
>>>>
>>>>
>>>> -------------------------------------------------------------------
>>>> #uname -a
>>>> FreeBSD i.x00.net 7.0-RELEASE-p5 FreeBSD 7.0-RELEASE-p5 #0: Mon Nov 10
>>>> 19:49:07 MSK 2008 root@i.x00.net:/usr/obj/usr/src/sys/KERNEL-4BSD
>>>> amd64
>>>> -------------------------------------------------------------------
>>>> #top
>>>>
>>>> last pid: 47964; load averages: 1.26, 1.62, 1.75 u=
p
>>>> 0+19:17:13 17:11:06
>>>> 287 processes: 10 running, 277 sleeping
>>>> CPU states: 2.2% user, 0.0% nice, 28.3% system, 0.2% interrupt, 69.=
3%
>>>> idle
>>>> Mem: 1286M Active, 1729M Inact, 478M Wired, 131M Cache, 214M Buf, 302M
>>>> Free
>>>> Swap: 8192M Total, 8192M Free
>>>> -------------------------------------------------------------------
>>>> #vmstat 5
>>>>
>>>> procs memory page disks faults c=
pu
>>>> r b w avm fre flt re pi po fr sr ad4 ad6 in sy =
cs
>>>> us
>>>> sy id
>>>> 1 24 0 4357672 419648 10598 1 0 0 10648 34 0 0 558 25212
>>>> 9072
>>>> 6 15 80
>>>> 1 29 0 4365116 414892 3060 0 0 0 2780 0 0 0 975 12270
>>>> 11501
>>>> 3 29 68
>>>> 1 25 0 4392488 408596 14142 0 0 0 13903 0 0 0 526 16696
>>>> 10389
>>>> 6 30 64
>>>> -------------------------------------------------------------------
>>>> #ps ax | grep " [DLW] "
>>>> 45585 ?? D 0:04.68 /usr/local/sbin/httpd
>>>> 45975 ?? D 0:04.92 /usr/local/sbin/httpd
>>>> 45981 ?? D 0:29.91 /usr/local/sbin/httpd
>>>> 45995 ?? D 0:23.99 /usr/local/sbin/httpd
>>>> 46019 ?? D 0:26.76 /usr/local/sbin/httpd
>>>> 46160 ?? D 0:18.89 /usr/local/sbin/httpd
>>>> 46287 ?? D 0:19.88 /usr/local/sbin/httpd
>>>> 46303 ?? D 0:05.14 /usr/local/sbin/httpd
>>>> 46307 ?? D 0:29.15 /usr/local/sbin/httpd
>>>> 46398 ?? D 0:09.18 /usr/local/sbin/httpd
>>>> 46617 ?? D 0:02.00 /usr/local/sbin/httpd
>>>> 46767 ?? D 0:05.26 /usr/local/sbin/httpd
>>>> 46771 ?? D 0:02.07 /usr/local/sbin/httpd
>>>> 46803 ?? D 0:30.51 /usr/local/sbin/httpd
>>>> 46807 ?? D 0:01.34 /usr/local/sbin/httpd
>>>> 46889 ?? D 0:01.35 /usr/local/sbin/httpd
>>>> 47659 ?? D 0:01.54 /usr/local/sbin/httpd
>>>> 47711 ?? D 0:00.92 /usr/local/sbin/httpd
>>>> 47849 ?? D 0:01.00 /usr/local/sbin/httpd
>>>> 47877 ?? D 0:00.40 /usr/local/sbin/httpd
>>>> -------------------------------------------------------------------
>>>>
>>>>
>>>> -------------------------------------------------------------------
>>>> cat ./KERNEL-4BSD | grep -v "^#"
>>>>
>>>> cpu HAMMER
>>>> ident KERNEL-4BSD
>>>>
>>>>
>>>> options SCHED_4BSD # 4BSD scheduler
>>>> options PREEMPTION # Enable kernel thread
>>>> preemption
>>>> options INET # InterNETworking
>>>> options INET6 # IPv6 communications protocol=
s
>>>> options SCTP # Stream Control Transmission
>>>> Protocol
>>>> options FFS # Berkeley Fast Filesystem
>>>> options SOFTUPDATES # Enable FFS soft updates
>>>> support
>>>> options UFS_ACL # Support for access control
>>>> lists
>>>> options UFS_DIRHASH # Improve performance on big
>>>> directories
>>>> options UFS_GJOURNAL # Enable gjournal-based UFS
>>>> journaling
>>>> options MD_ROOT # MD is a potential root devic=
e
>>>> options MSDOSFS # MSDOS Filesystem
>>>> options CD9660 # ISO 9660 Filesystem
>>>> options PROCFS # Process filesystem (requires
>>>> PSEUDOFS)
>>>> options PSEUDOFS # Pseudo-filesystem framework
>>>> options GEOM_PART_GPT # GUID Partition Tables.
>>>> options GEOM_LABEL # Provides labelization
>>>> options COMPAT_43TTY # BSD 4.3 TTY compat [KEEP
>>>> THIS!]
>>>> options COMPAT_IA32 # Compatible with i386 binarie=
s
>>>> options COMPAT_FREEBSD4 # Compatible with FreeBSD4
>>>> options COMPAT_FREEBSD5 # Compatible with FreeBSD5
>>>> options COMPAT_FREEBSD6 # Compatible with FreeBSD6
>>>> options SCSI_DELAY=3D5000 # Delay (in ms) before probi=
ng
>>>> SCSI
>>>> options KTRACE # ktrace(1) support
>>>> options SYSVSHM # SYSV-style shared memory
>>>> options SYSVMSG # SYSV-style message queues
>>>> options SYSVSEM # SYSV-style semaphores
>>>> options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time
>>>> extensions
>>>> options KBD_INSTALL_CDEV # install a CDEV entry in /dev
>>>> options ADAPTIVE_GIANT # Giant mutex is adaptive.
>>>> options STOP_NMI # Stop CPUS using NMI instead =
of
>>>> IPI
>>>> options AUDIT # Security event auditing
>>>>
>>>>
>>>> options SMP # Symmetric MultiProcessor
>>>> Kernel
>>>>
>>>> options IPFIREWALL
>>>> options IPFIREWALL_VERBOSE
>>>> options IPFIREWALL_VERBOSE_LIMIT=3D5
>>>> options IPFIREWALL_DEFAULT_TO_ACCEPT
>>>>
>>>> options QUOTA
>>>>
>>>> device cpufreq
>>>>
>>>> device acpi
>>>> device pci
>>>>
>>>> device fdc
>>>>
>>>> device ata
>>>> device atadisk # ATA disk drives
>>>> device ataraid # ATA RAID drives
>>>> device atapicd # ATAPI CDROM drives
>>>> options ATA_STATIC_ID # Static device numbering
>>>>
>>>> device ahc # AHA2940 and onboard AIC7xxx devices
>>>> options AHC_REG_PRETTY_PRINT # Print register bitfields in
>>>> debug
>>>> # output. Adds ~128k to driver.
>>>> device ahd # AHA39320/29320 and onboard AIC79xx
>>>> devices
>>>> options AHD_REG_PRETTY_PRINT # Print register bitfields in
>>>> debug
>>>> # output. Adds ~215k to driver.
>>>> device amd # AMD 53C974 (Tekram DC-390(T))
>>>> device hptiop # Highpoint RocketRaid 3xxx series
>>>> device isp # Qlogic family
>>>> device mpt # LSI-Logic MPT-Fusion
>>>> device sym # NCR/Symbios Logic (newer chipsets +
>>>> those
>>>> of `ncr')
>>>> device trm # Tekram DC395U/UW/F DC315U adapters
>>>>
>>>> device adv # Advansys SCSI adapters
>>>> device adw # Advansys wide SCSI adapters
>>>> device aic # Adaptec 15[012]x SCSI adapters,
>>>> AIC-6[23]60.
>>>> device bt # Buslogic/Mylex MultiMaster SCSI
>>>> adapters
>>>>
>>>>
>>>> device scbus # SCSI bus (required for SCSI)
>>>> device ch # SCSI media changers
>>>> device da # Direct Access (disks)
>>>> device sa # Sequential Access (tape etc)
>>>> device cd # CD
>>>> device pass # Passthrough device (direct SCSI
>>>> access)
>>>> device ses # SCSI Environmental Services (and
>>>> SAF-TE)
>>>>
>>>> device amr # AMI MegaRAID
>>>> device arcmsr # Areca SATA II RAID
>>>> device ciss # Compaq Smart RAID 5*
>>>> device dpt # DPT Smartcache III, IV - See NOTES f=
or
>>>> options
>>>> device hptmv # Highpoint RocketRAID 182x
>>>> device hptrr # Highpoint RocketRAID 17xx, 22xx, 23x=
x,
>>>> 25xx
>>>> device iir # Intel Integrated RAID
>>>> device ips # IBM (Adaptec) ServeRAID
>>>> device mly # Mylex AcceleRAID/eXtremeRAID
>>>> device twa # 3ware 9000 series PATA/SATA RAID
>>>>
>>>> device aac # Adaptec FSA RAID
>>>> device aacp # SCSI passthrough for aac (requires
>>>> CAM)
>>>> device ida # Compaq Smart RAID
>>>> device mfi # LSI MegaRAID SAS
>>>> device mlx # Mylex DAC960 family
>>>> device twe # 3ware ATA RAID
>>>>
>>>> device atkbdc # AT keyboard controller
>>>> device atkbd # AT keyboard
>>>> device psm # PS/2 mouse
>>>>
>>>> device kbdmux # keyboard multiplexer
>>>>
>>>> device vga # VGA video card driver
>>>>
>>>> device splash # Splash screen and screen saver suppo=
rt
>>>>
>>>> device sc
>>>>
>>>> device agp # support several AGP chipsets
>>>>
>>>>
>>>> device sio # 8250, 16[45]50 based serial ports
>>>> device uart # Generic UART driver
>>>>
>>>>
>>>>
>>>> device de # DEC/Intel DC21x4x (``Tulip'')
>>>> device em # Intel PRO/1000 adapter Gigabit
>>>> Ethernet
>>>> Card
>>>> device ixgb # Intel PRO/10GbE Ethernet Card
>>>> device le # AMD Am7900 LANCE and Am79C9xx PCnet
>>>> device txp # 3Com 3cR990 (``Typhoon'')
>>>> device vx # 3Com 3c590, 3c595 (``Vortex'')
>>>>
>>>> device miibus # MII bus support
>>>> device bce # Broadcom BCM5706/BCM5708 Gigabit
>>>> Ethernet
>>>> device bfe # Broadcom BCM440x 10/100 Ethernet
>>>> device bge # Broadcom BCM570xx Gigabit Ethernet
>>>> device dc # DEC/Intel 21143 and various workalik=
es
>>>> device fxp # Intel EtherExpress PRO/100B (82557,
>>>> 82558)
>>>> device lge # Level 1 LXT1001 gigabit Ethernet
>>>> device msk # Marvell/SysKonnect Yukon II Gigabit
>>>> Ethernet
>>>> device nfe # nVidia nForce MCP on-board Ethernet
>>>> device nge # NatSemi DP83820 gigabit Ethernet
>>>> device pcn # AMD Am79C97x PCI 10/100 (precedence
>>>> over
>>>> 'le')
>>>> device re # RealTek 8139C+/8169/8169S/8110S
>>>> device rl # RealTek 8129/8139
>>>> device sf # Adaptec AIC-6915 (``Starfire'')
>>>> device sis # Silicon Integrated Systems SiS 900/S=
iS
>>>> 7016
>>>> device sk # SysKonnect SK-984x & SK-982x gigabit
>>>> Ethernet
>>>> device ste # Sundance ST201 (D-Link DFE-550TX)
>>>> device ti # Alteon Networks Tigon I/II gigabit
>>>> Ethernet
>>>> device tl # Texas Instruments ThunderLAN
>>>> device tx # SMC EtherPower II (83c170 ``EPIC'')
>>>> device vge # VIA VT612x gigabit Ethernet
>>>> device vr # VIA Rhine, Rhine II
>>>> device wb # Winbond W89C840F
>>>> device xl # 3Com 3c90x (``Boomerang'',
>>>> ``Cyclone'')
>>>>
>>>>
>>>>
>>>> device loop # Network loopback
>>>> device random # Entropy device
>>>> device ether # Ethernet support
>>>> device sl # Kernel SLIP
>>>> device ppp # Kernel PPP
>>>> device tun # Packet tunnel.
>>>> device pty # Pseudo-ttys (telnet etc)
>>>> device md # Memory "disks"
>>>> device gif # IPv6 and IPv4 tunneling
>>>> device faith # IPv6-to-IPv4 relaying (translation)
>>>> device firmware # firmware assist module
>>>>
>>>> device bpf # Berkeley packet filter
>>>>
>>>> device uhci # UHCI PCI->USB interface
>>>> device ohci # OHCI PCI->USB interface
>>>> device ehci # EHCI PCI->USB interface (USB 2.0)
>>>> device usb # USB Bus (required)
>>>> device ugen # Generic
>>>> device uhid # "Human Interface Devices"
>>>> device ukbd # Keyboard
>>>> device umass # Disks/Mass storage - Requires scbus
>>>> and
>>>> da
>>>> device ums # Mouse
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>
>>
>>
>
--=20
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited. If you received
this in error, please contact the sender and delete the material from any
computer.
From owner-freebsd-stable@FreeBSD.ORG Wed Nov 19 09:06:02 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 055C51065675
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 09:06:02 +0000 (UTC)
(envelope-from kometen@gmail.com)
Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.27])
by mx1.freebsd.org (Postfix) with ESMTP id 84C938FC0C
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 09:06:01 +0000 (UTC)
(envelope-from kometen@gmail.com)
Received: by ey-out-2122.google.com with SMTP id 6so1317279eyi.7
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 01:06:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:message-id:date:from:to
:subject:cc:in-reply-to:mime-version:content-type
:content-transfer-encoding:content-disposition:references;
bh=Ku62eUzttAPyEHaJ97xva5sZpBQ5AKA+tuikL4l7DaI=;
b=wfd2CSwl2MzAqhMrgpvCxJfPdAM2rNpA4GKMxDLP/xTXWNGVcRSYTqFWBD/OIJHukK
JLusBvlyxstl+0LDBdoEuVkmJZ31sDoRODheE9hUwZW9Ih4DEViYtioUaJIMYlBmID4S
iKFVdjWQ34wzZOe9Wbsm3nt0M1DyOaMJkgh1g=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
:content-type:content-transfer-encoding:content-disposition
:references;
b=AGOD1bqGni9TLfhYtERI8KvxInF9uzBu3lAMlSAYcgIyC+J0LOtbwZDZfqbFUoPbOS
5EkjKqGqx4uHhOg3m0HxKjMItvR0H5tGV7PLMnRJDtEsV2vwG3nu0xewBGFTxymyhCVi
ao6z8TkEVFMZrUfIMUBqAs3NiFlvQWWLRMPwQ=
Received: by 10.103.117.9 with SMTP id u9mr291347mum.55.1227085560076;
Wed, 19 Nov 2008 01:06:00 -0800 (PST)
Received: by 10.103.249.11 with HTTP; Wed, 19 Nov 2008 01:06:00 -0800 (PST)
Message-ID: <b41c75520811190106w7f951760m95c12358f1008c5b@mail.gmail.com>
Date: Wed, 19 Nov 2008 10:06:00 +0100
From: "Claus Guttesen" <kometen@gmail.com>
To: "Bartosz Stec" <admin@kkip.pl>
In-Reply-To: <4923D460.5020900@kkip.pl>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <20081109174303.GA5146@ourbrains.org>
<20081109184349.GG51239@server.vk2pj.dyndns.org>
<4920D879.3070806@jrv.org> <20081117050441.GA16855@ourbrains.org>
<20081118175210.GA3753@hyperion.scode.org>
<20081119001742.GA21835@ourbrains.org> <49235D86.4050106@modulus.org>
<86bpwcp1d8.fsf@ds4.des.no> <4923D460.5020900@kkip.pl>
Cc: FreeBSD Stable <freebsd-stable@freebsd.org>
Subject: Re: Will XFS be adopted
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Nov 2008 09:06:02 -0000
>>> [...] I would wait until it has been considered stable and moved into
>>> the 7-STABLE tree before deploying a production server.
>>
>> ZFS has been in 7 for over a year.
>>
>> DES
>
> Yes, it's in STABLE, however zfs module says:
>
> This module (opensolaris) contains code covered by the
> Common Development and Distribution License (CDDL)
> see http://opensolaris.org/os/licensing/opensolaris_license/
> *WARNING: ZFS is considered to be an experimental feature in FreeBSD.*
>
> So ZFS in 7.X should not be considered as STABLE for now.
Install a server with zfs and test it. Then let it handle tasks that
are not critical. And if it works for you proceed and deploy it. It's
somewhat difficult to say that it works for your particular workload.
Some have rather positive experience and others are very reluctant.
I use it as an internal samba-server and the issues I have are related
to the external sas-cabinet rather than zfs itself.
--
regards
Claus
When lenity and cruelty play for a kingdom,
the gentler gamester is the soonest winner.
Shakespeare
From owner-freebsd-stable@FreeBSD.ORG Wed Nov 19 09:16:46 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 0E162106564A
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 09:16:46 +0000 (UTC)
(envelope-from jdc@koitsu.dyndns.org)
Received: from QMTA06.emeryville.ca.mail.comcast.net
(qmta06.emeryville.ca.mail.comcast.net [76.96.30.56])
by mx1.freebsd.org (Postfix) with ESMTP id E347D8FC18
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 09:16:45 +0000 (UTC)
(envelope-from jdc@koitsu.dyndns.org)
Received: from OMTA09.emeryville.ca.mail.comcast.net ([76.96.30.20])
by QMTA06.emeryville.ca.mail.comcast.net with comcast
id gxBb1a00B0S2fkCA6xGlya; Wed, 19 Nov 2008 09:16:45 +0000
Received: from koitsu.dyndns.org ([69.181.141.110])
by OMTA09.emeryville.ca.mail.comcast.net with comcast
id gxGk1a0062P6wsM8VxGl5t; Wed, 19 Nov 2008 09:16:45 +0000
X-Authority-Analysis: v=1.0 c=1 a=6fuZhc4rEvsA:10 a=QycZ5dHgAAAA:8
a=ya0qFwzgdmQcORjo6XAA:9 a=y7gby0SN1gQDTqntrW7CbvKkLGUA:4
a=EoioJ0NPDVgA:10 a=LY0hPdMaydYA:10
Received: by icarus.home.lan (Postfix, from userid 1000)
id B9CF133C36; Wed, 19 Nov 2008 01:16:44 -0800 (PST)
Date: Wed, 19 Nov 2008 01:16:44 -0800
From: Jeremy Chadwick <koitsu@FreeBSD.org>
To: Igor Lyapin <igor.lyapin@gmail.com>
Message-ID: <20081119091644.GA81663@icarus.home.lan>
References: <fd2a4c1f0811180637m6ee44d4fv4cf97d18e322ca5a@mail.gmail.com>
<49234CFF.4010207@blueboard.cz>
<fd2a4c1f0811182137n5c5ac427x15975b3c43038917@mail.gmail.com>
<4923D17A.6070209@blueboard.cz>
<fd2a4c1f0811190104k60e3288w9a77e1a78d51ad6c@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <fd2a4c1f0811190104k60e3288w9a77e1a78d51ad6c@mail.gmail.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: Tomas Randa <randa@blueboard.cz>, freebsd-stable@freebsd.org
Subject: Re: High system in %system load .
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Nov 2008 09:16:46 -0000
On Wed, Nov 19, 2008 at 12:04:10PM +0300, Igor Lyapin wrote:
> I have only one CPU: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
> (2400.10-MHz K8-class CPU)
> Origin = "GenuineIntel" Id = 0x6fb Stepping = 11
> Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,
>
> This is from systat -v and this behavior is not the same as yours, CSW
> during problems could be from normal 8k -11k CSW some time rise to 57k for a
> 1-2 sec but system load ~30% in system and 10-20 process in block state
> process.
>
>
> ---------------------------------------------------------------------------------------------------
> 3 users Load 1.45 1.95 1.77 Nov 19 11:58
>
> Mem:KB REAL VIRTUAL VN PAGER SWAP
> PAGER
> Tot Share Tot Share Free in out in
> out
Can you please fix whatever mail client you're using to not wrap lines?
The data you've sent is impossible to read because of this.
--
| Jeremy Chadwick jdc at parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |
From owner-freebsd-stable@FreeBSD.ORG Wed Nov 19 09:29:01 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 231881065678
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 09:29:01 +0000 (UTC)
(envelope-from igor.lyapin@gmail.com)
Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.25])
by mx1.freebsd.org (Postfix) with ESMTP id C1DB68FC0A
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 09:29:00 +0000 (UTC)
(envelope-from igor.lyapin@gmail.com)
Received: by qw-out-2122.google.com with SMTP id 9so1788352qwb.7
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 01:28:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:message-id:date:from:to
:subject:cc:in-reply-to:mime-version:content-type:references;
bh=qSHaqUD2d5MLTc744M+eyaovRX+gtfSYxaMQ93l3svs=;
b=pPWYI4X95yUT9w2HYu+6P/WK41BrOTZKDi32/Pcgfqn95E5W+9g66nZ0e63/iD1C9n
M4SaSo1tcneAWigkIlq2sFr0DZct89ltmkfpXSzX3nlqDyrUfJE3WI3sk0UkU1hx4e6p
W8TiBh0WxoVtYJ0GAOZ7aANZ5MJ+Ad3ckp9Yo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
:content-type:references;
b=dkrKXbT9aYAB9YRMxjYcbNGtmnGsmcGYcGVz5N26JHRupJhhF9SVT5A18Ul+dozVVK
Snf/CTFVfYMN+WZLSJT7fJq5U3YHsWorwvPKTxzHd+mQzvXmXtkvveiYDiN7UZk0s3+w
/Z8SPx2HvKysE7VlK51vPTkJAYydLQ8rFWvTA=
Received: by 10.214.241.10 with SMTP id o10mr826444qah.365.1227086939917;
Wed, 19 Nov 2008 01:28:59 -0800 (PST)
Received: by 10.214.43.11 with HTTP; Wed, 19 Nov 2008 01:28:59 -0800 (PST)
Message-ID: <fd2a4c1f0811190128s3885d458raae1f86b8a138772@mail.gmail.com>
Date: Wed, 19 Nov 2008 12:28:59 +0300
From: "Igor Lyapin" <igor.lyapin@gmail.com>
To: "Jeremy Chadwick" <koitsu@freebsd.org>
In-Reply-To: <20081119091644.GA81663@icarus.home.lan>
MIME-Version: 1.0
References: <fd2a4c1f0811180637m6ee44d4fv4cf97d18e322ca5a@mail.gmail.com>
<49234CFF.4010207@blueboard.cz>
<fd2a4c1f0811182137n5c5ac427x15975b3c43038917@mail.gmail.com>
<4923D17A.6070209@blueboard.cz>
<fd2a4c1f0811190104k60e3288w9a77e1a78d51ad6c@mail.gmail.com>
<20081119091644.GA81663@icarus.home.lan>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
Cc: Tomas Randa <randa@blueboard.cz>, freebsd-stable@freebsd.org
Subject: Re: High system in %system load .
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Nov 2008 09:29:01 -0000
> Can you please fix whatever mail client you're using to not wrap lines?
> The data you've sent is impossible to read because of this.
>
Sorry
3 users Load 1.91 1.87 1.89 Nov 19 12:26
Mem:KB REAL VIRTUAL VN PAGER SWAP
PAGER
Tot Share Tot Share Free in out in out
Act 1369324 17144 4197332 31032 227288 count
All 1419348 21020 8714160 73828 pages
Proc: Interrupts
r p d s w Csw Trp Sys Int Sof Flt 506 cow 9684 total
2 11 268 13k 9371 18k 1684 231 9151 8413 zfod ata0
irq14
ozfod 48 atapci1
19
28.9%Sys 0.5%Intr 4.3%User 0.0%Nice 66.4%Idle %ozfod 2011 cpu0:
time
| | | | | | | | | | | daefr 1636 bge0
256
==============+>> 839 prcfr 2011 cpu1:
time
324 dtbuf 8455 totfr 1989 cpu3:
time
Namei Name-cache Dir-cache 100000 desvn react 1989 cpu2:
time
Calls hits % hits % 82598 numvn pdwak
73493 72895 99 399 1 25001 frevn pdpgs
intrn
Disks ad4 ad6 ad10 ar0 508592 wire
KB/t 0.00 0.00 0.00 15.85 1366208 act
tps 0 0 0 13 1916668 inact
MB/s 0.00 0.00 0.00 0.21 152104 cache
%busy 0 0 0 1 74912 free
219632 buf
--
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited. If you received
this in error, please contact the sender and delete the material from any
computer.
From owner-freebsd-stable@FreeBSD.ORG Wed Nov 19 09:35:44 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 006F91065674
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 09:35:44 +0000 (UTC)
(envelope-from jdc@koitsu.dyndns.org)
Received: from QMTA10.emeryville.ca.mail.comcast.net
(qmta10.emeryville.ca.mail.comcast.net [76.96.30.17])
by mx1.freebsd.org (Postfix) with ESMTP id D3ED38FC13
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 09:35:43 +0000 (UTC)
(envelope-from jdc@koitsu.dyndns.org)
Received: from OMTA09.emeryville.ca.mail.comcast.net ([76.96.30.20])
by QMTA10.emeryville.ca.mail.comcast.net with comcast
id gxYd1a00H0S2fkCAAxbj9e; Wed, 19 Nov 2008 09:35:43 +0000
Received: from koitsu.dyndns.org ([69.181.141.110])
by OMTA09.emeryville.ca.mail.comcast.net with comcast
id gxbi1a0032P6wsM8VxbiDc; Wed, 19 Nov 2008 09:35:43 +0000
X-Authority-Analysis: v=1.0 c=1 a=6fuZhc4rEvsA:10 a=QycZ5dHgAAAA:8
a=VrchJLnL_sU7r4y3GPIA:9 a=AT5Mc13iPOprVwyv3lRQuRX-BzYA:4
a=h1s_zzJdJ8cA:10 a=EoioJ0NPDVgA:10 a=LY0hPdMaydYA:10
Received: by icarus.home.lan (Postfix, from userid 1000)
id 87CED33C36; Wed, 19 Nov 2008 01:35:42 -0800 (PST)
Date: Wed, 19 Nov 2008 01:35:42 -0800
From: Jeremy Chadwick <koitsu@freebsd.org>
To: Igor Lyapin <igor.lyapin@gmail.com>
Message-ID: <20081119093542.GA82078@icarus.home.lan>
References: <fd2a4c1f0811180637m6ee44d4fv4cf97d18e322ca5a@mail.gmail.com>
<49234CFF.4010207@blueboard.cz>
<fd2a4c1f0811182137n5c5ac427x15975b3c43038917@mail.gmail.com>
<4923D17A.6070209@blueboard.cz>
<fd2a4c1f0811190104k60e3288w9a77e1a78d51ad6c@mail.gmail.com>
<20081119091644.GA81663@icarus.home.lan>
<fd2a4c1f0811190128s3885d458raae1f86b8a138772@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <fd2a4c1f0811190128s3885d458raae1f86b8a138772@mail.gmail.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: Tomas Randa <randa@blueboard.cz>, freebsd-stable@freebsd.org
Subject: Re: High system in %system load .
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Nov 2008 09:35:44 -0000
On Wed, Nov 19, 2008 at 12:28:59PM +0300, Igor Lyapin wrote:
> > Can you please fix whatever mail client you're using to not wrap lines?
> > The data you've sent is impossible to read because of this.
> >
> Sorry
> 3 users Load 1.91 1.87 1.89 Nov 19 12:26
>
> Mem:KB REAL VIRTUAL VN PAGER SWAP
> PAGER
> Tot Share Tot Share Free in out in out
> Act 1369324 17144 4197332 31032 227288 count
> All 1419348 21020 8714160 73828 pages
> Proc: Interrupts
> r p d s w Csw Trp Sys Int Sof Flt 506 cow 9684 total
> 2 11 268 13k 9371 18k 1684 231 9151 8413 zfod ata0
> irq14
> ozfod 48 atapci1
> 19
> 28.9%Sys 0.5%Intr 4.3%User 0.0%Nice 66.4%Idle %ozfod 2011 cpu0:
> time
> | | | | | | | | | | | daefr 1636 bge0
> 256
> ==============+>> 839 prcfr 2011 cpu1:
> time
> 324 dtbuf 8455 totfr 1989 cpu3:
> time
> Namei Name-cache Dir-cache 100000 desvn react 1989 cpu2:
> time
> Calls hits % hits % 82598 numvn pdwak
> 73493 72895 99 399 1 25001 frevn pdpgs
> intrn
> Disks ad4 ad6 ad10 ar0 508592 wire
> KB/t 0.00 0.00 0.00 15.85 1366208 act
> tps 0 0 0 13 1916668 inact
> MB/s 0.00 0.00 0.00 0.21 152104 cache
> %busy 0 0 0 1 74912 free
> 219632 buf
These are still hard-wrapped.
--
| Jeremy Chadwick jdc at parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |
From owner-freebsd-stable@FreeBSD.ORG Wed Nov 19 09:55:10 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 38ABF1065677
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 09:55:10 +0000 (UTC)
(envelope-from phk@critter.freebsd.dk)
Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222])
by mx1.freebsd.org (Postfix) with ESMTP id EE5308FC08
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 09:55:09 +0000 (UTC)
(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (unknown [192.168.61.3])
by phk.freebsd.dk (Postfix) with ESMTP id 57D81170E5;
Wed, 19 Nov 2008 09:55:08 +0000 (UTC)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
by critter.freebsd.dk (8.14.3/8.14.3) with ESMTP id mAJ9t6Sc022929;
Wed, 19 Nov 2008 09:55:07 GMT (envelope-from phk@critter.freebsd.dk)
To: Mike Tancsa <mike@sentex.net>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Mon, 17 Nov 2008 01:03:24 EST."
<200811170603.mAH63Q54011870@lava.sentex.ca>
Date: Wed, 19 Nov 2008 09:55:06 +0000
Message-ID: <22928.1227088506@critter.freebsd.dk>
Sender: phk@critter.freebsd.dk
Cc: freebsd-stable@freebsd.org
Subject: Re: fifo log problem
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Nov 2008 09:55:10 -0000
In message <200811170603.mAH63Q54011870@lava.sentex.ca>, Mike Tancsa writes:
>>I could fear that you have two fifologs running at the same time,
>>possibly as a result of syslogd doing something strange on sighup...
>
>There is nothing really strange about the config. Any idea on how to resolve?
Not right now, there is nothing that rings a bell here and I have not
seen it on any of my systems.
As I said, I would fear that the SIGHUB to syslog results in some
weird config where two writers are competing or something like that
but that is purely a guess...
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
From owner-freebsd-stable@FreeBSD.ORG Wed Nov 19 10:16:40 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 85CE11065679
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 10:16:40 +0000 (UTC)
(envelope-from igor.lyapin@gmail.com)
Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.169])
by mx1.freebsd.org (Postfix) with ESMTP id 0FAF88FC24
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 10:16:39 +0000 (UTC)
(envelope-from igor.lyapin@gmail.com)
Received: by ug-out-1314.google.com with SMTP id 30so478452ugs.39
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 02:16:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:date:from:x-priority
:message-id:to:subject:in-reply-to:references:mime-version
:content-type:content-transfer-encoding;
bh=8+KPuUH/h2+6JR+q5eQZAWzrMdFVxCMTaBBfUtlPCIo=;
b=aHP/xf9/bJADXW3xcKOv6Sx1dfBgf1ZynVig/PRTKatSuGPARQTnbdtmPeJBarOG2z
bdaiuwAgHevSnKYtgihvaSte+sog7u18JrUMgelnOE4IYUx7eTIYHestR8862tV2aJMp
UEPL5RfKyzFwMEsuX+NO7Yi5NmK0C+LuaJEKA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=date:from:x-priority:message-id:to:subject:in-reply-to:references
:mime-version:content-type:content-transfer-encoding;
b=fqBfgZ4F0YSEK0HmzRF/H2Bla7urIidczHnq1fXnylAVZRXH+h17tTXVaS89XSgvDz
JwDzTb/YLE+L/P/oOgi4CMvcfBXhnx2nASR9OxR0/XzKtCsk/kyEj2zcAapsaNmeu00v
wUHSNYLXRd2yM41AKmGVS+FZLa9dDtkjikO+I=
Received: by 10.86.79.19 with SMTP id c19mr596325fgb.66.1227089798933;
Wed, 19 Nov 2008 02:16:38 -0800 (PST)
Received: from vk04mg43ialyapi.msk.vek (ns.vek.ru [194.84.13.9])
by mx.google.com with ESMTPS id 12sm900458fgg.0.2008.11.19.02.16.37
(version=TLSv1/SSLv3 cipher=OTHER);
Wed, 19 Nov 2008 02:16:38 -0800 (PST)
Date: Wed, 19 Nov 2008 13:16:34 +0300
From: igor.lyapin@gmail.com
X-Priority: 3 (Normal)
Message-ID: <691372944.20081119131634@gmail.com>
To: freebsd-stable@freebsd.org
In-Reply-To: <gfun0o$lvq$1@ger.gmane.org>
References: <fd2a4c1f0811180637m6ee44d4fv4cf97d18e322ca5a@mail.gmail.com>
<gfun0o$lvq$1@ger.gmane.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: Re[2]: High system in %system load .
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Nov 2008 10:16:40 -0000
Hello Ivan,
> Where is the system busy? For start, try to collect information about
> what are your processes doing - for example from top(1).
4 users Load 1.43 1.46 1.27 Nov 19 13:14
Mem:KB REAL VIRTUAL VN PAGER SWAP PAG=
ER
Tot Share Tot Share Free in out in o=
ut
Act 1367684 15208 4447732 27660 201372 count
All 1424692 26352 9032876 107292 pages
Proc: Interrupts
r p d s w Csw Trp Sys Int Sof Flt 467 cow 9218 total
2 9 282 13k 7775 36k 1218 350 7386 6832 zfod ata0 =
irq14
ozfod 286 atapc=
i1 19
30.3%Sys 0.4%Intr 6.7%User 0.0%Nice 62.6%Idle %ozfod 2014 cpu0:=
time
| | | | | | | | | | | daefr 932 bge0 =
256
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D>>>> =
1337 prcfr 2014 cpu1: time
146 dtbuf 7420 totfr 1986 cpu3:=
time
Namei Name-cache Dir-cache 100000 desvn react 1986 cpu2:=
time
Calls hits % hits % 85727 numvn pdwak
139486 138964 100 300 0 25001 frevn pdpgs
intrn
Disks ad4 ad6 ad10 ar0 503544 wire
KB/t 0.00 0.00 0.00 13.27 1363312 act
tps 0 0 0 73 1949608 inact
MB/s 0.00 0.00 0.00 0.95 168476 cache
%busy 0 0 0 12 32896 free
219632 buf
--=20
Best regards,
Gmail.com =20
From owner-freebsd-stable@FreeBSD.ORG Wed Nov 19 10:24:56 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id B751C1065674
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 10:24:56 +0000 (UTC)
(envelope-from admin@kkip.pl)
Received: from mainframe.kkip.pl (kkip.pl [87.105.164.78])
by mx1.freebsd.org (Postfix) with ESMTP id 5E1108FC19
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 10:24:56 +0000 (UTC)
(envelope-from admin@kkip.pl)
Received: from admin.admin.lan.kkip.pl ([10.66.3.254])
by mainframe.kkip.pl with esmtpsa (TLSv1:AES256-SHA:256)
(Exim 4.69 (FreeBSD)) (envelope-from <admin@kkip.pl>)
id 1L2kEv-00085J-Ga
for freebsd-stable@freebsd.org; Wed, 19 Nov 2008 11:24:55 +0100
Message-ID: <4923E977.8030107@kkip.pl>
Date: Wed, 19 Nov 2008 11:24:55 +0100
From: Bartosz Stec <admin@kkip.pl>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
CC: FreeBSD Stable <freebsd-stable@freebsd.org>
References: <20081109174303.GA5146@ourbrains.org>
<20081109184349.GG51239@server.vk2pj.dyndns.org>
<4920D879.3070806@jrv.org> <20081117050441.GA16855@ourbrains.org>
<20081118175210.GA3753@hyperion.scode.org>
<20081119001742.GA21835@ourbrains.org>
<49235D86.4050106@modulus.org> <86bpwcp1d8.fsf@ds4.des.no>
<4923D460.5020900@kkip.pl>
<b41c75520811190106w7f951760m95c12358f1008c5b@mail.gmail.com>
In-Reply-To: <b41c75520811190106w7f951760m95c12358f1008c5b@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Authenticated-User: admin@kkip.pl
X-Authenticator: plain
X-Sender-Verify: SUCCEEDED (sender exists & accepts mail)
X-Spam-Score: -8.3
X-Spam-Score-Int: -82
X-Exim-Version: 4.69 (build at 01-Nov-2008 10:39:57)
X-Date: 2008-11-19 11:24:55
X-Connected-IP: 10.66.3.254:1849
X-Message-Linecount: 56
X-Body-Linecount: 43
X-Message-Size: 2255
X-Body-Size: 1371
X-Received-Count: 1
X-Recipient-Count: 1
X-Local-Recipient-Count: 1
X-Local-Recipient-Defer-Count: 0
X-Local-Recipient-Fail-Count: 0
Subject: Re: Will XFS be adopted
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Nov 2008 10:24:56 -0000
Claus Guttesen pisze:
>>>> [...] I would wait until it has been considered stable and moved into
>>>> the 7-STABLE tree before deploying a production server.
>>>>
>>> ZFS has been in 7 for over a year.
>>>
>>> DES
>>>
>> Yes, it's in STABLE, however zfs module says:
>>
>> This module (opensolaris) contains code covered by the
>> Common Development and Distribution License (CDDL)
>> see http://opensolaris.org/os/licensing/opensolaris_license/
>> *WARNING: ZFS is considered to be an experimental feature in FreeBSD.*
>>
>> So ZFS in 7.X should not be considered as STABLE for now.
>>
>
> Install a server with zfs and test it. Then let it handle tasks that
> are not critical. And if it works for you proceed and deploy it. It's
> somewhat difficult to say that it works for your particular workload.
> Some have rather positive experience and others are very reluctant.
>
> I use it as an internal samba-server and the issues I have are related
> to the external sas-cabinet rather than zfs itself.
>
>
Well it's not simple indeed. I use ZFS on my home (not critical) box
(RAIDZ1). After 4 weeks uptime with varied workload I assumed it's
stable. Unfortunately ZFS crashed next week ;)
--
Bartosz Stec
AUXILIA Spółka z o.o.
ul. Wałbrzyska 43/2
52-314 Wrocław
tel. (71) 79 99 760 w. 69
GSM: 662171775
E-Mail: admin@kkip.pl
From owner-freebsd-stable@FreeBSD.ORG Wed Nov 19 10:42:31 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id AFB61106564A
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 10:42:31 +0000 (UTC)
(envelope-from freebsd-stable@m.gmane.org)
Received: from ciao.gmane.org (main.gmane.org [80.91.229.2])
by mx1.freebsd.org (Postfix) with ESMTP id 2FF8C8FC12
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 10:42:31 +0000 (UTC)
(envelope-from freebsd-stable@m.gmane.org)
Received: from list by ciao.gmane.org with local (Exim 4.43)
id 1L2kVu-0002nm-7J
for freebsd-stable@freebsd.org; Wed, 19 Nov 2008 10:42:26 +0000
Received: from lara.cc.fer.hr ([161.53.72.113])
by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
id 1AlnuQ-0007hv-00
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 10:42:26 +0000
Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian))
id 1AlnuQ-0007hv-00
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 10:42:26 +0000
X-Injected-Via-Gmane: http://gmane.org/
To: freebsd-stable@freebsd.org
From: Ivan Voras <ivoras@freebsd.org>
Date: Wed, 19 Nov 2008 11:43:09 +0100
Lines: 55
Message-ID: <gg0qi7$v7n$1@ger.gmane.org>
References: <fd2a4c1f0811180637m6ee44d4fv4cf97d18e322ca5a@mail.gmail.com> <gfun0o$lvq$1@ger.gmane.org>
<fd2a4c1f0811180904k396dff47m43d537a07ae87579@mail.gmail.com>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature";
boundary="------------enig6B3D92DE5DE51AF6DA33F1D7"
X-Complaints-To: usenet@ger.gmane.org
X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr
User-Agent: Thunderbird 2.0.0.17 (X11/20080925)
In-Reply-To: <fd2a4c1f0811180904k396dff47m43d537a07ae87579@mail.gmail.com>
X-Enigmail-Version: 0.95.0
Sender: news <news@ger.gmane.org>
Subject: Re: High system in %system load .
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Nov 2008 10:42:31 -0000
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig6B3D92DE5DE51AF6DA33F1D7
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Igor Lyapin wrote:
> I already sent # top head in my first mail
> that's all non idle top process
>=20
> last pid: 56920; load averages: 2.90, 2.25, 1.72 up=
> 0+22:10:12 20:04:05
> 210 processes: 2 running, 207 sleeping, 1 zombie
> CPU states: 8.3% user, 0.0% nice, 32.5% system, 0.3% interrupt, 58.9=
%
> idle
> Mem: 1268M Active, 1904M Inact, 479M Wired, 154M Cache, 214M Buf, 125M =
Free
> Swap: 8192M Total, 8192M Free
>=20
> PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU
> COMMAND
> 55546 www 1 -4 0 198M 24912K ufs 1 0:25 29.39% =
httpd
> 55986 www 1 -4 0 198M 23228K ufs 2 0:08 21.39% =
httpd
> 56030 www 1 -4 0 199M 23400K ufs 1 0:05 11.23% =
httpd
Ok, high sys load in "ufs" state for me was often caused by PHP session
storage. By default, PHP will store all session records in a single
directory, which can grow to monstruous sizes. If this is also your
case, here are some things to try:
a) increase vfs.ufs.dirhash_maxmem to 10 MB or something like that (look
at vfs.ufs.dirhash_mem to see if you're hitting the limit and if so,
monitor it to see what your dirhash_maxmem limit should be)
b) configure PHP to use "sharded" directory structure for sessions.
--------------enig6B3D92DE5DE51AF6DA33F1D7
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFJI+29ldnAQVacBcgRApC1AJ4nm+ZhR++M+H14SFkidstXOO0bnwCeKQck
x5KiLg8QZctkSNc98fKJH5k=
=tBBi
-----END PGP SIGNATURE-----
--------------enig6B3D92DE5DE51AF6DA33F1D7--
From owner-freebsd-stable@FreeBSD.ORG Wed Nov 19 11:26:16 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id F2A1C10656E4;
Wed, 19 Nov 2008 11:26:15 +0000 (UTC)
(envelope-from sebosik@demax.sk)
Received: from mail.demax.sk (mail.demax.sk [213.215.102.234])
by mx1.freebsd.org (Postfix) with ESMTP id 752B28FC14;
Wed, 19 Nov 2008 11:26:15 +0000 (UTC)
(envelope-from sebosik@demax.sk)
Received: from localhost (localhost [127.0.0.1])
by mail.demax.sk (Postfix) with ESMTP id 1B1F0873C2;
Wed, 19 Nov 2008 12:26:14 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at mail.demax.sk
Received: from mail.demax.sk ([127.0.0.1])
by localhost (mail.demax.sk [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id JcajdDRshUUh; Wed, 19 Nov 2008 12:26:14 +0100 (CET)
Received: from [192.168.0.2] (2D204.demax.sk [195.62.17.204])
by mail.demax.sk (Postfix) with ESMTP id E7CB487357;
Wed, 19 Nov 2008 12:26:13 +0100 (CET)
Message-ID: <4923F7D5.8030409@demax.sk>
Date: Wed, 19 Nov 2008 12:26:13 +0100
From: Jan Sebosik <sebosik@demax.sk>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Jeremy Chadwick <koitsu@FreeBSD.org>,
FreeBSD stable <freebsd-stable@freebsd.org>
References: <491F31B5.90403@demax.sk> <4923E5A2.2060402@demax.sk>
<20081119101530.GA82861@icarus.home.lan>
<4923E839.7090001@demax.sk>
<20081119102552.GA83022@icarus.home.lan>
<4923F0A6.9080304@demax.sk>
<20081119112102.GA84963@icarus.home.lan>
In-Reply-To: <20081119112102.GA84963@icarus.home.lan>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc:
Subject: Re: Frebsd 7-STABLE, atapicd, atapicam and Intel errors [SOLVED]
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Nov 2008 11:26:16 -0000
Yeah
I thought also about bios bug... it`s pretty new piece of HW with modern
chipset (Q45). I believe that the next release of BIOS comes soon.
But what about those atapicd problems? Is it related to SATA interface
of DVD/CD drive? Maybe also the LG drive has buggy FW :).
Best regards
Jeremy Chadwick napsal(a):
> On Wed, Nov 19, 2008 at 11:55:34AM +0100, Jan Sebosik wrote:
>> Allright, I`ve played again with an HPET in BIOS little bit.
>>
>> Results ->
>>
>> HPET disabled:
>>
>> kern.timecounter.choice: TSC(-100) ACPI-fast(1000) i8254(0)
>> dummy(-1000000)
>> kern.timecounter.hardware: ACPI-fast
>>
>> HPET enabled:
>>
>> kern.timecounter.choice: TSC(-100) HPET(900) ACPI-fast(1000) i8254(0)
>> dummy(-1000000)
>> kern.timecounter.hardware: ACPI-fast
>>
>>
>> But now FreeBSD boots also with HPET enabled (really don`t understand
>> what`s going on).
>>
>> When I was trying to mount cd with "mount -t cd9660 /dev/cd0 /mnt/cd0",
>> mount works as expected (atapicd module not loaded).
>>
>> Then I`ve kldload-ed atapicd, "mouunt -t cd9660 /dev/acd0 /mnt/cd0"
>> (acd0, not cd0), but this ended with messages like this:
>> unknown: FAILURE - READ_BIG timeout (retry count 0)
>>
>> Temporary I`ve disabled HPET in BIOS (Linux got problems too-> he
>> created gigabytes of log messages in /var/log/messages :D).
>>
>> Best regards, Jan
>>
>> Jeremy Chadwick napsal(a):
>>> On Wed, Nov 19, 2008 at 11:19:37AM +0100, Jan Sebosik wrote:
>>>> Hi
>>>>
>>>> Yeah, I`ve tested it 2 times (switching it in BIOS). To me it seems
>>>> bit mysterious, why there is a relationship between HPET setting and
>>>> acd/cd problems in FreeBSD.
>>>>
>>>>
>>>> Jeremy Chadwick napsal(a):
>>>>> On Wed, Nov 19, 2008 at 11:08:34AM +0100, Jan Sebosik wrote:
>>>>>> Hi again
>>>>>>
>>>>>> so it seems to be a problem with HPET timer which is onboard and
>>>>>> was enabled. If I turned him off, (acd | cd) problems went away.
>>>>>>
>>>>>>
>>>>>> Jan Sebosik napsal(a):
>>>>>>> Hi all
>>>>>>>
>>>>>>> OS: Freebsd 7-STABLE from CVS of today
>>>>>>> Problematic HW: Intel DQ45CB (Q45 chipset, ICH10, SATA in
>>>>>>> native mode, but not AHCI), LG SATA DVD-RW GH20NS15
>>>>>>>
>>>>>>> Problem: if I run freebsd without LG DVD connected to any SATA
>>>>>>> port onboard everything works allright. When I connect SATA
>>>>>>> DVD to board, then freebsd refuses to boot with messages
>>>>>>> similar to those:
>>>>>>>
>>>>>>> acd0: FAILURE-READ_BIG timed out
>>>>>>> unknown: FAILURE-READ_BIG timed out
>>>>>>> cddone: goit error 0x5 back
>>>>>>>
>>>>>>> Messages are repeating forever.
>>>>>>>
>>>>>>> Anybody knows where should be a bug?
>>>>>>> Temporary I`ve disconnected LG SATA burner from system board.
>>>>>>>
>>>>>>> Thanks for any idea.
>>>>>>>
>>>>>>> Best regards
>>>>> Are you ***absolutely 100% certain*** this is true? The time counter
>>>>> selected shouldn't have anything to do with the errors you see.
>>>>> Please thoroughly test this.
>>>>>
>>>>> I'd CC jhb@ to get confirmation of my statement, but I've promised
>>>>> myself I wouldn't bother him until 2009. :-)
>>> This is very bizarre. The errors being returned from acd0 are that an
>>> ATAPI/ATA command (READ_BIG, whatever the code for that is) did not
>>> receive a response from the controller or device within 5 seconds
>>> (assuming the ata(4) timeout values here; it could be something larger
>>> for ATAPI, I don't know). Maybe some a BIOS bug...
>>>
>>> Can you show us output from the following two commands?
>>>
>>> sysctl kern.timecounter.choice
>>> sysctl kern.timecounter.hardware
>>>
>>> Soren, do you know how/if the HPET time counter could cause this oddity?
>>> All of my systems use ACPI-fast, so I can't test this.
>
> What this proves is that disabling HPET in the BIOS makes absolutely no
> change to FreeBSD as far as the timecounter goes. It's still using
> ACPI-fast no matter if HPET is disabled or not. Disabling HPET does
> show up in FreeBSD (as you can tell), but the ATA/ATAPI stuff *should
> not* have some direct tie-in to HPET.
>
> I'm left believing you've found a BIOS bug. Please bring this up with
> your motherboard or system vendor.
>
--
Jan Sebosik, Slovakia
sebosik@demax.sk
From owner-freebsd-stable@FreeBSD.ORG Wed Nov 19 11:31:54 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 43330106568F
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 11:31:54 +0000 (UTC)
(envelope-from sebosik@demax.sk)
Received: from mail.demax.sk (mail.demax.sk [213.215.102.234])
by mx1.freebsd.org (Postfix) with ESMTP id D492B8FC1B
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 11:31:53 +0000 (UTC)
(envelope-from sebosik@demax.sk)
Received: from localhost (localhost [127.0.0.1])
by mail.demax.sk (Postfix) with ESMTP id E3F55873C2
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 12:31:52 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at mail.demax.sk
Received: from mail.demax.sk ([127.0.0.1])
by localhost (mail.demax.sk [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id 8gm69rKngwga for <freebsd-stable@freebsd.org>;
Wed, 19 Nov 2008 12:31:52 +0100 (CET)
Received: from [192.168.0.2] (2D204.demax.sk [195.62.17.204])
by mail.demax.sk (Postfix) with ESMTP id BD72587357
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 12:31:52 +0100 (CET)
Message-ID: <4923F928.8010604@demax.sk>
Date: Wed, 19 Nov 2008 12:31:52 +0100
From: Jan Sebosik <sebosik@demax.sk>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: FreeBSD stable <freebsd-stable@freebsd.org>
References: <491F31B5.90403@demax.sk>
<4923E5A2.2060402@demax.sk> <20081119101530.GA82861@icarus.home.lan> <4923E839.7090001@demax.sk> <20081119102552.GA83022@icarus.home.lan> <4923F0A6.9080304@demax.sk> <20081119112102.GA84963@icarus.home.lan>
<4923F7D5.8030409@demax.sk>
In-Reply-To: <4923F7D5.8030409@demax.sk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: Frebsd 7-STABLE, atapicd, atapicam and Intel errors [SOLVED]
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Nov 2008 11:31:54 -0000
Opps,
bad mailing-list... excuse me.
Jan Sebosik napsal(a):
> Yeah
>
> I thought also about bios bug... it`s pretty new piece of HW with modern
> chipset (Q45). I believe that the next release of BIOS comes soon.
>
> But what about those atapicd problems? Is it related to SATA interface
> of DVD/CD drive? Maybe also the LG drive has buggy FW :).
>
> Best regards
>
> Jeremy Chadwick napsal(a):
>> On Wed, Nov 19, 2008 at 11:55:34AM +0100, Jan Sebosik wrote:
>>> Allright, I`ve played again with an HPET in BIOS little bit.
>>>
>>> Results ->
>>>
>>> HPET disabled:
>>>
>>> kern.timecounter.choice: TSC(-100) ACPI-fast(1000) i8254(0)
>>> dummy(-1000000)
>>> kern.timecounter.hardware: ACPI-fast
>>>
>>> HPET enabled:
>>>
>>> kern.timecounter.choice: TSC(-100) HPET(900) ACPI-fast(1000)
>>> i8254(0) dummy(-1000000)
>>> kern.timecounter.hardware: ACPI-fast
>>>
>>>
>>> But now FreeBSD boots also with HPET enabled (really don`t
>>> understand what`s going on).
>>>
>>> When I was trying to mount cd with "mount -t cd9660 /dev/cd0
>>> /mnt/cd0", mount works as expected (atapicd module not loaded).
>>>
>>> Then I`ve kldload-ed atapicd, "mouunt -t cd9660 /dev/acd0 /mnt/cd0"
>>> (acd0, not cd0), but this ended with messages like this:
>>> unknown: FAILURE - READ_BIG timeout (retry count 0)
>>>
>>> Temporary I`ve disabled HPET in BIOS (Linux got problems too-> he
>>> created gigabytes of log messages in /var/log/messages :D).
>>>
>>> Best regards, Jan
>>>
>>> Jeremy Chadwick napsal(a):
>>>> On Wed, Nov 19, 2008 at 11:19:37AM +0100, Jan Sebosik wrote:
>>>>> Hi
>>>>>
>>>>> Yeah, I`ve tested it 2 times (switching it in BIOS). To me it seems
>>>>> bit mysterious, why there is a relationship between HPET setting
>>>>> and acd/cd problems in FreeBSD.
>>>>>
>>>>>
>>>>> Jeremy Chadwick napsal(a):
>>>>>> On Wed, Nov 19, 2008 at 11:08:34AM +0100, Jan Sebosik wrote:
>>>>>>> Hi again
>>>>>>>
>>>>>>> so it seems to be a problem with HPET timer which is onboard and
>>>>>>> was enabled. If I turned him off, (acd | cd) problems went away.
>>>>>>>
>>>>>>>
>>>>>>> Jan Sebosik napsal(a):
>>>>>>>> Hi all
>>>>>>>>
>>>>>>>> OS: Freebsd 7-STABLE from CVS of today
>>>>>>>> Problematic HW: Intel DQ45CB (Q45 chipset, ICH10, SATA in
>>>>>>>> native mode, but not AHCI), LG SATA DVD-RW GH20NS15
>>>>>>>>
>>>>>>>> Problem: if I run freebsd without LG DVD connected to any SATA
>>>>>>>> port onboard everything works allright. When I connect SATA DVD
>>>>>>>> to board, then freebsd refuses to boot with messages similar to
>>>>>>>> those:
>>>>>>>>
>>>>>>>> acd0: FAILURE-READ_BIG timed out
>>>>>>>> unknown: FAILURE-READ_BIG timed out
>>>>>>>> cddone: goit error 0x5 back
>>>>>>>>
>>>>>>>> Messages are repeating forever.
>>>>>>>>
>>>>>>>> Anybody knows where should be a bug?
>>>>>>>> Temporary I`ve disconnected LG SATA burner from system board.
>>>>>>>>
>>>>>>>> Thanks for any idea.
>>>>>>>>
>>>>>>>> Best regards
>>>>>> Are you ***absolutely 100% certain*** this is true? The time counter
>>>>>> selected shouldn't have anything to do with the errors you see.
>>>>>> Please thoroughly test this.
>>>>>>
>>>>>> I'd CC jhb@ to get confirmation of my statement, but I've promised
>>>>>> myself I wouldn't bother him until 2009. :-)
>>>> This is very bizarre. The errors being returned from acd0 are that an
>>>> ATAPI/ATA command (READ_BIG, whatever the code for that is) did not
>>>> receive a response from the controller or device within 5 seconds
>>>> (assuming the ata(4) timeout values here; it could be something larger
>>>> for ATAPI, I don't know). Maybe some a BIOS bug...
>>>>
>>>> Can you show us output from the following two commands?
>>>>
>>>> sysctl kern.timecounter.choice
>>>> sysctl kern.timecounter.hardware
>>>>
>>>> Soren, do you know how/if the HPET time counter could cause this
>>>> oddity?
>>>> All of my systems use ACPI-fast, so I can't test this.
>>
>> What this proves is that disabling HPET in the BIOS makes absolutely no
>> change to FreeBSD as far as the timecounter goes. It's still using
>> ACPI-fast no matter if HPET is disabled or not. Disabling HPET does
>> show up in FreeBSD (as you can tell), but the ATA/ATAPI stuff *should
>> not* have some direct tie-in to HPET.
>>
>> I'm left believing you've found a BIOS bug. Please bring this up with
>> your motherboard or system vendor.
>>
>
--
Jan Sebosik, Slovakia
sebosik@demax.sk
From owner-freebsd-stable@FreeBSD.ORG Wed Nov 19 11:35:58 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id E09D0106564A
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 11:35:58 +0000 (UTC)
(envelope-from jdc@koitsu.dyndns.org)
Received: from QMTA01.emeryville.ca.mail.comcast.net
(qmta01.emeryville.ca.mail.comcast.net [76.96.30.16])
by mx1.freebsd.org (Postfix) with ESMTP id C0FF28FC08
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 11:35:58 +0000 (UTC)
(envelope-from jdc@koitsu.dyndns.org)
Received: from OMTA14.emeryville.ca.mail.comcast.net ([76.96.30.60])
by QMTA01.emeryville.ca.mail.comcast.net with comcast
id gzUB1a0011HpZEsA1zbyyA; Wed, 19 Nov 2008 11:35:58 +0000
Received: from koitsu.dyndns.org ([69.181.141.110])
by OMTA14.emeryville.ca.mail.comcast.net with comcast
id gzbx1a0042P6wsM8azbxgW; Wed, 19 Nov 2008 11:35:58 +0000
X-Authority-Analysis: v=1.0 c=1 a=6fuZhc4rEvsA:10 a=QycZ5dHgAAAA:8
a=t0O1tD7uoo7NMGcE1SsA:9 a=bk0TJ2fgW5pgVvnoT3gA:7
a=MK6WSgTjkWC2Hn3cNuM6BtZigmwA:4 a=EoioJ0NPDVgA:10 a=LY0hPdMaydYA:10
Received: by icarus.home.lan (Postfix, from userid 1000)
id 8135333C36; Wed, 19 Nov 2008 03:35:57 -0800 (PST)
Date: Wed, 19 Nov 2008 03:35:57 -0800
From: Jeremy Chadwick <koitsu@FreeBSD.org>
To: Ivan Voras <ivoras@freebsd.org>
Message-ID: <20081119113557.GA85252@icarus.home.lan>
References: <fd2a4c1f0811180637m6ee44d4fv4cf97d18e322ca5a@mail.gmail.com>
<gfun0o$lvq$1@ger.gmane.org>
<fd2a4c1f0811180904k396dff47m43d537a07ae87579@mail.gmail.com>
<gg0qi7$v7n$1@ger.gmane.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <gg0qi7$v7n$1@ger.gmane.org>
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: freebsd-stable@freebsd.org
Subject: Re: High system in %system load .
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Nov 2008 11:35:59 -0000
On Wed, Nov 19, 2008 at 11:43:09AM +0100, Ivan Voras wrote:
> Igor Lyapin wrote:
> > I already sent # top head in my first mail
> > that's all non idle top process
> >
> > last pid: 56920; load averages: 2.90, 2.25, 1.72 up
> > 0+22:10:12 20:04:05
> > 210 processes: 2 running, 207 sleeping, 1 zombie
> > CPU states: 8.3% user, 0.0% nice, 32.5% system, 0.3% interrupt, 58.9%
> > idle
> > Mem: 1268M Active, 1904M Inact, 479M Wired, 154M Cache, 214M Buf, 125M Free
> > Swap: 8192M Total, 8192M Free
> >
> > PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU
> > COMMAND
> > 55546 www 1 -4 0 198M 24912K ufs 1 0:25 29.39% httpd
> > 55986 www 1 -4 0 198M 23228K ufs 2 0:08 21.39% httpd
> > 56030 www 1 -4 0 199M 23400K ufs 1 0:05 11.23% httpd
>
> Ok, high sys load in "ufs" state for me was often caused by PHP session
> storage. By default, PHP will store all session records in a single
> directory, which can grow to monstruous sizes. If this is also your
> case, here are some things to try:
>
> a) increase vfs.ufs.dirhash_maxmem to 10 MB or something like that (look
> at vfs.ufs.dirhash_mem to see if you're hitting the limit and if so,
> monitor it to see what your dirhash_maxmem limit should be)
> b) configure PHP to use "sharded" directory structure for sessions.
Good catch, Ivan!
Also, I recommend tuning the session.gc_* php.ini variables to expire
sessions more often (less files laying around means less CPU due to
readdir()). The defaults PHP uses are absurd.
I also hate how the session files end up in /var/tmp, making a gigantic
mess. I made a separate directory for them, with specific perms (1777)
for security:
drwxrwxrwt 2 root wheel 1024 Nov 19 03:33 /var/tmp/php_sessions/
The piece of php.ini we use on our production web servers:
[session]
session.save_path = "/var/tmp/php_sessions"
session.gc_maxlifetime = 900
session.gc_probability = 25
session.gc_divisor = 100
See the PHP documentation for what these variables do.
--
| Jeremy Chadwick jdc at parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |
From owner-freebsd-stable@FreeBSD.ORG Wed Nov 19 12:24:25 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id A57E31065673
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 12:24:25 +0000 (UTC)
(envelope-from matheusber@gmail.com)
Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.30])
by mx1.freebsd.org (Postfix) with ESMTP id 54B778FC1E
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 12:24:25 +0000 (UTC)
(envelope-from matheusber@gmail.com)
Received: by yw-out-2324.google.com with SMTP id 9so1417582ywe.13
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 04:24:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:received:received:message-id
:date:subject:from:to:user-agent:mime-version:content-type
:content-transfer-encoding:x-priority:importance:sender;
bh=FKgahte4PcWzqca8dXQ4l6LQ8z5ZLw5vtT+jOf4Tkus=;
b=kBxceepKg6dOgs0pbaUeAkmEM9d3Dd8F9UBNZrqq6/sIUM5356T2hCxuLJ2i4KsiPZ
P6M2sOZbp7vhhEWnvFRyO1/vKVyEJiyuFr95ZUDcBFv8MewQPwKYGsenb87G3uZxZv9N
OZhAnusEZz2HUvxYi6Rj8kxY6qqWFr67lpD9I=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=message-id:date:subject:from:to:user-agent:mime-version
:content-type:content-transfer-encoding:x-priority:importance:sender;
b=a/jQ7Y1EwxFcjmZrSf06ySeAe8UPNiWsnBfR1Vf3PPRjCFmPi8AhAK708HdcjJuFAn
c/nWrkNKH2ZXD98T3l6I11tZ4MdX/b6QDw4GdVoeeDavHi3Ubjpqv3ycthUmmgcaY3kQ
mJZCT/LrRrkY/7dk/GTz1X+rLA0vOJ5BJKcxQ=
Received: by 10.150.206.11 with SMTP id d11mr1932864ybg.160.1227095752752;
Wed, 19 Nov 2008 03:55:52 -0800 (PST)
Received: from cygnus.homeunix.com ([189.71.5.133])
by mx.google.com with ESMTPS id d25sm7080174elf.3.2008.11.19.03.55.44
(version=TLSv1/SSLv3 cipher=RC4-MD5);
Wed, 19 Nov 2008 03:55:50 -0800 (PST)
Received: by cygnus.homeunix.com (Postfix, from userid 80)
id 9C453B8210; Wed, 19 Nov 2008 08:55:07 -0300 (BRT)
Received: from 189.92.76.238 (SquirrelMail authenticated user matheus)
by cygnus.homeunix.com with HTTP;
Wed, 19 Nov 2008 09:55:07 -0200 (BRST)
Message-ID: <76f9bb3fd8d40028f22f4585d2b8e983.squirrel@cygnus.homeunix.com>
Date: Wed, 19 Nov 2008 09:55:07 -0200 (BRST)
From: "Nenhum_de_Nos" <matheus@eternamente.info>
To: freebsd-stable@freebsd.org
User-Agent: SquirrelMail/1.4.15
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Sender: Nenhum_de_Nos <matheusber@gmail.com>
Subject: gmirror and gstripe
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Nov 2008 12:24:25 -0000
hail,
I have an old AthlonXP 1700+ running 7-STABLE:
FreeBSD xxx 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #1: Thu Nov 13 23:54:59
BRT 2008 root@xxx:/usr/obj/usr/src/sys/xxx i386
where I have two 750GB Seagate SATA Disks. They are divided as two slices,
around the first 120GB are gathered in gmirror, and what left is in
gstripe. so that's whats going on. if the machine locks, and fsck comes to
make its job, the box just gets slower and slower till I have to reset it
the hard way. to make it not lock after just 5 minutes I have to boot and
umount the "arrays", and then run fsck_ufs on them. so this way I can have
the box running again.
as I can't count on no power outage till the end of days, what can I do ?
i just recompiled stable to make it stop this, but no go here ...
this is an AthlonXP as said, running on EPoX kt600 based board, sata I is
from via southbridge and 1GB of RAM. just another 40GB disk to the system.
thanks,
matheus
--
We will call you cygnus,
The God of balance you shall be
From owner-freebsd-stable@FreeBSD.ORG Wed Nov 19 12:39:36 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 344E91065675
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 12:39:36 +0000 (UTC)
(envelope-from igor.lyapin@gmail.com)
Received: from ik-out-1112.google.com (ik-out-1112.google.com [66.249.90.183])
by mx1.freebsd.org (Postfix) with ESMTP id B18128FC1A
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 12:39:35 +0000 (UTC)
(envelope-from igor.lyapin@gmail.com)
Received: by ik-out-1112.google.com with SMTP id c21so1580441ika.3
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 04:39:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:date:from:x-priority
:message-id:to:cc:subject:in-reply-to:references:mime-version
:content-type:content-transfer-encoding;
bh=CbaVFohwf8Uw2ZVns+HeFWtnyQrBVtwbJMg2qeOfXcA=;
b=fZ2H3Jcjzev1mfy71XDA/yYtLAGXkhPlhZWrc4zEsRVq2QdYN9/S+YrcQm+YCvBlOH
hXcjoNuKVWdQgti4Ko5h/RFMwz7JADPXis7ocb/hVxVtOEY2BzyZ4O3PFQ3W6adQdVDg
7EDl8hZOM1y6jlzWJTQILm+bj2TCqM49XdHMo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=date:from:x-priority:message-id:to:cc:subject:in-reply-to
:references:mime-version:content-type:content-transfer-encoding;
b=whWVzp5ZBjVjyaZzOLOn8/jx+Pw/2AId2X+ZQpFDk073KIZ3VZa8R09O12Hfb3DXwX
ImMBx7t1UQGIY/aWTBoNNlLLWNQIA0alRnDkoRjt1uRADkwIkhW/63eFO3KGPAUqknvd
qNAFJamhO3r52XcmsGCd71bhV4jY7suaUI5o4=
Received: by 10.86.59.2 with SMTP id h2mr689977fga.30.1227098374444;
Wed, 19 Nov 2008 04:39:34 -0800 (PST)
Received: from vk04mg43ialyapi.msk.vek (ns.vek.ru [194.84.13.9])
by mx.google.com with ESMTPS id 3sm1036822fge.3.2008.11.19.04.39.32
(version=TLSv1/SSLv3 cipher=OTHER);
Wed, 19 Nov 2008 04:39:33 -0800 (PST)
Date: Wed, 19 Nov 2008 15:39:29 +0300
From: Igor Lyapin <igor.lyapin@gmail.com>
X-Priority: 3 (Normal)
Message-ID: <1283377972.20081119153929@gmail.com>
To: freebsd-stable@freebsd.org
In-Reply-To: <gg0qi7$v7n$1@ger.gmane.org>
References: <fd2a4c1f0811180637m6ee44d4fv4cf97d18e322ca5a@mail.gmail.com>
<gfun0o$lvq$1@ger.gmane.org>
<fd2a4c1f0811180904k396dff47m43d537a07ae87579@mail.gmail.com>
<gg0qi7$v7n$1@ger.gmane.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Cc: Ivan Voras <ivoras@freebsd.org>
Subject: Re[2]: High system in %system load [SOLVED]
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Nov 2008 12:39:36 -0000
Hello Ivan,
Thank's Ivan you quite right this was problem with php session. Programmer =
set up in
script's 2 years of session life. It was about 460k files in /var/tmp.
>> COMMAND
>> 55546 www 1 -4 0 198M 24912K ufs 1 0:25 29.39% h=
ttpd
>> 55986 www 1 -4 0 198M 23228K ufs 2 0:08 21.39% h=
ttpd
>> 56030 www 1 -4 0 199M 23400K ufs 1 0:05 11.23% h=
ttpd
> Ok, high sys load in "ufs" state for me was often caused by PHP session
> storage. By default, PHP will store all session records in a single
> directory, which can grow to monstruous sizes. If this is also your
> case, here are some things to try:
> a) increase vfs.ufs.dirhash_maxmem to 10 MB or something like that (look
> at vfs.ufs.dirhash_mem to see if you're hitting the limit and if so,
> monitor it to see what your dirhash_maxmem limit should be)
> b) configure PHP to use "sharded" directory structure for sessions.
--=20
Best regards,
Igor =20
From owner-freebsd-stable@FreeBSD.ORG Wed Nov 19 12:39:51 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id C7F9D106568E
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 12:39:51 +0000 (UTC)
(envelope-from admin@kkip.pl)
Received: from mainframe.kkip.pl (kkip.pl [87.105.164.78])
by mx1.freebsd.org (Postfix) with ESMTP id 72EA48FC20
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 12:39:51 +0000 (UTC)
(envelope-from admin@kkip.pl)
Received: from admin.admin.lan.kkip.pl ([10.66.3.254])
by mainframe.kkip.pl with esmtpsa (TLSv1:AES256-SHA:256)
(Exim 4.69 (FreeBSD)) (envelope-from <admin@kkip.pl>)
id 1L2mLU-0008pe-5K; Wed, 19 Nov 2008 13:39:50 +0100
Message-ID: <49240915.5060201@kkip.pl>
Date: Wed, 19 Nov 2008 13:39:49 +0100
From: Bartosz Stec <admin@kkip.pl>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Nenhum_de_Nos <matheus@eternamente.info>
References: <76f9bb3fd8d40028f22f4585d2b8e983.squirrel@cygnus.homeunix.com>
In-Reply-To: <76f9bb3fd8d40028f22f4585d2b8e983.squirrel@cygnus.homeunix.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Authenticated-User: admin@kkip.pl
X-Authenticator: plain
X-Sender-Verify: SUCCEEDED (sender exists & accepts mail)
X-Spam-Score: -8.7
X-Spam-Score-Int: -86
X-Exim-Version: 4.69 (build at 01-Nov-2008 10:39:57)
X-Date: 2008-11-19 13:39:50
X-Connected-IP: 10.66.3.254:3156
X-Message-Linecount: 65
X-Body-Linecount: 51
X-Message-Size: 2235
X-Body-Size: 1645
X-Received-Count: 1
X-Recipient-Count: 2
X-Local-Recipient-Count: 2
X-Local-Recipient-Defer-Count: 0
X-Local-Recipient-Fail-Count: 0
Cc: freebsd-stable@freebsd.org
Subject: Re: gmirror and gstripe
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Nov 2008 12:39:51 -0000
Nenhum_de_Nos pisze:
> hail,
>
> I have an old AthlonXP 1700+ running 7-STABLE:
>
> FreeBSD xxx 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #1: Thu Nov 13 23:54:59
> BRT 2008 root@xxx:/usr/obj/usr/src/sys/xxx i386
>
> where I have two 750GB Seagate SATA Disks. They are divided as two slices,
> around the first 120GB are gathered in gmirror, and what left is in
> gstripe. so that's whats going on. if the machine locks, and fsck comes to
> make its job, the box just gets slower and slower till I have to reset it
> the hard way. to make it not lock after just 5 minutes I have to boot and
> umount the "arrays", and then run fsck_ufs on them. so this way I can have
> the box running again.
>
Did you mean that machine slows down while doing background fsck? If
yes, problem is probably related to snapshot which is created, and
background fsck is done on snapshot.
> as I can't count on no power outage till the end of days, what can I do ?
>
>
You may just disable background fsck and do it manually in single user
mode in that case just by typing fsck -y.
> i just recompiled stable to make it stop this, but no go here ...
>
> this is an AthlonXP as said, running on EPoX kt600 based board, sata I is
> from via southbridge and 1GB of RAM. just another 40GB disk to the system.
>
> thanks,
>
> matheus
>
If I am correct, your problem is old known and mksnap_ffs related.
Jeremy Chadwick wrote a lot about it:
http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues
Good luck.
--
Bartosz Stec
AUXILIA Spółka z o.o.
ul. Wałbrzyska 43/2
52-314 Wrocław
tel. (71) 79 99 760 w. 69
GSM: 662171775
E-Mail: admin@kkip.pl
From owner-freebsd-stable@FreeBSD.ORG Wed Nov 19 13:02:18 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id DA2D4106564A
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 13:02:18 +0000 (UTC)
(envelope-from lists@mschuette.name)
Received: from mail.asta.uni-potsdam.de (mail.asta.uni-potsdam.de
[141.89.58.198])
by mx1.freebsd.org (Postfix) with ESMTP id 904A18FC18
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 13:02:18 +0000 (UTC)
(envelope-from lists@mschuette.name)
Received: from localhost (mail.asta.uni-potsdam.de [141.89.58.198])
by mail.asta.uni-potsdam.de (Postfix) with ESMTP id 58137A26FC
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 13:45:25 +0100 (CET)
X-Virus-Scanned: on mail at asta.uni-potsdam.de
Received: from mail.asta.uni-potsdam.de ([141.89.58.198])
by localhost (mail.asta.uni-potsdam.de [141.89.58.198]) (amavisd-new,
port 10024)
with ESMTP id gGCdv9jhrQBM for <freebsd-stable@freebsd.org>;
Wed, 19 Nov 2008 13:45:13 +0100 (CET)
Received: from cordelia.mschuette.name (BAA7033.baa.pppool.de [77.128.112.51])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(Client CN "Martin Schuette", Issuer "AStA-CA" (verified OK))
by mail.asta.uni-potsdam.de (Postfix) with ESMTP id BB4A5A266A
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 13:45:13 +0100 (CET)
Message-ID: <49240A58.8010502@mschuette.name>
Date: Wed, 19 Nov 2008 13:45:12 +0100
From: =?UTF-8?B?TWFydGluIFNjaMO8dHRl?= <lists@mschuette.name>
User-Agent: Thunderbird 2.0.0.17 (X11/20081003)
MIME-Version: 1.0
To: freebsd-stable@freebsd.org
References: <49219959.8040209@dotcom.ts.it>
In-Reply-To: <49219959.8040209@dotcom.ts.it>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: swap_pager: indefinite wait
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Nov 2008 13:02:18 -0000
Sossi Andrej schrieb:
> swap_pager: indefinite wait buffer: bufobj: 0, blkno: 31, size: 4096
>
> Can somebody help me understand why the system crashed this way or how
> to avoid future crash?
This happens when it takes more than 20 seconds to swap out a page
(http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/troubleshoot.html#INDEFINITE-WAIT-BUFFER).
I had the same problem some time ago with FreeBSD 6.0 when making
Backups (so the disks were busy). For me it helped to increase the
timeout from 20 to 40 seconds in vm/swap_pager.c
(http://fxr.watson.org/fxr/source/vm/swap_pager.c?v=FREEBSD60#L1103)
--
Martin
From owner-freebsd-stable@FreeBSD.ORG Wed Nov 19 13:04:33 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 6D1131065672
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 13:04:33 +0000 (UTC)
(envelope-from jwb@homer.att.com)
Received: from mail167.messagelabs.com (mail167.messagelabs.com
[216.82.253.179])
by mx1.freebsd.org (Postfix) with ESMTP id 1589E8FC19
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 13:04:32 +0000 (UTC)
(envelope-from jwb@homer.att.com)
X-VirusChecked: Checked
X-Env-Sender: jwb@homer.att.com
X-Msg-Ref: server-2.tower-167.messagelabs.com!1227099871!9917317!1
X-StarScan-Version: 6.0.0; banners=-,-,-
X-Originating-IP: [144.160.20.54]
Received: (qmail 3630 invoked from network); 19 Nov 2008 13:04:31 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpi135.enaf.sfdc.sbc.com)
(144.160.20.54)
by server-2.tower-167.messagelabs.com with AES256-SHA encrypted SMTP;
19 Nov 2008 13:04:31 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1])
by mlpi135.enaf.sfdc.sbc.com (8.14.3/8.14.3) with ESMTP id
mAJD4UEv031276; Wed, 19 Nov 2008 08:04:30 -0500
Received: from alph001.aldc.att.com (alph001.aldc.att.com [135.53.7.26])
by mlpi135.enaf.sfdc.sbc.com (8.14.3/8.14.3) with ESMTP id
mAJD4RTT031258; Wed, 19 Nov 2008 08:04:28 -0500
Received: from aldc.att.com (localhost.localdomain [127.0.0.1])
by alph001.aldc.att.com (8.14.0/8.14.0) with ESMTP id mAJD4Rdv023349;
Wed, 19 Nov 2008 08:04:27 -0500
Received: from ulysses.homer.att.com (ulysses.homer.att.com [135.205.193.8])
by alph001.aldc.att.com (8.14.0/8.14.0) with ESMTP id mAJD4LaJ023264;
Wed, 19 Nov 2008 08:04:22 -0500
Received: from akiva.homer.att.com (akiva.homer.att.com [135.205.212.39])
by ulysses.homer.att.com (8.9.3/8.9.3) with ESMTP id IAA15436;
Wed, 19 Nov 2008 08:04:20 -0500 (EST)
Received: from akiva (localhost [127.0.0.1])
by akiva.homer.att.com (8.9.3/8.9.3) with ESMTP id IAA10005;
Wed, 19 Nov 2008 08:04:20 -0500 (EST)
Message-Id: <200811191304.IAA10005@akiva.homer.att.com>
X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.0.4
To: Peter Jeremy <peterjeremy@optushome.com.au>
In-reply-to: Your message of "Tue, 18 Nov 2008 04:56:45 +1100."
<20081117175645.GN51761@server.vk2pj.dyndns.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 19 Nov 2008 08:04:19 -0500
From: "J. W. Ballantine" <jwb@homer.att.com>
Cc: freebsd-stable@freebsd.org
Subject: Re: _nyssin undefined
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Nov 2008 13:04:33 -0000
Peter,
At this point, I've reinstalled the system, so I can't say.
Jim
---------- In Response to your message -------------
> Date: Tue, 18 Nov 2008 04:56:45 +1100
> To: "J. W. Ballantine" <jwb@homer.att.com>
> From: Peter Jeremy <peterjeremy@optushome.com.au>
> Subject: Re: _nyssin undefined
>
>
> --lHGcFxmlz1yfXmOs
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
> Content-Transfer-Encoding: quoted-printable
>
> On 2008-Nov-17 08:56:55 -0500, "J. W. Ballantine" <jwb@homer.att.com> wrote:
> >The problem started during the install of a new system build using
> >the Friday AM CVS bits, and I can't get on the system in any
> >mode.
>
> If you try to boot to single-user, do you get the "enter shell pathname"
> prompt? If so, does specifying "/rescue/sh" give you a shell?
>
> --=20
> Peter Jeremy
> Please excuse any delays as the result of my ISP's inability to implement
> an MTA that is either RFC2821-compliant or matches their claimed behaviour.
>
> --lHGcFxmlz1yfXmOs
> Content-Type: application/pgp-signature
> Content-Disposition: inline
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.9 (FreeBSD)
>
> iEYEARECAAYFAkkhsF0ACgkQ/opHv/APuIcTzgCfUSZeYDAiiuQFZS4DH7Jc5CtV
> t74An2s0lsq0r41mRUH4uF45Mn19K5K1
> =ZJAR
> -----END PGP SIGNATURE-----
>
> --lHGcFxmlz1yfXmOs--
>
From owner-freebsd-stable@FreeBSD.ORG Wed Nov 19 14:44:16 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 1C3EE106567A
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 14:44:16 +0000 (UTC)
(envelope-from matheusber@gmail.com)
Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.28])
by mx1.freebsd.org (Postfix) with ESMTP id B4E768FC16
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 14:44:15 +0000 (UTC)
(envelope-from matheusber@gmail.com)
Received: by yx-out-2324.google.com with SMTP id 8so1443621yxb.13
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 06:44:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:received:received:message-id
:in-reply-to:references:date:subject:from:to:user-agent:mime-version
:content-type:content-transfer-encoding:x-priority:importance:sender;
bh=0u2GXdy3h88s0SH3daEGO4y4h/VejhFzESCAjt6geK4=;
b=uYUrivkx4f53grBQwgawlxYaIGSBorvDBJio7/aeSG/lQyr5x4PqEbj+aaKN5/8Z3Y
G95n3SMHa+jVMjcst7tNJ847C9wFLcvN6s29kTvdzP+GeOHyYXhebq0wtk0SeTiiJ8tT
Gcygt0ypTyBz5wQC6xK9NjHqLsfv4uPfAbwI8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=message-id:in-reply-to:references:date:subject:from:to:user-agent
:mime-version:content-type:content-transfer-encoding:x-priority
:importance:sender;
b=ZTD9/YNDHO7SX4FD6zeXkwzMBeKIJq01ztdhJYTUwe+/G0k0MzAcxuw4YYF2Zqu/GG
MnalKVm5/NNbRBztNxaqPcE4UyJYIftkUNa31j++eqexRUwUbuGjMxCEdatTJ3tXKdU0
8SdHjkLi0jsOQOaSQtI3UlCUzLOhN5WFy/MwA=
Received: by 10.100.106.12 with SMTP id e12mr612741anc.18.1227105855049;
Wed, 19 Nov 2008 06:44:15 -0800 (PST)
Received: from cygnus.homeunix.com ([189.71.5.133])
by mx.google.com with ESMTPS id d21sm7652463and.26.2008.11.19.06.44.10
(version=TLSv1/SSLv3 cipher=RC4-MD5);
Wed, 19 Nov 2008 06:44:14 -0800 (PST)
Received: by cygnus.homeunix.com (Postfix, from userid 80)
id 22585B8210; Wed, 19 Nov 2008 11:44:01 -0300 (BRT)
Received: from 189.92.76.238 (SquirrelMail authenticated user matheus)
by cygnus.homeunix.com with HTTP;
Wed, 19 Nov 2008 12:44:01 -0200 (BRST)
Message-ID: <5d69df380871dba0b5d6918a356f3bf7.squirrel@cygnus.homeunix.com>
In-Reply-To: <49240915.5060201@kkip.pl>
References: <76f9bb3fd8d40028f22f4585d2b8e983.squirrel@cygnus.homeunix.com>
<49240915.5060201@kkip.pl>
Date: Wed, 19 Nov 2008 12:44:01 -0200 (BRST)
From: "Nenhum_de_Nos" <matheus@eternamente.info>
To: freebsd-stable@freebsd.org
User-Agent: SquirrelMail/1.4.15
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Sender: Nenhum_de_Nos <matheusber@gmail.com>
Subject: Re: gmirror and gstripe
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Nov 2008 14:44:16 -0000
On Wed, November 19, 2008 10:39 am, Bartosz Stec wrote:
> Nenhum_de_Nos pisze:
>> hail,
>>
>> I have an old AthlonXP 1700+ running 7-STABLE:
>>
>> FreeBSD xxx 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #1: Thu Nov 13
>> 23:54:59
>> BRT 2008 root@xxx:/usr/obj/usr/src/sys/xxx i386
>>
>> where I have two 750GB Seagate SATA Disks. They are divided as two
>> slices,
>> around the first 120GB are gathered in gmirror, and what left is in
>> gstripe. so that's whats going on. if the machine locks, and fsck comes
>> to
>> make its job, the box just gets slower and slower till I have to reset
>> it
>> the hard way. to make it not lock after just 5 minutes I have to boot
>> and
>> umount the "arrays", and then run fsck_ufs on them. so this way I can
>> have
>> the box running again.
>>
> Did you mean that machine slows down while doing background fsck? If
> yes, problem is probably related to snapshot which is created, and
> background fsck is done on snapshot.
I can say for slow down, as I can't do anything on it. ping to it responds
really slow, and if I plug an usb keyboard and try to use the machine, the
keyborad just is able to change consoles (from tty1 to tty2, and so on),
but I can't even login to the machine, as nothing I type gets to the
terminal. so I can't say its slow or locked.
>> as I can't count on no power outage till the end of days, what can I do
>> ?
>>
>>
> You may just disable background fsck and do it manually in single user
> mode in that case just by typing fsck -y.
ok, but this makes me have to be there every reboot, if it wasn't a reboot
from a command sent by me. and this makes my life hard, as I can't be
allways there (this is a home server, nfs+pf+postfix+webmail+dns), I just
want to put fsck_y on rc.conf ...
>> i just recompiled stable to make it stop this, but no go here ...
>>
>> this is an AthlonXP as said, running on EPoX kt600 based board, sata I
>> is
>> from via southbridge and 1GB of RAM. just another 40GB disk to the
>> system.
>>
>> thanks,
>>
>> matheus
>>
> If I am correct, your problem is old known and mksnap_ffs related.
> Jeremy Chadwick wrote a lot about it:
> http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues
gonna read :)
thanks
matheus
> Good luck.
>
> --
> Bartosz Stec
>
> AUXILIA Spółka z o.o.
> ul. Wałbrzyska 43/2
> 52-314 Wrocław
> tel. (71) 79 99 760 w. 69
> GSM: 662171775
> E-Mail: admin@kkip.pl
>
>
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
>
--
We will call you cygnus,
The God of balance you shall be
From owner-freebsd-stable@FreeBSD.ORG Wed Nov 19 15:14:27 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id A41601065673
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 15:14:27 +0000 (UTC)
(envelope-from matheusber@gmail.com)
Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.248])
by mx1.freebsd.org (Postfix) with ESMTP id 468F98FC2A
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 15:14:27 +0000 (UTC)
(envelope-from matheusber@gmail.com)
Received: by an-out-0708.google.com with SMTP id b6so1471846ana.13
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 07:14:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:received:received:message-id
:in-reply-to:references:date:subject:from:to:user-agent:mime-version
:content-type:content-transfer-encoding:x-priority:importance:sender;
bh=4Aeo7kLI534zav9tRgGkpDocVo+LIk4DNFuN2hY1M4k=;
b=e1dGNso5CH7T35vi/Bialej8wqnbsZkhfUVq99PHuLUJR8s/Ow/ryXQzjwX9aYsu+n
VtpStbrhbofkv6Wu3bfza96YRhfOmEa6V2iOztoXx87eykNPe/uyO+0Gcs49l4MnW3/M
F6nw+W8N/6Oog+rttqflEa0epi34euskMU5pg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=message-id:in-reply-to:references:date:subject:from:to:user-agent
:mime-version:content-type:content-transfer-encoding:x-priority
:importance:sender;
b=D0qQ5XMAYTExisQ1ALY22FH7C+x9qhjsYRQzywo/OIJNL+3rax9uddlAcT+mIaF1aI
H+VNaRSl3+6CItPmFh1cRGtUr8PgHQHQYDvEuAboy1z0OTxxEpY6PXCVlaORsfIHbzhM
9tzWLXcVvTNQ9hjmmI75f8vpqN7WfoRmcYEkQ=
Received: by 10.100.248.9 with SMTP id v9mr598723anh.115.1227107666134;
Wed, 19 Nov 2008 07:14:26 -0800 (PST)
Received: from cygnus.homeunix.com ([189.71.5.133])
by mx.google.com with ESMTPS id c28sm3958936anc.7.2008.11.19.07.14.21
(version=TLSv1/SSLv3 cipher=RC4-MD5);
Wed, 19 Nov 2008 07:14:25 -0800 (PST)
Received: by cygnus.homeunix.com (Postfix, from userid 80)
id A5F68B8210; Wed, 19 Nov 2008 12:14:12 -0300 (BRT)
Received: from 189.92.76.238 (SquirrelMail authenticated user matheus)
by cygnus.homeunix.com with HTTP;
Wed, 19 Nov 2008 13:14:12 -0200 (BRST)
Message-ID: <9b5d48672e38f20652cf315844965606.squirrel@cygnus.homeunix.com>
In-Reply-To: <4923C8D4.2000109@bsdforen.de>
References: <4923C8D4.2000109@bsdforen.de>
Date: Wed, 19 Nov 2008 13:14:12 -0200 (BRST)
From: "Nenhum_de_Nos" <matheus@eternamente.info>
To: freebsd-stable@freebsd.org
User-Agent: SquirrelMail/1.4.15
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Sender: Nenhum_de_Nos <matheusber@gmail.com>
Subject: Re: u3g and ubsa
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Nov 2008 15:14:27 -0000
On Wed, November 19, 2008 6:05 am, Dominic Fandrey wrote:
> I have recently been pointed to the u3g driver and gave it a try,
> because UBSA works very unreliable for me.
>
> - In combination with PF-NAT I get kernel panics under high load.
> - I have to hack some buffer sizes in the driver to get the full
> 3G speed.
> - Often my USB-3G stick is not detected, sometimes I spent several
> minutes plugging it in and out until it is detected.
> - It doesn't let me use the card reader in the stick.
>
> The u3g driver has NONE of these problems. Everything just works
> for me.
>
> So obviously I would like to have u3g in stable and chose for
> myself or even take support for devices out of ubsa that work
> better with u3g.
> _______________________________________________
same for me. I'm looking forward to see u3g in STABLE.
matheus
--
We will call you cygnus,
The God of balance you shall be
From owner-freebsd-stable@FreeBSD.ORG Wed Nov 19 17:41:53 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 5DB331065673
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 17:41:53 +0000 (UTC)
(envelope-from msams992000@yahoo.com.au)
Received: from web36108.mail.mud.yahoo.com (web36108.mail.mud.yahoo.com
[66.163.179.222])
by mx1.freebsd.org (Postfix) with SMTP id 223808FC22
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 17:41:52 +0000 (UTC)
(envelope-from msams992000@yahoo.com.au)
Received: (qmail 34775 invoked by uid 60001); 19 Nov 2008 17:15:12 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com.au;
h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID;
b=MW57nkHHGav57fmwmtPA3NzxJsY9eK3cEGB8r3+/kLAdFrsgFV0yb8qnVg8spy95GahhuIRKEGVLol+HKlcnUJKugEOKKKlouVajJd6BApWtAodJmDJhgpUH4MbLw7lucylAc+tqTigLLT0228KYF2sBjHgwSZjxBlkc7mCZCpc=;
X-YMail-OSG: QRoO1GgVM1n40F_8IUb79wIWqyehrFMnGTazzwVWN3U6A1eSYSe0jmgmVHG0z3806CgCLdNfh8_.SEytLkcmDTYBLt0m68PfTYNSihjKzIVjQep7qw1cmv9jFfbcao2aM6oTtl0aQKvi7ZpIAbSi2yLxpGLnaaI5gZUzItx7hSA3TyeZR6xETNHHA710
Received: from [75.101.20.105] by web36108.mail.mud.yahoo.com via HTTP;
Wed, 19 Nov 2008 09:15:12 PST
X-Mailer: YahooMailRC/1155.32 YahooMailWebService/0.7.260.1
Date: Wed, 19 Nov 2008 09:15:12 -0800 (PST)
From: Mark Sams <msams992000@yahoo.com.au>
To: freebsd-stable@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Message-ID: <610465.33671.qm@web36108.mail.mud.yahoo.com>
Subject: atacontrol missing drive after upgrade to 6.3
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Nov 2008 17:41:53 -0000
I upgraded from 6.2 to 6.3 p5 last night. Upon rebooting, the second disk i=
n the mirror is missing.=0A=0A# atacontrol status ar0=0Aar0: ATA RAID1 stat=
us: DEGRADED=0A subdisks:=0A 0 ad0 ONLINE=0A 1 ---- MISSING=0A=0A# gre=
p ata /var/run/dmesg.boot=0Aad0: 238475MB <WDC WD2500AVJB-63UDA0 00.02C01> =
at ata0-master UDMA100=0Aad1: 238475MB <WDC WD2500AVJB-63UDA0 00.02C01> at =
ata0-slave UDMA100=0Aar0: disk0 READY (master) using ad0 at ata0-master=0Aa=
r1: disk1 READY (mirror) using ad1 at ata0-slave=0A=0AI am unsure how to re=
-add the disk, or if this is a bug. I noticed a number of fixes for atacont=
rol.c beyond the current version in 6.3 (1.36.2.6)=0Ahttp://www.freebsd.org=
/cgi/cvsweb.cgi/src/sbin/atacontrol/atacontrol.c=0A=0AObviously it won't re=
build=0A# atacontrol rebuild ar0=0Aatacontrol: ioctl(IOCATARAIDREBUILD): In=
put/output error=0A=0ADo I do?=0Aatacontrol detach ata0-slave=0A&& atacontr=
ol attach ata0-slave && atacontrol addspare ad1 ar0 =0A&& atacontrol rebuil=
d ar0=0A=0A(not sure what channel I am supposed to be using) Or is this som=
ething that requires atacontrol.c to be patched?=0A=0AI am not sure where t=
o start, so I thought I would ask here first before trying anything.=0A=0Ab=
tw, its Intel ICH5:=0Aatapci1: <Intel ICH5 SATA150 controller> port 0xc000-=
0xc007,0xc400-0xc403,0xc800-0xc807,0xcc00-0xcc03,0xd000-0xd00f irq 18 at de=
vice 31.2 on pci0=0A=0AThank you in advance for any help you can provide.=
=0A=0AMark=0A=0A=0A Make the switch to the world's best email. Get=
Yahoo!7 Mail! http://au.yahoo.com/y7mail
From owner-freebsd-stable@FreeBSD.ORG Wed Nov 19 19:10:54 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 34C911065675
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 19:10:54 +0000 (UTC)
(envelope-from jdc@koitsu.dyndns.org)
Received: from QMTA04.westchester.pa.mail.comcast.net
(qmta04.westchester.pa.mail.comcast.net [76.96.62.40])
by mx1.freebsd.org (Postfix) with ESMTP id 7F3CA8FC0A
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 19:10:53 +0000 (UTC)
(envelope-from jdc@koitsu.dyndns.org)
Received: from OMTA12.westchester.pa.mail.comcast.net ([76.96.62.44])
by QMTA04.westchester.pa.mail.comcast.net with comcast
id h4l51a0020xGWP8547AmBz; Wed, 19 Nov 2008 19:10:46 +0000
Received: from koitsu.dyndns.org ([69.181.141.110])
by OMTA12.westchester.pa.mail.comcast.net with comcast
id h7Ai1a00M2P6wsM3Y7AjVj; Wed, 19 Nov 2008 19:10:43 +0000
X-Authority-Analysis: v=1.0 c=1 a=Kn1M_iXOy9EA:10 a=A7SOdGXiAqEA:10
a=6I5d2MoRAAAA:8 a=QycZ5dHgAAAA:8 a=Bb6xZOOrY9dJjkj89nkA:9
a=UeKiU9JpIt8RBL8SNiMA:7 a=OcdkrPxSK4s933lwrocbOpm7WzEA:4
a=EoioJ0NPDVgA:10 a=LY0hPdMaydYA:10
Received: by icarus.home.lan (Postfix, from userid 1000)
id 7FA3533C1C; Wed, 19 Nov 2008 11:10:42 -0800 (PST)
Date: Wed, 19 Nov 2008 11:10:42 -0800
From: Jeremy Chadwick <koitsu@FreeBSD.org>
To: Mark Sams <msams992000@yahoo.com.au>
Message-ID: <20081119191042.GA5284@icarus.home.lan>
References: <610465.33671.qm@web36108.mail.mud.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <610465.33671.qm@web36108.mail.mud.yahoo.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: freebsd-stable@freebsd.org
Subject: Re: atacontrol missing drive after upgrade to 6.3
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Nov 2008 19:10:54 -0000
On Wed, Nov 19, 2008 at 09:15:12AM -0800, Mark Sams wrote:
> I upgraded from 6.2 to 6.3 p5 last night. Upon rebooting, the second disk in the mirror is missing.
>
> # atacontrol status ar0
> ar0: ATA RAID1 status: DEGRADED
> subdisks:
> 0 ad0 ONLINE
> 1 ---- MISSING
>
> # grep ata /var/run/dmesg.boot
> ad0: 238475MB <WDC WD2500AVJB-63UDA0 00.02C01> at ata0-master UDMA100
> ad1: 238475MB <WDC WD2500AVJB-63UDA0 00.02C01> at ata0-slave UDMA100
> ar0: disk0 READY (master) using ad0 at ata0-master
> ar1: disk1 READY (mirror) using ad1 at ata0-slave
>
> I am unsure how to re-add the disk, or if this is a bug. I noticed a number of fixes for atacontrol.c beyond the current version in 6.3 (1.36.2.6)
> http://www.freebsd.org/cgi/cvsweb.cgi/src/sbin/atacontrol/atacontrol.c
>
> Obviously it won't rebuild
> # atacontrol rebuild ar0
> atacontrol: ioctl(IOCATARAIDREBUILD): Input/output error
>
> Do I do?
> atacontrol detach ata0-slave
> && atacontrol attach ata0-slave && atacontrol addspare ad1 ar0
> && atacontrol rebuild ar0
>
> (not sure what channel I am supposed to be using) Or is this something that requires atacontrol.c to be patched?
>
> I am not sure where to start, so I thought I would ask here first before trying anything.
>
> btw, its Intel ICH5:
> atapci1: <Intel ICH5 SATA150 controller> port 0xc000-0xc007,0xc400-0xc403,0xc800-0xc807,0xcc00-0xcc03,0xd000-0xd00f irq 18 at device 31.2 on pci0
You're using Intel MatrixRAID, aren't you? Please migrate away from
this immediately, your data is at risk.
http://wiki.freebsd.org/JeremyChadwick/ATA_issues_and_troubleshooting
The problem you're experiencing is documented there.
There is no solution, as far as I know. The problems still exist on
RELENG_7 also.
I recommend you back up (off-load) all of your data onto a disk or
system somewhere else, and use gmirror(8) instead. Please, stay away
from Intel MatrixRAID on FreeBSD.
--
| Jeremy Chadwick jdc at parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |
From owner-freebsd-stable@FreeBSD.ORG Wed Nov 19 19:29:20 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id D6EDF1065673
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 19:29:20 +0000 (UTC)
(envelope-from msams992000@yahoo.com.au)
Received: from web36103.mail.mud.yahoo.com (web36103.mail.mud.yahoo.com
[66.163.179.217])
by mx1.freebsd.org (Postfix) with SMTP id 830948FC14
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 19:29:20 +0000 (UTC)
(envelope-from msams992000@yahoo.com.au)
Received: (qmail 1394 invoked by uid 60001); 19 Nov 2008 19:29:20 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com.au;
h=X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID;
b=gORzrl+gjazxIH6+5TVEALV/cvD5z+4GMnYki0F2d3h6u74Lo+7BG6+TTvzh0LvTr01pkTDufWR1weY6BkUllQtfuAEJ8pUUqkPggrcEkPlGBU87sKCF4/P2unquWiJTedJqdMp1cCYsiFsR+2KFwCjqL3ST7A7qRLoZJDaWu24=;
X-YMail-OSG: U1bij94VM1m0kYLWzm8Eq8c9DIY4mKfxJ4SWX2dgUiUlUZKEKWekinKN.qkLpAMaE_ta4fUfpDMb38XVQ2yF5RbZyT0DDz7JS3OzxqAYVycrWVi0jOsTZgUkmlV.k.A1Rz_ns8vFiXHmPPAiSonc4AxMzcJSCwY9OSgB_u2D8cq.LCDvZEvvYISHc9jh
Received: from [75.101.20.105] by web36103.mail.mud.yahoo.com via HTTP;
Wed, 19 Nov 2008 11:29:19 PST
X-Mailer: YahooMailRC/1155.32 YahooMailWebService/0.7.260.1
References: <610465.33671.qm@web36108.mail.mud.yahoo.com>
<20081119191042.GA5284@icarus.home.lan>
Date: Wed, 19 Nov 2008 11:29:19 -0800 (PST)
From: Mark Sams <msams992000@yahoo.com.au>
To: freebsd-stable@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Message-ID: <957588.98964.qm@web36103.mail.mud.yahoo.com>
Subject: Re: atacontrol missing drive after upgrade to 6.3
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Nov 2008 19:29:20 -0000
----- Original Message ----=0A=0A> From: Jeremy Chadwick <koitsu@FreeBSD.or=
g>=0A> You're using Intel MatrixRAID, aren't you? Please migrate away from=
=0A> this immediately, your data is at risk.=0A=0AUmmm... I don't think so.=
It is just a standard RAID 1 mirror using the=0Abuilt in ICH5 chip. It has=
been running fine for a over a year now on=0Athe other builds of FreeBSD 6=
.x. It is not RAID 0+1 or whatever the=0AMatrix RAID thing is.=0A=0A=0A =
Make the switch to the world's best email. Get Yahoo!7 Mail! http://=
au.yahoo.com/y7mail
From owner-freebsd-stable@FreeBSD.ORG Wed Nov 19 19:33:15 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id CBDA91065680
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 19:33:15 +0000 (UTC)
(envelope-from jdc@koitsu.dyndns.org)
Received: from QMTA02.westchester.pa.mail.comcast.net
(qmta02.westchester.pa.mail.comcast.net [76.96.62.24])
by mx1.freebsd.org (Postfix) with ESMTP id 628C18FC1C
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 19:33:15 +0000 (UTC)
(envelope-from jdc@koitsu.dyndns.org)
Received: from OMTA07.westchester.pa.mail.comcast.net ([76.96.62.59])
by QMTA02.westchester.pa.mail.comcast.net with comcast
id h1zr1a00c1GhbT8527Ypqy; Wed, 19 Nov 2008 19:32:49 +0000
Received: from koitsu.dyndns.org ([69.181.141.110])
by OMTA07.westchester.pa.mail.comcast.net with comcast
id h7Yi1a00J2P6wsM3T7YjVR; Wed, 19 Nov 2008 19:32:43 +0000
X-Authority-Analysis: v=1.0 c=1 a=Kn1M_iXOy9EA:10 a=A7SOdGXiAqEA:10
a=QycZ5dHgAAAA:8 a=GQeh0uWabJovSvKF08AA:9
a=Cl6QI54iTMZT8yj5gIm3eJ-K0LcA:4
a=EoioJ0NPDVgA:10 a=SV7veod9ZcQA:10 a=LY0hPdMaydYA:10
Received: by icarus.home.lan (Postfix, from userid 1000)
id B752F33C1C; Wed, 19 Nov 2008 11:32:42 -0800 (PST)
Date: Wed, 19 Nov 2008 11:32:42 -0800
From: Jeremy Chadwick <koitsu@FreeBSD.org>
To: Mark Sams <msams992000@yahoo.com.au>
Message-ID: <20081119193242.GA5739@icarus.home.lan>
References: <610465.33671.qm@web36108.mail.mud.yahoo.com>
<20081119191042.GA5284@icarus.home.lan>
<957588.98964.qm@web36103.mail.mud.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <957588.98964.qm@web36103.mail.mud.yahoo.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: freebsd-stable@freebsd.org
Subject: Re: atacontrol missing drive after upgrade to 6.3
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Nov 2008 19:33:15 -0000
On Wed, Nov 19, 2008 at 11:29:19AM -0800, Mark Sams wrote:
> > From: Jeremy Chadwick <koitsu@FreeBSD.org>
> > You're using Intel MatrixRAID, aren't you? Please migrate away from
> > this immediately, your data is at risk.
>
> Ummm... I don't think so. It is just a standard RAID 1 mirror using the
> built in ICH5 chip. It has been running fine for a over a year now on
> the other builds of FreeBSD 6.x. It is not RAID 0+1 or whatever the
> Matrix RAID thing is.
The built-in ICH5 == Intel MatrixRAID. It's BIOS-level RAID under an
Intel ICH chip. It's called MatrixRAID.
I have no personal problem with Intel MatrixRAID. What I'm telling you
is that FreeBSD's support for it is horribly, horribly broken. You
*will* lose your data. Read my Wiki entries in full.
I'm only going to say this once more: please reconsider. You very
likely are not going to be able to recover that failed array. The last
person who had this problem had to boot a Linux LiveCD and attempt to
use Linux tools to repair it.
--
| Jeremy Chadwick jdc at parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |
From owner-freebsd-stable@FreeBSD.ORG Wed Nov 19 19:46:49 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id BB17E1065673
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 19:46:49 +0000 (UTC)
(envelope-from crapsh@monkeybrains.net)
Received: from ape.monkeybrains.net (mail.monkeybrains.net [208.69.40.9])
by mx1.freebsd.org (Postfix) with ESMTP id A16548FC0C
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 19:46:49 +0000 (UTC)
(envelope-from crapsh@monkeybrains.net)
Received: from [192.168.2.105] (adsl-76-203-175-18.dsl.pltn13.sbcglobal.net
[76.203.175.18]) (authenticated bits=0)
by ape.monkeybrains.net (8.14.1/8.14.1) with ESMTP id mAJJA5aX074080
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
Wed, 19 Nov 2008 11:10:06 -0800 (PST)
(envelope-from crapsh@monkeybrains.net)
Message-ID: <492464B3.4050306@monkeybrains.net>
Date: Wed, 19 Nov 2008 11:10:43 -0800
From: Rudy <crapsh@monkeybrains.net>
User-Agent: Thunderbird 2.0.0.17 (X11/20080925)
MIME-Version: 1.0
To: Bartosz Stec <admin@kkip.pl>
References: <20081109174303.GA5146@ourbrains.org> <20081109184349.GG51239@server.vk2pj.dyndns.org> <4920D879.3070806@jrv.org>
<20081117050441.GA16855@ourbrains.org> <20081118175210.GA3753@hyperion.scode.org> <20081119001742.GA21835@ourbrains.org> <49235D86.4050106@modulus.org>
<86bpwcp1d8.fsf@ds4.des.no> <4923D460.5020900@kkip.pl> <b41c75520811190106w7f951760m95c12358f1008c5b@mail.gmail.com>
<4923E977.8030107@kkip.pl>
In-Reply-To: <4923E977.8030107@kkip.pl>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV version 0.94,
clamav-milter version 0.94 on pita.monkeybrains.net
X-Virus-Status: Clean
Cc: FreeBSD Stable <freebsd-stable@freebsd.org>
Subject: (actually ZFS discussion) Re: Will XFS be adopted
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Nov 2008 19:46:49 -0000
> Well it's not simple indeed. I use ZFS on my home (not critical) box
> (RAIDZ1). After 4 weeks uptime with varied workload I assumed it's
> stable. Unfortunately ZFS crashed next week ;)
Tune your system for ZFS and the crashes will go away.
Read this: http://wiki.freebsd.org/ZFSTuningGuide
A running system with ZFS caches a lot of disk access (making it really
fast for some applications). WHen you run the 'top' command, you will
see that WIRED amount of ram is higher than a system without ZFS.
Mem: 161M Active, 114M Inact, 639M Wired, 1084K Cache, 199M Buf, 1086M
Free
What applications will benefit from ZFS? Read this article on MySQL and
ZFS:
http://dev.mysql.com/tech-resources/articles/mysql-zfs.html
It proposed that you allocate less ram to MySQL in your my.cnf and let
ZFS take care of caching.
Here are my loader.conf settings.
zfs_load="YES"
# ZFS tunings
vm.kmem_size="800M"
vm.kmem_size_max="800M"
# http://wiki.freebsd.org/ZFSTuningGuide
vfs.zfs.arc_max="160M"
vfs.zfs.vdev.cache.size="5M"
# and I have my root on zfs...
vfs.root.mountfrom="zfs:tank/root"
- Rudy
---------------------------------
** monkeybrains.net colocation **
---------------------------------
From owner-freebsd-stable@FreeBSD.ORG Wed Nov 19 19:48:57 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 61A611065675
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 19:48:57 +0000 (UTC)
(envelope-from erikt@midgard.homeip.net)
Received: from ch-smtp02.sth.basefarm.net (ch-smtp02.sth.basefarm.net
[80.76.149.213])
by mx1.freebsd.org (Postfix) with ESMTP id E7D878FC1F
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 19:48:56 +0000 (UTC)
(envelope-from erikt@midgard.homeip.net)
Received: from c83-255-48-78.bredband.comhem.se ([83.255.48.78]:58704
helo=falcon.midgard.homeip.net)
by ch-smtp02.sth.basefarm.net with esmtp (Exim 4.68)
(envelope-from <erikt@midgard.homeip.net>) id 1L2t2l-0004vN-8j
for freebsd-stable@freebsd.org; Wed, 19 Nov 2008 20:48:56 +0100
Received: (qmail 58410 invoked from network); 19 Nov 2008 20:48:51 +0100
Received: from owl.midgard.homeip.net (10.1.5.7)
by falcon.midgard.homeip.net with ESMTP; 19 Nov 2008 20:48:51 +0100
Received: (qmail 20915 invoked by uid 1001); 19 Nov 2008 20:48:51 +0100
Date: Wed, 19 Nov 2008 20:48:51 +0100
From: Erik Trulsson <ertr1013@student.uu.se>
To: Jeremy Chadwick <koitsu@FreeBSD.org>
Message-ID: <20081119194851.GA20898@owl.midgard.homeip.net>
References: <610465.33671.qm@web36108.mail.mud.yahoo.com>
<20081119191042.GA5284@icarus.home.lan>
<957588.98964.qm@web36103.mail.mud.yahoo.com>
<20081119193242.GA5739@icarus.home.lan>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20081119193242.GA5739@icarus.home.lan>
User-Agent: Mutt/1.5.18 (2008-05-17)
X-Originating-IP: 83.255.48.78
X-Scan-Result: No virus found in message 1L2t2l-0004vN-8j.
X-Scan-Signature: ch-smtp02.sth.basefarm.net 1L2t2l-0004vN-8j
ef1204270af6643ce49386de248bb9c2
Cc: freebsd-stable@freebsd.org, Mark Sams <msams992000@yahoo.com.au>
Subject: Re: atacontrol missing drive after upgrade to 6.3
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Nov 2008 19:48:57 -0000
On Wed, Nov 19, 2008 at 11:32:42AM -0800, Jeremy Chadwick wrote:
> On Wed, Nov 19, 2008 at 11:29:19AM -0800, Mark Sams wrote:
> > > From: Jeremy Chadwick <koitsu@FreeBSD.org>
> > > You're using Intel MatrixRAID, aren't you? Please migrate away from
> > > this immediately, your data is at risk.
> >
> > Ummm... I don't think so. It is just a standard RAID 1 mirror using the
> > built in ICH5 chip. It has been running fine for a over a year now on
> > the other builds of FreeBSD 6.x. It is not RAID 0+1 or whatever the
> > Matrix RAID thing is.
>
> The built-in ICH5 == Intel MatrixRAID. It's BIOS-level RAID under an
> Intel ICH chip. It's called MatrixRAID.
No, it is not. MatrixRAID was not introduced until with the ICH6R
controller. Earlier Intel ICH chips (including the ICH5) may well have
supported some kind of BIOS-level RAID, but it was not MatrixRAID.
(This is not to say that their earlier RAID implementations was any more
or less reliable - I have no data on that.)
>
> I have no personal problem with Intel MatrixRAID. What I'm telling you
> is that FreeBSD's support for it is horribly, horribly broken. You
> *will* lose your data. Read my Wiki entries in full.
>
> I'm only going to say this once more: please reconsider. You very
> likely are not going to be able to recover that failed array. The last
> person who had this problem had to boot a Linux LiveCD and attempt to
> use Linux tools to repair it.
--
<Insert your favourite quote here.>
Erik Trulsson
ertr1013@student.uu.se
From owner-freebsd-stable@FreeBSD.ORG Wed Nov 19 19:55:42 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id EBD6A106564A
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 19:55:42 +0000 (UTC)
(envelope-from jdc@koitsu.dyndns.org)
Received: from QMTA08.emeryville.ca.mail.comcast.net
(qmta08.emeryville.ca.mail.comcast.net [76.96.30.80])
by mx1.freebsd.org (Postfix) with ESMTP id B06538FC16
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 19:55:42 +0000 (UTC)
(envelope-from jdc@koitsu.dyndns.org)
Received: from OMTA13.emeryville.ca.mail.comcast.net ([76.96.30.52])
by QMTA08.emeryville.ca.mail.comcast.net with comcast
id h5As1a00H17UAYkA87vhs4; Wed, 19 Nov 2008 19:55:41 +0000
Received: from koitsu.dyndns.org ([69.181.141.110])
by OMTA13.emeryville.ca.mail.comcast.net with comcast
id h7vg1a00A2P6wsM8Z7vggw; Wed, 19 Nov 2008 19:55:41 +0000
X-Authority-Analysis: v=1.0 c=1 a=Kn1M_iXOy9EA:10 a=A7SOdGXiAqEA:10
a=QycZ5dHgAAAA:8 a=9O_rS1eGsEYHs9dy9-4A:9
a=esa0e8LPuXGUAOF094NT55y25LQA:4
a=EoioJ0NPDVgA:10 a=SV7veod9ZcQA:10 a=LY0hPdMaydYA:10
Received: by icarus.home.lan (Postfix, from userid 1000)
id 7A8EA33C1C; Wed, 19 Nov 2008 11:55:40 -0800 (PST)
Date: Wed, 19 Nov 2008 11:55:40 -0800
From: Jeremy Chadwick <koitsu@FreeBSD.org>
To: Erik Trulsson <ertr1013@student.uu.se>
Message-ID: <20081119195540.GA6217@icarus.home.lan>
References: <610465.33671.qm@web36108.mail.mud.yahoo.com>
<20081119191042.GA5284@icarus.home.lan>
<957588.98964.qm@web36103.mail.mud.yahoo.com>
<20081119193242.GA5739@icarus.home.lan>
<20081119194851.GA20898@owl.midgard.homeip.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20081119194851.GA20898@owl.midgard.homeip.net>
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: Mark Sams <msams992000@yahoo.com.au>, freebsd-stable@freebsd.org
Subject: Re: atacontrol missing drive after upgrade to 6.3
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Nov 2008 19:55:43 -0000
On Wed, Nov 19, 2008 at 08:48:51PM +0100, Erik Trulsson wrote:
> On Wed, Nov 19, 2008 at 11:32:42AM -0800, Jeremy Chadwick wrote:
> > On Wed, Nov 19, 2008 at 11:29:19AM -0800, Mark Sams wrote:
> > > > From: Jeremy Chadwick <koitsu@FreeBSD.org>
> > > > You're using Intel MatrixRAID, aren't you? Please migrate away from
> > > > this immediately, your data is at risk.
> > >
> > > Ummm... I don't think so. It is just a standard RAID 1 mirror using the
> > > built in ICH5 chip. It has been running fine for a over a year now on
> > > the other builds of FreeBSD 6.x. It is not RAID 0+1 or whatever the
> > > Matrix RAID thing is.
> >
> > The built-in ICH5 == Intel MatrixRAID. It's BIOS-level RAID under an
> > Intel ICH chip. It's called MatrixRAID.
>
> No, it is not. MatrixRAID was not introduced until with the ICH6R
> controller. Earlier Intel ICH chips (including the ICH5) may well have
> supported some kind of BIOS-level RAID, but it was not MatrixRAID.
>
> (This is not to say that their earlier RAID implementations was any more
> or less reliable - I have no data on that.)
This is news to me. I'll spend some time tonight at Intel's site
reading old chipset specifications. :-)
The ataraid(4) man page only mentions MatrixRAID with regards to Intel,
which is why I'm wondering what exactly the ICH5 offers. I wonder if
it's a very primitive RAID type which ataraid(4) simply handles under
the MatrixRAID code (which would explain the problems he's having with
getting the array back in order).
Thanks for the education lesson! Always appreciated. :-)
--
| Jeremy Chadwick jdc at parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |
From owner-freebsd-stable@FreeBSD.ORG Wed Nov 19 21:07:45 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id AA6541065670
for <stable@freebsd.org>; Wed, 19 Nov 2008 21:07:45 +0000 (UTC)
(envelope-from glen.j.barber@gmail.com)
Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.173])
by mx1.freebsd.org (Postfix) with ESMTP id 3915F8FC16
for <stable@freebsd.org>; Wed, 19 Nov 2008 21:07:45 +0000 (UTC)
(envelope-from glen.j.barber@gmail.com)
Received: by ug-out-1314.google.com with SMTP id 30so95408ugs.39
for <stable@freebsd.org>; Wed, 19 Nov 2008 13:07:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:message-id:date:from:to
:subject:cc:in-reply-to:mime-version:content-type
:content-transfer-encoding:content-disposition:references;
bh=1MaPcwahXhBZpoPA4deXX+hCXe4xpKhhzuQO8v8GzuM=;
b=Pvr4PRGmIxhFTrALvgm9W2pOnUZkL/cAp0Bb1/ndmkbOdT10obgfRM/xpaQOS/EdNp
hWtVQhK8WvSMCmK0/QyxNfLDtQXMpM7R0V2nLAt2alNNjBl5eOn1ultloFlYn4EbGSa8
EvxP367mZP/hHTrqwqdUBo2C3ZpFLZp7e/KfI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
:content-type:content-transfer-encoding:content-disposition
:references;
b=NfvvCA0teMOK+vOmuLO/EjF+3xvf4LTdQr4k8FIWnIiOeDaXzn44Kae1nAg2iDLFzt
YKlAmX49gGvqqd9DWhAfLjph71Qf93vs8gLDPOEiahdsBj1I3DKu6xeQj7WGr0FPlC0L
p8J4ob2RGqlsqD44jf3ZYg6e8JyrwY4SmAhY0=
Received: by 10.103.213.19 with SMTP id p19mr536793muq.9.1227128863985;
Wed, 19 Nov 2008 13:07:43 -0800 (PST)
Received: by 10.103.169.16 with HTTP; Wed, 19 Nov 2008 13:07:43 -0800 (PST)
Message-ID: <4ad871310811191307s1a87825ekf5557f347792e30@mail.gmail.com>
Date: Wed, 19 Nov 2008 16:07:43 -0500
From: "Glen Barber" <glen.j.barber@gmail.com>
To: "Ramesh Ayyagari" <rameshayyagari@yahoo.com>
In-Reply-To: <974618.15901.qm@web111109.mail.gq1.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <436595.20263.qm@web111109.mail.gq1.yahoo.com>
<4ad871310811181843v14e57474t8441b465dcb1ec99@mail.gmail.com>
<974618.15901.qm@web111109.mail.gq1.yahoo.com>
Cc: stable@freebsd.org
Subject: Re: What would be the appropriate value for kern.maxfiles
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Nov 2008 21:07:45 -0000
On Wed, Nov 19, 2008 at 3:51 PM, Ramesh Ayyagari
<rameshayyagari@yahoo.com> wrote:
> my server primarily runs postfix experiencing very huge inflow of mails
>>60000 per hour. There are some other services that the servers runs like
> caching DNS etc but postfix being the primary application running on it.
>
> Ram
>
1.) Please don't top-post.
2.) I gave you an example. You obviously know what your server is
doing, so you need to adjust the tunable accordingly. You can always
set the number "too high", then slim it down from there after testing
to see what meets your requirements.
--
Glen Barber
"If you have any trouble sounding condescending, find a Unix user to
show you how it's done."
--Scott Adams
From owner-freebsd-stable@FreeBSD.ORG Wed Nov 19 21:04:11 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 2BC941065673
for <stable@freebsd.org>; Wed, 19 Nov 2008 21:04:11 +0000 (UTC)
(envelope-from rameshayyagari@yahoo.com)
Received: from n66.bullet.mail.sp1.yahoo.com (n66.bullet.mail.sp1.yahoo.com
[98.136.44.50]) by mx1.freebsd.org (Postfix) with SMTP id 09D3C8FC08
for <stable@freebsd.org>; Wed, 19 Nov 2008 21:04:11 +0000 (UTC)
(envelope-from rameshayyagari@yahoo.com)
Received: from [69.147.84.145] by n66.bullet.mail.sp1.yahoo.com with NNFMP;
19 Nov 2008 20:51:17 -0000
Received: from [68.142.200.226] by t8.bullet.mail.sp1.yahoo.com with NNFMP;
19 Nov 2008 20:51:17 -0000
Received: from [68.142.201.240] by t7.bullet.mud.yahoo.com with NNFMP;
19 Nov 2008 20:51:16 -0000
Received: from [127.0.0.1] by omp401.mail.mud.yahoo.com with NNFMP;
19 Nov 2008 20:51:16 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 896218.77189.bm@omp401.mail.mud.yahoo.com
Received: (qmail 39240 invoked by uid 60001); 19 Nov 2008 20:51:16 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
h=X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:MIME-Version:Content-Type:Message-ID;
b=glsfSxzBnFg6vaS+P2bq9cVRZQPptJcttkESRCGPZn+WsW6afKApvbZqvlYGyfX/odWlNQEgZ54CGlM2g/BLzYGqgwridIGEmJ91hXyDxvCFSnXNBqWT+PaHMK8abV1fqj3ZhKyHYBqJ5koDlLgq1P56vmG9mqAsltEuZzOz/mU=;
X-YMail-OSG: 8g7vn14VM1n216IXKBNv8YNlr1MGsI_PspdJ0uSWzDFFjPgVqa00AoszLqU.wNZl1v5gzfsshACxCrj.n8tixSyNmWeZiwfVY.xnWkzFGQZE.xx.mBFM2.abFmzI4ma2Levu6.QI_6ORk5Sxh_PaDxDwA2Cs
Received: from [168.61.10.145] by web111109.mail.gq1.yahoo.com via HTTP;
Wed, 19 Nov 2008 12:51:15 PST
X-Mailer: YahooMailRC/1155.32 YahooMailWebService/0.7.260.1
References: <436595.20263.qm@web111109.mail.gq1.yahoo.com>
<4ad871310811181843v14e57474t8441b465dcb1ec99@mail.gmail.com>
Date: Wed, 19 Nov 2008 12:51:15 -0800 (PST)
From: Ramesh Ayyagari <rameshayyagari@yahoo.com>
To: Glen Barber <glen.j.barber@gmail.com>
MIME-Version: 1.0
Message-ID: <974618.15901.qm@web111109.mail.gq1.yahoo.com>
X-Mailman-Approved-At: Wed, 19 Nov 2008 21:11:48 +0000
Content-Type: text/plain; charset=us-ascii
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
Cc: stable@freebsd.org
Subject: Re: What would be the appropriate value for kern.maxfiles
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Nov 2008 21:04:11 -0000
my server primarily runs postfix experiencing very huge inflow of mails >60000 per hour. There are some other services that the servers runs like caching DNS etc but postfix being the primary application running on it.
Ram
________________________________
From: Glen Barber <glen.j.barber@gmail.com>
To: Ramesh Ayyagari <rameshayyagari@yahoo.com>
Cc: stable@freebsd.org
Sent: Tuesday, November 18, 2008 6:43:56 PM
Subject: Re: What would be the appropriate value for kern.maxfiles
On Tue, Nov 18, 2008 at 6:05 PM, Ramesh Ayyagari
<rameshayyagari@yahoo.com> wrote:
> Hello All,
>
> I have my client system running FreeBSD 6.3-RELEASE-p1 with 4 GB of RAM. This morning i have the following errors popping up on the console log -
>
> postfix/qmgr[94057]: fatal: socket: Too many open files
>
> Googling for this error, I found this is someway related to the kernel parameter kern.maxflies and increasing this value can have errors go away. The present value of this parameter is 24000. I also found this also depends of the RAM we have on the system.
>
> what would the appropriate value for kern.maxfiles for a system having 2GB RAM, a system having 4 GB and a system having 16GB of RAM. Please help
>
The Xorg meta-package recommends 'kern.maxfiles="25000"' for a desktop
system. This is a situation where it really depends on what you're
using your system for.
HTH
--
Glen Barber
570.328.0318
"If you have any trouble sounding condescending, find a Unix user to
show you how it's done."
--Scott Adams
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
From owner-freebsd-stable@FreeBSD.ORG Wed Nov 19 23:43:03 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 3844910656D2
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 23:43:03 +0000 (UTC)
(envelope-from msams992000@yahoo.com.au)
Received: from web36105.mail.mud.yahoo.com (web36105.mail.mud.yahoo.com
[66.163.179.219])
by mx1.freebsd.org (Postfix) with SMTP id D51458FC14
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 23:43:02 +0000 (UTC)
(envelope-from msams992000@yahoo.com.au)
Received: (qmail 38142 invoked by uid 60001); 19 Nov 2008 23:43:02 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com.au;
h=X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID;
b=bR2DYoZ6k6PuQBJQoFTsorIsyy4etk/YYOOGVDFvUT6Trk3oVVYLXtUZYXJYoMJVOLSacJ8fDkE/4zFBT0s1tG7M+vFDYEZ8dYdjRR05mPZYLWDTc9TjDN9hSJbkYfxAbkaj3gCYIbMI/GhZQzRJELPoIzZPDY/Ngx+MzYLYnoI=;
X-YMail-OSG: ITNfINcVM1lmSu3PpiQeOtJStkMvC4ELM6g1DQqkp.9hc1XSPRi3bLs5m9ilqPqI7zvD.TaMV.uUlMAAGdU8glbJnLmRQTAyRRPV6mCa2NaF6ibJMbqer2Qhcwc0kWheir3ax8mmLqNJsQ9ZBkFZ0O5TCbQ_LvqmUwmhuDneS1nTGRxO8yFvZ7VGngXY
Received: from [75.101.20.105] by web36105.mail.mud.yahoo.com via HTTP;
Wed, 19 Nov 2008 15:43:02 PST
X-Mailer: YahooMailRC/1155.32 YahooMailWebService/0.7.260.1
References: <610465.33671.qm@web36108.mail.mud.yahoo.com>
<20081119191042.GA5284@icarus.home.lan>
<957588.98964.qm@web36103.mail.mud.yahoo.com>
<20081119193242.GA5739@icarus.home.lan>
<20081119194851.GA20898@owl.midgard.homeip.net>
Date: Wed, 19 Nov 2008 15:43:02 -0800 (PST)
From: Mark Sams <msams992000@yahoo.com.au>
To: freebsd-stable@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Message-ID: <478001.37886.qm@web36105.mail.mud.yahoo.com>
Subject: Re: atacontrol missing drive after upgrade to 6.3
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Nov 2008 23:43:03 -0000
> > > > You're using Intel MatrixRAID, aren't you? Please migrate away fro=
m=0A=0A> > > > this immediately, your data is at risk.=0A=0AAlthough I am n=
ot using Matrix RAID, I guess I will switch to gmirror to be safe. Does the=
following approach seem valid?=0A=0A=0A1) Break the mirror (ar0)=0A2) Rebo=
ot using ad0=0A3) (from the link=0Ahttp://lantech.geekvenue.net/chucktips/j=
ason/chuck/1175552464/index_html ):=0A=0A Step 1: Use sysctl to allow the =
mounted disk to be modified=0A Step 2: Create the mirror (gm0) using ad0 w=
ith gmirror=0A Step 3: Modify /boot/loader.conf to load gmirror on startup=
=0A Step 4: Replace ar0 with gm0 in /etc/fstab=0A Step 6: Use gmirror ins=
ert command to add ad1 to gm0=0A Step 7: Check the mirroring status with g=
mirror statusShould I just call the mirror ar0 instead of gm0 and save doin=
g step4? Any problem with that?=0A=0AThanks in advance.=0A=0AMark=0A=0A=0A=
=0A Make the switch to the world's best email. Get Yahoo!7 Mail! h=
ttp://au.yahoo.com/y7mail
From owner-freebsd-stable@FreeBSD.ORG Wed Nov 19 23:54:52 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 358F81065673
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 23:54:52 +0000 (UTC)
(envelope-from erikt@midgard.homeip.net)
Received: from ch-smtp02.sth.basefarm.net (ch-smtp02.sth.basefarm.net
[80.76.149.213])
by mx1.freebsd.org (Postfix) with ESMTP id B66EF8FC1D
for <freebsd-stable@freebsd.org>; Wed, 19 Nov 2008 23:54:51 +0000 (UTC)
(envelope-from erikt@midgard.homeip.net)
Received: from c83-255-48-78.bredband.comhem.se ([83.255.48.78]:58747
helo=falcon.midgard.homeip.net)
by ch-smtp02.sth.basefarm.net with esmtp (Exim 4.68)
(envelope-from <erikt@midgard.homeip.net>) id 1L2wsj-0007XU-8d
for freebsd-stable@freebsd.org; Thu, 20 Nov 2008 00:54:50 +0100
Received: (qmail 59911 invoked from network); 20 Nov 2008 00:54:49 +0100
Received: from owl.midgard.homeip.net (10.1.5.7)
by falcon.midgard.homeip.net with ESMTP; 20 Nov 2008 00:54:49 +0100
Received: (qmail 23596 invoked by uid 1001); 20 Nov 2008 00:54:49 +0100
Date: Thu, 20 Nov 2008 00:54:49 +0100
From: Erik Trulsson <ertr1013@student.uu.se>
To: Mark Sams <msams992000@yahoo.com.au>
Message-ID: <20081119235449.GA23556@owl.midgard.homeip.net>
References: <610465.33671.qm@web36108.mail.mud.yahoo.com>
<20081119191042.GA5284@icarus.home.lan>
<957588.98964.qm@web36103.mail.mud.yahoo.com>
<20081119193242.GA5739@icarus.home.lan>
<20081119194851.GA20898@owl.midgard.homeip.net>
<478001.37886.qm@web36105.mail.mud.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <478001.37886.qm@web36105.mail.mud.yahoo.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
X-Originating-IP: 83.255.48.78
X-Scan-Result: No virus found in message 1L2wsj-0007XU-8d.
X-Scan-Signature: ch-smtp02.sth.basefarm.net 1L2wsj-0007XU-8d
d98ca73a957d0242e580bbe355c5f997
Cc: freebsd-stable@freebsd.org
Subject: Re: atacontrol missing drive after upgrade to 6.3
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Nov 2008 23:54:52 -0000
On Wed, Nov 19, 2008 at 03:43:02PM -0800, Mark Sams wrote:
> > > > > You're using Intel MatrixRAID, aren't you? Please migrate away from
>
> > > > > this immediately, your data is at risk.
>
> Although I am not using Matrix RAID, I guess I will switch to gmirror to be safe. Does the following approach seem valid?
>
You are missing one very important step that you should make regardless of
which approach you use:
0) Make a backup of any and all data that you don't want to lose (and check
that you can restore data from the backup while you still have the
original data.)
>
> 1) Break the mirror (ar0)
> 2) Reboot using ad0
> 3) (from the link
> http://lantech.geekvenue.net/chucktips/jason/chuck/1175552464/index_html ):
>
> Step 1: Use sysctl to allow the mounted disk to be modified
> Step 2: Create the mirror (gm0) using ad0 with gmirror
> Step 3: Modify /boot/loader.conf to load gmirror on startup
> Step 4: Replace ar0 with gm0 in /etc/fstab
> Step 6: Use gmirror insert command to add ad1 to gm0
> Step 7: Check the mirroring status with gmirror statusShould I just call the mirror ar0 instead of gm0 and save doing step4? Any problem with that?
>
> Thanks in advance.
>
> Mark
(Somebody else will have to answer if the above can be expected to work or
not, but I suspect that it would be easier and less errorprone to do as
follow:
1) Make backups of all data
2) Delete the old RAID array.
3) Create a new array from scratch
4) Restore data from backups)
--
<Insert your favourite quote here.>
Erik Trulsson
ertr1013@student.uu.se
From owner-freebsd-stable@FreeBSD.ORG Thu Nov 20 06:50:51 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@FreeBSD.ORG
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 75DA01065677
for <freebsd-stable@FreeBSD.ORG>; Thu, 20 Nov 2008 06:50:51 +0000 (UTC)
(envelope-from ganbold@micom.mng.net)
Received: from publicd.ub.mng.net (publicd.ub.mng.net [202.179.0.88])
by mx1.freebsd.org (Postfix) with ESMTP id 949768FC0A
for <freebsd-stable@FreeBSD.ORG>; Thu, 20 Nov 2008 06:50:50 +0000 (UTC)
(envelope-from ganbold@micom.mng.net)
Received: from [202.179.0.164] (helo=daemon.micom.mng.net)
by publicd.ub.mng.net with esmtpa (Exim 4.69 (FreeBSD))
(envelope-from <ganbold@micom.mng.net>)
id 1L33NG-000H9L-SA; Thu, 20 Nov 2008 14:50:46 +0800
Message-ID: <492508C6.3090005@micom.mng.net>
Date: Thu, 20 Nov 2008 14:50:46 +0800
From: Ganbold <ganbold@micom.mng.net>
User-Agent: Thunderbird 2.0.0.12 (X11/20080415)
MIME-Version: 1.0
To: freebsd-stable@FreeBSD.ORG
References: <4922906D.4060805@micom.mng.net>
In-Reply-To: <4922906D.4060805@micom.mng.net>
X-Enigmail-Version: 0.95.6
OpenPGP: id=78F6425E
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Kostik Belousov <kostikbel@gmail.com>, kib@FreeBSD.org
Subject: Re: shutdown -p now crashes
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Nov 2008 06:50:51 -0000
Ganbold wrote:
> #3 0xc06ab8b3 in vput (vp=0xc3d11ac8) at
> /usr/src/sys/kern/vfs_subr.c:2202
> #4 0xc06a69e6 in dounmount (mp=0xc3e59b30, flags=524288,
> td=0xc3b31d20) at /usr/src/sys/kern/vfs_mount.c:1288
> #5 0xc06aa493 in vfs_unmountall () at /usr/src/sys/kern/vfs_subr.c:2939
> #6 0xc062b7f4 in boot (howto=16392) at
> /usr/src/sys/kern/kern_shutdown.c:400
> #7 0xc062bc17 in reboot (td=0xc3b31d20, uap=0xeef55cfc) at
> /usr/src/sys/kern/kern_shutdown.c:172
> #8 0xc08171f5 in syscall (frame=0xeef55d38) at
> /usr/src/sys/i386/i386/trap.c:1090
> #9 0xc07fd710 in Xint0x80_syscall () at
> /usr/src/sys/i386/i386/exception.s:255
> #10 0x00000033 in ?? ()
> (kgdb)
> ..
I was able to reproduce the panic. I plugged in external ZFS/GELI HDD
via USB
and used 'zpool import' to import disk and did some 'ls' and then used
'zpool export' to umount disk.
Then I detached the disk from desktop and tried to "shutdown -p now".
This way panic is
reproduced 2 times.
More info:
daemon% uname -an
FreeBSD daemon.micom.mng.net 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #8
r185085M: Thu Nov 20 12:50:33 ULAT 2008
tsgan@daemon.micom.mng.net:/usr/obj/usr/src/sys/GDAEMON i386
daemon%
<118>.
<118>Writing entropy file:
<118>.
<118>Terminated
<118>.
<118>Nov 20 14:30:12 daemon syslogd: exiting on signal 15
rootvp 0xc3d11ac8 v_usecount 2
KDB: stack backtrace:
db_trace_self_wrapper(c086b1ee,f2c6bbac,c06abb23,c086faa8,c3d11ac8,...)
at db_trace_self_wrapper+0x26
kdb_backtrace(c086faa8,c3d11ac8,2,b,0,...) at kdb_backtrace+0x29
vrele(c3d11ac8,c3e6f690,0,0,0,...) at vrele+0x83
fdfree(c3e6f690,c3e8f000,48077bf0,f2c6bc80,c062ccfe,...) at fdfree+0x8b6
exit1(c3e6f690,0,f2c6bd2c,c0817245,c3e6f690,...) at exit1+0x5e9
sys_exit(c3e6f690,f2c6bcfc,4,c3e6f690,f2c6bd2c,...) at sys_exit+0x1d
syscall(f2c6bd38) at syscall+0x335
Xint0x80_syscall() at Xint0x80_syscall+0x20
--- syscall (1, FreeBSD ELF32, sys_exit), eip = 0x4810ed2f, esp =
0xbfbfe6bc, ebp = 0xbfbfe6c8 ---
rootvp 0xc3d11ac8 v_usecount 1
KDB: stack backtrace:
db_trace_self_wrapper(c086b1ee,f2c6bbac,c06abb23,c086faa8,c3d11ac8,...)
at db_trace_self_wrapper+0x26
kdb_backtrace(c086faa8,c3d11ac8,1,b,0,...) at kdb_backtrace+0x29
vrele(c3d11ac8,c3e6f690,0,0,0,...) at vrele+0x83
fdfree(c3e6f690,c3e8f000,48077bf0,f2c6bc80,c062ccfe,...) at fdfree+0x8c3
exit1(c3e6f690,0,f2c6bd2c,c0817245,c3e6f690,...) at exit1+0x5e9
sys_exit(c3e6f690,f2c6bcfc,4,c3e6f690,f2c6bd2c,...) at sys_exit+0x1d
syscall(f2c6bd38) at syscall+0x335
Xint0x80_syscall() at Xint0x80_syscall+0x20
--- syscall (1, FreeBSD ELF32, sys_exit), eip = 0x4810ed2f, esp =
0xbfbfe6bc, ebp = 0xbfbfe6c8 ---
Waiting (max 60 seconds) for system process `vnlru' to stop...done
Waiting (max 60 seconds) for system process `bufdaemon' to stop...done
Waiting (max 60 seconds) for system process `syncer' to stop...
Syncing disks, vnodes remaining...2 1 0 0 done
All buffers synced.
rootvp 0xc3d11ac8 v_usecount 1
KDB: stack backtrace:
db_trace_self_wrapper(c086b1ee,eef55ba8,c06abb23,c086faa8,c3d11ac8,...)
at db_trace_self_wrapper+0x26
kdb_backtrace(c086faa8,c3d11ac8,1,c3b31d20,eef55ba8,...) at
kdb_backtrace+0x29
vrele(c3d11ac8,2,eef55bf0,c3b31d20,0,...) at vrele+0x83
dounmount(c3e56b30,80000,c3b31d20,e3b61aec,0,...) at dounmount+0x491
vfs_unmountall(c0869007,0,c086906b,117,eef55c50,...) at vfs_unmountall+0x33
boot(c3b31d20,8,0,fffffffe,c3b31d20,...) at boot+0x444
reboot(c3b31d20,eef55cfc,4,8048290,9e7c9054,...) at reboot+0x67
syscall(eef55d38) at syscall+0x335
Xint0x80_syscall() at Xint0x80_syscall+0x20
--- syscall (55, FreeBSD ELF32, reboot), eip = 0x8050bb3, esp =
0xbfbfe8ec, ebp = 0xbfbfe9b8 ---
panic: vput: negative ref cnt
cpuid = 0
KDB: stack backtrace:
db_trace_self_wrapper(c086b1ee,eef55b68,c062bd39,c08832ea,0,...) at
db_trace_self_wrapper+0x26
kdb_backtrace(c08832ea,0,c086fac1,eef55b74,0,...) at kdb_backtrace+0x29
panic(c086fac1,eef55ba8,c06abcd0,c3d11ac8,eef55b90,...) at panic+0x119
vput(c3d11ac8,2,eef55bf0,c3b31d20,0,...) at vput+0xf3
dounmount(c3e56b30,80000,c3b31d20,e3b61aec,0,...) at dounmount+0x4a6
vfs_unmountall(c0869007,0,c086906b,117,eef55c50,...) at vfs_unmountall+0x33
boot(c3b31d20,8,0,fffffffe,c3b31d20,...) at boot+0x444
reboot(c3b31d20,eef55cfc,4,8048290,9e7c9054,...) at reboot+0x67
syscall(eef55d38) at syscall+0x335
Xint0x80_syscall() at Xint0x80_syscall+0x20
--- syscall (55, FreeBSD ELF32, reboot), eip = 0x8050bb3, esp =
0xbfbfe8ec, ebp = 0xbfbfe9b8 ---
Uptime: 7m3s
Physical memory: 1013 MB
Dumping 54 MB: 39 23 7
(kgdb) where
#0 doadump () at pcpu.h:196
#1 0xc062ba67 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418
#2 0xc062bd72 in panic (fmt=Variable "fmt" is not available.
) at /usr/src/sys/kern/kern_shutdown.c:574
#3 0xc06ab8e3 in vput (vp=0xc3d11ac8) at /usr/src/sys/kern/vfs_subr.c:2211
#4 0xc06a69e6 in dounmount (mp=0xc3e56b30, flags=524288, td=0xc3b31d20)
at /usr/src/sys/kern/vfs_mount.c:1288
#5 0xc06aa493 in vfs_unmountall () at /usr/src/sys/kern/vfs_subr.c:2948
#6 0xc062b7f4 in boot (howto=16392) at
/usr/src/sys/kern/kern_shutdown.c:400
#7 0xc062bc17 in reboot (td=0xc3b31d20, uap=0xeef55cfc) at
/usr/src/sys/kern/kern_shutdown.c:172
#8 0xc0817245 in syscall (frame=0xeef55d38) at
/usr/src/sys/i386/i386/trap.c:1090
#9 0xc07fd760 in Xint0x80_syscall () at
/usr/src/sys/i386/i386/exception.s:255
#10 0x00000033 in ?? ()
(kgdb) frame 4
#4 0xc06a69e6 in dounmount (mp=0xc3e56b30, flags=524288, td=0xc3b31d20)
at /usr/src/sys/kern/vfs_mount.c:1288
1288 vput(fsrootvp);
(kgdb) p *mp
$1 = {mnt_lock = {lk_object = {lo_name = 0xc086f234 "vfslock", lo_type =
0xc086f234 "vfslock", lo_flags = 70844416, lo_witness_data = {lod_list = {
stqe_next = 0x0}, lod_witness = 0x0}}, lk_interlock =
0xc0956fa8, lk_flags = 1310720, lk_sharecount = 0, lk_waitcount = 0,
lk_exclusivecount = 1,
lk_prio = 80, lk_timo = 0, lk_lockholder = 0xc3b31d20, lk_newlock =
0x0}, mnt_mtx = {lock_object = {lo_name = 0xc086f223 "struct mount mtx",
lo_type = 0xc086f223 "struct mount mtx", lo_flags = 16973824,
lo_witness_data = {lod_list = {stqe_next = 0x0}, lod_witness = 0x0}},
mtx_lock = 4,
mtx_recurse = 0}, mnt_gen = 1, mnt_list = {tqe_next = 0x0, tqe_prev
= 0xc091c224}, mnt_op = 0xc0926080, mnt_vfc = 0xc0926040,
mnt_vnodecovered = 0x0,
mnt_syncer = 0x0, mnt_ref = 736, mnt_nvnodelist = {tqh_first =
0xc3d11ac8, tqh_last = 0xc67fd350}, mnt_nvnodelistsize = 736,
mnt_writeopcount = 1,
mnt_kern_flag = 553648137, mnt_flag = 20480, mnt_noasync = 0, mnt_opt
= 0xc3c4cc90, mnt_optnew = 0x0, mnt_maxsymlinklen = 120, mnt_stat = {
f_version = 537068824, f_type = 1, f_flags = 20480, f_bsize = 2048,
f_iosize = 16384, f_blocks = 2538519, f_bfree = 2339932, f_bavail =
2136851,
f_files = 659454, f_ffree = 651413, f_syncwrites = 0, f_asyncwrites
= 0, f_syncreads = 0, f_asyncreads = 0, f_spare = {0, 0, 0, 0, 0, 0, 0,
0, 0, 0},
f_namemax = 255, f_owner = 0, f_fsid = {val = {1149777033,
1944990175}}, f_charspare = '\0' <repeats 79 times>,
f_fstypename = "ufs", '\0' <repeats 12 times>, f_mntfromname =
"/dev/ad4s1a", '\0' <repeats 76 times>, f_mntonname = "/", '\0' <repeats
86 times>},
mnt_cred = 0xc3e52700, mnt_data = 0xc3e52600, mnt_time = 1227162073,
mnt_iosize_max = 131072, mnt_export = 0x0, mnt_label = 0x0,
mnt_hashseed = 2358371174, mnt_markercnt = 0, mnt_holdcnt = 0,
mnt_holdcntwaiters = 0, mnt_secondary_writes = 0,
mnt_secondary_accwrites = 2874,
mnt_gjprovider = 0x0, mnt_explock = {lk_object = {lo_name = 0xc086f23c
"explock", lo_type = 0xc086f23c "explock", lo_flags = 70844416,
lo_witness_data = {
lod_list = {stqe_next = 0x0}, lod_witness = 0x0}}, lk_interlock
= 0xc0956fc0, lk_flags = 0, lk_sharecount = 0, lk_waitcount = 0,
lk_exclusivecount = 0, lk_prio = 80, lk_timo = 0, lk_lockholder =
0xffffffff, lk_newlock = 0x0}}
(kgdb) p fsrootvp
$2 = (struct vnode *) 0xc3d11ac8
(kgdb) p *fsrootvp
$3 = {v_type = VDIR, v_tag = 0xc0864e51 "ufs", v_op = 0xc0926280, v_data
= 0xc3e5d000, v_mount = 0xc3e56b30, v_nmntvnodes = {tqe_next = 0xc3d119b4,
tqe_prev = 0xc3e56b98}, v_un = {vu_mount = 0x0, vu_socket = 0x0,
vu_cdev = 0x0, vu_fifoinfo = 0x0, vu_yield = 0}, v_hashlist = {le_next =
0x0,
le_prev = 0xc3d09da0}, v_hash = 2, v_cache_src = {lh_first = 0x0},
v_cache_dst = {tqh_first = 0x0, tqh_last = 0xc3d11af8}, v_dd = 0x0,
v_cstart = 0,
v_lasta = 0, v_lastw = 0, v_clen = 0, v_lock = {lk_object = {lo_name =
0xc0864e51 "ufs", lo_type = 0xc0864e51 "ufs", lo_flags = 70844416,
lo_witness_data = {lod_list = {stqe_next = 0x0}, lod_witness =
0x0}}, lk_interlock = 0xc0956510, lk_flags = 262208, lk_sharecount = 0,
lk_waitcount = 0, lk_exclusivecount = 1, lk_prio = 80, lk_timo = 51,
lk_lockholder = 0xc3b31d20, lk_newlock = 0x0}, v_interlock =
{lock_object = {
lo_name = 0xc086fb51 "vnode interlock", lo_type = 0xc086fb51
"vnode interlock", lo_flags = 16973824, lo_witness_data = {lod_list =
{stqe_next = 0x0},
lod_witness = 0x0}}, mtx_lock = 3283295520, mtx_recurse = 0},
v_vnlock = 0xc3d11b20, v_holdcnt = 2, v_usecount = 0, v_iflag = 0,
v_vflag = 1,
v_writecount = 0, v_freelist = {tqe_next = 0x0, tqe_prev = 0x0},
v_bufobj = {bo_mtx = 0xc3d11b50, bo_clean = {bv_hd = {tqh_first =
0xe3d02594,
tqh_last = 0xe3d025cc}, bv_root = 0xe3d02594, bv_cnt = 1},
bo_dirty = {bv_hd = {tqh_first = 0x0, tqh_last = 0xc3d11b9c}, bv_root =
0x0,
bv_cnt = 0}, bo_numoutput = 0, bo_flag = 0, bo_ops = 0xc091ae00,
bo_bsize = 16384, bo_object = 0xc106183c, bo_synclist = {le_next = 0x0,
le_prev = 0x0}, bo_private = 0xc3d11ac8, __bo_vnode = 0xc3d11ac8},
v_pollinfo = 0x0, v_label = 0x0, v_lockf = 0x0}
(kgdb) p rootvnode
$4 = (struct vnode *) 0x0
(kgdb) p *rootvnode
Cannot access memory at address 0x0
(kgdb)
--
They are called computers simply because computation is the only
significant job that has so far been given to them.
From owner-freebsd-stable@FreeBSD.ORG Thu Nov 20 07:11:41 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 109B7106564A
for <freebsd-stable@freebsd.org>; Thu, 20 Nov 2008 07:11:41 +0000 (UTC)
(envelope-from jdc@koitsu.dyndns.org)
Received: from QMTA07.westchester.pa.mail.comcast.net
(qmta07.westchester.pa.mail.comcast.net [76.96.62.64])
by mx1.freebsd.org (Postfix) with ESMTP id C9F488FC18
for <freebsd-stable@freebsd.org>; Thu, 20 Nov 2008 07:11:39 +0000 (UTC)
(envelope-from jdc@koitsu.dyndns.org)
Received: from OMTA07.westchester.pa.mail.comcast.net ([76.96.62.59])
by QMTA07.westchester.pa.mail.comcast.net with comcast
id hKAA1a0011GhbT857KAoUk; Thu, 20 Nov 2008 07:10:48 +0000
Received: from koitsu.dyndns.org ([69.181.141.110])
by OMTA07.westchester.pa.mail.comcast.net with comcast
id hKBc1a0032P6wsM3TKBdjv; Thu, 20 Nov 2008 07:11:38 +0000
X-Authority-Analysis: v=1.0 c=1 a=6I5d2MoRAAAA:8 a=QycZ5dHgAAAA:8
a=AFzJLNVnVYuBpOHGbGgA:9 a=3telo9Gqa0uFKkogSGIA:7
a=r9g8t6t6mHK2g1TyIS-V3RKyoAAA:4 a=EoioJ0NPDVgA:10 a=SV7veod9ZcQA:10
a=LY0hPdMaydYA:10
Received: by icarus.home.lan (Postfix, from userid 1000)
id A903E33C1C; Wed, 19 Nov 2008 23:11:36 -0800 (PST)
Date: Wed, 19 Nov 2008 23:11:36 -0800
From: Jeremy Chadwick <koitsu@FreeBSD.org>
To: Ganbold <ganbold@micom.mng.net>
Message-ID: <20081120071136.GA19577@icarus.home.lan>
References: <4922906D.4060805@micom.mng.net> <492508C6.3090005@micom.mng.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <492508C6.3090005@micom.mng.net>
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: Kostik Belousov <kostikbel@gmail.com>, kib@FreeBSD.org,
freebsd-stable@FreeBSD.ORG
Subject: Re: shutdown -p now crashes
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Nov 2008 07:11:41 -0000
On Thu, Nov 20, 2008 at 02:50:46PM +0800, Ganbold wrote:
> Ganbold wrote:
>> #3 0xc06ab8b3 in vput (vp=0xc3d11ac8) at
>> /usr/src/sys/kern/vfs_subr.c:2202
>> #4 0xc06a69e6 in dounmount (mp=0xc3e59b30, flags=524288,
>> td=0xc3b31d20) at /usr/src/sys/kern/vfs_mount.c:1288
>> #5 0xc06aa493 in vfs_unmountall () at /usr/src/sys/kern/vfs_subr.c:2939
>> #6 0xc062b7f4 in boot (howto=16392) at
>> /usr/src/sys/kern/kern_shutdown.c:400
>> #7 0xc062bc17 in reboot (td=0xc3b31d20, uap=0xeef55cfc) at
>> /usr/src/sys/kern/kern_shutdown.c:172
>> #8 0xc08171f5 in syscall (frame=0xeef55d38) at
>> /usr/src/sys/i386/i386/trap.c:1090
>> #9 0xc07fd710 in Xint0x80_syscall () at
>> /usr/src/sys/i386/i386/exception.s:255
>> #10 0x00000033 in ?? ()
>> (kgdb)
>> ..
> I was able to reproduce the panic. I plugged in external ZFS/GELI HDD
> via USB
> and used 'zpool import' to import disk and did some 'ls' and then used
> 'zpool export' to umount disk.
> Then I detached the disk from desktop and tried to "shutdown -p now".
> This way panic is
> reproduced 2 times.
Are we sure that the problem isn't the well-known "do not yank a device
out from underneathe the rest of the OS" problem, e.g. removing
removable devices while filesystems are still mounted? If so, this
problem is very well-known, documented on my Wiki, and work is being
done in CURRENT to fix it (official ETA is 2009/02).
I see geli(8) has a "detach" option, which you might need to do after
the "zpool export", being as the GEOM provider is still attached to
the USB HDD. I would recommend trying that first.
> More info:
>
> daemon% uname -an
> FreeBSD daemon.micom.mng.net 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #8
> r185085M: Thu Nov 20 12:50:33 ULAT 2008
> tsgan@daemon.micom.mng.net:/usr/obj/usr/src/sys/GDAEMON i386
> daemon%
>
>
> <118>.
> <118>Writing entropy file:
> <118>.
> <118>Terminated
> <118>.
> <118>Nov 20 14:30:12 daemon syslogd: exiting on signal 15
> rootvp 0xc3d11ac8 v_usecount 2
> KDB: stack backtrace:
> db_trace_self_wrapper(c086b1ee,f2c6bbac,c06abb23,c086faa8,c3d11ac8,...)
> at db_trace_self_wrapper+0x26
> kdb_backtrace(c086faa8,c3d11ac8,2,b,0,...) at kdb_backtrace+0x29
> vrele(c3d11ac8,c3e6f690,0,0,0,...) at vrele+0x83
> fdfree(c3e6f690,c3e8f000,48077bf0,f2c6bc80,c062ccfe,...) at fdfree+0x8b6
> exit1(c3e6f690,0,f2c6bd2c,c0817245,c3e6f690,...) at exit1+0x5e9
> sys_exit(c3e6f690,f2c6bcfc,4,c3e6f690,f2c6bd2c,...) at sys_exit+0x1d
> syscall(f2c6bd38) at syscall+0x335
> Xint0x80_syscall() at Xint0x80_syscall+0x20
> --- syscall (1, FreeBSD ELF32, sys_exit), eip = 0x4810ed2f, esp =
> 0xbfbfe6bc, ebp = 0xbfbfe6c8 ---
> rootvp 0xc3d11ac8 v_usecount 1
> KDB: stack backtrace:
> db_trace_self_wrapper(c086b1ee,f2c6bbac,c06abb23,c086faa8,c3d11ac8,...)
> at db_trace_self_wrapper+0x26
> kdb_backtrace(c086faa8,c3d11ac8,1,b,0,...) at kdb_backtrace+0x29
> vrele(c3d11ac8,c3e6f690,0,0,0,...) at vrele+0x83
> fdfree(c3e6f690,c3e8f000,48077bf0,f2c6bc80,c062ccfe,...) at fdfree+0x8c3
> exit1(c3e6f690,0,f2c6bd2c,c0817245,c3e6f690,...) at exit1+0x5e9
> sys_exit(c3e6f690,f2c6bcfc,4,c3e6f690,f2c6bd2c,...) at sys_exit+0x1d
> syscall(f2c6bd38) at syscall+0x335
> Xint0x80_syscall() at Xint0x80_syscall+0x20
> --- syscall (1, FreeBSD ELF32, sys_exit), eip = 0x4810ed2f, esp =
> 0xbfbfe6bc, ebp = 0xbfbfe6c8 ---
> Waiting (max 60 seconds) for system process `vnlru' to stop...done
> Waiting (max 60 seconds) for system process `bufdaemon' to stop...done
> Waiting (max 60 seconds) for system process `syncer' to stop...
> Syncing disks, vnodes remaining...2 1 0 0 done
> All buffers synced.
> rootvp 0xc3d11ac8 v_usecount 1
> KDB: stack backtrace:
> db_trace_self_wrapper(c086b1ee,eef55ba8,c06abb23,c086faa8,c3d11ac8,...)
> at db_trace_self_wrapper+0x26
> kdb_backtrace(c086faa8,c3d11ac8,1,c3b31d20,eef55ba8,...) at
> kdb_backtrace+0x29
> vrele(c3d11ac8,2,eef55bf0,c3b31d20,0,...) at vrele+0x83
> dounmount(c3e56b30,80000,c3b31d20,e3b61aec,0,...) at dounmount+0x491
> vfs_unmountall(c0869007,0,c086906b,117,eef55c50,...) at vfs_unmountall+0x33
> boot(c3b31d20,8,0,fffffffe,c3b31d20,...) at boot+0x444
> reboot(c3b31d20,eef55cfc,4,8048290,9e7c9054,...) at reboot+0x67
> syscall(eef55d38) at syscall+0x335
> Xint0x80_syscall() at Xint0x80_syscall+0x20
> --- syscall (55, FreeBSD ELF32, reboot), eip = 0x8050bb3, esp =
> 0xbfbfe8ec, ebp = 0xbfbfe9b8 ---
> panic: vput: negative ref cnt
> cpuid = 0
> KDB: stack backtrace:
> db_trace_self_wrapper(c086b1ee,eef55b68,c062bd39,c08832ea,0,...) at
> db_trace_self_wrapper+0x26
> kdb_backtrace(c08832ea,0,c086fac1,eef55b74,0,...) at kdb_backtrace+0x29
> panic(c086fac1,eef55ba8,c06abcd0,c3d11ac8,eef55b90,...) at panic+0x119
> vput(c3d11ac8,2,eef55bf0,c3b31d20,0,...) at vput+0xf3
> dounmount(c3e56b30,80000,c3b31d20,e3b61aec,0,...) at dounmount+0x4a6
> vfs_unmountall(c0869007,0,c086906b,117,eef55c50,...) at vfs_unmountall+0x33
> boot(c3b31d20,8,0,fffffffe,c3b31d20,...) at boot+0x444
> reboot(c3b31d20,eef55cfc,4,8048290,9e7c9054,...) at reboot+0x67
> syscall(eef55d38) at syscall+0x335
> Xint0x80_syscall() at Xint0x80_syscall+0x20
> --- syscall (55, FreeBSD ELF32, reboot), eip = 0x8050bb3, esp =
> 0xbfbfe8ec, ebp = 0xbfbfe9b8 ---
> Uptime: 7m3s
> Physical memory: 1013 MB
> Dumping 54 MB: 39 23 7
> (kgdb) where
> #0 doadump () at pcpu.h:196
> #1 0xc062ba67 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418
> #2 0xc062bd72 in panic (fmt=Variable "fmt" is not available.
> ) at /usr/src/sys/kern/kern_shutdown.c:574
> #3 0xc06ab8e3 in vput (vp=0xc3d11ac8) at /usr/src/sys/kern/vfs_subr.c:2211
> #4 0xc06a69e6 in dounmount (mp=0xc3e56b30, flags=524288, td=0xc3b31d20)
> at /usr/src/sys/kern/vfs_mount.c:1288
> #5 0xc06aa493 in vfs_unmountall () at /usr/src/sys/kern/vfs_subr.c:2948
> #6 0xc062b7f4 in boot (howto=16392) at
> /usr/src/sys/kern/kern_shutdown.c:400
> #7 0xc062bc17 in reboot (td=0xc3b31d20, uap=0xeef55cfc) at
> /usr/src/sys/kern/kern_shutdown.c:172
> #8 0xc0817245 in syscall (frame=0xeef55d38) at
> /usr/src/sys/i386/i386/trap.c:1090
> #9 0xc07fd760 in Xint0x80_syscall () at
> /usr/src/sys/i386/i386/exception.s:255
> #10 0x00000033 in ?? ()
> (kgdb) frame 4
> #4 0xc06a69e6 in dounmount (mp=0xc3e56b30, flags=524288, td=0xc3b31d20)
> at /usr/src/sys/kern/vfs_mount.c:1288
> 1288 vput(fsrootvp);
> (kgdb) p *mp
> $1 = {mnt_lock = {lk_object = {lo_name = 0xc086f234 "vfslock", lo_type =
> 0xc086f234 "vfslock", lo_flags = 70844416, lo_witness_data = {lod_list =
> {
> stqe_next = 0x0}, lod_witness = 0x0}}, lk_interlock =
> 0xc0956fa8, lk_flags = 1310720, lk_sharecount = 0, lk_waitcount = 0,
> lk_exclusivecount = 1,
> lk_prio = 80, lk_timo = 0, lk_lockholder = 0xc3b31d20, lk_newlock =
> 0x0}, mnt_mtx = {lock_object = {lo_name = 0xc086f223 "struct mount mtx",
> lo_type = 0xc086f223 "struct mount mtx", lo_flags = 16973824,
> lo_witness_data = {lod_list = {stqe_next = 0x0}, lod_witness = 0x0}},
> mtx_lock = 4,
> mtx_recurse = 0}, mnt_gen = 1, mnt_list = {tqe_next = 0x0, tqe_prev =
> 0xc091c224}, mnt_op = 0xc0926080, mnt_vfc = 0xc0926040, mnt_vnodecovered
> = 0x0,
> mnt_syncer = 0x0, mnt_ref = 736, mnt_nvnodelist = {tqh_first =
> 0xc3d11ac8, tqh_last = 0xc67fd350}, mnt_nvnodelistsize = 736,
> mnt_writeopcount = 1,
> mnt_kern_flag = 553648137, mnt_flag = 20480, mnt_noasync = 0, mnt_opt =
> 0xc3c4cc90, mnt_optnew = 0x0, mnt_maxsymlinklen = 120, mnt_stat = {
> f_version = 537068824, f_type = 1, f_flags = 20480, f_bsize = 2048,
> f_iosize = 16384, f_blocks = 2538519, f_bfree = 2339932, f_bavail =
> 2136851,
> f_files = 659454, f_ffree = 651413, f_syncwrites = 0, f_asyncwrites =
> 0, f_syncreads = 0, f_asyncreads = 0, f_spare = {0, 0, 0, 0, 0, 0, 0, 0,
> 0, 0},
> f_namemax = 255, f_owner = 0, f_fsid = {val = {1149777033,
> 1944990175}}, f_charspare = '\0' <repeats 79 times>,
> f_fstypename = "ufs", '\0' <repeats 12 times>, f_mntfromname =
> "/dev/ad4s1a", '\0' <repeats 76 times>, f_mntonname = "/", '\0' <repeats
> 86 times>},
> mnt_cred = 0xc3e52700, mnt_data = 0xc3e52600, mnt_time = 1227162073,
> mnt_iosize_max = 131072, mnt_export = 0x0, mnt_label = 0x0,
> mnt_hashseed = 2358371174, mnt_markercnt = 0, mnt_holdcnt = 0,
> mnt_holdcntwaiters = 0, mnt_secondary_writes = 0,
> mnt_secondary_accwrites = 2874,
> mnt_gjprovider = 0x0, mnt_explock = {lk_object = {lo_name = 0xc086f23c
> "explock", lo_type = 0xc086f23c "explock", lo_flags = 70844416,
> lo_witness_data = {
> lod_list = {stqe_next = 0x0}, lod_witness = 0x0}}, lk_interlock =
> 0xc0956fc0, lk_flags = 0, lk_sharecount = 0, lk_waitcount = 0,
> lk_exclusivecount = 0, lk_prio = 80, lk_timo = 0, lk_lockholder =
> 0xffffffff, lk_newlock = 0x0}}
> (kgdb) p fsrootvp $2 = (struct vnode *) 0xc3d11ac8
> (kgdb) p *fsrootvp
> $3 = {v_type = VDIR, v_tag = 0xc0864e51 "ufs", v_op = 0xc0926280, v_data
> = 0xc3e5d000, v_mount = 0xc3e56b30, v_nmntvnodes = {tqe_next =
> 0xc3d119b4,
> tqe_prev = 0xc3e56b98}, v_un = {vu_mount = 0x0, vu_socket = 0x0,
> vu_cdev = 0x0, vu_fifoinfo = 0x0, vu_yield = 0}, v_hashlist = {le_next =
> 0x0,
> le_prev = 0xc3d09da0}, v_hash = 2, v_cache_src = {lh_first = 0x0},
> v_cache_dst = {tqh_first = 0x0, tqh_last = 0xc3d11af8}, v_dd = 0x0,
> v_cstart = 0,
> v_lasta = 0, v_lastw = 0, v_clen = 0, v_lock = {lk_object = {lo_name =
> 0xc0864e51 "ufs", lo_type = 0xc0864e51 "ufs", lo_flags = 70844416,
> lo_witness_data = {lod_list = {stqe_next = 0x0}, lod_witness =
> 0x0}}, lk_interlock = 0xc0956510, lk_flags = 262208, lk_sharecount = 0,
> lk_waitcount = 0, lk_exclusivecount = 1, lk_prio = 80, lk_timo = 51,
> lk_lockholder = 0xc3b31d20, lk_newlock = 0x0}, v_interlock =
> {lock_object = {
> lo_name = 0xc086fb51 "vnode interlock", lo_type = 0xc086fb51 "vnode
> interlock", lo_flags = 16973824, lo_witness_data = {lod_list =
> {stqe_next = 0x0},
> lod_witness = 0x0}}, mtx_lock = 3283295520, mtx_recurse = 0},
> v_vnlock = 0xc3d11b20, v_holdcnt = 2, v_usecount = 0, v_iflag = 0,
> v_vflag = 1,
> v_writecount = 0, v_freelist = {tqe_next = 0x0, tqe_prev = 0x0},
> v_bufobj = {bo_mtx = 0xc3d11b50, bo_clean = {bv_hd = {tqh_first =
> 0xe3d02594,
> tqh_last = 0xe3d025cc}, bv_root = 0xe3d02594, bv_cnt = 1},
> bo_dirty = {bv_hd = {tqh_first = 0x0, tqh_last = 0xc3d11b9c}, bv_root =
> 0x0,
> bv_cnt = 0}, bo_numoutput = 0, bo_flag = 0, bo_ops = 0xc091ae00,
> bo_bsize = 16384, bo_object = 0xc106183c, bo_synclist = {le_next = 0x0,
> le_prev = 0x0}, bo_private = 0xc3d11ac8, __bo_vnode = 0xc3d11ac8},
> v_pollinfo = 0x0, v_label = 0x0, v_lockf = 0x0}
> (kgdb) p rootvnode
> $4 = (struct vnode *) 0x0
> (kgdb) p *rootvnode
> Cannot access memory at address 0x0
> (kgdb)
>
>
> --
> They are called computers simply because computation is the only
> significant job that has so far been given to them.
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
--
| Jeremy Chadwick jdc at parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |
From owner-freebsd-stable@FreeBSD.ORG Thu Nov 20 07:18:14 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@FreeBSD.ORG
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id B6B221065673;
Thu, 20 Nov 2008 07:18:14 +0000 (UTC)
(envelope-from ganbold@micom.mng.net)
Received: from publicd.ub.mng.net (publicd.ub.mng.net [202.179.0.88])
by mx1.freebsd.org (Postfix) with ESMTP id 358278FC1A;
Thu, 20 Nov 2008 07:18:14 +0000 (UTC)
(envelope-from ganbold@micom.mng.net)
Received: from [202.179.0.164] (helo=daemon.micom.mng.net)
by publicd.ub.mng.net with esmtpa (Exim 4.69 (FreeBSD))
(envelope-from <ganbold@micom.mng.net>)
id 1L33nn-000Hsv-1g; Thu, 20 Nov 2008 15:18:11 +0800
Message-ID: <49250F32.5080807@micom.mng.net>
Date: Thu, 20 Nov 2008 15:18:10 +0800
From: Ganbold <ganbold@micom.mng.net>
User-Agent: Thunderbird 2.0.0.12 (X11/20080415)
MIME-Version: 1.0
To: Jeremy Chadwick <koitsu@FreeBSD.org>
References: <4922906D.4060805@micom.mng.net> <492508C6.3090005@micom.mng.net>
<20081120071136.GA19577@icarus.home.lan>
In-Reply-To: <20081120071136.GA19577@icarus.home.lan>
X-Enigmail-Version: 0.95.6
OpenPGP: id=78F6425E
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Kostik Belousov <kostikbel@gmail.com>, freebsd-stable@FreeBSD.ORG,
kib@FreeBSD.org
Subject: Re: shutdown -p now crashes
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Nov 2008 07:18:14 -0000
Jeremy Chadwick wrote:
> On Thu, Nov 20, 2008 at 02:50:46PM +0800, Ganbold wrote:
>
>> Ganbold wrote:
>>
>>> #3 0xc06ab8b3 in vput (vp=0xc3d11ac8) at
>>> /usr/src/sys/kern/vfs_subr.c:2202
>>> #4 0xc06a69e6 in dounmount (mp=0xc3e59b30, flags=524288,
>>> td=0xc3b31d20) at /usr/src/sys/kern/vfs_mount.c:1288
>>> #5 0xc06aa493 in vfs_unmountall () at /usr/src/sys/kern/vfs_subr.c:2939
>>> #6 0xc062b7f4 in boot (howto=16392) at
>>> /usr/src/sys/kern/kern_shutdown.c:400
>>> #7 0xc062bc17 in reboot (td=0xc3b31d20, uap=0xeef55cfc) at
>>> /usr/src/sys/kern/kern_shutdown.c:172
>>> #8 0xc08171f5 in syscall (frame=0xeef55d38) at
>>> /usr/src/sys/i386/i386/trap.c:1090
>>> #9 0xc07fd710 in Xint0x80_syscall () at
>>> /usr/src/sys/i386/i386/exception.s:255
>>> #10 0x00000033 in ?? ()
>>> (kgdb)
>>> ..
>>>
>> I was able to reproduce the panic. I plugged in external ZFS/GELI HDD
>> via USB
>> and used 'zpool import' to import disk and did some 'ls' and then used
>> 'zpool export' to umount disk.
>> Then I detached the disk from desktop and tried to "shutdown -p now".
>> This way panic is
>> reproduced 2 times.
>>
>
> Are we sure that the problem isn't the well-known "do not yank a device
> out from underneathe the rest of the OS" problem, e.g. removing
> removable devices while filesystems are still mounted? If so, this
> problem is very well-known, documented on my Wiki, and work is being
> done in CURRENT to fix it (official ETA is 2009/02).
>
> I see geli(8) has a "detach" option, which you might need to do after
> the "zpool export", being as the GEOM provider is still attached to
> the USB HDD. I would recommend trying that first.
>
Thanks for suggestion :) In my zfs_mount and zfs_umount scripts I have:
zfs_mount.sh
#!/bin/sh
geli attach -k /root/da0.key /dev/da0s1e
zpool import tank1
zpool import tank2
zfs_umount.sh
#!/bin/sh
zpool export tank1
zpool export tank2
geli detach da0s1e.eli
I hope that answers what you meant :)
Ganbold
>
>> More info:
>>
>> daemon% uname -an
>> FreeBSD daemon.micom.mng.net 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #8
>> r185085M: Thu Nov 20 12:50:33 ULAT 2008
>> tsgan@daemon.micom.mng.net:/usr/obj/usr/src/sys/GDAEMON i386
>> daemon%
>>
>>
>> <118>.
>> <118>Writing entropy file:
>> <118>.
>> <118>Terminated
>> <118>.
>> <118>Nov 20 14:30:12 daemon syslogd: exiting on signal 15
>> rootvp 0xc3d11ac8 v_usecount 2
>> KDB: stack backtrace:
>> db_trace_self_wrapper(c086b1ee,f2c6bbac,c06abb23,c086faa8,c3d11ac8,...)
>> at db_trace_self_wrapper+0x26
>> kdb_backtrace(c086faa8,c3d11ac8,2,b,0,...) at kdb_backtrace+0x29
>> vrele(c3d11ac8,c3e6f690,0,0,0,...) at vrele+0x83
>> fdfree(c3e6f690,c3e8f000,48077bf0,f2c6bc80,c062ccfe,...) at fdfree+0x8b6
>> exit1(c3e6f690,0,f2c6bd2c,c0817245,c3e6f690,...) at exit1+0x5e9
>> sys_exit(c3e6f690,f2c6bcfc,4,c3e6f690,f2c6bd2c,...) at sys_exit+0x1d
>> syscall(f2c6bd38) at syscall+0x335
>> Xint0x80_syscall() at Xint0x80_syscall+0x20
>> --- syscall (1, FreeBSD ELF32, sys_exit), eip = 0x4810ed2f, esp =
>> 0xbfbfe6bc, ebp = 0xbfbfe6c8 ---
>> rootvp 0xc3d11ac8 v_usecount 1
>> KDB: stack backtrace:
>> db_trace_self_wrapper(c086b1ee,f2c6bbac,c06abb23,c086faa8,c3d11ac8,...)
>> at db_trace_self_wrapper+0x26
>> kdb_backtrace(c086faa8,c3d11ac8,1,b,0,...) at kdb_backtrace+0x29
>> vrele(c3d11ac8,c3e6f690,0,0,0,...) at vrele+0x83
>> fdfree(c3e6f690,c3e8f000,48077bf0,f2c6bc80,c062ccfe,...) at fdfree+0x8c3
>> exit1(c3e6f690,0,f2c6bd2c,c0817245,c3e6f690,...) at exit1+0x5e9
>> sys_exit(c3e6f690,f2c6bcfc,4,c3e6f690,f2c6bd2c,...) at sys_exit+0x1d
>> syscall(f2c6bd38) at syscall+0x335
>> Xint0x80_syscall() at Xint0x80_syscall+0x20
>> --- syscall (1, FreeBSD ELF32, sys_exit), eip = 0x4810ed2f, esp =
>> 0xbfbfe6bc, ebp = 0xbfbfe6c8 ---
>> Waiting (max 60 seconds) for system process `vnlru' to stop...done
>> Waiting (max 60 seconds) for system process `bufdaemon' to stop...done
>> Waiting (max 60 seconds) for system process `syncer' to stop...
>> Syncing disks, vnodes remaining...2 1 0 0 done
>> All buffers synced.
>> rootvp 0xc3d11ac8 v_usecount 1
>> KDB: stack backtrace:
>> db_trace_self_wrapper(c086b1ee,eef55ba8,c06abb23,c086faa8,c3d11ac8,...)
>> at db_trace_self_wrapper+0x26
>> kdb_backtrace(c086faa8,c3d11ac8,1,c3b31d20,eef55ba8,...) at
>> kdb_backtrace+0x29
>> vrele(c3d11ac8,2,eef55bf0,c3b31d20,0,...) at vrele+0x83
>> dounmount(c3e56b30,80000,c3b31d20,e3b61aec,0,...) at dounmount+0x491
>> vfs_unmountall(c0869007,0,c086906b,117,eef55c50,...) at vfs_unmountall+0x33
>> boot(c3b31d20,8,0,fffffffe,c3b31d20,...) at boot+0x444
>> reboot(c3b31d20,eef55cfc,4,8048290,9e7c9054,...) at reboot+0x67
>> syscall(eef55d38) at syscall+0x335
>> Xint0x80_syscall() at Xint0x80_syscall+0x20
>> --- syscall (55, FreeBSD ELF32, reboot), eip = 0x8050bb3, esp =
>> 0xbfbfe8ec, ebp = 0xbfbfe9b8 ---
>> panic: vput: negative ref cnt
>> cpuid = 0
>> KDB: stack backtrace:
>> db_trace_self_wrapper(c086b1ee,eef55b68,c062bd39,c08832ea,0,...) at
>> db_trace_self_wrapper+0x26
>> kdb_backtrace(c08832ea,0,c086fac1,eef55b74,0,...) at kdb_backtrace+0x29
>> panic(c086fac1,eef55ba8,c06abcd0,c3d11ac8,eef55b90,...) at panic+0x119
>> vput(c3d11ac8,2,eef55bf0,c3b31d20,0,...) at vput+0xf3
>> dounmount(c3e56b30,80000,c3b31d20,e3b61aec,0,...) at dounmount+0x4a6
>> vfs_unmountall(c0869007,0,c086906b,117,eef55c50,...) at vfs_unmountall+0x33
>> boot(c3b31d20,8,0,fffffffe,c3b31d20,...) at boot+0x444
>> reboot(c3b31d20,eef55cfc,4,8048290,9e7c9054,...) at reboot+0x67
>> syscall(eef55d38) at syscall+0x335
>> Xint0x80_syscall() at Xint0x80_syscall+0x20
>> --- syscall (55, FreeBSD ELF32, reboot), eip = 0x8050bb3, esp =
>> 0xbfbfe8ec, ebp = 0xbfbfe9b8 ---
>> Uptime: 7m3s
>> Physical memory: 1013 MB
>> Dumping 54 MB: 39 23 7
>> (kgdb) where
>> #0 doadump () at pcpu.h:196
>> #1 0xc062ba67 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418
>> #2 0xc062bd72 in panic (fmt=Variable "fmt" is not available.
>> ) at /usr/src/sys/kern/kern_shutdown.c:574
>> #3 0xc06ab8e3 in vput (vp=0xc3d11ac8) at /usr/src/sys/kern/vfs_subr.c:2211
>> #4 0xc06a69e6 in dounmount (mp=0xc3e56b30, flags=524288, td=0xc3b31d20)
>> at /usr/src/sys/kern/vfs_mount.c:1288
>> #5 0xc06aa493 in vfs_unmountall () at /usr/src/sys/kern/vfs_subr.c:2948
>> #6 0xc062b7f4 in boot (howto=16392) at
>> /usr/src/sys/kern/kern_shutdown.c:400
>> #7 0xc062bc17 in reboot (td=0xc3b31d20, uap=0xeef55cfc) at
>> /usr/src/sys/kern/kern_shutdown.c:172
>> #8 0xc0817245 in syscall (frame=0xeef55d38) at
>> /usr/src/sys/i386/i386/trap.c:1090
>> #9 0xc07fd760 in Xint0x80_syscall () at
>> /usr/src/sys/i386/i386/exception.s:255
>> #10 0x00000033 in ?? ()
>> (kgdb) frame 4
>> #4 0xc06a69e6 in dounmount (mp=0xc3e56b30, flags=524288, td=0xc3b31d20)
>> at /usr/src/sys/kern/vfs_mount.c:1288
>> 1288 vput(fsrootvp);
>> (kgdb) p *mp
>> $1 = {mnt_lock = {lk_object = {lo_name = 0xc086f234 "vfslock", lo_type =
>> 0xc086f234 "vfslock", lo_flags = 70844416, lo_witness_data = {lod_list =
>> {
>> stqe_next = 0x0}, lod_witness = 0x0}}, lk_interlock =
>> 0xc0956fa8, lk_flags = 1310720, lk_sharecount = 0, lk_waitcount = 0,
>> lk_exclusivecount = 1,
>> lk_prio = 80, lk_timo = 0, lk_lockholder = 0xc3b31d20, lk_newlock =
>> 0x0}, mnt_mtx = {lock_object = {lo_name = 0xc086f223 "struct mount mtx",
>> lo_type = 0xc086f223 "struct mount mtx", lo_flags = 16973824,
>> lo_witness_data = {lod_list = {stqe_next = 0x0}, lod_witness = 0x0}},
>> mtx_lock = 4,
>> mtx_recurse = 0}, mnt_gen = 1, mnt_list = {tqe_next = 0x0, tqe_prev =
>> 0xc091c224}, mnt_op = 0xc0926080, mnt_vfc = 0xc0926040, mnt_vnodecovered
>> = 0x0,
>> mnt_syncer = 0x0, mnt_ref = 736, mnt_nvnodelist = {tqh_first =
>> 0xc3d11ac8, tqh_last = 0xc67fd350}, mnt_nvnodelistsize = 736,
>> mnt_writeopcount = 1,
>> mnt_kern_flag = 553648137, mnt_flag = 20480, mnt_noasync = 0, mnt_opt =
>> 0xc3c4cc90, mnt_optnew = 0x0, mnt_maxsymlinklen = 120, mnt_stat = {
>> f_version = 537068824, f_type = 1, f_flags = 20480, f_bsize = 2048,
>> f_iosize = 16384, f_blocks = 2538519, f_bfree = 2339932, f_bavail =
>> 2136851,
>> f_files = 659454, f_ffree = 651413, f_syncwrites = 0, f_asyncwrites =
>> 0, f_syncreads = 0, f_asyncreads = 0, f_spare = {0, 0, 0, 0, 0, 0, 0, 0,
>> 0, 0},
>> f_namemax = 255, f_owner = 0, f_fsid = {val = {1149777033,
>> 1944990175}}, f_charspare = '\0' <repeats 79 times>,
>> f_fstypename = "ufs", '\0' <repeats 12 times>, f_mntfromname =
>> "/dev/ad4s1a", '\0' <repeats 76 times>, f_mntonname = "/", '\0' <repeats
>> 86 times>},
>> mnt_cred = 0xc3e52700, mnt_data = 0xc3e52600, mnt_time = 1227162073,
>> mnt_iosize_max = 131072, mnt_export = 0x0, mnt_label = 0x0,
>> mnt_hashseed = 2358371174, mnt_markercnt = 0, mnt_holdcnt = 0,
>> mnt_holdcntwaiters = 0, mnt_secondary_writes = 0,
>> mnt_secondary_accwrites = 2874,
>> mnt_gjprovider = 0x0, mnt_explock = {lk_object = {lo_name = 0xc086f23c
>> "explock", lo_type = 0xc086f23c "explock", lo_flags = 70844416,
>> lo_witness_data = {
>> lod_list = {stqe_next = 0x0}, lod_witness = 0x0}}, lk_interlock =
>> 0xc0956fc0, lk_flags = 0, lk_sharecount = 0, lk_waitcount = 0,
>> lk_exclusivecount = 0, lk_prio = 80, lk_timo = 0, lk_lockholder =
>> 0xffffffff, lk_newlock = 0x0}}
>> (kgdb) p fsrootvp $2 = (struct vnode *) 0xc3d11ac8
>> (kgdb) p *fsrootvp
>> $3 = {v_type = VDIR, v_tag = 0xc0864e51 "ufs", v_op = 0xc0926280, v_data
>> = 0xc3e5d000, v_mount = 0xc3e56b30, v_nmntvnodes = {tqe_next =
>> 0xc3d119b4,
>> tqe_prev = 0xc3e56b98}, v_un = {vu_mount = 0x0, vu_socket = 0x0,
>> vu_cdev = 0x0, vu_fifoinfo = 0x0, vu_yield = 0}, v_hashlist = {le_next =
>> 0x0,
>> le_prev = 0xc3d09da0}, v_hash = 2, v_cache_src = {lh_first = 0x0},
>> v_cache_dst = {tqh_first = 0x0, tqh_last = 0xc3d11af8}, v_dd = 0x0,
>> v_cstart = 0,
>> v_lasta = 0, v_lastw = 0, v_clen = 0, v_lock = {lk_object = {lo_name =
>> 0xc0864e51 "ufs", lo_type = 0xc0864e51 "ufs", lo_flags = 70844416,
>> lo_witness_data = {lod_list = {stqe_next = 0x0}, lod_witness =
>> 0x0}}, lk_interlock = 0xc0956510, lk_flags = 262208, lk_sharecount = 0,
>> lk_waitcount = 0, lk_exclusivecount = 1, lk_prio = 80, lk_timo = 51,
>> lk_lockholder = 0xc3b31d20, lk_newlock = 0x0}, v_interlock =
>> {lock_object = {
>> lo_name = 0xc086fb51 "vnode interlock", lo_type = 0xc086fb51 "vnode
>> interlock", lo_flags = 16973824, lo_witness_data = {lod_list =
>> {stqe_next = 0x0},
>> lod_witness = 0x0}}, mtx_lock = 3283295520, mtx_recurse = 0},
>> v_vnlock = 0xc3d11b20, v_holdcnt = 2, v_usecount = 0, v_iflag = 0,
>> v_vflag = 1,
>> v_writecount = 0, v_freelist = {tqe_next = 0x0, tqe_prev = 0x0},
>> v_bufobj = {bo_mtx = 0xc3d11b50, bo_clean = {bv_hd = {tqh_first =
>> 0xe3d02594,
>> tqh_last = 0xe3d025cc}, bv_root = 0xe3d02594, bv_cnt = 1},
>> bo_dirty = {bv_hd = {tqh_first = 0x0, tqh_last = 0xc3d11b9c}, bv_root =
>> 0x0,
>> bv_cnt = 0}, bo_numoutput = 0, bo_flag = 0, bo_ops = 0xc091ae00,
>> bo_bsize = 16384, bo_object = 0xc106183c, bo_synclist = {le_next = 0x0,
>> le_prev = 0x0}, bo_private = 0xc3d11ac8, __bo_vnode = 0xc3d11ac8},
>> v_pollinfo = 0x0, v_label = 0x0, v_lockf = 0x0}
>> (kgdb) p rootvnode
>> $4 = (struct vnode *) 0x0
>> (kgdb) p *rootvnode
>> Cannot access memory at address 0x0
>> (kgdb)
>>
>>
>> --
>> They are called computers simply because computation is the only
>> significant job that has so far been given to them.
>> _______________________________________________
>> freebsd-stable@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
>> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
>>
>
>
--
The light at the end of the tunnel may be an oncoming dragon.
From owner-freebsd-stable@FreeBSD.ORG Thu Nov 20 07:34:05 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 8AD941065674
for <freebsd-stable@freebsd.org>; Thu, 20 Nov 2008 07:34:05 +0000 (UTC)
(envelope-from jdc@koitsu.dyndns.org)
Received: from QMTA06.westchester.pa.mail.comcast.net
(qmta06.westchester.pa.mail.comcast.net [76.96.62.56])
by mx1.freebsd.org (Postfix) with ESMTP id D66FA8FC12
for <freebsd-stable@freebsd.org>; Thu, 20 Nov 2008 07:34:04 +0000 (UTC)
(envelope-from jdc@koitsu.dyndns.org)
Received: from OMTA02.westchester.pa.mail.comcast.net ([76.96.62.19])
by QMTA06.westchester.pa.mail.comcast.net with comcast
id hKPe1a0010QuhwU56Ka3Wy; Thu, 20 Nov 2008 07:34:03 +0000
Received: from koitsu.dyndns.org ([69.181.141.110])
by OMTA02.westchester.pa.mail.comcast.net with comcast
id hKZr1a0082P6wsM3NKZrMo; Thu, 20 Nov 2008 07:34:03 +0000
X-Authority-Analysis: v=1.0 c=1 a=6I5d2MoRAAAA:8 a=QycZ5dHgAAAA:8
a=LwW87T2ub8asL7PGsRQA:9 a=GA4gTzArVwH3amJfPGUA:7
a=ODkVQrsv8JsqA3k-3IlcpbeL63QA:4 a=EoioJ0NPDVgA:10 a=SV7veod9ZcQA:10
a=LY0hPdMaydYA:10
Received: by icarus.home.lan (Postfix, from userid 1000)
id 2EEA433C1C; Wed, 19 Nov 2008 23:33:51 -0800 (PST)
Date: Wed, 19 Nov 2008 23:33:51 -0800
From: Jeremy Chadwick <koitsu@FreeBSD.org>
To: Ganbold <ganbold@micom.mng.net>
Message-ID: <20081120073351.GA20058@icarus.home.lan>
References: <4922906D.4060805@micom.mng.net> <492508C6.3090005@micom.mng.net>
<20081120071136.GA19577@icarus.home.lan>
<49250F32.5080807@micom.mng.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <49250F32.5080807@micom.mng.net>
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: Kostik Belousov <kostikbel@gmail.com>, kib@FreeBSD.org,
freebsd-stable@FreeBSD.ORG
Subject: Re: shutdown -p now crashes
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Nov 2008 07:34:05 -0000
On Thu, Nov 20, 2008 at 03:18:10PM +0800, Ganbold wrote:
> Jeremy Chadwick wrote:
>> On Thu, Nov 20, 2008 at 02:50:46PM +0800, Ganbold wrote:
>>
>>> Ganbold wrote:
>>>
>>>> #3 0xc06ab8b3 in vput (vp=0xc3d11ac8) at
>>>> /usr/src/sys/kern/vfs_subr.c:2202
>>>> #4 0xc06a69e6 in dounmount (mp=0xc3e59b30, flags=524288,
>>>> td=0xc3b31d20) at /usr/src/sys/kern/vfs_mount.c:1288
>>>> #5 0xc06aa493 in vfs_unmountall () at /usr/src/sys/kern/vfs_subr.c:2939
>>>> #6 0xc062b7f4 in boot (howto=16392) at
>>>> /usr/src/sys/kern/kern_shutdown.c:400
>>>> #7 0xc062bc17 in reboot (td=0xc3b31d20, uap=0xeef55cfc) at
>>>> /usr/src/sys/kern/kern_shutdown.c:172
>>>> #8 0xc08171f5 in syscall (frame=0xeef55d38) at
>>>> /usr/src/sys/i386/i386/trap.c:1090
>>>> #9 0xc07fd710 in Xint0x80_syscall () at
>>>> /usr/src/sys/i386/i386/exception.s:255
>>>> #10 0x00000033 in ?? ()
>>>> (kgdb)
>>>> ..
>>>>
>>> I was able to reproduce the panic. I plugged in external ZFS/GELI HDD
>>> via USB
>>> and used 'zpool import' to import disk and did some 'ls' and then
>>> used 'zpool export' to umount disk.
>>> Then I detached the disk from desktop and tried to "shutdown -p now".
>>> This way panic is
>>> reproduced 2 times.
>>>
>>
>> Are we sure that the problem isn't the well-known "do not yank a device
>> out from underneathe the rest of the OS" problem, e.g. removing
>> removable devices while filesystems are still mounted? If so, this
>> problem is very well-known, documented on my Wiki, and work is being
>> done in CURRENT to fix it (official ETA is 2009/02).
>>
>> I see geli(8) has a "detach" option, which you might need to do after
>> the "zpool export", being as the GEOM provider is still attached to
>> the USB HDD. I would recommend trying that first.
>>
>
> Thanks for suggestion :) In my zfs_mount and zfs_umount scripts I have:
>
> zfs_mount.sh
> #!/bin/sh
> geli attach -k /root/da0.key /dev/da0s1e
> zpool import tank1
> zpool import tank2
>
> zfs_umount.sh
> #!/bin/sh
> zpool export tank1
> zpool export tank2
> geli detach da0s1e.eli
>
> I hope that answers what you meant :)
Thanks -- it does. I was worried the detach was missing and might
explain the anomaly. It doesn't. I hope others can help...
>>> More info:
>>>
>>> daemon% uname -an
>>> FreeBSD daemon.micom.mng.net 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #8
>>> r185085M: Thu Nov 20 12:50:33 ULAT 2008
>>> tsgan@daemon.micom.mng.net:/usr/obj/usr/src/sys/GDAEMON i386
>>> daemon%
>>>
>>>
>>> <118>.
>>> <118>Writing entropy file:
>>> <118>.
>>> <118>Terminated
>>> <118>.
>>> <118>Nov 20 14:30:12 daemon syslogd: exiting on signal 15
>>> rootvp 0xc3d11ac8 v_usecount 2
>>> KDB: stack backtrace:
>>> db_trace_self_wrapper(c086b1ee,f2c6bbac,c06abb23,c086faa8,c3d11ac8,...)
>>> at db_trace_self_wrapper+0x26
>>> kdb_backtrace(c086faa8,c3d11ac8,2,b,0,...) at kdb_backtrace+0x29
>>> vrele(c3d11ac8,c3e6f690,0,0,0,...) at vrele+0x83
>>> fdfree(c3e6f690,c3e8f000,48077bf0,f2c6bc80,c062ccfe,...) at fdfree+0x8b6
>>> exit1(c3e6f690,0,f2c6bd2c,c0817245,c3e6f690,...) at exit1+0x5e9
>>> sys_exit(c3e6f690,f2c6bcfc,4,c3e6f690,f2c6bd2c,...) at sys_exit+0x1d
>>> syscall(f2c6bd38) at syscall+0x335
>>> Xint0x80_syscall() at Xint0x80_syscall+0x20
>>> --- syscall (1, FreeBSD ELF32, sys_exit), eip = 0x4810ed2f, esp =
>>> 0xbfbfe6bc, ebp = 0xbfbfe6c8 ---
>>> rootvp 0xc3d11ac8 v_usecount 1
>>> KDB: stack backtrace:
>>> db_trace_self_wrapper(c086b1ee,f2c6bbac,c06abb23,c086faa8,c3d11ac8,...)
>>> at db_trace_self_wrapper+0x26
>>> kdb_backtrace(c086faa8,c3d11ac8,1,b,0,...) at kdb_backtrace+0x29
>>> vrele(c3d11ac8,c3e6f690,0,0,0,...) at vrele+0x83
>>> fdfree(c3e6f690,c3e8f000,48077bf0,f2c6bc80,c062ccfe,...) at fdfree+0x8c3
>>> exit1(c3e6f690,0,f2c6bd2c,c0817245,c3e6f690,...) at exit1+0x5e9
>>> sys_exit(c3e6f690,f2c6bcfc,4,c3e6f690,f2c6bd2c,...) at sys_exit+0x1d
>>> syscall(f2c6bd38) at syscall+0x335
>>> Xint0x80_syscall() at Xint0x80_syscall+0x20
>>> --- syscall (1, FreeBSD ELF32, sys_exit), eip = 0x4810ed2f, esp =
>>> 0xbfbfe6bc, ebp = 0xbfbfe6c8 ---
>>> Waiting (max 60 seconds) for system process `vnlru' to stop...done
>>> Waiting (max 60 seconds) for system process `bufdaemon' to stop...done
>>> Waiting (max 60 seconds) for system process `syncer' to stop...
>>> Syncing disks, vnodes remaining...2 1 0 0 done
>>> All buffers synced.
>>> rootvp 0xc3d11ac8 v_usecount 1
>>> KDB: stack backtrace:
>>> db_trace_self_wrapper(c086b1ee,eef55ba8,c06abb23,c086faa8,c3d11ac8,...)
>>> at db_trace_self_wrapper+0x26
>>> kdb_backtrace(c086faa8,c3d11ac8,1,c3b31d20,eef55ba8,...) at
>>> kdb_backtrace+0x29
>>> vrele(c3d11ac8,2,eef55bf0,c3b31d20,0,...) at vrele+0x83
>>> dounmount(c3e56b30,80000,c3b31d20,e3b61aec,0,...) at dounmount+0x491
>>> vfs_unmountall(c0869007,0,c086906b,117,eef55c50,...) at vfs_unmountall+0x33
>>> boot(c3b31d20,8,0,fffffffe,c3b31d20,...) at boot+0x444
>>> reboot(c3b31d20,eef55cfc,4,8048290,9e7c9054,...) at reboot+0x67
>>> syscall(eef55d38) at syscall+0x335
>>> Xint0x80_syscall() at Xint0x80_syscall+0x20
>>> --- syscall (55, FreeBSD ELF32, reboot), eip = 0x8050bb3, esp =
>>> 0xbfbfe8ec, ebp = 0xbfbfe9b8 ---
>>> panic: vput: negative ref cnt
>>> cpuid = 0
>>> KDB: stack backtrace:
>>> db_trace_self_wrapper(c086b1ee,eef55b68,c062bd39,c08832ea,0,...) at
>>> db_trace_self_wrapper+0x26
>>> kdb_backtrace(c08832ea,0,c086fac1,eef55b74,0,...) at kdb_backtrace+0x29
>>> panic(c086fac1,eef55ba8,c06abcd0,c3d11ac8,eef55b90,...) at panic+0x119
>>> vput(c3d11ac8,2,eef55bf0,c3b31d20,0,...) at vput+0xf3
>>> dounmount(c3e56b30,80000,c3b31d20,e3b61aec,0,...) at dounmount+0x4a6
>>> vfs_unmountall(c0869007,0,c086906b,117,eef55c50,...) at vfs_unmountall+0x33
>>> boot(c3b31d20,8,0,fffffffe,c3b31d20,...) at boot+0x444
>>> reboot(c3b31d20,eef55cfc,4,8048290,9e7c9054,...) at reboot+0x67
>>> syscall(eef55d38) at syscall+0x335
>>> Xint0x80_syscall() at Xint0x80_syscall+0x20
>>> --- syscall (55, FreeBSD ELF32, reboot), eip = 0x8050bb3, esp =
>>> 0xbfbfe8ec, ebp = 0xbfbfe9b8 ---
>>> Uptime: 7m3s
>>> Physical memory: 1013 MB
>>> Dumping 54 MB: 39 23 7
>>> (kgdb) where
>>> #0 doadump () at pcpu.h:196
>>> #1 0xc062ba67 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418
>>> #2 0xc062bd72 in panic (fmt=Variable "fmt" is not available.
>>> ) at /usr/src/sys/kern/kern_shutdown.c:574
>>> #3 0xc06ab8e3 in vput (vp=0xc3d11ac8) at /usr/src/sys/kern/vfs_subr.c:2211
>>> #4 0xc06a69e6 in dounmount (mp=0xc3e56b30, flags=524288,
>>> td=0xc3b31d20) at /usr/src/sys/kern/vfs_mount.c:1288
>>> #5 0xc06aa493 in vfs_unmountall () at /usr/src/sys/kern/vfs_subr.c:2948
>>> #6 0xc062b7f4 in boot (howto=16392) at
>>> /usr/src/sys/kern/kern_shutdown.c:400
>>> #7 0xc062bc17 in reboot (td=0xc3b31d20, uap=0xeef55cfc) at
>>> /usr/src/sys/kern/kern_shutdown.c:172
>>> #8 0xc0817245 in syscall (frame=0xeef55d38) at
>>> /usr/src/sys/i386/i386/trap.c:1090
>>> #9 0xc07fd760 in Xint0x80_syscall () at
>>> /usr/src/sys/i386/i386/exception.s:255
>>> #10 0x00000033 in ?? ()
>>> (kgdb) frame 4
>>> #4 0xc06a69e6 in dounmount (mp=0xc3e56b30, flags=524288,
>>> td=0xc3b31d20) at /usr/src/sys/kern/vfs_mount.c:1288
>>> 1288 vput(fsrootvp);
>>> (kgdb) p *mp
>>> $1 = {mnt_lock = {lk_object = {lo_name = 0xc086f234 "vfslock",
>>> lo_type = 0xc086f234 "vfslock", lo_flags = 70844416, lo_witness_data
>>> = {lod_list = {
>>> stqe_next = 0x0}, lod_witness = 0x0}}, lk_interlock =
>>> 0xc0956fa8, lk_flags = 1310720, lk_sharecount = 0, lk_waitcount = 0,
>>> lk_exclusivecount = 1,
>>> lk_prio = 80, lk_timo = 0, lk_lockholder = 0xc3b31d20, lk_newlock
>>> = 0x0}, mnt_mtx = {lock_object = {lo_name = 0xc086f223 "struct mount
>>> mtx",
>>> lo_type = 0xc086f223 "struct mount mtx", lo_flags = 16973824,
>>> lo_witness_data = {lod_list = {stqe_next = 0x0}, lod_witness = 0x0}},
>>> mtx_lock = 4,
>>> mtx_recurse = 0}, mnt_gen = 1, mnt_list = {tqe_next = 0x0,
>>> tqe_prev = 0xc091c224}, mnt_op = 0xc0926080, mnt_vfc = 0xc0926040,
>>> mnt_vnodecovered = 0x0,
>>> mnt_syncer = 0x0, mnt_ref = 736, mnt_nvnodelist = {tqh_first =
>>> 0xc3d11ac8, tqh_last = 0xc67fd350}, mnt_nvnodelistsize = 736,
>>> mnt_writeopcount = 1,
>>> mnt_kern_flag = 553648137, mnt_flag = 20480, mnt_noasync = 0,
>>> mnt_opt = 0xc3c4cc90, mnt_optnew = 0x0, mnt_maxsymlinklen = 120,
>>> mnt_stat = {
>>> f_version = 537068824, f_type = 1, f_flags = 20480, f_bsize =
>>> 2048, f_iosize = 16384, f_blocks = 2538519, f_bfree = 2339932,
>>> f_bavail = 2136851,
>>> f_files = 659454, f_ffree = 651413, f_syncwrites = 0,
>>> f_asyncwrites = 0, f_syncreads = 0, f_asyncreads = 0, f_spare = {0,
>>> 0, 0, 0, 0, 0, 0, 0, 0, 0},
>>> f_namemax = 255, f_owner = 0, f_fsid = {val = {1149777033,
>>> 1944990175}}, f_charspare = '\0' <repeats 79 times>,
>>> f_fstypename = "ufs", '\0' <repeats 12 times>, f_mntfromname =
>>> "/dev/ad4s1a", '\0' <repeats 76 times>, f_mntonname = "/", '\0'
>>> <repeats 86 times>},
>>> mnt_cred = 0xc3e52700, mnt_data = 0xc3e52600, mnt_time = 1227162073,
>>> mnt_iosize_max = 131072, mnt_export = 0x0, mnt_label = 0x0,
>>> mnt_hashseed = 2358371174, mnt_markercnt = 0, mnt_holdcnt = 0,
>>> mnt_holdcntwaiters = 0, mnt_secondary_writes = 0,
>>> mnt_secondary_accwrites = 2874,
>>> mnt_gjprovider = 0x0, mnt_explock = {lk_object = {lo_name =
>>> 0xc086f23c "explock", lo_type = 0xc086f23c "explock", lo_flags =
>>> 70844416, lo_witness_data = {
>>> lod_list = {stqe_next = 0x0}, lod_witness = 0x0}},
>>> lk_interlock = 0xc0956fc0, lk_flags = 0, lk_sharecount = 0,
>>> lk_waitcount = 0,
>>> lk_exclusivecount = 0, lk_prio = 80, lk_timo = 0, lk_lockholder =
>>> 0xffffffff, lk_newlock = 0x0}}
>>> (kgdb) p fsrootvp $2 = (struct vnode *) 0xc3d11ac8
>>> (kgdb) p *fsrootvp
>>> $3 = {v_type = VDIR, v_tag = 0xc0864e51 "ufs", v_op = 0xc0926280,
>>> v_data = 0xc3e5d000, v_mount = 0xc3e56b30, v_nmntvnodes = {tqe_next
>>> = 0xc3d119b4,
>>> tqe_prev = 0xc3e56b98}, v_un = {vu_mount = 0x0, vu_socket = 0x0,
>>> vu_cdev = 0x0, vu_fifoinfo = 0x0, vu_yield = 0}, v_hashlist =
>>> {le_next = 0x0,
>>> le_prev = 0xc3d09da0}, v_hash = 2, v_cache_src = {lh_first = 0x0},
>>> v_cache_dst = {tqh_first = 0x0, tqh_last = 0xc3d11af8}, v_dd = 0x0,
>>> v_cstart = 0,
>>> v_lasta = 0, v_lastw = 0, v_clen = 0, v_lock = {lk_object = {lo_name
>>> = 0xc0864e51 "ufs", lo_type = 0xc0864e51 "ufs", lo_flags = 70844416,
>>> lo_witness_data = {lod_list = {stqe_next = 0x0}, lod_witness =
>>> 0x0}}, lk_interlock = 0xc0956510, lk_flags = 262208, lk_sharecount =
>>> 0,
>>> lk_waitcount = 0, lk_exclusivecount = 1, lk_prio = 80, lk_timo =
>>> 51, lk_lockholder = 0xc3b31d20, lk_newlock = 0x0}, v_interlock =
>>> {lock_object = {
>>> lo_name = 0xc086fb51 "vnode interlock", lo_type = 0xc086fb51
>>> "vnode interlock", lo_flags = 16973824, lo_witness_data = {lod_list =
>>> {stqe_next = 0x0},
>>> lod_witness = 0x0}}, mtx_lock = 3283295520, mtx_recurse = 0},
>>> v_vnlock = 0xc3d11b20, v_holdcnt = 2, v_usecount = 0, v_iflag = 0,
>>> v_vflag = 1,
>>> v_writecount = 0, v_freelist = {tqe_next = 0x0, tqe_prev = 0x0},
>>> v_bufobj = {bo_mtx = 0xc3d11b50, bo_clean = {bv_hd = {tqh_first =
>>> 0xe3d02594,
>>> tqh_last = 0xe3d025cc}, bv_root = 0xe3d02594, bv_cnt = 1},
>>> bo_dirty = {bv_hd = {tqh_first = 0x0, tqh_last = 0xc3d11b9c}, bv_root
>>> = 0x0,
>>> bv_cnt = 0}, bo_numoutput = 0, bo_flag = 0, bo_ops = 0xc091ae00,
>>> bo_bsize = 16384, bo_object = 0xc106183c, bo_synclist = {le_next =
>>> 0x0,
>>> le_prev = 0x0}, bo_private = 0xc3d11ac8, __bo_vnode =
>>> 0xc3d11ac8}, v_pollinfo = 0x0, v_label = 0x0, v_lockf = 0x0}
>>> (kgdb) p rootvnode
>>> $4 = (struct vnode *) 0x0
>>> (kgdb) p *rootvnode
>>> Cannot access memory at address 0x0
>>> (kgdb)
>>>
>>>
>>> --
>>> They are called computers simply because computation is the only
>>> significant job that has so far been given to them.
>>> _______________________________________________
>>> freebsd-stable@freebsd.org mailing list
>>> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
>>> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
>>>
>>
>>
>
>
> --
> The light at the end of the tunnel may be an oncoming dragon.
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
--
| Jeremy Chadwick jdc at parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |
From owner-freebsd-stable@FreeBSD.ORG Thu Nov 20 10:07:01 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 5DFC11065670
for <freebsd-stable@freebsd.org>; Thu, 20 Nov 2008 10:07:01 +0000 (UTC)
(envelope-from jespasac@minibofh.org)
Received: from smtp01.cdmon.com (smtp01.cdmon.com [212.36.75.232])
by mx1.freebsd.org (Postfix) with ESMTP id 2479D8FC08
for <freebsd-stable@freebsd.org>; Thu, 20 Nov 2008 10:07:00 +0000 (UTC)
(envelope-from jespasac@minibofh.org)
Received: from jespasac.cdmon.com (62.Red-217-126-43.staticIP.rima-tde.net
[217.126.43.62])
by smtp01.cdmon.com (Postfix) with ESMTP id 02DE9F7ABA
for <freebsd-stable@freebsd.org>; Thu, 20 Nov 2008 11:06:58 +0100 (CET)
Message-ID: <492536C2.6060605@minibofh.org>
Date: Thu, 20 Nov 2008 11:06:58 +0100
From: Jordi Espasa Clofent <jespasac@minibofh.org>
User-Agent: Thunderbird 2.0.0.17 (X11/20081001)
MIME-Version: 1.0
To: freebsd-stable@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Error in 7.0p5 upgrade
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Nov 2008 10:07:01 -0000
Hi all,
I'm upgrading a FreeBSD amd64 box from 6.2p9 to 7.0p5.
After update the sources amd make world with success, I get this error:
[...]
newfs.lo(.text+0x659): In function `main':
: undefined reference to `__mb_sb_limit'
newfs_msdos.lo(.text+0x13): In function `mklabel':
: undefined reference to `__mb_sb_limit'
restore.lo(.text+0xc60): In function `mkentry':
: undefined reference to `__mb_sb_limit'
restore.lo(.text+0xa6d6): In function `rmthost':
: undefined reference to `__mb_sb_limit'
sysctl.lo(.text+0xf9f): more undefined references to `__mb_sb_limit' follow
tar.lo(.text+0x28f4): In function `read_archive':
: undefined reference to `archive_read_support_compression_program'
tar.lo(.text+0x3a81): In function `yes':
: undefined reference to `__mb_sb_limit'
tar.lo(.text+0x432a): In function `safe_fprintf':
: undefined reference to `__mb_sb_limit'
tar.lo(.text+0x6156): In function `tar_mode_c':
: undefined reference to `archive_write_set_compression_program'
vi.lo(.text+0x2f80): In function `cut':
: undefined reference to `__mb_sb_limit'
vi.lo(.text+0x2fb0): In function `cut':
: undefined reference to `__mb_sb_limit'
vi.lo(.text+0x311e): In function `cut':
: undefined reference to `__mb_sb_limit'
vi.lo(.text+0x5c29): In function `v_key_name':
: undefined reference to `__mb_sb_limit'
vi.lo(.text+0x5cf3): In function `v_key_name':
: undefined reference to `__mb_sb_limit'
vi.lo(.text+0x63b8): more undefined references to `__mb_sb_limit' follow
*** Error code 1
Stop in /usr/obj/usr/src/rescue/rescue.
*** Error code 1
Stop in /usr/src/rescue/rescue.
*** Error code 1
Stop in /usr/src/rescue.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.
after try the classical kernel compilation ( cd /usr/src && make
-DINSTALL_NODEBUG KERNCONF=MYKERNEL)
I've not found any related info in the net. Anyones knows about? Last
week I upgraded two others 6.2 amd boxes without problem.
PD1. I use the "classical" method over "new" binary method because of my
kernel is customized.
PD2. I use -DINSTALL_NODEBUG flag because of my / partition is so small
and need to preserve the maximum space.
--
Thanks,
Jordi Espasa Clofent
From owner-freebsd-stable@FreeBSD.ORG Thu Nov 20 17:33:56 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 2C4621065670;
Thu, 20 Nov 2008 17:33:56 +0000 (UTC)
(envelope-from jrhett@netconsonance.com)
Received: from mail.netconsonance.com (mail.netconsonance.com [198.207.204.4])
by mx1.freebsd.org (Postfix) with ESMTP id E76E58FC1C;
Thu, 20 Nov 2008 17:33:55 +0000 (UTC)
(envelope-from jrhett@netconsonance.com)
Received: from [172.16.12.8] (covad-jrhett.meer.net [209.157.140.144])
(authenticated bits=0)
by mail.netconsonance.com (8.14.1/8.14.1) with ESMTP id mAKHXqsn092560;
Thu, 20 Nov 2008 09:33:52 -0800 (PST)
(envelope-from jrhett@netconsonance.com)
X-Virus-Scanned: amavisd-new at netconsonance.com
X-Spam-Flag: NO
X-Spam-Score: -2.295
X-Spam-Level:
X-Spam-Status: No, score=-2.295 tagged_above=-999 required=3.5
tests=[ALL_TRUSTED=-1.44, AWL=-0.855]
Message-Id: <406FCA6C-B7FE-4A39-AD0C-4A5DBC556CF9@netconsonance.com>
From: Jo Rhett <jrhett@netconsonance.com>
To: John Baldwin <jhb@freebsd.org>
In-Reply-To: <C6DC3DB1-40FF-4896-81DB-EF37874428AF@netconsonance.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 20 Nov 2008 09:33:52 -0800
References: <A5A9A4D4-CD16-45FA-A2AC-62C4B5AE976D@netconsonance.com>
<BEBF7B15-DECE-4872-9687-4AD4BE65DB05@netconsonance.com>
<84E1EC10-5323-4A8C-AD60-31142621DB32@netconsonance.com>
<200810271151.47366.jhb@freebsd.org>
<C6DC3DB1-40FF-4896-81DB-EF37874428AF@netconsonance.com>
X-Mailer: Apple Mail (2.929.2)
Cc: freebsd-stable Stable <freebsd-stable@freebsd.org>
Subject: Want one of the affected systems for your lab? (Was: 6.4 RC1 locks
up solid on first reboot)
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Nov 2008 17:33:56 -0000
John, I can ship you one of these machines for your own testing if you
like. Or send me a public key and I can give you SSH access to the
console serial port, whichever would be easiest for you to get what
you need.
Let me know how I can help.
On Nov 5, 2008, at 3:41 PM, Jo Rhett wrote:
> On Oct 27, 2008, at 8:51 AM, John Baldwin wrote:
>> On Friday 24 October 2008 02:48:13 pm Jo Rhett wrote:
>>> So I booted up by CD and used Fixit mode to switch the system to
>>> boot
>>> via serial (keyboard detached), but this gathered me even less.
>>>
>>> /boot.config: -Dh
>>> Consoles: internal video/keyboard serial port
>>> BIOS drive A: is disk0
>>> BIOS drive C: is disk1
>>> BIOS drive D: is disk2
>>> BIOS 639kB/4062144kB available memory
>>>
>>> FreeBSD/i386 bootstrap loader, Revision 1.1
>>> (root@dessler.cse.b
>>>
>>> Plugging back in the monitor after lockup showed only a single char
>>> more:
>>> (root@dessler.cse.bu
>>
>> This confirms it is hanging in one of the two BIOS routines to
>> output a
>> character. One thing you can do would be to boot up and do the
>> following:
>>
>> dd if=/dev/mem bs=0x400 count=1 of=idt.out
>> dd if=/dev/mem bs=64k iseek=15 count=1 of=bios.out
>>
>> Then place those files some place I can fetch them.
>
> Both files are at http://support.netconsonance.com/freebsd/
>
> FYI, this is notable -- the keyboard does not respond at the boot
> prompt. I mean the menu where you can escape to the loader prompt,
> with the fat freebsd ascii art. No keyboard presses are observed
> here. This is also true for the boot menu on the 6.4 installation
> CD too.
>
> No problems with 6.2 or 6.3
>
> --
> Jo Rhett
> Net Consonance : consonant endings by net philanthropy, open source
> and other randomness
>
>
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org
> "
From owner-freebsd-stable@FreeBSD.ORG Thu Nov 20 19:10:24 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id DB0881065672
for <freebsd-stable@freebsd.org>; Thu, 20 Nov 2008 19:10:24 +0000 (UTC)
(envelope-from freebsd-stable@m.gmane.org)
Received: from ciao.gmane.org (main.gmane.org [80.91.229.2])
by mx1.freebsd.org (Postfix) with ESMTP id 8BE468FC18
for <freebsd-stable@freebsd.org>; Thu, 20 Nov 2008 19:10:24 +0000 (UTC)
(envelope-from freebsd-stable@m.gmane.org)
Received: from list by ciao.gmane.org with local (Exim 4.43)
id 1L3Euw-0006bG-RX
for freebsd-stable@freebsd.org; Thu, 20 Nov 2008 19:10:18 +0000
Received: from 200.41.broadband11.iol.cz ([90.178.41.200])
by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
id 1AlnuQ-0007hv-00
for <freebsd-stable@freebsd.org>; Thu, 20 Nov 2008 19:10:18 +0000
Received: from gamato by 200.41.broadband11.iol.cz with local (Gmexim 0.1
(Debian)) id 1AlnuQ-0007hv-00
for <freebsd-stable@freebsd.org>; Thu, 20 Nov 2008 19:10:18 +0000
X-Injected-Via-Gmane: http://gmane.org/
To: freebsd-stable@freebsd.org
From: martinko <gamato@users.sf.net>
Date: Thu, 20 Nov 2008 20:10:10 +0100
Lines: 13
Message-ID: <gg4cmi$r6k$1@ger.gmane.org>
References: <20081109174303.GA5146@ourbrains.org> <20081109184349.GG51239@server.vk2pj.dyndns.org> <4920D879.3070806@jrv.org>
<20081117050441.GA16855@ourbrains.org> <20081118175210.GA3753@hyperion.scode.org> <20081119001742.GA21835@ourbrains.org> <49235D86.4050106@modulus.org>
<86bpwcp1d8.fsf@ds4.des.no> <4923D460.5020900@kkip.pl> <b41c75520811190106w7f951760m95c12358f1008c5b@mail.gmail.com>
<4923E977.8030107@kkip.pl>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Complaints-To: usenet@ger.gmane.org
X-Gmane-NNTP-Posting-Host: 200.41.broadband11.iol.cz
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US;
rv:1.8.1.17) Gecko/20081009 SeaMonkey/1.1.12
In-Reply-To: <4923E977.8030107@kkip.pl>
Sender: news <news@ger.gmane.org>
Subject: Re: Will XFS be adopted
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Nov 2008 19:10:24 -0000
Bartosz Stec wrote:
>>
> Well it's not simple indeed. I use ZFS on my home (not critical) box
> (RAIDZ1). After 4 weeks uptime with varied workload I assumed it's
> stable. Unfortunately ZFS crashed next week ;)
>
How did it crash ? Just the system went down or did you lose any data ?
I'm planning to build new home server and put all my valuable data on
ZFS but after reading all the mailing lists I'm not so sure about it. :(
M.
From owner-freebsd-stable@FreeBSD.ORG Thu Nov 20 21:11:55 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id CFA561065674
for <stable@freebsd.org>; Thu, 20 Nov 2008 21:11:55 +0000 (UTC)
(envelope-from uspoerlein@gmail.com)
Received: from acme.spoerlein.net (cl-43.dus-01.de.sixxs.net
[IPv6:2a01:198:200:2a::2])
by mx1.freebsd.org (Postfix) with ESMTP id DF1868FC18
for <stable@freebsd.org>; Thu, 20 Nov 2008 21:11:54 +0000 (UTC)
(envelope-from uspoerlein@gmail.com)
Received: from roadrunner.spoerlein.net (e180158175.adsl.alicedsl.de
[85.180.158.175])
by acme.spoerlein.net (8.14.2/8.14.2) with ESMTP id mAKLBocr084674
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK)
for <stable@freebsd.org>; Thu, 20 Nov 2008 22:11:52 +0100 (CET)
(envelope-from uspoerlein@gmail.com)
Received: from roadrunner.spoerlein.net (localhost [127.0.0.1])
by roadrunner.spoerlein.net (8.14.3/8.14.3) with ESMTP id
mAKLBmal005209
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
for <stable@freebsd.org>; Thu, 20 Nov 2008 22:11:49 +0100 (CET)
(envelope-from uspoerlein@gmail.com)
Received: (from uqs@localhost)
by roadrunner.spoerlein.net (8.14.3/8.14.3/Submit) id mAKLBmDY005208
for stable@freebsd.org; Thu, 20 Nov 2008 22:11:48 +0100 (CET)
(envelope-from uspoerlein@gmail.com)
Date: Thu, 20 Nov 2008 22:11:48 +0100
From: Ulrich Spoerlein <uspoerlein@gmail.com>
To: stable@freebsd.org
Message-ID: <20081120211148.GA5178@roadrunner.spoerlein.net>
Mail-Followup-To: stable@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc:
Subject: LORs in RELENG_7
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Nov 2008 21:11:55 -0000
Hi,
I'm running my RELENG_7 kernel with WITNESS and there's always a LOR
when pf(4) is enabled:
lock order reversal:
1st 0xc09ca828 ifnet (ifnet) @ /usr/src/sys/net/if.c:849
2nd 0xc45d604c pf task mtx (pf task mtx) @ /usr/src/sys/modules/pf/../../contrib/pf/net/pf_if.c:916
KDB: stack backtrace:
db_trace_self_wrapper(c08df797,fb671764,c0630e8e,c08e1c96,c45d604c,...) at db_trace_self_wrapper+0x26
kdb_backtrace(c08e1c96,c45d604c,c45d3b1c,c45d3b1c,c45d379e,...) at kdb_backtrace+0x29
witness_checkorder(c45d604c,9,c45d379e,394,c08e9058,...) at witness_checkorder+0x6de
_mtx_lock_flags(c45d604c,0,c45d379e,394,fb6717dc,...) at _mtx_lock_flags+0xbc
pfi_attach_group_event(0,c4450000,c08e9058,374,c44a920c,...) at pfi_attach_group_event+0x4e
if_addgroup(c441c000,c08f70d6,4,0,0,...) at if_addgroup+0x2c7
if_clone_createif(0,0,c08e9563,87,0,...) at if_clone_createif+0x81
if_clone_create(fb671943,4,0,44,180,...) at if_clone_create+0x8c
tunclone(0,c461e400,fb671943,4,fb67195c,...) at tunclone+0x17a
devfs_lookup(fb6719d0,fb6719d0,fb671b7c,c418de04,2,...) at devfs_lookup+0x50e
VOP_LOOKUP_APV(c0928f40,fb6719d0,c412f230,c08e77ef,2a9,...) at VOP_LOOKUP_APV+0xa5
lookup(fb671b7c,c08e77ef,c6,bf,c461e92c,...) at lookup+0x58e
namei(fb671b7c,c412f230,fb671a74,246,c0983774,...) at namei+0x34b
vn_open_cred(fb671b7c,fb671c78,ce8,c461e400,c4460558,...) at vn_open_cred+0x2c9
vn_open(fb671b7c,fb671c78,ce8,c4460558,c05e807d,...) at vn_open+0x33
kern_open(c412f230,80a0f18,0,3,808ecfa,...) at kern_open+0xe7
open(c412f230,fb671cfc,c,c08e28c3,c092c0b8,...) at open+0x30
syscall(fb671d38) at syscall+0x2b3
Xint0x80_syscall() at Xint0x80_syscall+0x20
--- syscall (5, FreeBSD ELF32, open), eip = 0x2835a65b, esp = 0xbfbfeafc, ebp = 0xbfbfeb38 ---
And there are these LORs when I shut down my external firewire attached
disk:
fwohci0: BUS reset
fwohci0: node_id=0xc800ffc1, gen=2, CYCLEMASTER mode
firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 (me)
firewire0: bus manager 1 (me)
uma_zalloc_arg: zone "16" with the following non-sleepable locks held:
exclusive sleep mutex sbp r = 0 (0xc402f7ac) locked @ /usr/src/sys/dev/firewire/sbp.c:2203
KDB: stack backtrace:
db_trace_self_wrapper(c08df797,f93a931c,c0630007,c08dfb5a,f93a9330,...) at db_trace_self_wrapper+0x26
kdb_backtrace(c08dfb5a,f93a9330,4,1,0,...) at kdb_backtrace+0x29
witness_warn(5,0,c0901ae5,c08c59ce,86,...) at witness_warn+0x1d7
uma_zalloc_arg(c1472960,0,2,2,f93a93e0,...) at uma_zalloc_arg+0x34
malloc(b,c09308c0,2,c05be59a,c08d7a2c,...) at malloc+0xd2
notify(c4150a00,4,c08d7856,34f,c05be4ea,...) at notify+0x49
destroy_devl(f93a9410,c046a6ce,c4150a00,0,c3f18370,...) at destroy_devl+0x236
destroy_dev(c4150a00,0,c3f18370,c3f69000,f93a9690,...) at destroy_dev+0x10
passcleanup(c3f69000,c08b50c7,0,0,0,...) at passcleanup+0x2e
camperiphfree(c3f69000,0,f93a96b0,c04568dd,c3f69000,...) at camperiphfree+0xbb
cam_periph_invalidate(c3f69000,c0983774,f93a96e4,c046a5ea,c3f69000,...) at cam_periph_invalidate+0x3e
cam_periph_async(c3f69000,100,c418a260,0,f93a96e0,...) at cam_periph_async+0x2d
passasync(c3f69000,100,c418a260,0,c42f8c00,...) at passasync+0xca
xpt_async_bcast(0,4,c08b53c5,11a5,c404d280,...) at xpt_async_bcast+0x32
xpt_async(100,c418a260,0,89b,0,...) at xpt_async+0x194
sbp_cam_detach_sdev(c402f45c,0,c402f418,0,f93a982c,...) at sbp_cam_detach_sdev+0xa4
sbp_cam_detach_target(c14729a8,c14729a8,c08250c6,c7373b40,10,...) at sbp_cam_detach_target+0x5b
sbp_post_explore(c402f400,f93a9ce8,f93a9ce4,675,0,...) at sbp_post_explore+0xa2
fw_bus_probe_thread(c404f000,f93a9d38,c08d8d0f,31c,c402b570,...) at fw_bus_probe_thread+0x69b
fork_exit(c0513500,c404f000,f93a9d38) at fork_exit+0xb8
fork_trampoline() at fork_trampoline+0x8
--- trap 0, eip = 0, esp = 0xf93a9d70, ebp = 0 ---
(da0:sbp0:0:0:0): lost device
(da0:sbp0:0:0:0): removing device entry
cam_periph_alloc: attempt to re-allocate valid device pass1 rejected
passasync: Unable to attach new device due to status 0x6: CCB request was invalid
cam_periph_alloc: attempt to re-allocate valid device da1 rejected
daasync: Unable to attach to new device due to status 0x6
fwohci0: BUS reset
fwohci0: node_id=0xc800ffc0, gen=3, CYCLEMASTER mode
firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me)
firewire0: bus manager 0 (me)
uma_zalloc_arg: zone "16" with the following non-sleepable locks held:
exclusive sleep mutex sbp r = 0 (0xc402f7ac) locked @ /usr/src/sys/dev/firewire/sbp.c:2203
KDB: stack backtrace:
db_trace_self_wrapper(c08df797,f93a931c,c0630007,c08dfb5a,f93a9330,...) at db_trace_self_wrapper+0x26
kdb_backtrace(c08dfb5a,f93a9330,4,1,0,...) at kdb_backtrace+0x29
witness_warn(5,0,c0901ae5,c08c59ce,86,...) at witness_warn+0x1d7
uma_zalloc_arg(c1472960,0,2,2,f93a93e0,...) at uma_zalloc_arg+0x34
malloc(b,c09308c0,2,c05be59a,c08d7a2c,...) at malloc+0xd2
notify(c4150d00,4,c08d7856,34f,c05be4ea,...) at notify+0x49
destroy_devl(f93a9410,c046a6ce,c4150d00,0,c3f18370,...) at destroy_devl+0x236
destroy_dev(c4150d00,0,c3f18370,c42c6700,f93a9690,...) at destroy_dev+0x10
passcleanup(c42c6700,c08b50c7,c09eff00,4,c08db41b,...) at passcleanup+0x2e
camperiphfree(c42c6700,0,f93a96b0,c04568dd,c42c6700,...) at camperiphfree+0xbb
cam_periph_invalidate(c42c6700,c0983774,f93a96e4,c046a5ea,c42c6700,...) at cam_periph_invalidate+0x3e
cam_periph_async(c42c6700,100,c418a250,0,f93a96e0,...) at cam_periph_async+0x2d
passasync(c42c6700,100,c418a250,0,c42f8a00,...) at passasync+0xca
xpt_async_bcast(0,4,c08b53c5,11a5,c404d280,...) at xpt_async_bcast+0x32
xpt_async(100,c418a250,0,89b,0,...) at xpt_async+0x194
sbp_cam_detach_sdev(c402f4c8,0,c402f484,1,f93a982c,...) at sbp_cam_detach_sdev+0xa4
sbp_cam_detach_target(c14729a8,c14729a8,c08250c6,c44263f0,10,...) at sbp_cam_detach_target+0x5b
sbp_post_explore(c402f400,f93a9ce8,f93a9ce4,675,0,...) at sbp_post_explore+0xa2
fw_bus_probe_thread(c404f000,f93a9d38,c08d8d0f,31c,c402b570,...) at fw_bus_probe_thread+0x69b
fork_exit(c0513500,c404f000,f93a9d38) at fork_exit+0xb8
fork_trampoline() at fork_trampoline+0x8
--- trap 0, eip = 0, esp = 0xf93a9d70, ebp = 0 ---
(da1:sbp0:0:1:0): lost device
(da1:sbp0:0:1:0): removing device entry
I reckon these problems should appear in -STABLE ...
Cheers,
Ulrich Spoerlein
--
It is better to remain silent and be thought a fool,
than to speak, and remove all doubt.
From owner-freebsd-stable@FreeBSD.ORG Thu Nov 20 23:18:35 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 439401065670
for <stable@freebsd.org>; Thu, 20 Nov 2008 23:18:35 +0000 (UTC)
(envelope-from mike@jellydonut.org)
Received: from mu-out-0910.google.com (mu-out-0910.google.com [209.85.134.187])
by mx1.freebsd.org (Postfix) with ESMTP id B39688FC08
for <stable@freebsd.org>; Thu, 20 Nov 2008 23:18:34 +0000 (UTC)
(envelope-from mike@jellydonut.org)
Received: by mu-out-0910.google.com with SMTP id i2so636767mue.3
for <stable@freebsd.org>; Thu, 20 Nov 2008 15:18:33 -0800 (PST)
Received: by 10.181.137.13 with SMTP id p13mr885357bkn.173.1227221767759;
Thu, 20 Nov 2008 14:56:07 -0800 (PST)
Received: by 10.181.240.8 with HTTP; Thu, 20 Nov 2008 14:56:07 -0800 (PST)
Message-ID: <1de79840811201456pc2ceb9atb3532430fb605160@mail.gmail.com>
Date: Thu, 20 Nov 2008 17:56:07 -0500
From: "Michael Proto" <mike@jellydonut.org>
To: stable@freebsd.org
In-Reply-To: <20081120211148.GA5178@roadrunner.spoerlein.net>
MIME-Version: 1.0
References: <20081120211148.GA5178@roadrunner.spoerlein.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
Cc:
Subject: Re: LORs in RELENG_7
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Nov 2008 23:18:35 -0000
On Thu, Nov 20, 2008 at 4:11 PM, Ulrich Spoerlein <uspoerlein@gmail.com>wrote:
> Hi,
>
> I'm running my RELENG_7 kernel with WITNESS and there's always a LOR
> when pf(4) is enabled:
>
> lock order reversal:
> 1st 0xc09ca828 ifnet (ifnet) @ /usr/src/sys/net/if.c:849
> 2nd 0xc45d604c pf task mtx (pf task mtx) @
> /usr/src/sys/modules/pf/../../contrib/pf/net/pf_if.c:916
> KDB: stack backtrace:
> db_trace_self_wrapper(c08df797,fb671764,c0630e8e,c08e1c96,c45d604c,...) at
> db_trace_self_wrapper+0x26
> kdb_backtrace(c08e1c96,c45d604c,c45d3b1c,c45d3b1c,c45d379e,...) at
> kdb_backtrace+0x29
> witness_checkorder(c45d604c,9,c45d379e,394,c08e9058,...) at
> witness_checkorder+0x6de
> _mtx_lock_flags(c45d604c,0,c45d379e,394,fb6717dc,...) at
> _mtx_lock_flags+0xbc
> pfi_attach_group_event(0,c4450000,c08e9058,374,c44a920c,...) at
> pfi_attach_group_event+0x4e
> if_addgroup(c441c000,c08f70d6,4,0,0,...) at if_addgroup+0x2c7
> if_clone_createif(0,0,c08e9563,87,0,...) at if_clone_createif+0x81
> if_clone_create(fb671943,4,0,44,180,...) at if_clone_create+0x8c
> tunclone(0,c461e400,fb671943,4,fb67195c,...) at tunclone+0x17a
> devfs_lookup(fb6719d0,fb6719d0,fb671b7c,c418de04,2,...) at
> devfs_lookup+0x50e
> VOP_LOOKUP_APV(c0928f40,fb6719d0,c412f230,c08e77ef,2a9,...) at
> VOP_LOOKUP_APV+0xa5
> lookup(fb671b7c,c08e77ef,c6,bf,c461e92c,...) at lookup+0x58e
> namei(fb671b7c,c412f230,fb671a74,246,c0983774,...) at namei+0x34b
> vn_open_cred(fb671b7c,fb671c78,ce8,c461e400,c4460558,...) at
> vn_open_cred+0x2c9
> vn_open(fb671b7c,fb671c78,ce8,c4460558,c05e807d,...) at vn_open+0x33
> kern_open(c412f230,80a0f18,0,3,808ecfa,...) at kern_open+0xe7
> open(c412f230,fb671cfc,c,c08e28c3,c092c0b8,...) at open+0x30
> syscall(fb671d38) at syscall+0x2b3
> Xint0x80_syscall() at Xint0x80_syscall+0x20
> --- syscall (5, FreeBSD ELF32, open), eip = 0x2835a65b, esp = 0xbfbfeafc,
> ebp = 0xbfbfeb38 ---
>
>
>
Are you using user or group rules in your pf.conf? IIRC there is still a
known LOR in the socket layer with rules using the user or group filters.
-Proto
From owner-freebsd-stable@FreeBSD.ORG Thu Nov 20 23:28:17 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id F03321065675;
Thu, 20 Nov 2008 23:28:17 +0000 (UTC)
(envelope-from david@catwhisker.org)
Received: from bunrab.catwhisker.org
(adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122])
by mx1.freebsd.org (Postfix) with ESMTP id C08E08FC0A;
Thu, 20 Nov 2008 23:28:17 +0000 (UTC)
(envelope-from david@catwhisker.org)
Received: from bunrab.catwhisker.org (localhost [127.0.0.1])
by bunrab.catwhisker.org (8.13.3/8.13.3) with ESMTP id mAKNSHH3027525;
Thu, 20 Nov 2008 15:28:17 -0800 (PST)
(envelope-from david@bunrab.catwhisker.org)
Received: (from david@localhost)
by bunrab.catwhisker.org (8.13.3/8.13.1/Submit) id mAKNSHgj027524;
Thu, 20 Nov 2008 15:28:17 -0800 (PST) (envelope-from david)
Date: Thu, 20 Nov 2008 15:28:17 -0800
From: David Wolfskill <david@catwhisker.org>
To: stable@freebsd.org
Message-ID: <20081120232817.GC83287@bunrab.catwhisker.org>
Mail-Followup-To: David Wolfskill <david@catwhisker.org>,
stable@freebsd.org
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="oFGQ2VdWvpciDCpb"
Content-Disposition: inline
User-Agent: Mutt/1.4.2.1i
Cc:
Subject: Modest MFC request: src/Makefile.inc1, rev. 1.614 (SVN rev 184860)
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Nov 2008 23:28:18 -0000
--oFGQ2VdWvpciDCpb
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
I'm writing to encourage an MFC for src/Makefile.inc1, rev. 1.614.
I tested it for the committer. :-} And if we're to make use of
amd64 arch "build" machines at $WORK, we'll need that change.
(Symptoms prior to the commit are that 32-bit executables that use
crypto libraries will fail to run because the 32-bit crypto libraries
won't be found. And since the version of CVS that our developers use
is linked against crypto libraries (as that's the default), that's just
one example of a fairly basic bit of infrastructure that would be
broken.)
It's been in CURRENT for over a week --and as obrien@ noted, we've been
building the libraries all along; the install32 target just didn't
include them, so we weren't installing them.
Please? Thanks!
Peace,
david
--=20
David H. Wolfskill david@catwhisker.org
Depriving a girl or boy of an opportunity for education is evil.
See http://www.catwhisker.org/~david/publickey.gpg for my public key.
--oFGQ2VdWvpciDCpb
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (FreeBSD)
iEYEARECAAYFAkkl8pAACgkQmprOCmdXAD1aDwCfTXE0R8fkYAkBNutoet4rfdya
BhsAniyP3fYwC+xIh8F2l5vAtCWwkHO7
=loIB
-----END PGP SIGNATURE-----
--oFGQ2VdWvpciDCpb--
From owner-freebsd-stable@FreeBSD.ORG Thu Nov 20 23:38:38 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 368EC1065686
for <stable@freebsd.org>; Thu, 20 Nov 2008 23:38:38 +0000 (UTC)
(envelope-from sbruno@miralink.com)
Received: from plato.miralink.com (mail.miralink.com [70.103.185.20])
by mx1.freebsd.org (Postfix) with ESMTP id 069598FC20
for <stable@freebsd.org>; Thu, 20 Nov 2008 23:38:38 +0000 (UTC)
(envelope-from sbruno@miralink.com)
Received: from localhost (localhost.localdomain [127.0.0.1])
by plato.miralink.com (Postfix) with ESMTP id 40F2C1A9175;
Thu, 20 Nov 2008 15:22:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.33
X-Spam-Level:
X-Spam-Status: No, score=-4.33 tagged_above=-10 required=6.6
tests=[ALL_TRUSTED=-1.8, AWL=0.069, BAYES_00=-2.599]
Received: from plato.miralink.com ([127.0.0.1])
by localhost (plato.miralink.com [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id 8PYU550dSec6; Thu, 20 Nov 2008 15:22:05 -0800 (PST)
Received: from [10.47.1.10] (vpn.office.miralink.com [10.0.0.5])
by plato.miralink.com (Postfix) with ESMTP id 89FAC1A916F;
Thu, 20 Nov 2008 15:22:05 -0800 (PST)
Message-ID: <4925F11C.4080508@miralink.com>
Date: Thu, 20 Nov 2008 15:22:04 -0800
From: Sean Bruno <sbruno@miralink.com>
User-Agent: Thunderbird 2.0.0.16 (X11/20080723)
MIME-Version: 1.0
To: stable@freebsd.org, uspoerlein@gmail.com
References: <20081120211148.GA5178@roadrunner.spoerlein.net>
In-Reply-To: <20081120211148.GA5178@roadrunner.spoerlein.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc:
Subject: Re: LORs in RELENG_7
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Nov 2008 23:38:38 -0000
>
> And there are these LORs when I shut down my external firewire attached
> disk:
>
> fwohci0: BUS reset
> fwohci0: node_id=0xc800ffc1, gen=2, CYCLEMASTER mode
> firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 (me)
> firewire0: bus manager 1 (me)
> uma_zalloc_arg: zone "16" with the following non-sleepable locks held:
> exclusive sleep mutex sbp r = 0 (0xc402f7ac) locked @ /usr/src/sys/dev/firewire/sbp.c:2203
> KDB: stack backtrace:
> db_trace_self_wrapper(c08df797,f93a931c,c0630007,c08dfb5a,f93a9330,...) at db_trace_self_wrapper+0x26
> kdb_backtrace(c08dfb5a,f93a9330,4,1,0,...) at kdb_backtrace+0x29
> witness_warn(5,0,c0901ae5,c08c59ce,86,...) at witness_warn+0x1d7
> uma_zalloc_arg(c1472960,0,2,2,f93a93e0,...) at uma_zalloc_arg+0x34
> malloc(b,c09308c0,2,c05be59a,c08d7a2c,...) at malloc+0xd2
> notify(c4150a00,4,c08d7856,34f,c05be4ea,...) at notify+0x49
> destroy_devl(f93a9410,c046a6ce,c4150a00,0,c3f18370,...) at destroy_devl+0x236
> destroy_dev(c4150a00,0,c3f18370,c3f69000,f93a9690,...) at destroy_dev+0x10
> passcleanup(c3f69000,c08b50c7,0,0,0,...) at passcleanup+0x2e
> camperiphfree(c3f69000,0,f93a96b0,c04568dd,c3f69000,...) at camperiphfree+0xbb
> cam_periph_invalidate(c3f69000,c0983774,f93a96e4,c046a5ea,c3f69000,...) at cam_periph_invalidate+0x3e
> cam_periph_async(c3f69000,100,c418a260,0,f93a96e0,...) at cam_periph_async+0x2d
> passasync(c3f69000,100,c418a260,0,c42f8c00,...) at passasync+0xca
> xpt_async_bcast(0,4,c08b53c5,11a5,c404d280,...) at xpt_async_bcast+0x32
> xpt_async(100,c418a260,0,89b,0,...) at xpt_async+0x194
> sbp_cam_detach_sdev(c402f45c,0,c402f418,0,f93a982c,...) at sbp_cam_detach_sdev+0xa4
> sbp_cam_detach_target(c14729a8,c14729a8,c08250c6,c7373b40,10,...) at sbp_cam_detach_target+0x5b
> sbp_post_explore(c402f400,f93a9ce8,f93a9ce4,675,0,...) at sbp_post_explore+0xa2
> fw_bus_probe_thread(c404f000,f93a9d38,c08d8d0f,31c,c402b570,...) at fw_bus_probe_thread+0x69b
> fork_exit(c0513500,c404f000,f93a9d38) at fork_exit+0xb8
> fork_trampoline() at fork_trampoline+0x8
> --- trap 0, eip = 0, esp = 0xf93a9d70, ebp = 0 ---
> (da0:sbp0:0:0:0): lost device
> (da0:sbp0:0:0:0): removing device entry
> cam_periph_alloc: attempt to re-allocate valid device pass1 rejected
> passasync: Unable to attach new device due to status 0x6: CCB request was invalid
> cam_periph_alloc: attempt to re-allocate valid device da1 rejected
> daasync: Unable to attach to new device due to status 0x6
> fwohci0: BUS reset
> fwohci0: node_id=0xc800ffc0, gen=3, CYCLEMASTER mode
> firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me)
> firewire0: bus manager 0 (me)
> uma_zalloc_arg: zone "16" with the following non-sleepable locks held:
> exclusive sleep mutex sbp r = 0 (0xc402f7ac) locked @ /usr/src/sys/dev/firewire/sbp.c:2203
> KDB: stack backtrace:
> db_trace_self_wrapper(c08df797,f93a931c,c0630007,c08dfb5a,f93a9330,...) at db_trace_self_wrapper+0x26
> kdb_backtrace(c08dfb5a,f93a9330,4,1,0,...) at kdb_backtrace+0x29
> witness_warn(5,0,c0901ae5,c08c59ce,86,...) at witness_warn+0x1d7
> uma_zalloc_arg(c1472960,0,2,2,f93a93e0,...) at uma_zalloc_arg+0x34
> malloc(b,c09308c0,2,c05be59a,c08d7a2c,...) at malloc+0xd2
> notify(c4150d00,4,c08d7856,34f,c05be4ea,...) at notify+0x49
> destroy_devl(f93a9410,c046a6ce,c4150d00,0,c3f18370,...) at destroy_devl+0x236
> destroy_dev(c4150d00,0,c3f18370,c42c6700,f93a9690,...) at destroy_dev+0x10
> passcleanup(c42c6700,c08b50c7,c09eff00,4,c08db41b,...) at passcleanup+0x2e
> camperiphfree(c42c6700,0,f93a96b0,c04568dd,c42c6700,...) at camperiphfree+0xbb
> cam_periph_invalidate(c42c6700,c0983774,f93a96e4,c046a5ea,c42c6700,...) at cam_periph_invalidate+0x3e
> cam_periph_async(c42c6700,100,c418a250,0,f93a96e0,...) at cam_periph_async+0x2d
> passasync(c42c6700,100,c418a250,0,c42f8a00,...) at passasync+0xca
> xpt_async_bcast(0,4,c08b53c5,11a5,c404d280,...) at xpt_async_bcast+0x32
> xpt_async(100,c418a250,0,89b,0,...) at xpt_async+0x194
> sbp_cam_detach_sdev(c402f4c8,0,c402f484,1,f93a982c,...) at sbp_cam_detach_sdev+0xa4
> sbp_cam_detach_target(c14729a8,c14729a8,c08250c6,c44263f0,10,...) at sbp_cam_detach_target+0x5b
> sbp_post_explore(c402f400,f93a9ce8,f93a9ce4,675,0,...) at sbp_post_explore+0xa2
> fw_bus_probe_thread(c404f000,f93a9d38,c08d8d0f,31c,c402b570,...) at fw_bus_probe_thread+0x69b
> fork_exit(c0513500,c404f000,f93a9d38) at fork_exit+0xb8
> fork_trampoline() at fork_trampoline+0x8
> --- trap 0, eip = 0, esp = 0xf93a9d70, ebp = 0 ---
> (da1:sbp0:0:1:0): lost device
> (da1:sbp0:0:1:0): removing device entry
>
> I reckon these problems should appear in -STABLE ...
>
> Cheers,
> Ulrich Spoerlein
>
You are able to make this happen simply by powering off your Firewire
Hard Drive? What about pulling the cable out?
--
Sean Bruno
MiraLink Corporation
6015 NE 80th Ave, Ste 100
Portland, OR 97218
Cell 503-358-6832
Phone 503-621-5143
Fax 503-621-5199
MSN: sbruno@miralink.com
Google: seanwbruno@gmail.com
From owner-freebsd-stable@FreeBSD.ORG Fri Nov 21 00:41:14 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 3CCC81065673
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 00:41:14 +0000 (UTC)
(envelope-from crapsh@MonkeyBrains.NET)
Received: from ape.monkeybrains.net (mail.monkeybrains.net [208.69.40.9])
by mx1.freebsd.org (Postfix) with ESMTP id 0844E8FC16
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 00:41:14 +0000 (UTC)
(envelope-from crapsh@MonkeyBrains.NET)
Received: from Penelope-Thomas-Computer.local
(adsl-76-203-175-18.dsl.pltn13.sbcglobal.net [76.203.175.18])
(authenticated bits=0)
by ape.monkeybrains.net (8.14.1/8.14.1) with ESMTP id mAL0eUbD003577
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
Thu, 20 Nov 2008 16:40:30 -0800 (PST)
(envelope-from crapsh@MonkeyBrains.NET)
Message-ID: <492603B2.4060709@MonkeyBrains.NET>
Date: Thu, 20 Nov 2008 16:41:22 -0800
From: Rudy <crapsh@MonkeyBrains.NET>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: martinko <gamato@users.sf.net>
References: <20081109174303.GA5146@ourbrains.org> <20081109184349.GG51239@server.vk2pj.dyndns.org> <4920D879.3070806@jrv.org> <20081117050441.GA16855@ourbrains.org> <20081118175210.GA3753@hyperion.scode.org> <20081119001742.GA21835@ourbrains.org> <49235D86.4050106@modulus.org> <86bpwcp1d8.fsf@ds4.des.no> <4923D460.5020900@kkip.pl> <b41c75520811190106w7f951760m95c12358f1008c5b@mail.gmail.com> <4923E977.8030107@kkip.pl>
<gg4cmi$r6k$1@ger.gmane.org>
In-Reply-To: <gg4cmi$r6k$1@ger.gmane.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV version 0.94,
clamav-milter version 0.94 on pita.monkeybrains.net
X-Virus-Status: Clean
Cc: freebsd-stable@freebsd.org
Subject: (actually ZFS) Re: Will XFS be adopted
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Nov 2008 00:41:14 -0000
martinko wrote:
> Bartosz Stec wrote:
>>>
>> Well it's not simple indeed. I use ZFS on my home (not critical) box
>> (RAIDZ1). After 4 weeks uptime with varied workload I assumed it's
>> stable. Unfortunately ZFS crashed next week ;)
>>
>
> How did it crash ? Just the system went down or did you lose any data ?
Read my previous email on tuning your system so ZFS doesn't crash.
> I'm planning to build new home server and put all my valuable data on
> ZFS but after reading all the mailing lists I'm not so sure about it. :(
I've been using it on a shared machine with hundreds of customers for over 8 months. It has worked
flawlessly. People who complain about the crashes often have not searched the net for: "freebsd zfs
tuning".
Speaking of losing data on a ZFS system, I haven't yet (knock on wood) had a disk failure. Anyone
have a disk failure occur and have an easy/hard time replacing the bad disk?
Rudy
From owner-freebsd-stable@FreeBSD.ORG Fri Nov 21 01:08:27 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id F099E106564A
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 01:08:27 +0000 (UTC)
(envelope-from andrew@modulus.org)
Received: from email.octopus.com.au (email.octopus.com.au [122.100.2.232])
by mx1.freebsd.org (Postfix) with ESMTP id 9FFCE8FC19
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 01:08:27 +0000 (UTC)
(envelope-from andrew@modulus.org)
Received: by email.octopus.com.au (Postfix, from userid 1002)
id 535DF1775E; Fri, 21 Nov 2008 12:08:24 +1100 (EST)
X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on email.octopus.com.au
X-Spam-Level:
X-Spam-Status: No, score=-1.3 required=10.0 tests=ALL_TRUSTED,
DNS_FROM_SECURITYSAGE autolearn=no version=3.2.3
Received: from [10.1.50.60] (ppp121-44-7-122.lns10.syd7.internode.on.net
[121.44.7.122])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(No client certificate requested)
(Authenticated sender: admin@email.octopus.com.au)
by email.octopus.com.au (Postfix) with ESMTP id 3A4D1172FE;
Fri, 21 Nov 2008 12:08:20 +1100 (EST)
Message-ID: <49260972.4010201@modulus.org>
Date: Fri, 21 Nov 2008 12:05:54 +1100
From: Andrew Snow <andrew@modulus.org>
User-Agent: Thunderbird 2.0.0.14 (X11/20080523)
MIME-Version: 1.0
To: Rudy <crapsh@MonkeyBrains.NET>
References: <20081109174303.GA5146@ourbrains.org> <20081109184349.GG51239@server.vk2pj.dyndns.org> <4920D879.3070806@jrv.org> <20081117050441.GA16855@ourbrains.org> <20081118175210.GA3753@hyperion.scode.org> <20081119001742.GA21835@ourbrains.org> <49235D86.4050106@modulus.org> <86bpwcp1d8.fsf@ds4.des.no> <4923D460.5020900@kkip.pl> <b41c75520811190106w7f951760m95c12358f1008c5b@mail.gmail.com> <4923E977.8030107@kkip.pl> <gg4cmi$r6k$1@ger.gmane.org>
<492603B2.4060709@MonkeyBrains.NET>
In-Reply-To: <492603B2.4060709@MonkeyBrains.NET>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: freebsd-stable@freebsd.org
Subject: Re: (actually ZFS) Re: Will XFS be adopted
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Nov 2008 01:08:28 -0000
Rudy wrote:
> Speaking of losing data on a ZFS system, I haven't yet (knock on wood)
> had a disk failure. Anyone have a disk failure occur and have an
> easy/hard time replacing the bad disk?
On a system with AHCI, I can literally yank the SATA disks, zfs keeps
working after a pause, and when I replace them, it rebuilds without
intervention.
However with the latest 8-current this stopped working and now the
system crashes when I try this without using "atacontrol". But it seems
related to ATA code and not ZFS.
- Andrew
From owner-freebsd-stable@FreeBSD.ORG Fri Nov 21 01:18:35 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 1B6BF1065674
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 01:18:35 +0000 (UTC)
(envelope-from morganw@chemikals.org)
Received: from warped.bluecherry.net (unknown [IPv6:2001:440:eeee:fffb::2])
by mx1.freebsd.org (Postfix) with ESMTP id 7B70D8FC0A
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 01:18:34 +0000 (UTC)
(envelope-from morganw@chemikals.org)
Received: from volatile.chemikals.org (unknown [74.193.182.107])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(Client did not present a certificate)
by warped.bluecherry.net (Postfix) with ESMTPSA id 5DED787F831C;
Thu, 20 Nov 2008 19:18:33 -0600 (CST)
Received: from localhost (morganw@localhost [127.0.0.1])
by volatile.chemikals.org (8.14.3/8.14.3) with ESMTP id mAL1IUHu006406;
Thu, 20 Nov 2008 19:18:30 -0600 (CST)
(envelope-from morganw@chemikals.org)
Date: Thu, 20 Nov 2008 19:18:30 -0600 (CST)
From: Wes Morgan <morganw@chemikals.org>
To: Rudy <crapsh@MonkeyBrains.NET>
In-Reply-To: <492603B2.4060709@MonkeyBrains.NET>
Message-ID: <alpine.BSF.2.00.0811201917180.1465@ibyngvyr.purzvxnyf.bet>
References: <20081109174303.GA5146@ourbrains.org>
<20081109184349.GG51239@server.vk2pj.dyndns.org>
<4920D879.3070806@jrv.org> <20081117050441.GA16855@ourbrains.org>
<20081118175210.GA3753@hyperion.scode.org>
<20081119001742.GA21835@ourbrains.org>
<49235D86.4050106@modulus.org> <86bpwcp1d8.fsf@ds4.des.no>
<4923D460.5020900@kkip.pl>
<b41c75520811190106w7f951760m95c12358f1008c5b@mail.gmail.com>
<4923E977.8030107@kkip.pl> <gg4cmi$r6k$1@ger.gmane.org>
<492603B2.4060709@MonkeyBrains.NET>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: freebsd-stable@freebsd.org, martinko <gamato@users.sf.net>
Subject: Re: (actually ZFS) Re: Will XFS be adopted
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Nov 2008 01:18:35 -0000
On Thu, 20 Nov 2008, Rudy wrote:
> martinko wrote:
>> Bartosz Stec wrote:
>>>>
>>> Well it's not simple indeed. I use ZFS on my home (not critical) box
>>> (RAIDZ1). After 4 weeks uptime with varied workload I assumed it's stable.
>>> Unfortunately ZFS crashed next week ;)
>>>
>>
>> How did it crash ? Just the system went down or did you lose any data ?
>
> Read my previous email on tuning your system so ZFS doesn't crash.
>
>> I'm planning to build new home server and put all my valuable data on ZFS
>> but after reading all the mailing lists I'm not so sure about it. :(
>
> I've been using it on a shared machine with hundreds of customers for over 8
> months. It has worked flawlessly. People who complain about the crashes
> often have not searched the net for: "freebsd zfs tuning".
>
> Speaking of losing data on a ZFS system, I haven't yet (knock on wood) had a
> disk failure. Anyone have a disk failure occur and have an easy/hard time
> replacing the bad disk?
I had a Samsung drive fail on me a few months back. Samsung does not do
"advance shipment" like Seagate or WD. I had to run a raidz one drive
short for about a week. The replacement was as simple as you'd expect -
"zpool replace ..."
Note, I will not be purchasing any more Samsung drives :)
From owner-freebsd-stable@FreeBSD.ORG Fri Nov 21 07:48:27 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id DCDEA106564A
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 07:48:27 +0000 (UTC)
(envelope-from admin@kkip.pl)
Received: from mainframe.kkip.pl (kkip.pl [87.105.164.78])
by mx1.freebsd.org (Postfix) with ESMTP id 8504C8FC14
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 07:48:26 +0000 (UTC)
(envelope-from admin@kkip.pl)
Received: from admin.admin.lan.kkip.pl ([10.66.3.254])
by mainframe.kkip.pl with esmtpsa (TLSv1:AES256-SHA:256)
(Exim 4.69 (FreeBSD)) (envelope-from <admin@kkip.pl>)
id 1L3QkY-0007or-D7; Fri, 21 Nov 2008 08:48:24 +0100
Message-ID: <492667C8.5010505@kkip.pl>
Date: Fri, 21 Nov 2008 08:48:24 +0100
From: Bartosz Stec <admin@kkip.pl>
User-Agent: Thunderbird 2.0.0.18 (Windows/20081105)
MIME-Version: 1.0
To: martinko <gamato@users.sf.net>
References: <20081109174303.GA5146@ourbrains.org> <20081109184349.GG51239@server.vk2pj.dyndns.org> <4920D879.3070806@jrv.org> <20081117050441.GA16855@ourbrains.org> <20081118175210.GA3753@hyperion.scode.org> <20081119001742.GA21835@ourbrains.org> <49235D86.4050106@modulus.org> <86bpwcp1d8.fsf@ds4.des.no> <4923D460.5020900@kkip.pl> <b41c75520811190106w7f951760m95c12358f1008c5b@mail.gmail.com> <4923E977.8030107@kkip.pl>
<gg4cmi$r6k$1@ger.gmane.org>
In-Reply-To: <gg4cmi$r6k$1@ger.gmane.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Authenticated-User: admin@kkip.pl
X-Authenticator: plain
X-Sender-Verify: SUCCEEDED (sender exists & accepts mail)
X-Spam-Score: -8.9
X-Spam-Score-Int: -88
X-Exim-Version: 4.69 (build at 01-Nov-2008 10:39:57)
X-Date: 2008-11-21 08:48:24
X-Connected-IP: 10.66.3.254:1124
X-Message-Linecount: 67
X-Body-Linecount: 53
X-Message-Size: 2720
X-Body-Size: 1795
X-Received-Count: 1
X-Recipient-Count: 2
X-Local-Recipient-Count: 2
X-Local-Recipient-Defer-Count: 0
X-Local-Recipient-Fail-Count: 0
Cc: freebsd-stable@freebsd.org
Subject: Re: Will XFS be adopted
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Nov 2008 07:48:27 -0000
martinko pisze:
> Bartosz Stec wrote:
>>>
>> Well it's not simple indeed. I use ZFS on my home (not critical) box
>> (RAIDZ1). After 4 weeks uptime with varied workload I assumed it's
>> stable. Unfortunately ZFS crashed next week ;)
>>
>
> How did it crash ? Just the system went down or did you lose any data ?
>
> I'm planning to build new home server and put all my valuable data on
> ZFS but after reading all the mailing lists I'm not so sure about it. :(
>
> M.
I didn't loose any data , and system was up (ping and packet filter did
still working), but filesystem was unaccesible so any kind of process
which need hdd acces didn't work correctly (like ssh shell or mail
server). Hard reboot was one and only solution ;)
Feel free to test ZFS for yourself. Good tuning should made it stable
enough for you. You also shouldn't worry for your data, ZFS problems are
mainly related to kernel memory exhaustion, not a data corruption
(Backups however are always recomended before tasks like this). Check
the ZFS tuning guide http://wiki.freebsd.org/ZFSTuningGuide and good luck.
My home system is i386 with 1,5GB of memory and tuned with:
KERNEL:
options KVA_PAGES=512
loader.conf:
vm.kmem_size="1024M"
vm.kmem_size_max="1024M"
It's a very simple tuning, just for tests. My system probably needs ARC
settings or vfs.zfs.prefetch_disable=1 to be (more) stable. I'll do more
tests, but you probably should do your own - there's no one good tuning
solution for every system configuration. Just search this list - there's
a lot of examples and hints. Jeremy Chadwick explained a lot of those
settings too.
--
Bartosz Stec
AUXILIA Spółka z o.o.
ul. Wałbrzyska 43/2
52-314 Wrocław
tel. (71) 79 99 760 w. 69
GSM: 662171775
E-Mail: admin@kkip.pl
From owner-freebsd-stable@FreeBSD.ORG Fri Nov 21 08:07:27 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id DE9A01065678
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 08:07:27 +0000 (UTC)
(envelope-from bounces@nabble.com)
Received: from kuber.nabble.com (kuber.nabble.com [216.139.236.158])
by mx1.freebsd.org (Postfix) with ESMTP id B72748FC1D
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 08:07:27 +0000 (UTC)
(envelope-from bounces@nabble.com)
Received: from isper.nabble.com ([192.168.236.156])
by kuber.nabble.com with esmtp (Exim 4.63)
(envelope-from <bounces@nabble.com>) id 1L3R30-0007As-9Z
for freebsd-stable@freebsd.org; Fri, 21 Nov 2008 00:07:26 -0800
Message-ID: <20616760.post@talk.nabble.com>
Date: Fri, 21 Nov 2008 00:07:26 -0800 (PST)
From: hamtilla <tangel@gmail.com>
To: freebsd-stable@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Nabble-From: tangel@gmail.com
Subject: Integrated RTL8168/8111 NIC not assigned interface
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Nov 2008 08:07:27 -0000
I'm running 7.0-RELEASE-i386 on Jetway's NC92-N230 mainboard. The board has
one integrated RTL8168/8111 gigabit NIC as well as an expansion board with
three RTL8168/8111 NICs. Why would the three NICs work while the onboard NIC
does not?
none2@pci0:1:0:0: class=0x020000 card=0x816810ec chip=0x816810ec
rev=0x02 hdr=0x00
vendor = 'Realtek Semiconductor'
device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC'
class = network
subclass = ethernet
re0@pci0:2:4:0: class=0x020000 card=0x10ec16f3 chip=0x816710ec rev=0x10
hdr=0x00
vendor = 'Realtek Semiconductor'
device = 'RTL8169/8110 Family Gigabit Ethernet NIC'
class = network
subclass = ethernet
re1@pci0:2:6:0: class=0x020000 card=0x10ec16f3 chip=0x816710ec rev=0x10
hdr=0x00
vendor = 'Realtek Semiconductor'
device = 'RTL8169/8110 Family Gigabit Ethernet NIC'
class = network
subclass = ethernet
re2@pci0:2:7:0: class=0x020000 card=0x10ec16f3 chip=0x816710ec rev=0x10
hdr=0x00
vendor = 'Realtek Semiconductor'
device = 'RTL8169/8110 Family Gigabit Ethernet NIC'
class = network
subclass = ethernet
--
View this message in context: http://www.nabble.com/Integrated-RTL8168-8111-NIC-not-assigned-interface-tp20616760p20616760.html
Sent from the freebsd-stable mailing list archive at Nabble.com.
From owner-freebsd-stable@FreeBSD.ORG Fri Nov 21 10:08:37 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id F117B106564A
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 10:08:37 +0000 (UTC)
(envelope-from kamikaze@bsdforen.de)
Received: from mail.bsdforen.de (bsdforen.de [212.204.60.79])
by mx1.freebsd.org (Postfix) with ESMTP id B289C8FC0A
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 10:08:37 +0000 (UTC)
(envelope-from kamikaze@bsdforen.de)
Received: from mobileKamikaze.norad (vpn-cl-162-55.rz.uni-karlsruhe.de
[141.3.162.55])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(No client certificate requested)
by mail.bsdforen.de (Postfix) with ESMTP id 51B358A00D1;
Fri, 21 Nov 2008 11:08:15 +0100 (CET)
Message-ID: <4926887E.9000303@bsdforen.de>
Date: Fri, 21 Nov 2008 11:07:58 +0100
From: Dominic Fandrey <kamikaze@bsdforen.de>
User-Agent: Thunderbird 2.0.0.17 (X11/20080927)
MIME-Version: 1.0
To: Nenhum_de_Nos <matheus@eternamente.info>
References: <4923C8D4.2000109@bsdforen.de>
<9b5d48672e38f20652cf315844965606.squirrel@cygnus.homeunix.com>
In-Reply-To: <9b5d48672e38f20652cf315844965606.squirrel@cygnus.homeunix.com>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: freebsd-stable@freebsd.org
Subject: Re: u3g and ubsa
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Nov 2008 10:08:38 -0000
Nenhum_de_Nos wrote:
> On Wed, November 19, 2008 6:05 am, Dominic Fandrey wrote:
>> I have recently been pointed to the u3g driver and gave it a try,
>> because UBSA works very unreliable for me.
>>
>> - In combination with PF-NAT I get kernel panics under high load.
>> - I have to hack some buffer sizes in the driver to get the full
>> 3G speed.
>> - Often my USB-3G stick is not detected, sometimes I spent several
>> minutes plugging it in and out until it is detected.
>> - It doesn't let me use the card reader in the stick.
>>
>> The u3g driver has NONE of these problems. Everything just works
>> for me.
>>
>> So obviously I would like to have u3g in stable and chose for
>> myself or even take support for devices out of ubsa that work
>> better with u3g.
>> _______________________________________________
>
> same for me. I'm looking forward to see u3g in STABLE.
>
> matheus
>
Do you know about anyone pushing this? I think it's not even in
CURRENT!
From owner-freebsd-stable@FreeBSD.ORG Fri Nov 21 12:57:37 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 4F2A21065675
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 12:57:37 +0000 (UTC)
(envelope-from sclark46@earthlink.net)
Received: from elasmtp-curtail.atl.sa.earthlink.net
(elasmtp-curtail.atl.sa.earthlink.net [209.86.89.64])
by mx1.freebsd.org (Postfix) with ESMTP id 2280E8FC08
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 12:57:36 +0000 (UTC)
(envelope-from sclark46@earthlink.net)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net;
b=jos9SaSzUbpm3pRAqfYIDXI0IyuidujZw6HKR+W1SY15oQGUADAOlU2HMYHlYzMv;
h=Received:Message-ID:Date:From:Reply-To:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [208.118.36.229] (helo=joker.seclark.com)
by elasmtp-curtail.atl.sa.earthlink.net with esmtpsa
(TLSv1:AES256-SHA:256) (Exim 4.67)
(envelope-from <sclark46@earthlink.net>) id 1L3VZo-0006XI-49
for freebsd-stable@freebsd.org; Fri, 21 Nov 2008 07:57:36 -0500
Message-ID: <4926B03E.6020108@earthlink.net>
Date: Fri, 21 Nov 2008 07:57:34 -0500
From: Stephen Clark <sclark46@earthlink.net>
User-Agent: Thunderbird 2.0.0.16 (X11/20080723)
MIME-Version: 1.0
To: FreeBSD Stable <freebsd-stable@freebsd.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: a437fbc6971e80f61aa676d7e74259b7b3291a7d08dfec79eb9c3682f0fd0557662bd2a5e63c8502350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 208.118.36.229
Subject: support for natted ftp server and passive mode
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: sclark46@earthlink.net
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Nov 2008 12:57:37 -0000
Do any of the firewall products on FreeBSD provide support
for a natted ftp server sitting behind the FreeBSD FW.
Without having the ftp server advertise the external address
in its passive mode packet, in other words have the firewall
product look inside the packet and change the internal address
in the data portion of the packet to the external address.
Thanks,
Steve
--
"They that give up essential liberty to obtain temporary safety,
deserve neither liberty nor safety." (Ben Franklin)
"The course of history shows that as a government grows, liberty
decreases." (Thomas Jefferson)
From owner-freebsd-stable@FreeBSD.ORG Fri Nov 21 13:03:53 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id B52401065679
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 13:03:53 +0000 (UTC)
(envelope-from admin@kkip.pl)
Received: from mainframe.kkip.pl (kkip.pl [87.105.164.78])
by mx1.freebsd.org (Postfix) with ESMTP id 67A3F8FC17
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 13:03:53 +0000 (UTC)
(envelope-from admin@kkip.pl)
Received: from admin.admin.lan.kkip.pl ([10.66.3.254])
by mainframe.kkip.pl with esmtpsa (TLSv1:AES256-SHA:256)
(Exim 4.69 (FreeBSD)) (envelope-from <admin@kkip.pl>)
id 1L3Vfq-000NQo-JR; Fri, 21 Nov 2008 14:03:52 +0100
Message-ID: <4926B1B8.8000707@kkip.pl>
Date: Fri, 21 Nov 2008 14:03:52 +0100
From: Bartosz Stec <admin@kkip.pl>
User-Agent: Thunderbird 2.0.0.18 (Windows/20081105)
MIME-Version: 1.0
To: sclark46@earthlink.net
References: <4926B03E.6020108@earthlink.net>
In-Reply-To: <4926B03E.6020108@earthlink.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Authenticated-User: admin@kkip.pl
X-Authenticator: plain
X-Sender-Verify: SUCCEEDED (sender exists & accepts mail)
X-Spam-Score: -8.9
X-Spam-Score-Int: -88
X-Exim-Version: 4.69 (build at 01-Nov-2008 10:39:57)
X-Date: 2008-11-21 14:03:52
X-Connected-IP: 10.66.3.254:3107
X-Message-Linecount: 43
X-Body-Linecount: 29
X-Message-Size: 1218
X-Body-Size: 664
X-Received-Count: 1
X-Recipient-Count: 2
X-Local-Recipient-Count: 2
X-Local-Recipient-Defer-Count: 0
X-Local-Recipient-Fail-Count: 0
Cc: FreeBSD Stable <freebsd-stable@freebsd.org>
Subject: Re: support for natted ftp server and passive mode
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Nov 2008 13:03:53 -0000
Stephen Clark pisze:
> Do any of the firewall products on FreeBSD provide support
> for a natted ftp server sitting behind the FreeBSD FW.
>
> Without having the ftp server advertise the external address
> in its passive mode packet, in other words have the firewall
> product look inside the packet and change the internal address
> in the data portion of the packet to the external address.
>
> Thanks,
> Steve
>
pf + ftp-proxy
http://www.openbsd.org/cgi-bin/man.cgi?query=ftp-proxy&sektion=8&manpath=OpenBSD+4.4
--
Bartosz Stec
AUXILIA Spółka z o.o.
ul. Wałbrzyska 43/2
52-314 Wrocław
tel. (71) 79 99 760 w. 69
GSM: 662171775
E-Mail: admin@kkip.pl
From owner-freebsd-stable@FreeBSD.ORG Fri Nov 21 13:14:27 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 4B1101065680
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 13:14:27 +0000 (UTC)
(envelope-from avg@icyb.net.ua)
Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140])
by mx1.freebsd.org (Postfix) with ESMTP id 774AA8FC1D
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 13:14:25 +0000 (UTC)
(envelope-from avg@icyb.net.ua)
Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua
[212.40.38.101])
by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id PAA13769
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 15:14:23 +0200 (EET)
(envelope-from avg@icyb.net.ua)
Message-ID: <4926B42E.2010408@icyb.net.ua>
Date: Fri, 21 Nov 2008 15:14:22 +0200
From: Andriy Gapon <avg@icyb.net.ua>
User-Agent: Thunderbird 2.0.0.17 (X11/20081106)
MIME-Version: 1.0
To: FreeBSD Stable <freebsd-stable@freebsd.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: pciconf: incorrect description for chip=0x610111ab
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Nov 2008 13:14:27 -0000
I wasn't sure where this belongs, so writing here.
This is stable/7 on Intel DG33TL:
$ pciconf -lv
...
atapci0@pci0:3:0:0: class=0x01018f card=0x610111ab chip=0x610111ab
rev=0xb2 hdr=0x00
vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)'
device = '6101 SATA2 Controller'
class = mass storage
subclass = ATA
...
This is actually a PATA controller (SATA is provided by ICH9).
lspci is more correct:
$ lspci -v
...
03:00.0 IDE interface: Marvell Technology Group Ltd. 88SE6101
single-port PATA133 interface (rev b2) (prog-if 8f [Master SecP SecO
PriP PriO])
Subsystem: Marvell Technology Group Ltd. 88SE6101 single-port
PATA133 interface
...
ATA driver is also cool:
atapci0: <Marvell 88SX6101 UDMA133 controller>
--
Andriy Gapon
From owner-freebsd-stable@FreeBSD.ORG Fri Nov 21 13:39:23 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 06F011065670
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 13:39:23 +0000 (UTC)
(envelope-from petefrench@ticketswitch.com)
Received: from constantine.ticketswitch.com (constantine.ticketswitch.com
[IPv6:2002:57e0:1d4e:1::3])
by mx1.freebsd.org (Postfix) with ESMTP id C55018FC0C
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 13:39:22 +0000 (UTC)
(envelope-from petefrench@ticketswitch.com)
Received: from dilbert.rattatosk ([10.64.50.6] helo=dilbert.ticketswitch.com)
by constantine.ticketswitch.com with esmtps (TLSv1:AES256-SHA:256)
(Exim 4.69 (FreeBSD)) (envelope-from <petefrench@ticketswitch.com>)
id 1L3WEC-000Cpb-PW
for freebsd-stable@freebsd.org; Fri, 21 Nov 2008 13:39:20 +0000
Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.69
(FreeBSD)) (envelope-from <petefrench@ticketswitch.com>)
id 1L3WEC-0000SM-No
for freebsd-stable@freebsd.org; Fri, 21 Nov 2008 13:39:20 +0000
To: freebsd-stable@freebsd.org
Message-Id: <E1L3WEC-0000SM-No@dilbert.ticketswitch.com>
From: Pete French <petefrench@ticketswitch.com>
Date: Fri, 21 Nov 2008 13:39:20 +0000
Subject: Curious failure of ZFS snapshots
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Nov 2008 13:39:24 -0000
I have a couple of boxes here which make daily snapshots
of their filesystems. One just makes a snapshot at 7am, called '7am'
which it does by deleting the previous days and making a new one called
'7am'. The other has snapshots called 'today', 'yesterday', '2daysago'
etc, up to a week. It does this by deleting the '5daysago' snapshot,
renaming all the others to shuffle them down by one, and then creating
a new snapshot for 'today'.
On the box with the snapshots being created every day with the same
name I quickly end up with unavailable snapshots, and the error
message: 'Bad file descriptor'. On the machine which is creating
dailys which do not have the same name this does not happen.
Interesting - and unexpected. The machines are running identical
kernels, being 7-STABLE form a few days ago.
-pete.
From owner-freebsd-stable@FreeBSD.ORG Fri Nov 21 13:55:58 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 32E571065672
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 13:55:58 +0000 (UTC)
(envelope-from avg@icyb.net.ua)
Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140])
by mx1.freebsd.org (Postfix) with ESMTP id 6E99B8FC1A
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 13:55:57 +0000 (UTC)
(envelope-from avg@icyb.net.ua)
Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua
[212.40.38.101])
by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id PAA15248;
Fri, 21 Nov 2008 15:55:51 +0200 (EET) (envelope-from avg@icyb.net.ua)
Message-ID: <4926BDE5.5020708@icyb.net.ua>
Date: Fri, 21 Nov 2008 15:55:49 +0200
From: Andriy Gapon <avg@icyb.net.ua>
User-Agent: Thunderbird 2.0.0.17 (X11/20081106)
MIME-Version: 1.0
To: joerg_wunsch@uriah.heep.sax.de, FreeBSD Stable <freebsd-stable@freebsd.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc:
Subject: smbmsg(8): slave address confusion?
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Nov 2008 13:55:58 -0000
It seems that smbmsg is another victim in "Great SMBus Slave Address
Confusion" - there are two schools: one that think that slave address is
(addr >> 1) and there other thinks that slave address is (addr & ~0x1).
It seems that smb driver in FreeBSD takes the first approach, but smbmsg
is keen on the second.
smbmsg.c:
...
/*
* The I2C specs say that all addresses below 16 and above or equal
* 240 are reserved. Address 0 is the global address, but we do not
* care for this detail.
*/
#define MIN_I2C_ADDR 16
#define MAX_I2C_ADDR 240
.
.
.
static void
probe_i2c(void)
{
...
for (addr = MIN_I2C_ADDR; addr < MAX_I2C_ADDR; addr += 2) {
...
And sample output on my machine (releng/7 amd64):
$ mbmsg -p
Probing for devices on /dev/smb0:
Device @0x44: rw
Device @0x50: rw
Device @0x52: rw
Device @0x80: rw
Device @0x88: w
Device @0xc4: rw
Device @0xd0: rw
Device @0xd2: rw
Now:
(0x44 << 1) & 0xff == (0xc4 << 1) & 0xff = 0x88 (looks like RTC)
(0x50 << 1) & 0xff == (0xd0 << 1) & 0xff = 0xa0 (well known SPD addr)
(0x52 << 1) & 0xff == (0xd2 << 1) & 0xff = 0xa4 (well known SPD addr)
(0x80 << 1) & 0xff = 0x0 (mentioned above "global address")
(0x88 << 1) & 0xff == MIN_I2C_ADDR = 0x10 (something weird)
I think that this demonstrates that FreeBSD smb driver expects slave
addresses in range 0x0-0x7f.
--
Andriy Gapon
From owner-freebsd-stable@FreeBSD.ORG Fri Nov 21 14:15:25 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 5BEEA1065677
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 14:15:25 +0000 (UTC)
(envelope-from gerrit@pmp.uni-hannover.de)
Received: from mrelay1.uni-hannover.de (mrelay1.uni-hannover.de [130.75.2.106])
by mx1.freebsd.org (Postfix) with ESMTP id E0B6B8FC2E
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 14:15:24 +0000 (UTC)
(envelope-from gerrit@pmp.uni-hannover.de)
Received: from www.pmp.uni-hannover.de (www.pmp.uni-hannover.de [130.75.117.2])
by mrelay1.uni-hannover.de (8.14.2/8.14.2) with ESMTP id mALEFIfZ011088;
Fri, 21 Nov 2008 15:15:21 +0100
Received: from pmp.uni-hannover.de (arc.pmp.uni-hannover.de [130.75.117.1])
by www.pmp.uni-hannover.de (Postfix) with SMTP
id 4A5D72E6; Fri, 21 Nov 2008 15:15:18 +0100 (CET)
Date: Fri, 21 Nov 2008 15:15:18 +0100
From: Gerrit =?ISO-8859-1?Q?K=FChn?= <gerrit@pmp.uni-hannover.de>
To: Pete French <petefrench@ticketswitch.com>
Message-Id: <20081121151518.9f4f6af8.gerrit@pmp.uni-hannover.de>
In-Reply-To: <E1L3WEC-0000SM-No@dilbert.ticketswitch.com>
References: <E1L3WEC-0000SM-No@dilbert.ticketswitch.com>
Organization: Albert-Einstein-Institut (MPI =?ISO-8859-1?Q?f=FCr?=
Gravitationsphysik & IGP =?ISO-8859-1?Q?Universit=E4t?= Hannover)
X-Mailer: Sylpheed 2.4.8 (GTK+ 2.12.11; i386-portbld-freebsd7.0)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-PMX-Version: 5.4.1.325704, Antispam-Engine: 2.6.0.325393,
Antispam-Data: 2008.11.21.140126
Cc: freebsd-stable@freebsd.org
Subject: Re: Curious failure of ZFS snapshots
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Nov 2008 14:15:25 -0000
On Fri, 21 Nov 2008 13:39:20 +0000 Pete French
<petefrench@ticketswitch.com> wrote about Curious failure of ZFS snapshots:
PF> On the box with the snapshots being created every day with the same
PF> name I quickly end up with unavailable snapshots, and the error
PF> message: 'Bad file descriptor'. On the machine which is creating
PF> dailys which do not have the same name this does not happen.
PF>
PF> Interesting - and unexpected. The machines are running identical
PF> kernels, being 7-STABLE form a few days ago.
I have a similar setup (creating daily.0 every night and rotating the
rest) for some home directories here...
Right now 3 of them are fine, and one is showing the same problem you
described:
mclane# ll /tank/home/pt/.zfs/
ls: snapshot: Bad file descriptor
total 0
Note that zfs still thinks the snapshots are there:
mclane# zfs list -r tank/home/pt
NAME USED AVAIL REFER MOUNTPOINT
tank/home/pt 454M 1.78T 262M /tank/home/pt
tank/home/pt@weekly.1 32.5M - 260M -
tank/home/pt@daily.6 29.6M - 262M -
tank/home/pt@weekly.0 45.3K - 262M -
tank/home/pt@daily.5 45.3K - 262M -
tank/home/pt@daily.4 28.2M - 262M -
tank/home/pt@daily.3 28.7M - 262M -
tank/home/pt@daily.2 27.8M - 262M -
tank/home/pt@daily.1 374K - 262M -
tank/home/pt@hourly.7 45.3K - 262M -
tank/home/pt@hourly.6 45.3K - 262M -
tank/home/pt@hourly.5 45.3K - 262M -
tank/home/pt@hourly.4 45.3K - 262M -
tank/home/pt@daily.0 45.3K - 262M -
tank/home/pt@hourly.3 45.3K - 262M -
tank/home/pt@hourly.2 45.3K - 262M -
tank/home/pt@hourly.1 45.3K - 262M -
tank/home/pt@hourly.0 45.3K - 262M -
I even do autoamtic incremental backups via send/receive. There are no
errors (up to today) and the snapshots are accessible on the backup
machine.
I am a bit troubled by unaccessible snapshots. Does anyone else here have
the same problem (or can even offer a solution)?
cu
Gerrit
From owner-freebsd-stable@FreeBSD.ORG Fri Nov 21 14:19:37 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id B68121065670
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 14:19:37 +0000 (UTC)
(envelope-from sclark46@earthlink.net)
Received: from elasmtp-kukur.atl.sa.earthlink.net
(elasmtp-kukur.atl.sa.earthlink.net [209.86.89.65])
by mx1.freebsd.org (Postfix) with ESMTP id 876568FC0C
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 14:19:37 +0000 (UTC)
(envelope-from sclark46@earthlink.net)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net;
b=eyto03hWHbmp6/o0nVLVfxbqbC3Mb7j9AI28ITXSLj5HVQ97dXW/2zKeKa4JbWj5;
h=Received:Message-ID:Date:From:Reply-To:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [208.118.36.229] (helo=joker.seclark.com)
by elasmtp-kukur.atl.sa.earthlink.net with esmtpsa
(TLSv1:AES256-SHA:256) (Exim 4.67)
(envelope-from <sclark46@earthlink.net>)
id 1L3Wr8-0007rP-Fd; Fri, 21 Nov 2008 09:19:34 -0500
Message-ID: <4926C375.5070108@earthlink.net>
Date: Fri, 21 Nov 2008 09:19:33 -0500
From: Stephen Clark <sclark46@earthlink.net>
User-Agent: Thunderbird 2.0.0.16 (X11/20080723)
MIME-Version: 1.0
To: Bartosz Stec <admin@kkip.pl>
References: <4926B03E.6020108@earthlink.net> <4926B1B8.8000707@kkip.pl>
In-Reply-To: <4926B1B8.8000707@kkip.pl>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: a437fbc6971e80f61aa676d7e74259b7b3291a7d08dfec79829de2439918dab95a8754628ce5d0dd350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 208.118.36.229
Cc: FreeBSD Stable <freebsd-stable@freebsd.org>
Subject: Re: support for natted ftp server and passive mode
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: sclark46@earthlink.net
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Nov 2008 14:19:37 -0000
Bartosz Stec wrote:
> Stephen Clark pisze:
>> Do any of the firewall products on FreeBSD provide support
>> for a natted ftp server sitting behind the FreeBSD FW.
>>
>> Without having the ftp server advertise the external address
>> in its passive mode packet, in other words have the firewall
>> product look inside the packet and change the internal address
>> in the data portion of the packet to the external address.
>>
>> Thanks,
>> Steve
>>
> pf + ftp-proxy
>
> http://www.openbsd.org/cgi-bin/man.cgi?query=ftp-proxy&sektion=8&manpath=OpenBSD+4.4
>
>
Thanks,
this seems to do the trick on 6.3 - unfortunately it doesn't work on FreeBSD
4.9. We have a number of installations which are still running on 4.9 :(
Steve
--
"They that give up essential liberty to obtain temporary safety,
deserve neither liberty nor safety." (Ben Franklin)
"The course of history shows that as a government grows, liberty
decreases." (Thomas Jefferson)
From owner-freebsd-stable@FreeBSD.ORG Fri Nov 21 14:21:35 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 26AA11065672
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 14:21:35 +0000 (UTC)
(envelope-from avg@icyb.net.ua)
Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140])
by mx1.freebsd.org (Postfix) with ESMTP id 614018FC12
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 14:21:34 +0000 (UTC)
(envelope-from avg@icyb.net.ua)
Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua
[212.40.38.101])
by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id QAA15561;
Fri, 21 Nov 2008 16:21:28 +0200 (EET) (envelope-from avg@icyb.net.ua)
Message-ID: <4926C3E7.7010001@icyb.net.ua>
Date: Fri, 21 Nov 2008 16:21:27 +0200
From: Andriy Gapon <avg@icyb.net.ua>
User-Agent: Thunderbird 2.0.0.17 (X11/20081106)
MIME-Version: 1.0
To: joerg_wunsch@uriah.heep.sax.de, FreeBSD Stable <freebsd-stable@freebsd.org>
References: <4926BDE5.5020708@icyb.net.ua>
In-Reply-To: <4926BDE5.5020708@icyb.net.ua>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc:
Subject: Re: smbmsg(8): slave address confusion?
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Nov 2008 14:21:35 -0000
on 21/11/2008 15:55 Andriy Gapon said the following:
> It seems that smbmsg is another victim in "Great SMBus Slave Address
> Confusion" - there are two schools: one that think that slave address is
> (addr >> 1) and there other thinks that slave address is (addr & ~0x1).
> It seems that smb driver in FreeBSD takes the first approach, but smbmsg
> is keen on the second.
Patch and new output:
diff --git a/usr.sbin/smbmsg/smbmsg.c b/usr.sbin/smbmsg/smbmsg.c
index 425b782..f2b8139 100644
--- a/usr.sbin/smbmsg/smbmsg.c
+++ b/usr.sbin/smbmsg/smbmsg.c
@@ -68,8 +68,8 @@ static unsigned short oword, iword;
* 240 are reserved. Address 0 is the global address, but we do not
* care for this detail.
*/
-#define MIN_I2C_ADDR 16
-#define MAX_I2C_ADDR 240
+#define MIN_I2C_ADDR 8
+#define MAX_I2C_ADDR 120
static int do_io(void);
static int getnum(const char *s);
@@ -109,7 +109,7 @@ probe_i2c(void)
printf("Probing for devices on %s:\n", dev);
- for (addr = MIN_I2C_ADDR; addr < MAX_I2C_ADDR; addr += 2) {
+ for (addr = MIN_I2C_ADDR; addr < MAX_I2C_ADDR; addr++) {
c.slave = addr;
flags = 0;
if (ioctl(fd, SMB_RECVB, &c) != -1)
$ smbmsg -p
Probing for devices on /dev/smb0:
Device @0x08: w
Device @0x44: rw
Device @0x50: rw
Device @0x52: rw
Device @0x69: rw
The only thing I am hesitant about - which address format is to present
to user? (addr >> 1) as above or (addr & ~0x1) as conventional for linux
folk.
--
Andriy Gapon
From owner-freebsd-stable@FreeBSD.ORG Fri Nov 21 14:41:58 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 021F0106568C
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 14:41:58 +0000 (UTC)
(envelope-from gerrit@pmp.uni-hannover.de)
Received: from mrelay1.uni-hannover.de (mrelay1.uni-hannover.de [130.75.2.106])
by mx1.freebsd.org (Postfix) with ESMTP id 6C98E8FC16
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 14:41:57 +0000 (UTC)
(envelope-from gerrit@pmp.uni-hannover.de)
Received: from www.pmp.uni-hannover.de (www.pmp.uni-hannover.de [130.75.117.2])
by mrelay1.uni-hannover.de (8.14.2/8.14.2) with ESMTP id mALEfsDA013420;
Fri, 21 Nov 2008 15:41:55 +0100
Received: from pmp.uni-hannover.de (arc.pmp.uni-hannover.de [130.75.117.1])
by www.pmp.uni-hannover.de (Postfix) with SMTP
id F1B9A72; Fri, 21 Nov 2008 15:41:53 +0100 (CET)
Date: Fri, 21 Nov 2008 15:41:53 +0100
From: Gerrit =?ISO-8859-1?Q?K=FChn?= <gerrit@pmp.uni-hannover.de>
To: freebsd-stable@freebsd.org
Message-Id: <20081121154153.a741e391.gerrit@pmp.uni-hannover.de>
In-Reply-To: <20081121151518.9f4f6af8.gerrit@pmp.uni-hannover.de>
References: <E1L3WEC-0000SM-No@dilbert.ticketswitch.com>
<20081121151518.9f4f6af8.gerrit@pmp.uni-hannover.de>
Organization: Albert-Einstein-Institut (MPI =?ISO-8859-1?Q?f=FCr?=
Gravitationsphysik & IGP =?ISO-8859-1?Q?Universit=E4t?= Hannover)
X-Mailer: Sylpheed 2.4.8 (GTK+ 2.12.11; i386-portbld-freebsd7.0)
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-PMX-Version: 5.4.1.325704, Antispam-Engine: 2.6.0.325393,
Antispam-Data: 2008.11.21.142521
Cc: Pete French <petefrench@ticketswitch.com>
Subject: Re: Curious failure of ZFS snapshots
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Nov 2008 14:41:58 -0000
On Fri, 21 Nov 2008 15:15:18 +0100 Gerrit K=FChn
<gerrit@pmp.uni-hannover.de> wrote about Re: Curious failure of ZFS
snapshots:
GK> Right now 3 of them are fine, and one is showing the same problem you
GK> described:
GK>=20
GK> mclane# ll /tank/home/pt/.zfs/
GK> ls: snapshot: Bad file descriptor
GK> total 0
[...]
One addition: I just tried to unmount tank/home/pt (in the hope the after
a remount everything would be fine again). This paniced the kernel, even
the coredump did not finish. After rebooting everything came back fine,
though. Now the snapshots are accessible again.
cu
Gerrit
From owner-freebsd-stable@FreeBSD.ORG Fri Nov 21 15:02:14 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 10AF41065677
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 15:02:14 +0000 (UTC)
(envelope-from ndenev@gmail.com)
Received: from gv-out-0910.google.com (gv-out-0910.google.com [216.239.58.186])
by mx1.freebsd.org (Postfix) with ESMTP id 9355B8FC0A
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 15:02:13 +0000 (UTC)
(envelope-from ndenev@gmail.com)
Received: by gv-out-0910.google.com with SMTP id n8so217542gve.39
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 07:02:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:cc:message-id:from:to
:in-reply-to:content-type:content-transfer-encoding:mime-version
:subject:date:references:x-pgp-agent:x-mailer;
bh=Hoqn1SxwksLj5SHncyXIXNKhNGjsO+sn9jxNk82umjo=;
b=TK9nkTlPk5q6V7xmaxt+qIBy7h1ebObPtou4OhgpOKaZ0cb+1Wjl/GNK/DNpLg1R3T
UbtGAiFHVrJp0gvN1pYS3rb5lhaWPRECqhgJ4cChJXxUnIsgKmUC296nn5ENDYpyfDYI
QVjkV4BvCWAnj4JUTyLAflUjEQeN7wS2aDwdA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=cc:message-id:from:to:in-reply-to:content-type
:content-transfer-encoding:mime-version:subject:date:references
:x-pgp-agent:x-mailer;
b=csWuQpBP5b1x3OXgur/sjo4/tBN9nCD30Vi2BaXyHzU/rPwRXmy7L4TjmzTzi4etv+
JOPQiQoY7TjOWb/7gqFchqXPfsvSWQD2zlFlccOuvhZk9YgkSocFqmAIVjuBgYDxmlDu
4T8AK0JDF4fI4nEn73qnrUC19VRhRWmaCM0Cw=
Received: by 10.103.160.9 with SMTP id m9mr74197muo.96.1227279731796;
Fri, 21 Nov 2008 07:02:11 -0800 (PST)
Received: from ndenev.cmotd.com (blah.sun-fish.com [217.18.249.150])
by mx.google.com with ESMTPS id j2sm13444mue.5.2008.11.21.07.02.09
(version=TLSv1/SSLv3 cipher=RC4-MD5);
Fri, 21 Nov 2008 07:02:10 -0800 (PST)
Message-Id: <67D4F3F5-C6B7-4413-A88C-04B1DA959AA3@gmail.com>
From: Nikolay Denev <ndenev@gmail.com>
To: =?ISO-8859-1?Q?Gerrit_K=FChn?= <gerrit@pmp.uni-hannover.de>
In-Reply-To: <20081121154153.a741e391.gerrit@pmp.uni-hannover.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 21 Nov 2008 17:02:07 +0200
References: <E1L3WEC-0000SM-No@dilbert.ticketswitch.com>
<20081121151518.9f4f6af8.gerrit@pmp.uni-hannover.de>
<20081121154153.a741e391.gerrit@pmp.uni-hannover.de>
X-Pgp-Agent: GPGMail d53 (v53, Leopard)
X-Mailer: Apple Mail (2.929.2)
Cc: freebsd-stable@freebsd.org, Pete French <petefrench@ticketswitch.com>
Subject: Re: Curious failure of ZFS snapshots
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Nov 2008 15:02:14 -0000
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 21 Nov, 2008, at 16:41 , Gerrit K=FChn wrote:
> On Fri, 21 Nov 2008 15:15:18 +0100 Gerrit K=FChn
> <gerrit@pmp.uni-hannover.de> wrote about Re: Curious failure of ZFS
> snapshots:
>
> GK> Right now 3 of them are fine, and one is showing the same =20
> problem you
> GK> described:
> GK>
> GK> mclane# ll /tank/home/pt/.zfs/
> GK> ls: snapshot: Bad file descriptor
> GK> total 0
>
> [...]
>
> One addition: I just tried to unmount tank/home/pt (in the hope the =20=
> after
> a remount everything would be fine again). This paniced the kernel, =20=
> even
> the coredump did not finish. After rebooting everything came back =20
> fine,
> though. Now the snapshots are accessible again.
>
>
> cu
> Gerrit
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to =
"freebsd-stable-unsubscribe@freebsd.org=20
> "
>
I've experienced this problem in the past : =
http://markmail.org/message/tmle6lqmkfit46ho
But the machine I was having these issues are no longer operational so =20=
I can't test again.
I hope the new ZFS import will fix this...
- --
Regards,
Nikolay Denev
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (Darwin)
iEYEARECAAYFAkkmzW8ACgkQHNAJ/fLbfrlyUwCgtNbPPMJ5UG/TOr7/qL8D4pmE
DWoAniqAzyygR3ce0HrW9en6Q8GTM4Ed
=3D9jpw
-----END PGP SIGNATURE-----
From owner-freebsd-stable@FreeBSD.ORG Fri Nov 21 15:13:48 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id CE83E1065673
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 15:13:48 +0000 (UTC)
(envelope-from gerrit@pmp.uni-hannover.de)
Received: from mrelay1.uni-hannover.de (mrelay1.uni-hannover.de [130.75.2.106])
by mx1.freebsd.org (Postfix) with ESMTP id 419CE8FC14
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 15:13:47 +0000 (UTC)
(envelope-from gerrit@pmp.uni-hannover.de)
Received: from www.pmp.uni-hannover.de (www.pmp.uni-hannover.de [130.75.117.2])
by mrelay1.uni-hannover.de (8.14.2/8.14.2) with ESMTP id mALFDjue016200;
Fri, 21 Nov 2008 16:13:46 +0100
Received: from pmp.uni-hannover.de (arc.pmp.uni-hannover.de [130.75.117.1])
by www.pmp.uni-hannover.de (Postfix) with SMTP
id 4A66172; Fri, 21 Nov 2008 16:13:45 +0100 (CET)
Date: Fri, 21 Nov 2008 16:13:45 +0100
From: Gerrit =?ISO-8859-1?Q?K=FChn?= <gerrit@pmp.uni-hannover.de>
To: Nikolay Denev <ndenev@gmail.com>
Message-Id: <20081121161345.4347efcd.gerrit@pmp.uni-hannover.de>
In-Reply-To: <67D4F3F5-C6B7-4413-A88C-04B1DA959AA3@gmail.com>
References: <E1L3WEC-0000SM-No@dilbert.ticketswitch.com>
<20081121151518.9f4f6af8.gerrit@pmp.uni-hannover.de>
<20081121154153.a741e391.gerrit@pmp.uni-hannover.de>
<67D4F3F5-C6B7-4413-A88C-04B1DA959AA3@gmail.com>
Organization: Albert-Einstein-Institut (MPI =?ISO-8859-1?Q?f=FCr?=
Gravitationsphysik & IGP =?ISO-8859-1?Q?Universit=E4t?= Hannover)
X-Mailer: Sylpheed 2.4.8 (GTK+ 2.12.11; i386-portbld-freebsd7.0)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-PMX-Version: 5.4.1.325704, Antispam-Engine: 2.6.0.325393,
Antispam-Data: 2008.11.21.150431
Cc: freebsd-stable@freebsd.org, Pete French <petefrench@ticketswitch.com>
Subject: Re: Curious failure of ZFS snapshots
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Nov 2008 15:13:48 -0000
On Fri, 21 Nov 2008 17:02:07 +0200 Nikolay Denev <ndenev@gmail.com> wrote
about Re: Curious failure of ZFS snapshots:
ND> I've experienced this problem in the past :
ND> http://markmail.org/message/tmle6lqmkfit46ho
Yes, that looks quite the same (even the panic).
ND> But the machine I was having these issues are no longer operational
ND> so I can't test again.
ND> I hope the new ZFS import will fix this...
I'm a bit worried about moving from -stable to -current with this machine.
Does anyone know (Pawel? :-) when the patches will arrive in -stable, and
if this issue is expected to be fixed then?
cu
Gerrit
From owner-freebsd-stable@FreeBSD.ORG Fri Nov 21 16:01:56 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 4917C106564A
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 16:01:56 +0000 (UTC)
(envelope-from ler@lerctr.org)
Received: from thebighonker.lerctr.org (thebighonker.lerctr.org
[192.147.25.65])
by mx1.freebsd.org (Postfix) with ESMTP id 243D28FC16
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 16:01:56 +0000 (UTC)
(envelope-from ler@lerctr.org)
Received: from thebighonker.lerctr.org ([192.147.25.65]:62839)
by thebighonker.lerctr.org with esmtpsa (TLSv1:AES256-SHA:256)
(Exim 4.69 (FreeBSD)) (envelope-from <ler@lerctr.org>)
id 1L3YDQ-0005CL-FC; Fri, 21 Nov 2008 09:46:41 -0600
Date: Fri, 21 Nov 2008 09:46:38 -0600 (CST)
From: Larry Rosenman <ler@lerctr.org>
To: Rudy <crapsh@MonkeyBrains.NET>
In-Reply-To: <492603B2.4060709@MonkeyBrains.NET>
Message-ID: <alpine.BSF.2.00.0811210944300.19844@thebighonker.lerctr.org>
References: <20081109174303.GA5146@ourbrains.org>
<20081109184349.GG51239@server.vk2pj.dyndns.org>
<4920D879.3070806@jrv.org> <20081117050441.GA16855@ourbrains.org>
<20081118175210.GA3753@hyperion.scode.org>
<20081119001742.GA21835@ourbrains.org>
<49235D86.4050106@modulus.org> <86bpwcp1d8.fsf@ds4.des.no>
<4923D460.5020900@kkip.pl>
<b41c75520811190106w7f951760m95c12358f1008c5b@mail.gmail.com>
<4923E977.8030107@kkip.pl> <gg4cmi$r6k$1@ger.gmane.org>
<492603B2.4060709@MonkeyBrains.NET>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Spam-Score: -4.3 (----)
X-LERCTR-Spam-Score: -4.3 (----)
X-Spam-Report: SpamScore (-4.3/5.0) ALL_TRUSTED=-1.8, BAYES_00=-2.599,
SARE_SUB_OBFU_OTHER=0.135
X-LERCTR-Spam-Report: SpamScore (-4.3/5.0) ALL_TRUSTED=-1.8, BAYES_00=-2.599,
SARE_SUB_OBFU_OTHER=0.135
DomainKey-Status: no signature
Cc: freebsd-stable@freebsd.org, martinko <gamato@users.sf.net>
Subject: Re: (actually ZFS) Re: Will XFS be adopted
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Nov 2008 16:01:56 -0000
On Thu, 20 Nov 2008, Rudy wrote:
>
> Speaking of losing data on a ZFS system, I haven't yet (knock on wood) had a
> disk failure. Anyone have a disk failure occur and have an easy/hard time
> replacing the bad disk?
I had a bad cable and also a bad disk. zpool scrub would whine about
checksum errors, but I did NOT lose any data. Replaced the drive
and still got the checksum errors. Replaced the cable, and it's
been rock solid.
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 512-248-2683 E-Mail: ler@lerctr.org
US Mail: 430 Valona Loop, Round Rock, TX 78681-3893
From owner-freebsd-stable@FreeBSD.ORG Fri Nov 21 16:16:39 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 9562F1065673
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 16:16:39 +0000 (UTC)
(envelope-from fjwcash@gmail.com)
Received: from smtp.sd73.bc.ca (smtp.sd73.bc.ca [142.24.13.140])
by mx1.freebsd.org (Postfix) with ESMTP id 77DAC8FC0C
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 16:16:39 +0000 (UTC)
(envelope-from fjwcash@gmail.com)
Received: from localhost (localhost [127.0.0.1])
by localhost.sd73.bc.ca (Postfix) with ESMTP id 07E6C1A0007AA
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 08:16:39 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at smtp.sd73.bc.ca
Received: from smtp.sd73.bc.ca ([127.0.0.1])
by localhost (smtp.sd73.bc.ca [127.0.0.1]) (amavisd-new, port 10024)
with LMTP id Fj3Na6+NLw3H for <freebsd-stable@freebsd.org>;
Fri, 21 Nov 2008 08:16:35 -0800 (PST)
Received: from coal (s10.sbo [192.168.0.10])
by smtp.sd73.bc.ca (Postfix) with ESMTP id A41EE1A0007A9
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 08:16:35 -0800 (PST)
From: Freddie Cash <fjwcash@gmail.com>
To: freebsd-stable@freebsd.org
Date: Fri, 21 Nov 2008 08:16:35 -0800
User-Agent: KMail/1.9.9
References: <E1L3WEC-0000SM-No@dilbert.ticketswitch.com>
<20081121151518.9f4f6af8.gerrit@pmp.uni-hannover.de>
<20081121154153.a741e391.gerrit@pmp.uni-hannover.de>
In-Reply-To: <20081121154153.a741e391.gerrit@pmp.uni-hannover.de>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200811210816.35573.fjwcash@gmail.com>
Subject: Re: Curious failure of ZFS snapshots
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Nov 2008 16:16:39 -0000
On November 21, 2008 06:41 am Gerrit K=FChn wrote:
> On Fri, 21 Nov 2008 15:15:18 +0100 Gerrit K=FChn
> <gerrit@pmp.uni-hannover.de> wrote about Re: Curious failure of ZFS
> snapshots:
>
> GK> Right now 3 of them are fine, and one is showing the same problem
> you GK> described:
> GK>
> GK> mclane# ll /tank/home/pt/.zfs/
> GK> ls: snapshot: Bad file descriptor
> GK> total 0
Which shell are you using? I've seen quite a few=20
different "non-existent"/"invalid directory" errors when using tcsh to=20
navigate through the .zfs/ hierarchy. Can do "cd ..", "ls .", or tab=20
completion when in anything under .zfs/
Using sh or zsh, these errors don't occur.
Just curious if this is the same kind of thing.
=2D-=20
=46reddie Cash
fjwcash@gmail.com
From owner-freebsd-stable@FreeBSD.ORG Fri Nov 21 16:35:14 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 0BE6F1065757
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 16:35:14 +0000 (UTC)
(envelope-from j@uriah.heep.sax.de)
Received: from uriah.heep.sax.de (uriah.heep.sax.de [213.240.137.9])
by mx1.freebsd.org (Postfix) with ESMTP id ABF768FC16
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 16:35:13 +0000 (UTC)
(envelope-from j@uriah.heep.sax.de)
Received: by uriah.heep.sax.de (Postfix, from userid 107)
id C0EED4F; Fri, 21 Nov 2008 17:16:29 +0100 (MET)
Date: Fri, 21 Nov 2008 17:16:29 +0100
From: Joerg Wunsch <j@uriah.heep.sax.de>
To: Andriy Gapon <avg@icyb.net.ua>
Message-ID: <20081121161629.GJ99866@uriah.heep.sax.de>
References: <4926BDE5.5020708@icyb.net.ua>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4926BDE5.5020708@icyb.net.ua>
X-Phone: +49-351-2012 669
X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E
X-GPG-Fingerprint: 5E84 F980 C3CA FD4B B584 1070 F48C A81B 69A8 5873
User-Agent: Mutt/1.5.11
Cc: FreeBSD Stable <freebsd-stable@freebsd.org>
Subject: Re: smbmsg(8): slave address confusion?
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Joerg Wunsch <joerg_wunsch@uriah.heep.sax.de>
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Nov 2008 16:35:14 -0000
As Andriy Gapon wrote:
> Now:
>
> (0x44 << 1) & 0xff == (0xc4 << 1) & 0xff = 0x88 (looks like RTC)
> (0x50 << 1) & 0xff == (0xd0 << 1) & 0xff = 0xa0 (well known SPD addr)
> (0x52 << 1) & 0xff == (0xd2 << 1) & 0xff = 0xa4 (well known SPD addr)
> (0x80 << 1) & 0xff = 0x0 (mentioned above "global address")
> (0x88 << 1) & 0xff == MIN_I2C_ADDR = 0x10 (something weird)
>
> I think that this demonstrates that FreeBSD smb driver expects slave
> addresses in range 0x0-0x7f.
Well, the machine I've been writing smbmsg(8) on has been a Sun E450 I
don't have access to any longer, so I cannot post a live example
output. However, I could swear the output did make sense on that
machine, i. e. the typical 0xa0 etc. addresses were populated there.
Basically, the 0xa0 example you can find in the EXAMPLES section of
the man page has been tailored after an actual session transcript made
on said Sun E450. (I'm not completely sure about the 0x70 example
anymore, this could be a hypothetical one.)
So could that be a backend driver issue, so various backend drivers
use different addressing formats? *shudder*
--
cheers, J"org .-.-. --... ...-- -.. . DL8DTL
http://www.sax.de/~joerg/ NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)
From owner-freebsd-stable@FreeBSD.ORG Fri Nov 21 16:48:40 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 6ABB71065670
for <freebsd-stable@FreeBSD.org>; Fri, 21 Nov 2008 16:48:40 +0000 (UTC)
(envelope-from gavin@FreeBSD.org)
Received: from mail-gw2.york.ac.uk (mail-gw2.york.ac.uk [144.32.128.247])
by mx1.freebsd.org (Postfix) with ESMTP id E18898FC13
for <freebsd-stable@FreeBSD.org>; Fri, 21 Nov 2008 16:48:39 +0000 (UTC)
(envelope-from gavin@FreeBSD.org)
Received: from mail-gw7.york.ac.uk (mail-gw7.york.ac.uk [144.32.129.30])
by mail-gw2.york.ac.uk (8.13.6/8.13.6) with ESMTP id mALGmXrJ021954;
Fri, 21 Nov 2008 16:48:33 GMT
Received: from buffy-128.york.ac.uk ([144.32.128.160] helo=buffy.york.ac.uk)
by mail-gw7.york.ac.uk with esmtps (TLSv1:AES256-SHA:256) (Exim 4.68)
(envelope-from <gavin@FreeBSD.org>)
id 1L3ZBJ-000378-Je; Fri, 21 Nov 2008 16:48:33 +0000
Received: from buffy.york.ac.uk (localhost [127.0.0.1])
by buffy.york.ac.uk (8.14.2/8.14.2) with ESMTP id mALGmXts042211;
Fri, 21 Nov 2008 16:48:33 GMT (envelope-from gavin@FreeBSD.org)
Received: (from ga9@localhost)
by buffy.york.ac.uk (8.14.2/8.14.2/Submit) id mALGmWAC042210;
Fri, 21 Nov 2008 16:48:32 GMT (envelope-from gavin@FreeBSD.org)
X-Authentication-Warning: buffy.york.ac.uk: ga9 set sender to
gavin@FreeBSD.org using -f
From: Gavin Atkinson <gavin@FreeBSD.org>
To: Joerg Wunsch <joerg_wunsch@uriah.heep.sax.de>
In-Reply-To: <20081121161629.GJ99866@uriah.heep.sax.de>
References: <4926BDE5.5020708@icyb.net.ua>
<20081121161629.GJ99866@uriah.heep.sax.de>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Date: Fri, 21 Nov 2008 16:48:32 +0000
Message-Id: <1227286112.40570.12.camel@buffy.york.ac.uk>
Mime-Version: 1.0
X-Mailer: Evolution 2.22.2 FreeBSD GNOME Team Port
X-York-MailScanner: Found to be clean
X-York-MailScanner-From: gavin@freebsd.org
Cc: FreeBSD Stable <freebsd-stable@FreeBSD.org>, Andriy Gapon <avg@icyb.net.ua>
Subject: Re: smbmsg(8): slave address confusion?
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Nov 2008 16:48:40 -0000
On Fri, 2008-11-21 at 17:16 +0100, Joerg Wunsch wrote:
> As Andriy Gapon wrote:
>
> > Now:
> >
> > (0x44 << 1) & 0xff == (0xc4 << 1) & 0xff = 0x88 (looks like RTC)
> > (0x50 << 1) & 0xff == (0xd0 << 1) & 0xff = 0xa0 (well known SPD addr)
> > (0x52 << 1) & 0xff == (0xd2 << 1) & 0xff = 0xa4 (well known SPD addr)
> > (0x80 << 1) & 0xff = 0x0 (mentioned above "global address")
> > (0x88 << 1) & 0xff == MIN_I2C_ADDR = 0x10 (something weird)
> >
> > I think that this demonstrates that FreeBSD smb driver expects slave
> > addresses in range 0x0-0x7f.
>
> Well, the machine I've been writing smbmsg(8) on has been a Sun E450 I
> don't have access to any longer, so I cannot post a live example
> output. However, I could swear the output did make sense on that
> machine, i. e. the typical 0xa0 etc. addresses were populated there.
> Basically, the 0xa0 example you can find in the EXAMPLES section of
> the man page has been tailored after an actual session transcript made
> on said Sun E450. (I'm not completely sure about the 0x70 example
> anymore, this could be a hypothetical one.)
>
> So could that be a backend driver issue, so various backend drivers
> use different addressing formats? *shudder*
I believe this is the case, yes. See for example, PR kern/100513. It
appears that some frivers treat the adfdress one way, and others treat
it the other.
Gavin
From owner-freebsd-stable@FreeBSD.ORG Fri Nov 21 17:14:15 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 2A0D61065675
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 17:14:15 +0000 (UTC)
(envelope-from sam@errno.com)
Received: from ebb.errno.com (ebb.errno.com [69.12.149.25])
by mx1.freebsd.org (Postfix) with ESMTP id DC1198FC14
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 17:14:14 +0000 (UTC)
(envelope-from sam@errno.com)
Received: from trouble.errno.com (trouble.errno.com [10.0.0.248])
(authenticated bits=0)
by ebb.errno.com (8.13.6/8.12.6) with ESMTP id mALH3xO0024437
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 09:03:59 -0800 (PST)
(envelope-from sam@errno.com)
Message-ID: <4926E9FE.1070302@errno.com>
Date: Fri, 21 Nov 2008 09:03:58 -0800
From: Sam Leffler <sam@errno.com>
User-Agent: Thunderbird 2.0.0.9 (X11/20071125)
MIME-Version: 1.0
To: freebsd-stable@freebsd.org
Content-Type: multipart/mixed; boundary="------------000101020904040304050309"
X-DCC-Misty-Metrics: ebb.errno.com; whitelist
Subject: [Fwd: Re: kern/123552: [ath] [panic] kernel panic during network
activity on ath0]
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Nov 2008 17:14:15 -0000
This is a multi-part message in MIME format.
--------------000101020904040304050309
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Folks having problems with ath on releng7 should try the attached patch.
Sam
--------------000101020904040304050309
Content-Type: text/plain;
name="net80211.patch"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename="net80211.patch"
Index: ieee80211_freebsd.h
===================================================================
RCS file: /usr/ncvs/src/sys/net80211/ieee80211_freebsd.h,v
retrieving revision 1.15.2.1
diff -u -r1.15.2.1 ieee80211_freebsd.h
--- ieee80211_freebsd.h 11 Nov 2007 17:44:35 -0000 1.15.2.1
+++ ieee80211_freebsd.h 21 Nov 2008 03:32:42 -0000
@@ -197,9 +197,10 @@
#define M_LINK0 M_PROTO1 /* WEP requested */
#define M_PWR_SAV M_PROTO4 /* bypass PS handling */
#define M_MORE_DATA M_PROTO5 /* more data frames to follow */
-#define M_FF 0x20000 /* fast frame */
-#define M_TXCB 0x40000 /* do tx complete callback */
-#define M_80211_TX (0x60000|M_PROTO1|M_WME_AC_MASK|M_PROTO4|M_PROTO5)
+#define M_FF M_PROTO6 /* fast frame */
+#define M_TXCB M_PROTO7 /* do tx complete callback */
+#define M_80211_TX \
+ (M_LINK0|M_WME_AC_MASK|M_PWR_SAV|M_MORE_DATA|M_FF|M_TXCB)
/* rx path usage */
#define M_AMPDU M_PROTO1 /* A-MPDU processing done */
--------------000101020904040304050309
Content-Type: message/rfc822;
name="Re: kern/123552: [ath] [panic] kernel panic during network
activity on ath0.eml"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename*0="Re: kern/123552: [ath] [panic] kernel panic during network
a"; filename*1="ctivity on ath0.eml"
Message-ID: <49261239.7060003@freebsd.org>
Date: Thu, 20 Nov 2008 17:43:21 -0800
From: Sam Leffler <sam@freebsd.org>
Organization: FreeBSD Project
User-Agent: Thunderbird 2.0.0.9 (X11/20071125)
MIME-Version: 1.0
To: Guy Coleman <gtc@mm.st>
Subject: Re: kern/123552: [ath] [panic] kernel panic during network activity
on ath0
References: <200811202220.mAKMK3h9042175@freefall.freebsd.org>
In-Reply-To: <200811202220.mAKMK3h9042175@freefall.freebsd.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Here is the reason in net80211/ieee80211_freebsd.h:
/* tx path usage */
#define M_LINK0 M_PROTO1 /* WEP requested */
#define M_PWR_SAV M_PROTO4 /* bypass PS handling */
#define M_MORE_DATA M_PROTO5 /* more data frames to
follow */
#define M_FF 0x20000 /* fast frame */
#define M_TXCB 0x40000 /* do tx complete
callback */
#define M_80211_TX (0x60000|M_PROTO1|M_WME_AC_MASK|M_PROTO4|M_PROTO5)
M_FF and M_TXCB overlay M_PROMISC and M_NOFREE. Please try reverting
your change and then set M_FF to M_PROTO6 and M_TXCB M_PROTO7.
Sam
Guy Coleman wrote:
> The following reply was made to PR kern/123552; it has been noted by GNATS.
>
> From: Guy Coleman <gtc@mm.st>
> To: bug-followup@FreeBSD.org
> Cc:
> Subject: Re: kern/123552: [ath] [panic] kernel panic during network activity
> on ath0
> Date: Thu, 20 Nov 2008 21:51:37 +0000
>
> I've found that partially reverting revs 1.181.2.2 and 1.181.2.4 of
> sys/net/bpf.c stops the panic from happening. I have no idea why.
>
> --- bpf.c.bak 2008-11-09 19:46:55.000000000 +0000
> +++ bpf.c 2008-11-16 22:37:10.000000000 +0000
> @@ -85,6 +85,8 @@
>
> #define PRINET 26 /* interruptible */
>
> +#define M_SKIP_BPF M_SKIP_FIREWALL
> +
> /*
> * bpf_iflist is a list of BPF interface structures, each
> corresponding to a
> * specific DLT. The same network interface might have several BPF
> interface
> @@ -653,7 +655,7 @@
> mc->m_pkthdr.rcvif = ifp;
> /* Set M_PROMISC for outgoing packets to be discarded. */
> if (d->bd_direction == BPF_D_INOUT)
> - m->m_flags |= M_PROMISC;
> + m->m_flags |= M_SKIP_BPF;
> } else
> mc = NULL;
>
> @@ -1358,9 +1360,8 @@
> int gottime;
> struct timeval tv;
>
> - /* Skip outgoing duplicate packets. */
> - if ((m->m_flags & M_PROMISC) != 0 && m->m_pkthdr.rcvif == NULL) {
> - m->m_flags &= ~M_PROMISC;
> + if (m->m_flags & M_SKIP_BPF) {
> + m->m_flags &= ~M_SKIP_BPF;
> return;
> }
>
> @@ -1413,9 +1414,8 @@
> int gottime;
> struct timeval tv;
>
> - /* Skip outgoing duplicate packets. */
> - if ((m->m_flags & M_PROMISC) != 0 && m->m_pkthdr.rcvif == NULL) {
> - m->m_flags &= ~M_PROMISC;
> + if (m->m_flags & M_SKIP_BPF) {
> + m->m_flags &= ~M_SKIP_BPF;
> return;
> }
>
>
>
>
>
--------------000101020904040304050309--
From owner-freebsd-stable@FreeBSD.ORG Fri Nov 21 17:15:05 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 3726C1065672;
Fri, 21 Nov 2008 17:15:05 +0000 (UTC) (envelope-from avg@icyb.net.ua)
Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140])
by mx1.freebsd.org (Postfix) with ESMTP id 222DE8FC19;
Fri, 21 Nov 2008 17:15:03 +0000 (UTC) (envelope-from avg@icyb.net.ua)
Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua
[212.40.38.101])
by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id TAA19547;
Fri, 21 Nov 2008 19:15:01 +0200 (EET) (envelope-from avg@icyb.net.ua)
Message-ID: <4926EC94.8060609@icyb.net.ua>
Date: Fri, 21 Nov 2008 19:15:00 +0200
From: Andriy Gapon <avg@icyb.net.ua>
User-Agent: Thunderbird 2.0.0.17 (X11/20081106)
MIME-Version: 1.0
To: Gavin Atkinson <gavin@FreeBSD.org>
References: <4926BDE5.5020708@icyb.net.ua>
<20081121161629.GJ99866@uriah.heep.sax.de>
<1227286112.40570.12.camel@buffy.york.ac.uk>
In-Reply-To: <1227286112.40570.12.camel@buffy.york.ac.uk>
Content-Type: text/plain; charset=KOI8-U
Content-Transfer-Encoding: 7bit
Cc: Joerg Wunsch <joerg_wunsch@uriah.heep.sax.de>,
FreeBSD Stable <freebsd-stable@FreeBSD.org>
Subject: Re: smbmsg(8): slave address confusion?
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Nov 2008 17:15:05 -0000
on 21/11/2008 18:48 Gavin Atkinson said the following:
> On Fri, 2008-11-21 at 17:16 +0100, Joerg Wunsch wrote:
>> As Andriy Gapon wrote:
>>
>>> Now:
>>>
>>> (0x44 << 1) & 0xff == (0xc4 << 1) & 0xff = 0x88 (looks like RTC)
>>> (0x50 << 1) & 0xff == (0xd0 << 1) & 0xff = 0xa0 (well known SPD addr)
>>> (0x52 << 1) & 0xff == (0xd2 << 1) & 0xff = 0xa4 (well known SPD addr)
>>> (0x80 << 1) & 0xff = 0x0 (mentioned above "global address")
>>> (0x88 << 1) & 0xff == MIN_I2C_ADDR = 0x10 (something weird)
>>>
>>> I think that this demonstrates that FreeBSD smb driver expects slave
>>> addresses in range 0x0-0x7f.
>> Well, the machine I've been writing smbmsg(8) on has been a Sun E450 I
>> don't have access to any longer, so I cannot post a live example
>> output. However, I could swear the output did make sense on that
>> machine, i. e. the typical 0xa0 etc. addresses were populated there.
>> Basically, the 0xa0 example you can find in the EXAMPLES section of
>> the man page has been tailored after an actual session transcript made
>> on said Sun E450. (I'm not completely sure about the 0x70 example
>> anymore, this could be a hypothetical one.)
>>
>> So could that be a backend driver issue, so various backend drivers
>> use different addressing formats? *shudder*
>
> I believe this is the case, yes. See for example, PR kern/100513. It
> appears that some frivers treat the adfdress one way, and others treat
> it the other.
Darn it! Thank you!
I also started to have doubts and almost came to conclusion that this is
6.X vs 7.X issue, because on my 6.X machine everything worked
reasonably. But I now see that my 6.X machine has nfsmb and 7.X machines
have ichsmb.
PR link for convenience:
http://www.freebsd.org/cgi/query-pr.cgi?pr=100513
We have to settle to one addressing scheme or the other.
--
Andriy Gapon
From owner-freebsd-stable@FreeBSD.ORG Fri Nov 21 17:47:42 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id D74601065670;
Fri, 21 Nov 2008 17:47:42 +0000 (UTC)
(envelope-from uspoerlein@gmail.com)
Received: from acme.spoerlein.net (cl-43.dus-01.de.sixxs.net
[IPv6:2a01:198:200:2a::2])
by mx1.freebsd.org (Postfix) with ESMTP id 7B2D88FC1D;
Fri, 21 Nov 2008 17:47:42 +0000 (UTC)
(envelope-from uspoerlein@gmail.com)
Received: from roadrunner.spoerlein.net (e180143034.adsl.alicedsl.de
[85.180.143.34])
by acme.spoerlein.net (8.14.2/8.14.2) with ESMTP id mALHldJp010938
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK);
Fri, 21 Nov 2008 18:47:40 +0100 (CET)
(envelope-from uspoerlein@gmail.com)
Received: from roadrunner.spoerlein.net (localhost [127.0.0.1])
by roadrunner.spoerlein.net (8.14.3/8.14.3) with ESMTP id
mALHdYO4002856
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
Fri, 21 Nov 2008 18:39:34 +0100 (CET)
(envelope-from uspoerlein@gmail.com)
Received: (from uqs@localhost)
by roadrunner.spoerlein.net (8.14.3/8.14.3/Submit) id mALHdX5L002855;
Fri, 21 Nov 2008 18:39:33 +0100 (CET)
(envelope-from uspoerlein@gmail.com)
Date: Fri, 21 Nov 2008 18:39:33 +0100
From: Ulrich Spoerlein <uspoerlein@gmail.com>
To: Michael Proto <mike@jellydonut.org>
Message-ID: <20081121173933.GA2426@roadrunner.spoerlein.net>
Mail-Followup-To: Michael Proto <mike@jellydonut.org>, stable@freebsd.org,
Max Laier <mlaier@freebsd.org>
References: <20081120211148.GA5178@roadrunner.spoerlein.net>
<1de79840811201456pc2ceb9atb3532430fb605160@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1de79840811201456pc2ceb9atb3532430fb605160@mail.gmail.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: stable@freebsd.org, Max Laier <mlaier@freebsd.org>
Subject: Re: LORs in RELENG_7
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Nov 2008 17:47:42 -0000
On Thu, 20.11.2008 at 17:56:07 -0500, Michael Proto wrote:
> On Thu, Nov 20, 2008 at 4:11 PM, Ulrich Spoerlein <uspoerlein@gmail.com>wrote:
> > Hi,
> >
> > I'm running my RELENG_7 kernel with WITNESS and there's always a LOR
> > when pf(4) is enabled:
> >
> > lock order reversal:
> > 1st 0xc09ca828 ifnet (ifnet) @ /usr/src/sys/net/if.c:849
> > 2nd 0xc45d604c pf task mtx (pf task mtx) @
> > /usr/src/sys/modules/pf/../../contrib/pf/net/pf_if.c:916
> > KDB: stack backtrace:
> > db_trace_self_wrapper(c08df797,fb671764,c0630e8e,c08e1c96,c45d604c,...) at
> > db_trace_self_wrapper+0x26
> > kdb_backtrace(c08e1c96,c45d604c,c45d3b1c,c45d3b1c,c45d379e,...) at
> > kdb_backtrace+0x29
> > witness_checkorder(c45d604c,9,c45d379e,394,c08e9058,...) at
> > witness_checkorder+0x6de
> > _mtx_lock_flags(c45d604c,0,c45d379e,394,fb6717dc,...) at
> > _mtx_lock_flags+0xbc
> > pfi_attach_group_event(0,c4450000,c08e9058,374,c44a920c,...) at
> > pfi_attach_group_event+0x4e
> > if_addgroup(c441c000,c08f70d6,4,0,0,...) at if_addgroup+0x2c7
> > if_clone_createif(0,0,c08e9563,87,0,...) at if_clone_createif+0x81
> > if_clone_create(fb671943,4,0,44,180,...) at if_clone_create+0x8c
> > tunclone(0,c461e400,fb671943,4,fb67195c,...) at tunclone+0x17a
> > devfs_lookup(fb6719d0,fb6719d0,fb671b7c,c418de04,2,...) at
> > devfs_lookup+0x50e
> > VOP_LOOKUP_APV(c0928f40,fb6719d0,c412f230,c08e77ef,2a9,...) at
> > VOP_LOOKUP_APV+0xa5
> > lookup(fb671b7c,c08e77ef,c6,bf,c461e92c,...) at lookup+0x58e
> > namei(fb671b7c,c412f230,fb671a74,246,c0983774,...) at namei+0x34b
> > vn_open_cred(fb671b7c,fb671c78,ce8,c461e400,c4460558,...) at
> > vn_open_cred+0x2c9
> > vn_open(fb671b7c,fb671c78,ce8,c4460558,c05e807d,...) at vn_open+0x33
> > kern_open(c412f230,80a0f18,0,3,808ecfa,...) at kern_open+0xe7
> > open(c412f230,fb671cfc,c,c08e28c3,c092c0b8,...) at open+0x30
> > syscall(fb671d38) at syscall+0x2b3
> > Xint0x80_syscall() at Xint0x80_syscall+0x20
> > --- syscall (5, FreeBSD ELF32, open), eip = 0x2835a65b, esp = 0xbfbfeafc,
> > ebp = 0xbfbfeb38 ---
> >
> >
> Are you using user or group rules in your pf.conf? IIRC there is still a
> known LOR in the socket layer with rules using the user or group filters.
No, I'm aware of the problems with pf(4) and user/group rules. This LOR
is in combination with rules on tun(4) devices, as you can see from the
backtrace. I wonder what tunclone() is doing in there, though.
Cheers,
Ulrich Spoerlein
--
It is better to remain silent and be thought a fool,
than to speak, and remove all doubt.
From owner-freebsd-stable@FreeBSD.ORG Fri Nov 21 17:47:44 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 1C1401065672;
Fri, 21 Nov 2008 17:47:44 +0000 (UTC)
(envelope-from uspoerlein@gmail.com)
Received: from acme.spoerlein.net (cl-43.dus-01.de.sixxs.net
[IPv6:2a01:198:200:2a::2])
by mx1.freebsd.org (Postfix) with ESMTP id 6C3658FC16;
Fri, 21 Nov 2008 17:47:43 +0000 (UTC)
(envelope-from uspoerlein@gmail.com)
Received: from roadrunner.spoerlein.net (e180143034.adsl.alicedsl.de
[85.180.143.34])
by acme.spoerlein.net (8.14.2/8.14.2) with ESMTP id mALHldJr010938
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK);
Fri, 21 Nov 2008 18:47:41 +0100 (CET)
(envelope-from uspoerlein@gmail.com)
Received: from roadrunner.spoerlein.net (localhost [127.0.0.1])
by roadrunner.spoerlein.net (8.14.3/8.14.3) with ESMTP id
mALHlT3V003031
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
Fri, 21 Nov 2008 18:47:29 +0100 (CET)
(envelope-from uspoerlein@gmail.com)
Received: (from uqs@localhost)
by roadrunner.spoerlein.net (8.14.3/8.14.3/Submit) id mALHlSlo003030;
Fri, 21 Nov 2008 18:47:28 +0100 (CET)
(envelope-from uspoerlein@gmail.com)
Date: Fri, 21 Nov 2008 18:47:28 +0100
From: Ulrich Spoerlein <uspoerlein@gmail.com>
To: Sean Bruno <sbruno@miralink.com>
Message-ID: <20081121174728.GA1474@roadrunner.spoerlein.net>
Mail-Followup-To: Sean Bruno <sbruno@miralink.com>, stable@freebsd.org,
Hidetoshi Shimokawa <simokawa@freebsd.org>,
Scott Long <scottl@FreeBSD.org>
References: <20081120211148.GA5178@roadrunner.spoerlein.net>
<4925F11C.4080508@miralink.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4925F11C.4080508@miralink.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: Hidetoshi Shimokawa <simokawa@freebsd.org>, stable@freebsd.org,
Scott Long <scottl@freebsd.org>
Subject: Re: LORs in RELENG_7
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Nov 2008 17:47:44 -0000
On Thu, 20.11.2008 at 15:22:04 -0800, Sean Bruno wrote:
> > And there are these LORs when I shut down my external firewire attached
> > disk:
> >
> > fwohci0: BUS reset
> > fwohci0: node_id=0xc800ffc1, gen=2, CYCLEMASTER mode
> > firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 (me)
> > firewire0: bus manager 1 (me)
> > uma_zalloc_arg: zone "16" with the following non-sleepable locks held:
> > exclusive sleep mutex sbp r = 0 (0xc402f7ac) locked @ /usr/src/sys/dev/firewire/sbp.c:2203
> > KDB: stack backtrace:
> > db_trace_self_wrapper(c08df797,f93a931c,c0630007,c08dfb5a,f93a9330,...) at db_trace_self_wrapper+0x26
> > kdb_backtrace(c08dfb5a,f93a9330,4,1,0,...) at kdb_backtrace+0x29
> > witness_warn(5,0,c0901ae5,c08c59ce,86,...) at witness_warn+0x1d7
> > uma_zalloc_arg(c1472960,0,2,2,f93a93e0,...) at uma_zalloc_arg+0x34
> > malloc(b,c09308c0,2,c05be59a,c08d7a2c,...) at malloc+0xd2
> > notify(c4150a00,4,c08d7856,34f,c05be4ea,...) at notify+0x49
> > destroy_devl(f93a9410,c046a6ce,c4150a00,0,c3f18370,...) at destroy_devl+0x236
> > destroy_dev(c4150a00,0,c3f18370,c3f69000,f93a9690,...) at destroy_dev+0x10
> > passcleanup(c3f69000,c08b50c7,0,0,0,...) at passcleanup+0x2e
> > camperiphfree(c3f69000,0,f93a96b0,c04568dd,c3f69000,...) at camperiphfree+0xbb
> > cam_periph_invalidate(c3f69000,c0983774,f93a96e4,c046a5ea,c3f69000,...) at cam_periph_invalidate+0x3e
> > cam_periph_async(c3f69000,100,c418a260,0,f93a96e0,...) at cam_periph_async+0x2d
> > passasync(c3f69000,100,c418a260,0,c42f8c00,...) at passasync+0xca
> > xpt_async_bcast(0,4,c08b53c5,11a5,c404d280,...) at xpt_async_bcast+0x32
> > xpt_async(100,c418a260,0,89b,0,...) at xpt_async+0x194
> > sbp_cam_detach_sdev(c402f45c,0,c402f418,0,f93a982c,...) at sbp_cam_detach_sdev+0xa4
> > sbp_cam_detach_target(c14729a8,c14729a8,c08250c6,c7373b40,10,...) at sbp_cam_detach_target+0x5b
> > sbp_post_explore(c402f400,f93a9ce8,f93a9ce4,675,0,...) at sbp_post_explore+0xa2
> > fw_bus_probe_thread(c404f000,f93a9d38,c08d8d0f,31c,c402b570,...) at fw_bus_probe_thread+0x69b
> > fork_exit(c0513500,c404f000,f93a9d38) at fork_exit+0xb8
> > fork_trampoline() at fork_trampoline+0x8
> > --- trap 0, eip = 0, esp = 0xf93a9d70, ebp = 0 ---
> > (da0:sbp0:0:0:0): lost device
> > (da0:sbp0:0:0:0): removing device entry
> > cam_periph_alloc: attempt to re-allocate valid device pass1 rejected
> > passasync: Unable to attach new device due to status 0x6: CCB request was invalid
> > cam_periph_alloc: attempt to re-allocate valid device da1 rejected
> > daasync: Unable to attach to new device due to status 0x6
> > fwohci0: BUS reset
> > fwohci0: node_id=0xc800ffc0, gen=3, CYCLEMASTER mode
> > firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me)
> > firewire0: bus manager 0 (me)
> > uma_zalloc_arg: zone "16" with the following non-sleepable locks held:
> > exclusive sleep mutex sbp r = 0 (0xc402f7ac) locked @ /usr/src/sys/dev/firewire/sbp.c:2203
> > KDB: stack backtrace:
> > db_trace_self_wrapper(c08df797,f93a931c,c0630007,c08dfb5a,f93a9330,...) at db_trace_self_wrapper+0x26
> > kdb_backtrace(c08dfb5a,f93a9330,4,1,0,...) at kdb_backtrace+0x29
> > witness_warn(5,0,c0901ae5,c08c59ce,86,...) at witness_warn+0x1d7
> > uma_zalloc_arg(c1472960,0,2,2,f93a93e0,...) at uma_zalloc_arg+0x34
> > malloc(b,c09308c0,2,c05be59a,c08d7a2c,...) at malloc+0xd2
> > notify(c4150d00,4,c08d7856,34f,c05be4ea,...) at notify+0x49
> > destroy_devl(f93a9410,c046a6ce,c4150d00,0,c3f18370,...) at destroy_devl+0x236
> > destroy_dev(c4150d00,0,c3f18370,c42c6700,f93a9690,...) at destroy_dev+0x10
> > passcleanup(c42c6700,c08b50c7,c09eff00,4,c08db41b,...) at passcleanup+0x2e
> > camperiphfree(c42c6700,0,f93a96b0,c04568dd,c42c6700,...) at camperiphfree+0xbb
> > cam_periph_invalidate(c42c6700,c0983774,f93a96e4,c046a5ea,c42c6700,...) at cam_periph_invalidate+0x3e
> > cam_periph_async(c42c6700,100,c418a250,0,f93a96e0,...) at cam_periph_async+0x2d
> > passasync(c42c6700,100,c418a250,0,c42f8a00,...) at passasync+0xca
> > xpt_async_bcast(0,4,c08b53c5,11a5,c404d280,...) at xpt_async_bcast+0x32
> > xpt_async(100,c418a250,0,89b,0,...) at xpt_async+0x194
> > sbp_cam_detach_sdev(c402f4c8,0,c402f484,1,f93a982c,...) at sbp_cam_detach_sdev+0xa4
> > sbp_cam_detach_target(c14729a8,c14729a8,c08250c6,c44263f0,10,...) at sbp_cam_detach_target+0x5b
> > sbp_post_explore(c402f400,f93a9ce8,f93a9ce4,675,0,...) at sbp_post_explore+0xa2
> > fw_bus_probe_thread(c404f000,f93a9d38,c08d8d0f,31c,c402b570,...) at fw_bus_probe_thread+0x69b
> > fork_exit(c0513500,c404f000,f93a9d38) at fork_exit+0xb8
> > fork_trampoline() at fork_trampoline+0x8
> > --- trap 0, eip = 0, esp = 0xf93a9d70, ebp = 0 ---
> > (da1:sbp0:0:1:0): lost device
> > (da1:sbp0:0:1:0): removing device entry
> >
> > I reckon these problems should appear in -STABLE ...
"shouldn't"
> You are able to make this happen simply by powering off your Firewire
> Hard Drive? What about pulling the cable out?
Pulling the cable is exactly the same as removing power to the device,
so I dont see how this should make a difference.
It is also very clear, that this code is violating locking restraints
if xpt_async() is calling into uma (as it obviously does).
sys/dev/firewire/sbp.c:
2202 if (sdev->path) {
2203 SBP_LOCK(sdev->target->sbp);
2204 xpt_release_devq(sdev->path,
2205 sdev->freeze, TRUE);
2206 sdev->freeze = 0;
2207 xpt_async(AC_LOST_DEVICE, sdev->path, NULL);
2208 xpt_free_path(sdev->path);
2209 sdev->path = NULL;
2210 SBP_UNLOCK(sdev->target->sbp);
2211 }
Cheers,
Ulrich Spoerlein
--
It is better to remain silent and be thought a fool,
than to speak, and remove all doubt.
From owner-freebsd-stable@FreeBSD.ORG Fri Nov 21 17:51:45 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 1A2A01065670;
Fri, 21 Nov 2008 17:51:45 +0000 (UTC)
(envelope-from peter@simons-rock.edu)
Received: from hedwig.simons-rock.edu (hedwig.simons-rock.edu [208.81.88.14])
by mx1.freebsd.org (Postfix) with ESMTP id D054B8FC0C;
Fri, 21 Nov 2008 17:51:44 +0000 (UTC)
(envelope-from peter@simons-rock.edu)
Received: from cesium.hyperfine.info (c2.8d.5646.static.theplanet.com
[70.86.141.194])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(No client certificate requested)
by hedwig.simons-rock.edu (Postfix) with ESMTP id 18DEFECFF8;
Fri, 21 Nov 2008 12:23:20 -0500 (EST)
Date: Fri, 21 Nov 2008 12:20:46 -0500
From: "Peter C. Lai" <peter@simons-rock.edu>
To: freebsd-stable@FreeBSD.org, freebsd-scsi@freebsd.org
Message-ID: <20081121172028.GQ92091@cesium.hyperfine.info>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.17 (2007-11-01)
Cc:
Subject: ahc(4) on aic7899 wedges with a Tandberg LTO-2 sa drive
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Nov 2008 17:51:45 -0000
I've got a Tandberg TS 400 LTO-2 drive in a Dell PE1800 which is
wedging ahc(4) after writing about 5 GB of data.
I've attached dmesg.boot.
uname -a:
FreeBSD phoenix.simons-rock.edu 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #0: Fri Oct 17 23:17:38 EDT 2008 root@phoenix.simons-rock.edu:/usr/obj/usr/src/sys/PHOENIXPCL i386
I put in a tape, and mt -f /dev/sa0 status gives the following kernel
message:
Nov 21 12:06:28 phoenix kernel: (ahc0:A:6:0): Sending PPR bus_width 1, period 9, offset 7e, ppr_options 2
Nov 21 12:06:28 phoenix kernel: (ahc0:A:6:0): Received PPR width 1, period 9, offset 7e,options 2
Nov 21 12:06:28 phoenix kernel: Filtered to width 1, period 9, offset 7e, options 2
Nov 21 12:06:28 phoenix kernel: (sa0:ahc0:0:6:0): error 6
Nov 21 12:06:28 phoenix kernel: (sa0:ahc0:0:6:0): Unretryable Error
Nov 21 12:06:28 phoenix kernel: (ahc0:A:6:0): Sending PPR bus_width 1, period 9, offset 7e, ppr_options 2
Nov 21 12:06:28 phoenix kernel: (ahc0:A:6:0): Received PPR width 1, period 9, offset 7e,options 2
Nov 21 12:06:28 phoenix kernel: Filtered to width 1, period 9, offset 7e, options 2
Nov 21 12:06:28 phoenix kernel: (sa0:ahc0:0:6:0): error 6
Nov 21 12:06:28 phoenix kernel: (sa0:ahc0:0:6:0): Unretryable Error
Nov 21 12:06:28 phoenix kernel: (ahc0:A:6:0): Sending PPR bus_width 1, period 9, offset 7e, ppr_options 2
Nov 21 12:06:28 phoenix kernel: (ahc0:A:6:0): Received PPR width 1, period 9, offset 7e,options 2
Nov 21 12:06:28 phoenix kernel:
Nov 21 12:06:28 phoenix kernel: Filtered to width 1, period 9, offset 7e, options 2
Nov 21 12:06:28 phoenix kernel: (sa0:ahc0:0:6:0): error 6
Nov 21 12:06:28 phoenix kernel: (sa0:ahc0:0:6:0): Unretryable Error
Nov 21 12:07:30 phoenix kernel: (ahc0:A:6:0): Sending PPR bus_width 1, period 9, offset 7e, ppr_options 2
Nov 21 12:07:30 phoenix kernel: (ahc0:A:6:0): Received PPR width 1, period 9, offset 7e,options 2
Nov 21 12:07:30 phoenix kernel: Filtered to width 1, period 9, offset 7e, options 2
Nov 21 12:07:30 phoenix kernel: (sa0:ahc0:0:6:0): Retrying Command
but it returns ok at the end:
Mode Density Blocksize bpi Compression
Current: 0x42 variable 0 0x1
---------available modes---------
0: 0x42 variable 0 0x1
1: 0x42 variable 0 0x1
2: 0x42 variable 0 0x1
3: 0x42 variable 0 0x1
---------------------------------
Current Driver State: at rest.
---------------------------------
File Number: 0 Record Number: 0 Residual Count 0
I am using star bs=32k -no-fifo to write to the tape. ahc(4) crashes
regardless of setting the blocksize on the hardware (to 32k) or not:
Nov 21 08:58:15 phoenix kernel: ahc0: Recovery Initiated
Nov 21 08:58:15 phoenix kernel: >>>>>>>>>>>>>>>>>> Dump Card State Begins <<<<<<<<<<<<<<<<<
Nov 21 08:58:15 phoenix kernel: ahc0: Dumping Card State while idle, at SEQADDR 0x8
Nov 21 08:58:15 phoenix kernel: Card was paused
Nov 21 08:58:15 phoenix kernel: ACCUM = 0x4, SINDEX = 0x67, DINDEX = 0x27, ARG_2 = 0x3b
Nov 21 08:58:15 phoenix kernel: HCNT = 0x0 SCBPTR = 0x0
Nov 21 08:58:15 phoenix kernel: SCSIPHASE[0x0] SCSISIGI[0x0] ERROR[0x0] SCSIBUSL[0x0]
Nov 21 08:58:15 phoenix kernel: LASTPHASE[0x1]:(P_BUSFREE) SCSISEQ[0x12]:(ENAUTOATNP|ENRSELI)
Nov 21 08:58:15 phoenix kernel: SBLKCTL[0xa]:(SELWIDE|SELBUSB) SCSIRATE[0x0] SEQCTL[0x10]:(FASTMODE)
Nov 21 08:58:15 phoenix kernel: SEQ_FLAGS[0xc0]:(NO_CDB_SENT|NOT_IDENTIFIED) SSTAT0[0x0]
Nov 21 08:58:15 phoenix kernel: SSTAT1[0x0] SSTAT2[0x0] SSTAT3[0x0] SIMODE0[0x8]:(ENSWRAP)
Nov 21 08:58:15 phoenix kernel: SIMODE1[0xa4]:(ENSCSIPERR|ENSCSIRST|ENSELTIMO) SXFRCTL0[0x80]:(DFON)
Nov 21 08:58:15 phoenix kernel: DFCNTRL[0x0] DFSTATUS[0x89]:(FIFOEMP|HDONE|PRELOAD_AVAIL)
Nov 21 08:58:15 phoenix kernel: STACK: 0x0 0x164 0x179 0x3
Nov 21 08:58:15 phoenix kernel: SCB count = 254
Nov 21 08:58:15 phoenix kernel: Kernel NEXTQSCB = 247
Nov 21 08:58:15 phoenix kernel: Card NEXTQSCB = 247
Nov 21 08:58:15 phoenix kernel: QINFIFO entries:
Nov 21 08:58:15 phoenix kernel: Waiting Queue entries:
Nov 21 08:58:15 phoenix kernel: Disconnected Queue entries: 0:238
Nov 21 08:58:15 phoenix kernel: QOUTFIFO entries:
Nov 21 08:58:15 phoenix kernel: Sequencer Free SCB List: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
Nov 21 08:58:15 phoenix kernel: Sequencer SCB Info:
Nov 21 08:58:15 phoenix kernel: 0 SCB_CONTROL[0x44]:(DISCONNECTED|DISCENB) SCB_SCSIID[0x67]
Nov 21 08:58:15 phoenix kernel: SCB_LUN[0x0] SCB_TAG[0xee]
Nov 21 08:58:15 phoenix kernel: 1 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID)
Nov 21 08:58:15 phoenix kernel: SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff]
Nov 21 08:58:15 phoenix kernel: 2 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID)
Nov 21 08:58:15 phoenix kernel: SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff]
Nov 21 08:58:15 phoenix kernel: 3 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID)
Nov 21 08:58:15 phoenix kernel: SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff]
Nov 21 08:58:15 phoenix kernel: 4 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID)
...
Nov 21 08:58:15 phoenix kernel: 31 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID)
Nov 21 08:58:15 phoenix kernel: SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff]
Nov 21 08:58:15 phoenix kernel: Pending list:
Nov 21 08:58:15 phoenix kernel: 238 SCB_CONTROL[0x40]:(DISCENB) SCB_SCSIID[0x67] SCB_LUN[0x0]
Nov 21 08:58:15 phoenix kernel: Kernel Free SCB list: 239 240 241 242 243 244 245 246 248 249 250 251 252 253 237 236 235 234 233 232 231 230 229 228 227 226 225 224 223 222 221 220 219 218 217 216 215 214 213 212 211 210 209 208 207 206 205 204 203 202 201 200 199 198 197 196 195 194 193 192 191 190 189 188 187 186 185 184 183 182 181 180 179 178 177 176 175 174 173 172 171 170 169 168 167 166 165 164 163 162 161 160 159 158 157 156 155 154 153 152 151 150 149 148 147 146 145 144 143 142 141 140 139 138 137 136 135 134 133 132 131 130 129 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Nov 21 08:58:15 phoenix kernel: Untagged Q(6): 238
Nov 21 08:58:15 phoenix kernel:
Nov 21 08:58:15 phoenix kernel: <<<<<<<<<<<<<<<<< Dump Card State Ends >>>>>>>>>>>>>>>>>>
Nov 21 08:58:15 phoenix kernel: (sa0:ahc0:0:6:0): SCB 0xee - timed out
Nov 21 08:58:15 phoenix kernel: sg[0] - Addr 0x21706000 : Length 4096
Nov 21 08:58:15 phoenix kernel: sg[1] - Addr 0x217aa000 : Length 4096
Nov 21 08:58:15 phoenix kernel: sg[2] - Addr 0x2183b000 : Length 4096
...
Nov 21 08:58:15 phoenix kernel: sg[7] - Addr 0x221f6000 : Length 4096
Nov 21 08:58:15 phoenix kernel: (sa0:ahc0:0:6:0): Queuing a BDR SCB
Nov 21 08:58:15 phoenix kernel: Infinite interrupt loop, INTSTAT = 0ahc0: Timedout SCBs already complete. Interrupts may not be functioning.
Nov 21 08:58:17 phoenix kernel: Infinite interrupt loop, INTSTAT = 0ahc0: Recovery Initiated
Nov 21 08:58:17 phoenix kernel: >>>>>>>>>>>>>>>>>> Dump Card State Begins <<<<<<<<<<<<<<<<<
Nov 21 08:58:17 phoenix kernel: ahc0: Dumping Card State while idle, at SEQADDR 0x18
Nov 21 08:58:17 phoenix kernel: Card was paused
...
Nov 21 08:58:17 phoenix kernel: (sa0:ahc0:0:6:0): no longer in timeout, status = 24b
Nov 21 08:58:17 phoenix kernel: ahc0: target 6 using 8bit transfers
Nov 21 08:58:17 phoenix kernel: ahc0: target 6 using asynchronous transfers
Nov 21 08:58:17 phoenix kernel: ahc0: Issued Channel A Bus Reset. 1 SCBs aborted
Nov 21 08:58:17 phoenix kernel: (sa0:ahc0:0:6:0): Command timed out
Nov 21 08:58:17 phoenix kernel: (sa0:ahc0:0:6:0): error 5
Nov 21 08:58:17 phoenix kernel: (sa0:ahc0:0:6:0): Retries Exausted
Nov 21 08:58:17 phoenix kernel: ahc0: Timedout SCBs already complete. Interrupts may not be functioning.
Nov 21 08:58:17 phoenix kernel: (ahc0:A:6:0): Sending PPR bus_width 1, period 9, offset 7e, ppr_options 2
Nov 21 08:58:17 phoenix kernel: (ahc0:A:6:0): Received PPR width 1, period 9, offset 7e,options 2
Nov 21 08:58:17 phoenix kernel: Filtered to width 1, period 9, offset 7e, options 2
Nov 21 08:58:17 phoenix kernel: ahc0: target 6 using 16bit transfers
Nov 21 08:58:17 phoenix kernel: ahc0: target 6 synchronous at 80.0MHz DT, offset = 0x7e
Nov 21 09:02:17 phoenix kernel: ahc0: Recovery Initiated
...
until shutdown.
A shutdown -r will still leave the controller wedged until a fullblow
powercycle is done without the tape in the drive.
Reading from tapes work just fine though. Also this identical hardware
work just fine under Linux.
Please help. Thanks!
--
===========================================================
Peter C. Lai | Bard College at Simon's Rock
Systems Administrator | 84 Alford Rd.
Information Technology Svcs. | Gt. Barrington, MA 01230 USA
peter AT simons-rock.edu | (413) 528-7428
===========================================================
From owner-freebsd-stable@FreeBSD.ORG Fri Nov 21 19:16:48 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 52F29106564A
for <stable@freebsd.org>; Fri, 21 Nov 2008 19:16:48 +0000 (UTC)
(envelope-from max@love2party.net)
Received: from moutng.kundenserver.de (moutng.kundenserver.de
[212.227.126.171])
by mx1.freebsd.org (Postfix) with ESMTP id DDE818FC12
for <stable@freebsd.org>; Fri, 21 Nov 2008 19:16:47 +0000 (UTC)
(envelope-from max@love2party.net)
Received: from vampire.homelinux.org (dslb-088-066-059-171.pools.arcor-ip.net
[88.66.59.171])
by mrelayeu.kundenserver.de (node=mrelayeu8) with ESMTP (Nemesis)
id 0ML31I-1L3bUk14kv-0007qt; Fri, 21 Nov 2008 20:16:46 +0100
Received: (qmail 3492 invoked from network); 21 Nov 2008 19:16:45 -0000
Received: from fbsd8.laiers.local (192.168.4.151)
by ns1.laiers.local with SMTP; 21 Nov 2008 19:16:45 -0000
From: Max Laier <max@love2party.net>
Organization: FreeBSD
To: Ulrich Spoerlein <uspoerlein@gmail.com>
Date: Fri, 21 Nov 2008 20:16:44 +0100
User-Agent: KMail/1.10.1 (FreeBSD/8.0-CURRENT; KDE/4.1.1; i386; ; )
References: <20081120211148.GA5178@roadrunner.spoerlein.net>
<1de79840811201456pc2ceb9atb3532430fb605160@mail.gmail.com>
<20081121173933.GA2426@roadrunner.spoerlein.net>
In-Reply-To: <20081121173933.GA2426@roadrunner.spoerlein.net>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200811212016.45474.max@love2party.net>
X-Provags-ID: V01U2FsdGVkX194ebi3sJncFb13v23rVyiu+dDVfluz5Sovjim
uxdZCqRLhC1pSSqKofw+xTBPB06PKgewtQY5ClOtaOYfTvxhja
GK49QBU6gHXEOe+mRtV0A==
Cc: Michael Proto <mike@jellydonut.org>, stable@freebsd.org,
Max Laier <mlaier@freebsd.org>
Subject: Re: LORs in RELENG_7
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Nov 2008 19:16:48 -0000
On Friday 21 November 2008 18:39:33 Ulrich Spoerlein wrote:
> On Thu, 20.11.2008 at 17:56:07 -0500, Michael Proto wrote:
> > On Thu, Nov 20, 2008 at 4:11 PM, Ulrich Spoerlein
<uspoerlein@gmail.com>wrote:
> > > Hi,
> > >
> > > I'm running my RELENG_7 kernel with WITNESS and there's always a LOR
> > > when pf(4) is enabled:
> > >
> > > lock order reversal:
> > > 1st 0xc09ca828 ifnet (ifnet) @ /usr/src/sys/net/if.c:849
> > > 2nd 0xc45d604c pf task mtx (pf task mtx) @
> > > /usr/src/sys/modules/pf/../../contrib/pf/net/pf_if.c:916
> > > KDB: stack backtrace:
> > > db_trace_self_wrapper(c08df797,fb671764,c0630e8e,c08e1c96,c45d604c,...)
> > > at db_trace_self_wrapper+0x26
> > > kdb_backtrace(c08e1c96,c45d604c,c45d3b1c,c45d3b1c,c45d379e,...) at
> > > kdb_backtrace+0x29
> > > witness_checkorder(c45d604c,9,c45d379e,394,c08e9058,...) at
> > > witness_checkorder+0x6de
> > > _mtx_lock_flags(c45d604c,0,c45d379e,394,fb6717dc,...) at
> > > _mtx_lock_flags+0xbc
> > > pfi_attach_group_event(0,c4450000,c08e9058,374,c44a920c,...) at
> > > pfi_attach_group_event+0x4e
> > > if_addgroup(c441c000,c08f70d6,4,0,0,...) at if_addgroup+0x2c7
> > > if_clone_createif(0,0,c08e9563,87,0,...) at if_clone_createif+0x81
> > > if_clone_create(fb671943,4,0,44,180,...) at if_clone_create+0x8c
> > > tunclone(0,c461e400,fb671943,4,fb67195c,...) at tunclone+0x17a
> > > devfs_lookup(fb6719d0,fb6719d0,fb671b7c,c418de04,2,...) at
> > > devfs_lookup+0x50e
> > > VOP_LOOKUP_APV(c0928f40,fb6719d0,c412f230,c08e77ef,2a9,...) at
> > > VOP_LOOKUP_APV+0xa5
> > > lookup(fb671b7c,c08e77ef,c6,bf,c461e92c,...) at lookup+0x58e
> > > namei(fb671b7c,c412f230,fb671a74,246,c0983774,...) at namei+0x34b
> > > vn_open_cred(fb671b7c,fb671c78,ce8,c461e400,c4460558,...) at
> > > vn_open_cred+0x2c9
> > > vn_open(fb671b7c,fb671c78,ce8,c4460558,c05e807d,...) at vn_open+0x33
> > > kern_open(c412f230,80a0f18,0,3,808ecfa,...) at kern_open+0xe7
> > > open(c412f230,fb671cfc,c,c08e28c3,c092c0b8,...) at open+0x30
> > > syscall(fb671d38) at syscall+0x2b3
> > > Xint0x80_syscall() at Xint0x80_syscall+0x20
> > > --- syscall (5, FreeBSD ELF32, open), eip = 0x2835a65b, esp =
> > > 0xbfbfeafc, ebp = 0xbfbfeb38 ---
> >
> > Are you using user or group rules in your pf.conf? IIRC there is still a
> > known LOR in the socket layer with rules using the user or group filters.
>
> No, I'm aware of the problems with pf(4) and user/group rules. This LOR
> is in combination with rules on tun(4) devices, as you can see from the
> backtrace. I wonder what tunclone() is doing in there, though.
This LOR is believed to be harmless. There should be an easy fix, even. I'll
have to take a look over the weekend.
--
/"\ Best regards, | mlaier@freebsd.org
\ / Max Laier | ICQ #67774661
X http://pf4freebsd.love2party.net/ | mlaier@EFnet
/ \ ASCII Ribbon Campaign | Against HTML Mail and News
From owner-freebsd-stable@FreeBSD.ORG Fri Nov 21 19:49:44 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 4D27E1065672
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 19:49:44 +0000 (UTC)
(envelope-from freebsd-stable-local@be-well.ilk.org)
Received: from mail3.sea5.speakeasy.net (mail3.sea5.speakeasy.net
[69.17.117.5]) by mx1.freebsd.org (Postfix) with ESMTP id 2FFD88FC16
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 19:49:43 +0000 (UTC)
(envelope-from freebsd-stable-local@be-well.ilk.org)
Received: (qmail 5362 invoked from network); 21 Nov 2008 19:49:43 -0000
Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org)
([66.92.78.145])
(envelope-sender <freebsd-stable-local@be-well.ilk.org>)
by mail3.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP
for <freebsd-stable@freebsd.org>; 21 Nov 2008 19:49:43 -0000
Received: by be-well.ilk.org (Postfix, from userid 1147)
id E207D5087C; Fri, 21 Nov 2008 14:49:42 -0500 (EST)
To: Jordi Espasa Clofent <jespasac@minibofh.org>
References: <492536C2.6060605@minibofh.org>
From: Lowell Gilbert <freebsd-stable-local@be-well.ilk.org>
Date: Fri, 21 Nov 2008 14:49:42 -0500
In-Reply-To: <492536C2.6060605@minibofh.org> (Jordi Espasa Clofent's message
of "Thu\, 20 Nov 2008 11\:06\:58 +0100")
Message-ID: <447i6wvoyx.fsf@be-well.ilk.org>
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.3 (berkeley-unix)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: freebsd-stable@freebsd.org
Subject: Re: Error in 7.0p5 upgrade
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Nov 2008 19:49:44 -0000
Jordi Espasa Clofent <jespasac@minibofh.org> writes:
> Hi all,
>
> I'm upgrading a FreeBSD amd64 box from 6.2p9 to 7.0p5.
> After update the sources amd make world with success, I get this error:
>
> [...]
> newfs.lo(.text+0x659): In function `main':
> : undefined reference to `__mb_sb_limit'
> newfs_msdos.lo(.text+0x13): In function `mklabel':
> : undefined reference to `__mb_sb_limit'
> restore.lo(.text+0xc60): In function `mkentry':
> : undefined reference to `__mb_sb_limit'
> restore.lo(.text+0xa6d6): In function `rmthost':
> : undefined reference to `__mb_sb_limit'
> sysctl.lo(.text+0xf9f): more undefined references to `__mb_sb_limit' follow
> tar.lo(.text+0x28f4): In function `read_archive':
> : undefined reference to `archive_read_support_compression_program'
> tar.lo(.text+0x3a81): In function `yes':
> : undefined reference to `__mb_sb_limit'
> tar.lo(.text+0x432a): In function `safe_fprintf':
> : undefined reference to `__mb_sb_limit'
> tar.lo(.text+0x6156): In function `tar_mode_c':
> : undefined reference to `archive_write_set_compression_program'
> vi.lo(.text+0x2f80): In function `cut':
> : undefined reference to `__mb_sb_limit'
> vi.lo(.text+0x2fb0): In function `cut':
> : undefined reference to `__mb_sb_limit'
> vi.lo(.text+0x311e): In function `cut':
> : undefined reference to `__mb_sb_limit'
> vi.lo(.text+0x5c29): In function `v_key_name':
> : undefined reference to `__mb_sb_limit'
> vi.lo(.text+0x5cf3): In function `v_key_name':
> : undefined reference to `__mb_sb_limit'
> vi.lo(.text+0x63b8): more undefined references to `__mb_sb_limit' follow
> *** Error code 1
>
> Stop in /usr/obj/usr/src/rescue/rescue.
> *** Error code 1
>
> Stop in /usr/src/rescue/rescue.
> *** Error code 1
>
> Stop in /usr/src/rescue.
> *** Error code 1
>
> Stop in /usr/src.
> *** Error code 1
>
> Stop in /usr/src.
>
> after try the classical kernel compilation ( cd /usr/src && make
> -DINSTALL_NODEBUG KERNCONF=MYKERNEL)
>
> I've not found any related info in the net. Anyones knows about? Last
> week I upgraded two others 6.2 amd boxes without problem.
>
> PD1. I use the "classical" method over "new" binary method because of
> my kernel is customized.
Neither of those methods seem to be the officially supported source
update method, which includes (in order, but with some other steps left
out)
make buildworld
make buildkernel
make installkernel
<REBOOT into single-user>
make installworld
Is that actually what you did?
If not, what did you mean when you said you did "make world"?
> PD2. I use -DINSTALL_NODEBUG flag because of my / partition is so
> small and need to preserve the maximum space.
That should be fine, and doesn't seem to be related to the symptoms.
From owner-freebsd-stable@FreeBSD.ORG Fri Nov 21 20:31:59 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 778491065670
for <freebsd-stable@FreeBSD.org>; Fri, 21 Nov 2008 20:31:59 +0000 (UTC)
(envelope-from scf@FreeBSD.org)
Received: from mail.farley.org (farley.org [67.64.95.201])
by mx1.freebsd.org (Postfix) with ESMTP id 333B48FC1E
for <freebsd-stable@FreeBSD.org>; Fri, 21 Nov 2008 20:31:59 +0000 (UTC)
(envelope-from scf@FreeBSD.org)
Received: from thor.farley.org (HPooka@thor.farley.org [192.168.1.5])
by mail.farley.org (8.14.3/8.14.3) with ESMTP id mALKVtwA039909;
Fri, 21 Nov 2008 14:31:55 -0600 (CST) (envelope-from scf@FreeBSD.org)
Date: Fri, 21 Nov 2008 14:31:55 -0600 (CST)
From: "Sean C. Farley" <scf@FreeBSD.org>
To: Sam Leffler <sam@errno.com>
In-Reply-To: <4926E9FE.1070302@errno.com>
Message-ID: <alpine.BSF.2.00.0811211430550.46525@thor.farley.org>
References: <4926E9FE.1070302@errno.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Spam-Status: No, score=-4.4 required=3.0 tests=ALL_TRUSTED,BAYES_00
autolearn=ham version=3.2.5
X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on mail.farley.org
Cc: freebsd-stable@FreeBSD.org
Subject: Re: [Fwd: Re: kern/123552: [ath] [panic] kernel panic during network
activity on ath0]
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Nov 2008 20:31:59 -0000
On Fri, 21 Nov 2008, Sam Leffler wrote:
> Folks having problems with ath on releng7 should try the attached
> patch.
It fixed the panic when SuperG was activated on the wireless router for
me. Thank you!
Sean
--
scf@FreeBSD.org
From owner-freebsd-stable@FreeBSD.ORG Fri Nov 21 21:09:34 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id CBD65106567C
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 21:09:34 +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 67FD48FC32
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 21:09:34 +0000 (UTC)
(envelope-from peterjeremy@optushome.com.au)
Received: from server.vk2pj.dyndns.org
(c122-106-215-175.belrs3.nsw.optusnet.com.au [122.106.215.175])
by mail14.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id
mALL9V01020711
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
Sat, 22 Nov 2008 08:09:32 +1100
X-Bogosity: Ham, spamicity=0.000000
Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1])
by server.vk2pj.dyndns.org (8.14.3/8.14.3) with ESMTP id mALL9VA6095858;
Sat, 22 Nov 2008 08:09:31 +1100 (EST)
(envelope-from peter@server.vk2pj.dyndns.org)
Received: (from peter@localhost)
by server.vk2pj.dyndns.org (8.14.3/8.14.3/Submit) id mALL9VBC095857;
Sat, 22 Nov 2008 08:09:31 +1100 (EST) (envelope-from peter)
Date: Sat, 22 Nov 2008 08:09:31 +1100
From: Peter Jeremy <peterjeremy@optushome.com.au>
To: hamtilla <tangel@gmail.com>
Message-ID: <20081121210931.GY51761@server.vk2pj.dyndns.org>
References: <20616760.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="PZYVFYZbFYjzBslI"
Content-Disposition: inline
In-Reply-To: <20616760.post@talk.nabble.com>
X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: freebsd-stable@freebsd.org
Subject: Re: Integrated RTL8168/8111 NIC not assigned interface
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Nov 2008 21:09:34 -0000
--PZYVFYZbFYjzBslI
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On 2008-Nov-21 00:07:26 -0800, hamtilla <tangel@gmail.com> wrote:
>I'm running 7.0-RELEASE-i386 on Jetway's NC92-N230 mainboard. The board has
>one integrated RTL8168/8111 gigabit NIC as well as an expansion board with
>three RTL8168/8111 NICs. Why would the three NICs work while the onboard N=
IC
>does not?=20
>
>none2@pci0:1:0:0: class=3D0x020000 card=3D0x816810ec chip=3D0x816810=
ec
>rev=3D0x02 hdr=3D0x00
> vendor =3D 'Realtek Semiconductor'
> device =3D 'RTL8168/8111 PCI-E Gigabit Ethernet NIC'
> class =3D network
> subclass =3D ethernet
>re0@pci0:2:4:0: class=3D0x020000 card=3D0x10ec16f3 chip=3D0x816710ec rev=
=3D0x10
>hdr=3D0x00
> vendor =3D 'Realtek Semiconductor'
> device =3D 'RTL8169/8110 Family Gigabit Ethernet NIC'
> class =3D network
> subclass =3D ethernet
=2E..
The on-board NIC is a different type to your expansion cards (note the
different 'chip=3D' values. Looking at the code, it appears that only
some variants of the RTL8168 are supported in 7.x. Unfortunately, pciconf
doesn't report the actual hardware revision, so you can't tell from the
pciconf output whether it's supported or not.
Can you report the output of 'pciconf -r pci0:1:0:0 0x40' (which should
report the hw revision) and 'pciconf -r pci0:2:4:0 0x40' (which gives
me a double-check).
You could try booting -current and see if the on-board NIC works there -
the range of supported NICs has changed.
--=20
Peter Jeremy
Please excuse any delays as the result of my ISP's inability to implement
an MTA that is either RFC2821-compliant or matches their claimed behaviour.
--PZYVFYZbFYjzBslI
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (FreeBSD)
iEYEARECAAYFAkknI4sACgkQ/opHv/APuIcFwQCgm+za+8ePHH4wrk1IcpFbtqw8
s/sAoLafpFaKXwRU4X4/dJ1vc5kIs/fJ
=A0ap
-----END PGP SIGNATURE-----
--PZYVFYZbFYjzBslI--
From owner-freebsd-stable@FreeBSD.ORG Fri Nov 21 21:24:42 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 766461065673
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 21:24:42 +0000 (UTC)
(envelope-from peter@simons-rock.edu)
Received: from hedwig.simons-rock.edu (hedwig.simons-rock.edu [208.81.88.14])
by mx1.freebsd.org (Postfix) with ESMTP id 3CE888FC18
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 21:24:41 +0000 (UTC)
(envelope-from peter@simons-rock.edu)
Received: from cesium.hyperfine.info (c2.8d.5646.static.theplanet.com
[70.86.141.194])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(No client certificate requested)
by hedwig.simons-rock.edu (Postfix) with ESMTP id 79863ED002;
Fri, 21 Nov 2008 16:24:40 -0500 (EST)
Date: Fri, 21 Nov 2008 16:22:06 -0500
From: "Peter C. Lai" <peter@simons-rock.edu>
To: Peter Jeremy <peterjeremy@optushome.com.au>
Message-ID: <20081121212206.GI58082@cesium.hyperfine.info>
References: <20616760.post@talk.nabble.com>
<20081121210931.GY51761@server.vk2pj.dyndns.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20081121210931.GY51761@server.vk2pj.dyndns.org>
User-Agent: Mutt/1.5.17 (2007-11-01)
Cc: hamtilla <tangel@gmail.com>, freebsd-stable@freebsd.org
Subject: Re: Integrated RTL8168/8111 NIC not assigned interface
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Nov 2008 21:24:42 -0000
On 2008-11-22 08:09:31AM +1100, Peter Jeremy wrote:
> On 2008-Nov-21 00:07:26 -0800, hamtilla <tangel@gmail.com> wrote:
> >I'm running 7.0-RELEASE-i386 on Jetway's NC92-N230 mainboard. The board has
> >one integrated RTL8168/8111 gigabit NIC as well as an expansion board with
> >three RTL8168/8111 NICs. Why would the three NICs work while the onboard NIC
> >does not?
> >
> >none2@pci0:1:0:0: class=0x020000 card=0x816810ec chip=0x816810ec
> >rev=0x02 hdr=0x00
> > vendor = 'Realtek Semiconductor'
> > device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC'
> > class = network
> > subclass = ethernet
> >re0@pci0:2:4:0: class=0x020000 card=0x10ec16f3 chip=0x816710ec rev=0x10
> >hdr=0x00
> > vendor = 'Realtek Semiconductor'
> > device = 'RTL8169/8110 Family Gigabit Ethernet NIC'
> > class = network
> > subclass = ethernet
> ...
>
> The on-board NIC is a different type to your expansion cards (note the
> different 'chip=' values. Looking at the code, it appears that only
> some variants of the RTL8168 are supported in 7.x. Unfortunately, pciconf
> doesn't report the actual hardware revision, so you can't tell from the
> pciconf output whether it's supported or not.
>
> Can you report the output of 'pciconf -r pci0:1:0:0 0x40' (which should
> report the hw revision) and 'pciconf -r pci0:2:4:0 0x40' (which gives
> me a double-check).
>
> You could try booting -current and see if the on-board NIC works there -
> the range of supported NICs has changed.
>
> --
> Peter Jeremy
> Please excuse any delays as the result of my ISP's inability to implement
> an MTA that is either RFC2821-compliant or matches their claimed behaviour.
Yes, 7.0-R is pretty old in terms of re(4) work. I believe yongari@
is still working on this driver. 7.1 is close enough for patching
with patches from http://people.freebsd.org/~yongari/re/
Currently development is stifled because he has to basically guess
the appropriate magic values for various PHY permutations in these
8111C/8168C gigabit cards everyone seems to be putting in their
motherboards these days.
--
===========================================================
Peter C. Lai | Bard College at Simon's Rock
Systems Administrator | 84 Alford Rd.
Information Technology Svcs. | Gt. Barrington, MA 01230 USA
peter AT simons-rock.edu | (413) 528-7428
===========================================================
From owner-freebsd-stable@FreeBSD.ORG Fri Nov 21 23:58:52 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id EE32F1065691
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 23:58:52 +0000 (UTC)
(envelope-from zbeeble@gmail.com)
Received: from mail-gx0-f12.google.com (mail-gx0-f12.google.com
[209.85.217.12])
by mx1.freebsd.org (Postfix) with ESMTP id 9C6038FC08
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 23:58:52 +0000 (UTC)
(envelope-from zbeeble@gmail.com)
Received: by gxk5 with SMTP id 5so88830gxk.19
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 15:58:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:message-id:date:from:to
:subject:mime-version:content-type;
bh=mX6ySWm0IEEovORKzKZOFUR7Y0H9MGUBF4rYMG5Uadg=;
b=g3YtG1SlrsF6HaYFt2/l/RdMW3mTE/tQn69GOfBH3ViooiVfS1DRJZKDWcYcFQtb4J
IV8JAsmvc03WLdNUKQg/veWSozwzh0RfUB2tB3SN1Nzaf2CrhmMhKJuYrUH33ZMuSCzu
YJzWce7pvY5m/FSKbqkk4vPp1KhO0F9/Xsy40=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=message-id:date:from:to:subject:mime-version:content-type;
b=RWXVGdbj7mlOB1yNZxiFPkrQiTc3ZDXbZHtJ1Q4VvSzugA0Le+tvFU/fAY6S5llL64
1eJNOr6ejWVR7XO3t3UjOO4FxtmQik0XOi8+g3ysnnE8J79+AC3hguI4z0Gkocxg3sIP
TgALpvsI4U/Y40qRqs0UnoRqiW6KBz6XLo0lo=
Received: by 10.151.156.1 with SMTP id i1mr1932540ybo.31.1227311931791;
Fri, 21 Nov 2008 15:58:51 -0800 (PST)
Received: by 10.151.72.7 with HTTP; Fri, 21 Nov 2008 15:58:51 -0800 (PST)
Message-ID: <5f67a8c40811211558n5fc77a54v3d4589dc838af443@mail.gmail.com>
Date: Fri, 21 Nov 2008 18:58:51 -0500
From: "Zaphod Beeblebrox" <zbeeble@gmail.com>
To: "FreeBSD Stable Mailing List" <freebsd-stable@freebsd.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
Subject: MFC ZFS: when?
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Nov 2008 23:58:53 -0000
In several of the recent ZFS posts, multiple people have asked when this
will be MFC'd to 7.x. This query has been studiously ignored as other
chatter about whatever ZFS issue is discussed.
So in a post with no other bug report or discussion content to distract us,
when is it intended that ZFS be MFC'd to 7.x?
From owner-freebsd-stable@FreeBSD.ORG Sat Nov 22 00:09:14 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id B2AB81065670
for <freebsd-stable@freebsd.org>; Sat, 22 Nov 2008 00:09:14 +0000 (UTC)
(envelope-from onemda@gmail.com)
Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.31])
by mx1.freebsd.org (Postfix) with ESMTP id 5C60E8FC0C
for <freebsd-stable@freebsd.org>; Sat, 22 Nov 2008 00:09:14 +0000 (UTC)
(envelope-from onemda@gmail.com)
Received: by yw-out-2324.google.com with SMTP id 9so525138ywe.13
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 16:09:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:message-id:date:from:to
:subject:cc:in-reply-to:mime-version:content-type
:content-transfer-encoding:content-disposition:references;
bh=56rTANJBPBISjpESvP++rTuoP/eS/0Cj1+bqVM5X+gQ=;
b=a4x0hfR2p9I/BDq60f7VqF/V5hKomc2/tMosRaN4sR55UgMfbEan7s3mPt9q3sp7cY
/Q0ToijkAing13g7xSVfMW4AToZi7PbwM2tONkCP4A1jPYWY2M4qKq7mVKEuTQUlxBp6
kW/VSyEiRiU/fYg0jStxBnSy8tE+lUmpe4OVk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
:content-type:content-transfer-encoding:content-disposition
:references;
b=a6nFa8LLIPL93Iy/PLz9GyP1m9K8HLvMb5nLbQ5lkf3bNNUt76pYe54CJzcTO3PtsQ
rDcUft+UN+ts+9wbJ5VKn69SgJTcJdO9qmBzg/qigDzgPjC3alNy+oqrP2/fD3mXCjzJ
eyULfiH4y5M4sAUKZxuLT/hNiZJkKs7wqFNyY=
Received: by 10.231.39.65 with SMTP id f1mr28057ibe.25.1227312553017;
Fri, 21 Nov 2008 16:09:13 -0800 (PST)
Received: by 10.231.11.7 with HTTP; Fri, 21 Nov 2008 16:09:12 -0800 (PST)
Message-ID: <3a142e750811211609u67969c2fqe16a88aea52309fb@mail.gmail.com>
Date: Sat, 22 Nov 2008 01:09:12 +0100
From: "Paul B. Mahol" <onemda@gmail.com>
To: "Zaphod Beeblebrox" <zbeeble@gmail.com>
In-Reply-To: <5f67a8c40811211558n5fc77a54v3d4589dc838af443@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <5f67a8c40811211558n5fc77a54v3d4589dc838af443@mail.gmail.com>
Cc: FreeBSD Stable Mailing List <freebsd-stable@freebsd.org>
Subject: Re: MFC ZFS: when?
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Nov 2008 00:09:14 -0000
On 11/22/08, Zaphod Beeblebrox <zbeeble@gmail.com> wrote:
> In several of the recent ZFS posts, multiple people have asked when this
> will be MFC'd to 7.x. This query has been studiously ignored as other
> chatter about whatever ZFS issue is discussed.
>
> So in a post with no other bug report or discussion content to distract us,
> when is it intended that ZFS be MFC'd to 7.x?
Once no new bugs appear any more, and old one are fixed.
--
Paul
From owner-freebsd-stable@FreeBSD.ORG Sat Nov 22 00:20:06 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id B06131065670
for <freebsd-stable@freebsd.org>; Sat, 22 Nov 2008 00:20:06 +0000 (UTC)
(envelope-from zbeeble@gmail.com)
Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.31])
by mx1.freebsd.org (Postfix) with ESMTP id 5AF438FC12
for <freebsd-stable@freebsd.org>; Sat, 22 Nov 2008 00:20:05 +0000 (UTC)
(envelope-from zbeeble@gmail.com)
Received: by yw-out-2324.google.com with SMTP id 9so526168ywe.13
for <freebsd-stable@freebsd.org>; Fri, 21 Nov 2008 16:20:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:message-id:date:from:to
:subject:cc:in-reply-to:mime-version:content-type:references;
bh=Y6n9d6xPPbK71DRAlqIer//TVQRuMlA6HPalHhwOsEc=;
b=aD1sTKw9ckX8r9BScZjlqX6nGXnNBRoBSh0Is3xS9kn1RV8CjEokx9i2YwJcWQQd75
yqBuj8HfiYx+uuLeqa2ndu8R/5P3gvWgrZ4o+oQf2iIue5NYzwynLvLAc9YHLBUOaXod
MgyJGt2gPlOCotOGbdzc8gFF9HgejLKl5IPV4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
:content-type:references;
b=pPMyG064KhIv0G8zKJRVa4PxFMTz7wnEeplgChXOH6NHFS/NLsLr7Ykrd7DFOEeyPz
Ft0cB96eakZAJXMh8UiKc0pglL4sqP/R/Mx1JUR+5HhUFBKr9qjJ5bJy2JMJiThOZdZV
EBvZGtrDORoBwfhbpXcAZEkSkgYXgdcHynwI4=
Received: by 10.151.41.14 with SMTP id t14mr1899425ybj.234.1227313205413;
Fri, 21 Nov 2008 16:20:05 -0800 (PST)
Received: by 10.151.72.7 with HTTP; Fri, 21 Nov 2008 16:20:05 -0800 (PST)
Message-ID: <5f67a8c40811211620x63ea3095m6817d9b9de2d2f9a@mail.gmail.com>
Date: Fri, 21 Nov 2008 19:20:05 -0500
From: "Zaphod Beeblebrox" <zbeeble@gmail.com>
To: "Paul B. Mahol" <onemda@gmail.com>
In-Reply-To: <3a142e750811211609u67969c2fqe16a88aea52309fb@mail.gmail.com>
MIME-Version: 1.0
References: <5f67a8c40811211558n5fc77a54v3d4589dc838af443@mail.gmail.com>
<3a142e750811211609u67969c2fqe16a88aea52309fb@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
Cc: FreeBSD Stable Mailing List <freebsd-stable@freebsd.org>
Subject: Re: MFC ZFS: when?
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Nov 2008 00:20:06 -0000
On Fri, Nov 21, 2008 at 7:09 PM, Paul B. Mahol <onemda@gmail.com> wrote:
> On 11/22/08, Zaphod Beeblebrox <zbeeble@gmail.com> wrote:
> > In several of the recent ZFS posts, multiple people have asked when this
> > will be MFC'd to 7.x. This query has been studiously ignored as other
> > chatter about whatever ZFS issue is discussed.
> >
> > So in a post with no other bug report or discussion content to distract
> us,
> > when is it intended that ZFS be MFC'd to 7.x?
>
> Once no new bugs appear any more, and old one are fixed.
That's a pretty cop-out answer. Considering the the version of ZFS in 7.x
has significant issues and the ZFS patches havn't shown any propensity to
affect non-ZFS systems when ZFS is not running or loaded, the benefit of
importing the new code seems to outweigh any caution you might feel. I can
understand an answer such as "not in 7.1, but immediately after" ... given
the standards we apply to release branches ... but a vague "when no bugs
seem to appear" applies much less to a system like ZFS (still in flux) than,
say, the new USB stack.
From owner-freebsd-stable@FreeBSD.ORG Sat Nov 22 01:32:03 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 83C4C106564A
for <freebsd-stable@FreeBSD.org>; Sat, 22 Nov 2008 01:32:03 +0000 (UTC)
(envelope-from sam@errno.com)
Received: from ebb.errno.com (ebb.errno.com [69.12.149.25])
by mx1.freebsd.org (Postfix) with ESMTP id 397148FC13
for <freebsd-stable@FreeBSD.org>; Sat, 22 Nov 2008 01:32:03 +0000 (UTC)
(envelope-from sam@errno.com)
Received: from trouble.errno.com (trouble.errno.com [10.0.0.248])
(authenticated bits=0)
by ebb.errno.com (8.13.6/8.12.6) with ESMTP id mAM1W2Z2028099
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
Fri, 21 Nov 2008 17:32:02 -0800 (PST) (envelope-from sam@errno.com)
Message-ID: <49276112.3080200@errno.com>
Date: Fri, 21 Nov 2008 17:32:02 -0800
From: Sam Leffler <sam@errno.com>
User-Agent: Thunderbird 2.0.0.9 (X11/20071125)
MIME-Version: 1.0
To: "Sean C. Farley" <scf@FreeBSD.org>
References: <4926E9FE.1070302@errno.com>
<alpine.BSF.2.00.0811211430550.46525@thor.farley.org>
In-Reply-To: <alpine.BSF.2.00.0811211430550.46525@thor.farley.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-DCC--Metrics: ebb.errno.com; whitelist
Cc: freebsd-stable@FreeBSD.org
Subject: Re: [Fwd: Re: kern/123552: [ath] [panic] kernel panic during network
activity on ath0]
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Nov 2008 01:32:03 -0000
Sean C. Farley wrote:
> On Fri, 21 Nov 2008, Sam Leffler wrote:
>
>> Folks having problems with ath on releng7 should try the attached
>> patch.
>
> It fixed the panic when SuperG was activated on the wireless router for
> me. Thank you!
>
Guy Coleman gets any credit; I just recognized what the root cause was.
Sam
From owner-freebsd-stable@FreeBSD.ORG Sat Nov 22 08:11:53 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 374FA1065672
for <freebsd-stable@freebsd.org>; Sat, 22 Nov 2008 08:11:53 +0000 (UTC)
(envelope-from ruben@verweg.com)
Received: from erg.verweg.com (unknown [IPv6:2001:980:fff:96::c0a8:181])
by mx1.freebsd.org (Postfix) with ESMTP id 7DAE88FC17
for <freebsd-stable@freebsd.org>; Sat, 22 Nov 2008 08:11:52 +0000 (UTC)
(envelope-from ruben@verweg.com)
Received: from neon.niet.verweg.com (helium.xs4all.nl [194.109.251.55])
(authenticated bits=0)
by erg.verweg.com (8.14.3/8.14.3) with ESMTP id mAM8BL6q001550
(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
Sat, 22 Nov 2008 08:11:22 GMT (envelope-from ruben@verweg.com)
X-Authentication-Warning: erg.verweg.com: Host helium.xs4all.nl
[194.109.251.55] claimed to be neon.niet.verweg.com
Message-Id: <98B825A0-9882-42C8-8F66-1DFF4308D4F5@verweg.com>
From: Ruben van Staveren <ruben@verweg.com>
To: Zaphod Beeblebrox <zbeeble@gmail.com>
In-Reply-To: <5f67a8c40811211620x63ea3095m6817d9b9de2d2f9a@mail.gmail.com>
Content-Type: multipart/signed; protocol="application/pgp-signature";
micalg=pgp-sha1; boundary="Apple-Mail-6--73800363"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Sat, 22 Nov 2008 09:11:42 +0100
References: <5f67a8c40811211558n5fc77a54v3d4589dc838af443@mail.gmail.com>
<3a142e750811211609u67969c2fqe16a88aea52309fb@mail.gmail.com>
<5f67a8c40811211620x63ea3095m6817d9b9de2d2f9a@mail.gmail.com>
X-Pgp-Agent: GPGMail d52 (v52, Leopard)
X-Mailer: Apple Mail (2.929.2)
X-Spam-Status: No, score=3.9 required=5.0 tests=DATE_IN_FUTURE_96_XX, SPF_PASS
autolearn=no version=3.2.5
X-Spam-Level: ***
X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on erg.verweg.com
X-Virus-Scanned: ClamAV 0.94.1/8661/Fri Nov 21 15:39:30 2008 on erg.verweg.com
X-Virus-Status: Clean
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1
(erg.verweg.com [192.168.1.129]);
Sat, 22 Nov 2008 08:11:27 +0000 (UTC)
Cc: "Paul B. Mahol" <onemda@gmail.com>,
FreeBSD Stable Mailing List <freebsd-stable@freebsd.org>
Subject: Re: MFC ZFS: when?
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Nov 2008 08:11:53 -0000
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--Apple-Mail-6--73800363
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Hi,
On 22 Nov 2008, at 1:20, Zaphod Beeblebrox wrote:
> That's a pretty cop-out answer. Considering the the version of ZFS
> in 7.x
> has significant issues and the ZFS patches havn't shown any
> propensity to
> affect non-ZFS systems when ZFS is not running or loaded, the
> benefit of
Please, give them some time.... zfs v13 has just ended up in -current
after a long time and hard workmanship. I think everyone likes to see
it up in RELENG_7 someday, but until that happens I'll be just
patient. It definitely needs the time to settle before people can even
think about mfc'ing it, which is not a trivial task either.
Regards,
Ruben
--Apple-Mail-6--73800363
content-type: application/pgp-signature; x-mac-type=70674453;
name=PGP.sig
content-description: This is a digitally signed message part
content-disposition: inline; filename=PGP.sig
content-transfer-encoding: 7bit
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (Darwin)
iD8DBQFJJ76+Z88+mcQxRw0RAvoSAKCDknYgBJSHbGBDu8VUPAg/a2id3gCdE7In
45TV3jK+ASCZE4MdcMUvWp8=
=fRGB
-----END PGP SIGNATURE-----
--Apple-Mail-6--73800363--
From owner-freebsd-stable@FreeBSD.ORG Sat Nov 22 09:52:32 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id B0A81106564A
for <freebsd-stable@freebsd.org>; Sat, 22 Nov 2008 09:52:32 +0000 (UTC)
(envelope-from unga888@yahoo.com)
Received: from web57007.mail.re3.yahoo.com (web57007.mail.re3.yahoo.com
[66.196.97.111]) by mx1.freebsd.org (Postfix) with SMTP id 39B9F8FC14
for <freebsd-stable@freebsd.org>; Sat, 22 Nov 2008 09:52:32 +0000 (UTC)
(envelope-from unga888@yahoo.com)
Received: (qmail 6581 invoked by uid 60001); 22 Nov 2008 09:25:50 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Message-ID;
b=zC1lwu7XVrSJ2+HbFwDOGDYkyz/kNN5uBKTNwzXe0v+9+/wnOxemsJIWZUc6EOuRdNuWhdMyLuS0P6lVgqpPMFlesfwI1djOCxBvya5O8raAKY/19sr6Q3SD/oGPQwpCgm+PwwOpZtuDgx1nHCariACmBTJxG3zzLAXZAtAKvn8=;
X-YMail-OSG: E4aObrcVM1l_NDtgxGHdBGXA.3Flqoz.ujvMJCYLMjnKYyHz7kROebFC422a1kLbfe.90anfIg9HVLCQptZ8Th6tGELJ_4t38P8DcPmdCK7U9sXT1JHgaO5bzohDy13sXZAjQqSxAV4BpHPxMbRsHmHOW84f80nOL3NHhK0Hk6accuhBOkwVds.ZrQ--
Received: from [220.255.7.231] by web57007.mail.re3.yahoo.com via HTTP;
Sat, 22 Nov 2008 01:25:49 PST
X-Mailer: YahooMailWebService/0.7.260.1
Date: Sat, 22 Nov 2008 01:25:49 -0800 (PST)
From: Unga <unga888@yahoo.com>
To: freebsd-stable@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Message-ID: <88609.6523.qm@web57007.mail.re3.yahoo.com>
Subject: Weird priority for normal
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: unga888@yahoo.com
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Nov 2008 09:52:32 -0000
Hi all
I'm using FreeBSD RELENG_7 on i386 and noted with rtprio(2) the priority for root and other normal users is "normal priority" with 65504 as the priority value (rtp.prio).
Please note, this is not the latest RELENG_7, my system is compiled somewhere on May.
I checked the program flow from /usr/src/usr.bin/su/su.c to /usr/src/lib/libutil/login_class.c and found setusercontext() is setting the priority right but the moment it come out from the setusercontext() call in su.c, the priority has already turn to 65504.
It looks like this is a bug. I had a quite thorough look but did not see any error. I'm not sure by now is it been fixed. Do others experience it?
Best regards
Unga
From owner-freebsd-stable@FreeBSD.ORG Sat Nov 22 11:25:47 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 35FB41065672
for <freebsd-stable@freebsd.org>; Sat, 22 Nov 2008 11:25:47 +0000 (UTC)
(envelope-from amon@aelita.org)
Received: from aelita.org (unknown [IPv6:2001:7a8:7003::3])
by mx1.freebsd.org (Postfix) with ESMTP id 991988FC18
for <freebsd-stable@freebsd.org>; Sat, 22 Nov 2008 11:25:46 +0000 (UTC)
(envelope-from amon@aelita.org)
Received: from ra.aabs (localhost [127.0.0.1])
by aelita.org (8.14.2/8.14.2) with ESMTP id mAMCOBWa078541;
Sat, 22 Nov 2008 13:24:11 +0100 (CET) (envelope-from amon@ra.aabs)
Received: (from amon@localhost)
by ra.aabs (8.14.2/8.14.2/Submit) id mAMCOBQs078540;
Sat, 22 Nov 2008 13:24:11 +0100 (CET) (envelope-from amon)
Date: Sat, 22 Nov 2008 13:24:11 +0100
From: Herve Boulouis <amon@aelita.org>
To: Herve Boulouis <amon@aelita.org>
Message-ID: <20081122122411.GA63134@ra.aabs>
References: <20081106102931.GD596@ra.aabs> <20081106150548.GF596@ra.aabs>
<20081114161328.GO596@ra.aabs>
Mime-Version: 1.0
Content-Type: text/plain; charset=unknown-8bit
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20081114161328.GO596@ra.aabs>
User-Agent: Mutt/1.4.2.1i
Cc: freebsd-stable@freebsd.org
Subject: Re: Multiple panics with 7.1-PRERELEASE amd64/i386 and varnish
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Nov 2008 11:25:47 -0000
Le 14/11/2008 17:13, Herve Boulouis a écrit:
> Le 06/11/2008 16:05, Herve Boulouis a écrit:
> > Le 06/11/2008 11:29, Herve Boulouis a écrit:
> >
> > I just tried to reboot one of the boxes without kern.ipc.maxpipekva=104857600 to check for kva problems
> > but crashes persists, though the stack is completely different now. This time I included all the corrupt
> > parts of the stack that I had stripped in my original email but they are similar (from frame 18 to end).
> >
> > Any ideas ?
>
> We just found the same kind of crash with a 7.0-STABLE i386 from August so there is a serious bug in the kernel making
> varnish with file backend totaly unusable on FreeBSD 7.
Found the culprit: removing ZERO_COPY_SOCKETS from kernel config allows varnish to run happily with mmap'ed backend.
(at least no crash in the past 17 hours)
Tested on amd64 only.
--
Herve Boulouis
From owner-freebsd-stable@FreeBSD.ORG Sat Nov 22 12:18:16 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id C86661065672
for <freebsd-stable@freebsd.org>; Sat, 22 Nov 2008 12:18:16 +0000 (UTC)
(envelope-from edmunds@it-depo.lv)
Received: from smtp.it-depo.lv (smtp.it-depo.lv [159.148.37.66])
by mx1.freebsd.org (Postfix) with ESMTP id 7DF328FC18
for <freebsd-stable@freebsd.org>; Sat, 22 Nov 2008 12:18:16 +0000 (UTC)
(envelope-from edmunds@it-depo.lv)
Received: from [192.168.10.10] (prime.kalnz.id.lv [87.226.86.172])
by smtp.it-depo.lv (ESMTP daemon) with ESMTP id E48448A6133
for <freebsd-stable@freebsd.org>; Sat, 22 Nov 2008 14:28:48 +0200 (EET)
Message-ID: <4927F54C.4030003@it-depo.lv>
Date: Sat, 22 Nov 2008 14:04:28 +0200
From: Edmunds Bergs <edmunds@it-depo.lv>
Organization: IT-DEPO SIA
User-Agent: Thunderbird 2.0.0.18 (Windows/20081105)
MIME-Version: 1.0
To: freebsd-stable@freebsd.org
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-SVQtREVQTw==-Scanner: Found to be clean
X-SVQtREVQTw==-Scanner-SpamCheck: not spam (whitelisted),
SpamAssassin (timed out)
Subject: traffic using ISP proxy
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: edmunds@it-depo.lv
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Nov 2008 12:18:16 -0000
Hi.
I have running firewall, just simple NAT with pf at the moment.
My Desktop PC <--> My Router <--> ISP <--> INTERNET
All the traffic goes directly (no proxy).
There is also available proxy server from my ISP so I want that all
traffic would go through it (except local domains)
My Desktop PC <--> My Router <--> ISP [Proxy] <--> INTERNET
How should I configure my FreeBSD box to achieve this, what tools I
should use?
Best Regards,
Kalnz
FreeBSD 7.1
From owner-freebsd-stable@FreeBSD.ORG Sat Nov 22 12:48:21 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 2B2E3106564A
for <freebsd-stable@freebsd.org>; Sat, 22 Nov 2008 12:48:21 +0000 (UTC)
(envelope-from robert@ml.erje.net)
Received: from smtpout-1.iphouse.net (smtpout-1.iphouse.net [216.250.188.190])
by mx1.freebsd.org (Postfix) with ESMTP id E9DF18FC13
for <freebsd-stable@freebsd.org>; Sat, 22 Nov 2008 12:48:20 +0000 (UTC)
(envelope-from robert@ml.erje.net)
Received: from smtpout-1.iphouse.net (localhost [127.0.0.1])
by outbound-clamsmtpd.iphouse.net (Postfix) with ESMTP id AF8252AC612
for <freebsd-stable@freebsd.org>; Sat, 22 Nov 2008 06:31:56 -0600 (CST)
Received: from ziemel.erje.net (erje.net [80.126.62.176])
(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
(No client certificate requested)
by smtpout-1.iphouse.net (Postfix) with ESMTP id 669CA2AC5FD
for <freebsd-stable@freebsd.org>; Sat, 22 Nov 2008 06:31:56 -0600 (CST)
Received: from ismet.erje.net (ismet.erje.net [IPv6:2001:888:1f33::8e45:5e])
by ziemel.erje.net (PostFix 2.5.5) with ESMTP id C18B8CA091B
for <freebsd-stable@freebsd.org>; Sat, 22 Nov 2008 13:30:30 +0100 (CET)
Received: (from robert@localhost)
by ismet.erje.net (8.14.2/8.14.2/Submit) id mAMCUUSR002727
for freebsd-stable@freebsd.org; Sat, 22 Nov 2008 13:30:30 +0100 (CET)
(envelope-from robert@ml.erje.net)
X-Authentication-Warning: ismet.erje.net: robert set sender to
robert@ml.erje.net using -f
Date: Sat, 22 Nov 2008 13:30:30 +0100
From: Robert Joosten <robert@ml.erje.net>
To: freebsd-stable@freebsd.org
Message-ID: <20081122123029.GC877@iphouse.com>
References: <4927F54C.4030003@it-depo.lv>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4927F54C.4030003@it-depo.lv>
User-Agent: Mutt/1.5.17 (2007-11-01)
X-ziemel.erje.net-MailScanner: Ok, found to be clean
X-Spam-Status: No
X-Virus-Scanned: ClamAV using ClamSMTP
Subject: Re: traffic using ISP proxy
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Nov 2008 12:48:21 -0000
Hi,
> How should I configure my FreeBSD box to achieve this, what tools I should
> use?
You can only proxy traffic that the proxyserver itself understands. I
suppose that proxyserver from your ISP is an http proxy, so you have to
adjust your browser. You cannot proxy smtp or pop3, sip or whatever
through, let's say, squid. It doesn't understand any protocol other than
http (and ftp). Natting all outbound traffic to that proxyserver will not
work as you expect. There is ofcourse other proxyserver software that do
understand pop3, smtp, sip, etc etc but I don't think your ISP will
offer that service. Otherwise, give them a call and find out.
Hth.
Regards,
Robert
From owner-freebsd-stable@FreeBSD.ORG Sat Nov 22 13:46:10 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 4A6BB106568A
for <freebsd-stable@freebsd.org>; Sat, 22 Nov 2008 13:46:10 +0000 (UTC)
(envelope-from kostikbel@gmail.com)
Received: from mail.terabit.net.ua (mail.terabit.net.ua [195.137.202.147])
by mx1.freebsd.org (Postfix) with ESMTP id D795C8FC21
for <freebsd-stable@freebsd.org>; Sat, 22 Nov 2008 13:46:09 +0000 (UTC)
(envelope-from kostikbel@gmail.com)
Received: from skuns.zoral.com.ua ([91.193.166.194] helo=mail.zoral.com.ua)
by mail.terabit.net.ua with esmtps (TLSv1:AES256-SHA:256)
(Exim 4.63 (FreeBSD)) (envelope-from <kostikbel@gmail.com>)
id 1L3soK-000MDO-Ft; Sat, 22 Nov 2008 15:46:08 +0200
Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua
[10.1.1.148])
by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id mAMDk5u6053053
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
Sat, 22 Nov 2008 15:46:05 +0200 (EET)
(envelope-from kostikbel@gmail.com)
Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1])
by deviant.kiev.zoral.com.ua (8.14.3/8.14.3) with ESMTP id
mAMDk5eG023314; Sat, 22 Nov 2008 15:46:05 +0200 (EET)
(envelope-from kostikbel@gmail.com)
Received: (from kostik@localhost)
by deviant.kiev.zoral.com.ua (8.14.3/8.14.3/Submit) id mAMDk5un023313;
Sat, 22 Nov 2008 15:46:05 +0200 (EET)
(envelope-from kostikbel@gmail.com)
X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to
kostikbel@gmail.com using -f
Date: Sat, 22 Nov 2008 15:46:05 +0200
From: Kostik Belousov <kostikbel@gmail.com>
To: Oleg Kozheltsev <axel@dnepr.net>
Message-ID: <20081122134605.GG6408@deviant.kiev.zoral.com.ua>
References: <491D28BD.4050309@dnepr.net>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="9Iq5ULCa7nGtWwZS"
Content-Disposition: inline
In-Reply-To: <491D28BD.4050309@dnepr.net>
User-Agent: Mutt/1.4.2.3i
X-Virus-Scanned: ClamAV version 0.93.3,
clamav-milter version 0.93.3 on skuns.kiev.zoral.com.ua
X-Virus-Status: Clean
X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00
autolearn=ham version=3.2.5
X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on
skuns.kiev.zoral.com.ua
X-Virus-Scanned: mail.terabit.net.ua 1L3soK-000MDO-Ft
de6714ecfcbf248dda79a8322f03dae0
X-Terabit: YES
Cc: freebsd-stable@freebsd.org
Subject: Re: can't write dvd (interrupt storm)
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Nov 2008 13:46:10 -0000
--9Iq5ULCa7nGtWwZS
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Fri, Nov 14, 2008 at 09:29:01AM +0200, Oleg Kozheltsev wrote:
> Hello,
>=20
> yesterday I buy new motherboard INTEL DP43TF and now I can't write dvd=20
> disks in any format (on PATA dvd-drive). but still can read any dvd and=
=20
> cd. cd write and blank procedure for dvd-rw done well too. when I start=
=20
> write dvd by growisofs (/dev/cd0 - atapicam), in log I get:
>=20
> Nov 14 08:28:06 <kern.crit> gx kernel: acd0: FAILURE - RESERVE_TRACK=20
> ILLEGAL REQUEST asc=3D0x30 ascq=3D0x05
> Nov 14 08:28:06 <kern.crit> gx kernel: interrupt storm detected on=20
> "irq4:"; throttling interrupt source
> Nov 14 08:28:50 <kern.crit> gx last message repeated <many> times
> Nov 14 08:31:07 <kern.crit> gx kernel: acd0: FAILURE - WRITE_BIG timed out
>=20
> if I use burncd (/dev/acd0. with, or without atapicam in kernel), then I=
=20
> get only second string in log.
Does cdrecord works for you when writing CD-ROM or CD-RW ?
I got the same motherboard, and so far I had no problems with cd.
pooma% camcontrol devlist
<SONY DVD-ROM DDU1612 DYS3> at scbus0 target 0 lun 0 (pass0,sg0,cd0)
<Optiarc DVD RW AD-7170A 1.02> at scbus0 target 1 lun 0 (pass1,sg1,cd1)
I have no blank dvd at the hands now to verify growisofs operations.
>=20
> before upgrade, I had 6.3-RELEASE-p3, update to 7.0-RELEASE-p5, and=20
> after to 7.1-PRELEASE #5, it doesn't change anything. drive=20
> configuration in BIOS - too (change only SATA controller ICH10/AHCI).=20
> this IRQ is also used by USB and COM. turning off both in BIOS and/or=20
> kernel change IRQ map, but drive still not work correctly. present or=20
> not ACPI module - doesn't matter too. by the way, COM port I also can't=
=20
> reach (/dev/cuad0), but without interrupt storm in log's (through APCI=20
What do you mean by "cannot reach" ?
> or ISA. even if USB and atapicd is turned off).
>=20
> someone had the same problem?... thanks for attention :)
>=20
>=20
> system info:
>=20
> FreeBSD gx.dnepr.net 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #3: Thu Nov=20
> 13 16:23:09 EET 2008 root@gx.dnepr.net:/usr/obj/usr/src/sys/KERN i386
>=20
> pcib3: <ACPI PCI-PCI bridge> irq 4 at device 28.3 on pci0
> pci3: <ACPI PCI bus> on pcib3
>=20
> atapci0: <JMicron JMB368 UDMA133 controller> port=20
> 0xd040-0xd047,0xd030-0xd033,0xd020-0xd027,0xd010-0xd013,0xd000-0xd00f=20
> irq 4 at device 0.0 on pci3
> atapci0: [ITHREAD]
> ata2: <ATA channel 0> on atapci0
> ata2: [ITHREAD]
>=20
> usb4: <UHCI (generic) USB controller> on uhci3
> usb4: USB revision 1.0
> uhub4: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb4
> uhub4: 2 ports with 2 removable, self powered
> uhci4: <UHCI (generic) USB controller> port 0xf060-0xf07f irq 4 at=20
> device 29.1 on pci0
> uhci4: [GIANT-LOCKED]
> uhci4: [ITHREAD]
>=20
> sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on=
=20
> acpi0
> sio0: type 16550A
>=20
> acd0: DVDR <NEC DVD RW ND-3550A/1.05> at ata2-<master or slave> UDMA33
> cd0 at ata2 bus 0 target 1 lun 0
> cd0: <_NEC DVD_RW ND-3550A 1.05> Removable CD-ROM SCSI-0 device
> cd0: 33.000MB/s transfers
> cd0: Attempt to query device size failed: NOT READY, Medium not present
>=20
> (if media present in boot time - interrupt storm again)
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
--9Iq5ULCa7nGtWwZS
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (FreeBSD)
iEYEARECAAYFAkkoDRwACgkQC3+MBN1Mb4hlQwCcDEEKAfns05FT23hMuQdQ2Pi/
wZ0AoJ+KUito7XRS/iPrYPPJd3iatFkh
=td9T
-----END PGP SIGNATURE-----
--9Iq5ULCa7nGtWwZS--
From owner-freebsd-stable@FreeBSD.ORG Sat Nov 22 23:29:24 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id F32CA106564A
for <freebsd-stable@freebsd.org>; Sat, 22 Nov 2008 23:29:24 +0000 (UTC)
(envelope-from v.velox@vvelox.net)
Received: from vulpes.vvelox.net (vulpes.vvelox.NET [74.200.198.26])
by mx1.freebsd.org (Postfix) with ESMTP id CBEC88FC13
for <freebsd-stable@freebsd.org>; Sat, 22 Nov 2008 23:29:24 +0000 (UTC)
(envelope-from v.velox@vvelox.net)
Received: from vixen42 (c-67-176-214-76.hsd1.il.comcast.net [67.176.214.76])
(Authenticated sender: v.velox)
by vulpes.vvelox.net (Postfix) with ESMTP id 7B34AB82E
for <freebsd-stable@freebsd.org>; Sat, 22 Nov 2008 17:17:58 -0600 (CST)
Date: Sat, 22 Nov 2008 17:11:47 -0600
From: "Zane C.B." <v.velox@vvelox.net>
To: freebsd-stable@freebsd.org
Message-ID: <20081122171147.5fa7f665@vixen42>
X-Mailer: Claws Mail 3.5.0 (GTK+ 2.12.11; i386-portbld-freebsd6.3)
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="Sig_/xH1NaBKZXuqqp7pucWku1lu";
protocol="application/pgp-signature"; micalg=PGP-SHA1
Subject: ddd issue with 6.4-PRERELEASE #2 and udf/cd9660
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Nov 2008 23:29:25 -0000
--Sig_/xH1NaBKZXuqqp7pucWku1lu
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
When ever I try try to mount any burned CD/DVD media I get the error
below.
mount_cd9660 -v /dev/cd0 /mnt
using starting sector 0
mount_cd9660: /dev/cd0: Input/output error
Exit 1
Which in dmesg results in...
g_vfs_done():cd0[READ(offset=3D-2207623839744, length=3D2048)]error =3D 5
This is odd because if I unplug the USB CD drive and plug it into my
netbook running a old RELENG 7.0-STABLE it works. On the machine that
it errors on it has been doing this for any burned CD/DVD media in
either the DVD drive in it or on the USB one I've been testing with.
I know the disk is good as I can mount it on other machines I've
tested it on with the same drive and different drives.
Any one have any ideas?
--Sig_/xH1NaBKZXuqqp7pucWku1lu
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (FreeBSD)
iEYEARECAAYFAkkokb0ACgkQqrJJy0yxYQDYVwCeLGOYU1eOWssB4LI9xCXvt0s6
yhQAoIs5vcI1Zx3YEzfdG1ri8vocqGQA
=vgZI
-----END PGP SIGNATURE-----
--Sig_/xH1NaBKZXuqqp7pucWku1lu--