From owner-freebsd-stable@FreeBSD.ORG Sun Jun 29 12:54:18 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3719237B401 for ; Sun, 29 Jun 2003 12:54:18 -0700 (PDT) Received: from cauchy.axista.com (cauchy.axista.com [209.61.216.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9020A44027 for ; Sun, 29 Jun 2003 12:54:17 -0700 (PDT) (envelope-from cce@cauchy.axista.com) Received: by cauchy.axista.com (Postfix, from userid 1000) id BB4AD6CEA1; Sun, 29 Jun 2003 20:12:06 +0000 (GMT) Date: Sun, 29 Jun 2003 20:12:06 +0000 From: "Clark C. Evans" To: freebsd-stable@freebsd.org Message-ID: <20030629201206.GA73157@doublegemini.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i Sender: cce+pub@clarkevans.com Subject: vinum drive referenced / disklabel inconsistency X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jun 2003 19:54:18 -0000 I am trying to setup vinum on a box using 4.8 RELENG_4 (as of about a week ago snapshot). This box was running 4.6 /w vinum on same hard drives for the last 4 months wonderfully... but since it is my current 'scratch/backup' box, I just reinstalled with -STABLE. # uname -a FreeBSD polya.axista.com 4.8-STABLE FreeBSD 4.8-STABLE #22: Tue Jun 24 17:01:07 EDT 2003 cce@cantor.local:/usr/obj/usr/src/sys/GENERIC i386 Anyway, my problems seem to be coming from a disklabel issue. Following the instructions in the handbook (for disk addition), I go through the following steps: # dd if=/dev/zero of=/dev/ad2 bs=1k count=1 # fdisk -BI ad2 # disklabel -B -w -r ad2s1 auto And at this point, I use the following to extract the current label, and then I edit it with vi, and then update it: # disklabel ad2s1 > label # vim label # disklabel -R -r ad2s1 label Following is the tail end of the label (I don't edit anything else) where I add 'swap' and 'vinum' partitions: a: 4193280 0 swap c: 156301425 0 unused 0 0 e: 152107200 4193280 vinum The results, when "restoring" the label, however, are inconsistent, with # disklabel ad2s1 # disklabel ad2 # disklabel -r ad2s1 # disklabel -r ad2 # disklabel /dev/ad2s1 # disklabel -r /dev/ad2s1 the results are expected (and identical): 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 4193280 0 swap # (Cyl. 0 - 4159) c: 156301425 0 unused 0 0 # (Cyl. 0 - 155060*) e: 152107200 4193280 vinum # (Cyl. 4160 - 155059) However, for the other two permutations... the results are different: # disklabel /dev/ad2 8 partitions: # size offset fstype [fsize bsize bps/cpg] c: 156301488 0 unused 0 0 # (Cyl. 0 - 155060) # disklabel -r /dev/ad2 disklabel: bad pack magic number (label is damaged, or pack is unlabeled) At this point, I use the following vinum configuration file to setup vinum "vinum create -f vinum.conf" drive d2 device /dev/ad2s1e volume tmp setupstate plex name tmp.2 org concat sd length 2000m drive d2 And this produces... 1 drives: D d2 State: referenced Device Avail: 0/0 MB 1 volumes: V tmp State: down Plexes: 1 Size: 2000 MB 1 plexes: P tmp.2 C State: faulty Subdisks: 1 Size: 2000 MB 1 subdisks: S tmp.2.s0 State: crashed PO: 0 B Size: 2000 MB And of course, this is where I get stuck... With 4.6 I didn't have any of these problems (from the bad pack magic number to the missing device in the vinum state). Anyway, following is the full output from the disklabel. # disklabel -r /dev/ad2s1 # /dev/ad2s1: type: unknown disk: amnesiac label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 16 sectors/cylinder: 1008 cylinders: 155060 sectors/unit: 156301425 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 4193280 0 swap # (Cyl. 0 - 4159) c: 156301425 0 unused 0 0 # (Cyl. 0 - 155060*) e: 152107200 4193280 vinum # (Cyl. 4160 - 155059) Thank you for any suggestions you may have, Clark From owner-freebsd-stable@FreeBSD.ORG Sun Jun 29 12:58:49 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EB42A37B401 for ; Sun, 29 Jun 2003 12:58:49 -0700 (PDT) Received: from main.gmane.org (main.gmane.org [80.91.224.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id DC9C843FF5 for ; Sun, 29 Jun 2003 12:58:46 -0700 (PDT) (envelope-from freebsd-stable@m.gmane.org) Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 19WiJW-0007D5-00 for ; Sun, 29 Jun 2003 21:58:18 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org Received: from news by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 19WiJR-0007Cd-00 for ; Sun, 29 Jun 2003 21:58:13 +0200 From: Samuel Tardieu Date: Sun, 29 Jun 2003 21:58:22 +0200 Organization: Avian Carrier & Friends Lines: 14 Message-ID: <874r28odup.fsf@inf.enst.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@main.gmane.org Mail-Copies-To: sam@rfc1149.net User-Agent: Gnus/5.090007 (Oort Gnus v0.07) XEmacs/21.5 (cauliflower, i386--freebsd) Cancel-Lock: sha1:SyHHJIKNLQ1V/eAU38eqSeC0brA= Sender: news Subject: IPFilter & IPv6 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jun 2003 19:58:50 -0000 With a up-to-date -STABLE kernel and userland, I cannot use IPv6 rules with IPFilter. # ipf -6 -f /tmp/t 1:ioctl(add/insert rule): No such process Any idea of what could be wrong? Sam PS/ /tmp/t contains "pass out all" for this test, but I get the message with every valid file -- Samuel Tardieu -- sam@rfc1149.net -- http://www.rfc1149.net/sam From owner-freebsd-stable@FreeBSD.ORG Sun Jun 29 14:30:58 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F091437B401 for ; Sun, 29 Jun 2003 14:30:57 -0700 (PDT) Received: from cauchy.axista.com (cauchy.axista.com [209.61.216.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id 451404402B for ; Sun, 29 Jun 2003 14:30:57 -0700 (PDT) (envelope-from cce@cauchy.axista.com) Received: by cauchy.axista.com (Postfix, from userid 1000) id 534146CEA1; Sun, 29 Jun 2003 21:48:47 +0000 (GMT) Date: Sun, 29 Jun 2003 21:48:47 +0000 From: "Clark C. Evans" To: freebsd-stable@freebsd.org Message-ID: <20030629214847.GA73653@doublegemini.com> References: <20030629201206.GA73157@doublegemini.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030629201206.GA73157@doublegemini.com> User-Agent: Mutt/1.4i Sender: cce+pub@clarkevans.com Subject: Re: vinum drive referenced / disklabel inconsistency X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jun 2003 21:30:58 -0000 Perhaps I was being too clever trying to setup a swap partition, beacuse If I change my label so that vinum part is idential to the "unused" part (but assigned to a:) it works. *puzzles* Best, Clark On Sun, Jun 29, 2003 at 08:12:06PM +0000, Clark C. Evans wrote: | I am trying to setup vinum on a box using 4.8 RELENG_4 (as of about a | week ago snapshot). This box was running 4.6 /w vinum on same hard | drives for the last 4 months wonderfully... but since it is my | current 'scratch/backup' box, I just reinstalled with -STABLE. | | # uname -a | FreeBSD polya.axista.com 4.8-STABLE FreeBSD 4.8-STABLE #22: Tue Jun 24 | 17:01:07 EDT 2003 cce@cantor.local:/usr/obj/usr/src/sys/GENERIC i386 | | Anyway, my problems seem to be coming from a disklabel issue. Following | the instructions in the handbook (for disk addition), I go through the | following steps: | | # dd if=/dev/zero of=/dev/ad2 bs=1k count=1 | # fdisk -BI ad2 | # disklabel -B -w -r ad2s1 auto | | And at this point, I use the following to extract the current | label, and then I edit it with vi, and then update it: | | # disklabel ad2s1 > label | # vim label | # disklabel -R -r ad2s1 label | | Following is the tail end of the label (I don't edit anything else) | where I add 'swap' and 'vinum' partitions: | | a: 4193280 0 swap | c: 156301425 0 unused 0 0 | e: 152107200 4193280 vinum | | The results, when "restoring" the label, however, are inconsistent, with | | # disklabel ad2s1 | # disklabel ad2 | # disklabel -r ad2s1 | # disklabel -r ad2 | # disklabel /dev/ad2s1 | # disklabel -r /dev/ad2s1 | | the results are expected (and identical): | | | | 8 partitions: | # size offset fstype [fsize bsize bps/cpg] | a: 4193280 0 swap # (Cyl. 0 - 4159) | c: 156301425 0 unused 0 0 # (Cyl. 0 - 155060*) | e: 152107200 4193280 vinum # (Cyl. 4160 - 155059) | | However, for the other two permutations... the results are different: | | # disklabel /dev/ad2 | | | | 8 partitions: | # size offset fstype [fsize bsize bps/cpg] | c: 156301488 0 unused 0 0 # (Cyl. 0 - 155060) | | # disklabel -r /dev/ad2 | disklabel: bad pack magic number (label is damaged, or pack is unlabeled) | | At this point, I use the following vinum configuration file to | setup vinum "vinum create -f vinum.conf" | | drive d2 device /dev/ad2s1e | volume tmp setupstate | plex name tmp.2 org concat | sd length 2000m drive d2 | | And this produces... | | 1 drives: | D d2 State: referenced Device Avail: 0/0 MB | | 1 volumes: | V tmp State: down Plexes: 1 Size: 2000 MB | | 1 plexes: | P tmp.2 C State: faulty Subdisks: 1 Size: 2000 MB | | 1 subdisks: | S tmp.2.s0 State: crashed PO: 0 B Size: 2000 MB | | | And of course, this is where I get stuck... With 4.6 I didn't have any | of these problems (from the bad pack magic number to the missing device | in the vinum state). Anyway, following is the full output from the | disklabel. | | # disklabel -r /dev/ad2s1 | # /dev/ad2s1: | type: unknown | disk: amnesiac | label: | flags: | bytes/sector: 512 | sectors/track: 63 | tracks/cylinder: 16 | sectors/cylinder: 1008 | cylinders: 155060 | sectors/unit: 156301425 | rpm: 3600 | interleave: 1 | trackskew: 0 | cylinderskew: 0 | headswitch: 0 # milliseconds | track-to-track seek: 0 # milliseconds | drivedata: 0 | | 8 partitions: | # size offset fstype [fsize bsize bps/cpg] | a: 4193280 0 swap # (Cyl. 0 - 4159) | c: 156301425 0 unused 0 0 # (Cyl. 0 - 155060*) | e: 152107200 4193280 vinum # (Cyl. 4160 - 155059) | | Thank you for any suggestions you may have, | | Clark | _______________________________________________ | 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 Sun Jun 29 16:37:36 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A549637B404; Sun, 29 Jun 2003 16:37:36 -0700 (PDT) Received: from cecov.masternet.it (cecov.masternet.it [194.184.65.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0376244008; Sun, 29 Jun 2003 16:37:35 -0700 (PDT) (envelope-from gmarco@scotty.masternet.it) Received: from usul.scotty.masternet.it (freebsd.giovannelli.com [194.184.65.139]) by cecov.masternet.it (8.12.9/8.12.9) with ESMTP id h5TNdLto001847; Mon, 30 Jun 2003 01:39:22 +0200 (CEST) (envelope-from gmarco@scotty.masternet.it) Message-Id: <5.2.1.1.2.20030630013114.0419dc98@194.184.65.7> X-Sender: gmarco@194.184.65.7 (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.2.1 Date: Mon, 30 Jun 2003 01:37:33 +0200 To: Robert Watson From: Gianmarco Giovannelli In-Reply-To: References: <5.2.1.1.2.20030626212835.063e6950@194.184.65.4> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed cc: stable@freebsd.org Subject: Re: apache panics on a recent 4.8-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jun 2003 23:37:37 -0000 At 27/06/2003, Robert Watson wrote: >On Thu, 26 Jun 2003, Gianmarco Giovannelli wrote: > > > Yesterday I begin a couple of update to the latest 4.8-STABLE. After > > that the two boxes continues to go in panics as soon as Apache (1.3 from > > the ports, also freshly recompiled, 2.0.x seems NOT to hang) starts. > > > > I don't know if it is related to the other thread : "Kernel core dump in > > recent 4.8-STABLE" but it is easily reproducible by cvsupping to a today > > -STABLE and then running apache 1.3 ... > > > > Thanks very much for any info you con provide. > >Any chance you have a serial console set up on one or more of the machines >and can copy/paste the panic output into an e-mail? A stack trace from >DDB would also be good; there's quite a decent chapter in the Developer's >Handbook on getting stack traces, etc, from dumps: > >http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html I am organizing for the kernel debugging... In the meantime I have isolated the problem. It starts happening with cvsup of 2003.06.07.00.00.00, infact I have made some world/kernel using the following cvsup date (the ok mean that apache is running fine, the ko it panics the freebsd boxes I have) The tests was made on a P4 -1.7, but the panics happened also on an epia 533, epia 933, 2 boxes with p4 - 2.4 (one with 1.024 ddr ram the other one with 1.024 pc133 ram). 01.06 --> ok 15.06 --> ko 10.06 --> ko 05.06 --> ok ( date=2003.06.05.00.00.00 ) Edit src/sys/modules/hifn/Makefile Add delta 1.2.2.2 2003.06.05.04.13.47 sam Edit src/sys/modules/ubsec/Makefile Add delta 1.2.2.2 2003.06.05.04.13.48 sam 06.06 --> ok ( date=2003.06.06.00.00.00 ) Edit src/lib/libfetch/common.c Add delta 1.7.2.13 2003.06.06.06.45.25 des Edit src/lib/libfetch/common.h Add delta 1.7.2.10 2003.06.06.06.45.25 des Edit src/lib/libfetch/fetch.3 Add delta 1.11.2.28 2003.06.06.06.45.25 des Edit src/lib/libfetch/fetch.c Add delta 1.10.2.14 2003.06.06.06.45.25 des Edit src/lib/libfetch/ftp.c Add delta 1.16.2.31 2003.06.06.06.45.25 des Edit src/lib/libfetch/http.c Add delta 1.13.2.23 2003.06.06.06.45.25 des Edit src/sbin/vinum/commands.c Add delta 1.31.2.6 2003.06.06.05.13.29 grog Edit src/sys/dev/ata/ata-pci.c Add delta 1.32.2.15 2003.06.06.13.27.05 fjoe Edit src/sys/kern/init_main.c Add delta 1.134.2.8 2003.06.06.20.21.32 tegge Edit src/sys/kern/kern_descrip.c Add delta 1.81.2.17 2003.06.06.20.21.32 tegge Edit src/sys/kern/kern_fork.c Add delta 1.72.2.13 2003.06.06.20.21.32 tegge Edit src/sys/sys/filedesc.h Add delta 1.19.2.5 2003.06.06.20.21.32 tegge Edit src/sys/sys/proc.h Add delta 1.99.2.9 2003.06.06.20.21.32 tegge Edit src/usr.bin/fetch/fetch.1 Add delta 1.33.2.12 2003.06.06.06.48.42 des Edit src/usr.bin/fetch/fetch.c Add delta 1.10.2.21 2003.06.06.06.48.42 des 06.07 --> KO ( date=2003.06.07.00.00.00 ) So I presume the panics are related to these changes, even if I can't say why they happens ... Any idea ? Best Regards, Gianmarco Giovannelli , "Unix expert since yesterday" http://www.gufi.org/~gmarco From owner-freebsd-stable@FreeBSD.ORG Sun Jun 29 16:41:56 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4BF2737B401 for ; Sun, 29 Jun 2003 16:41:56 -0700 (PDT) Received: from grummit.biaix.org (86.Red-213-97-212.pooles.rima-tde.net [213.97.212.86]) by mx1.FreeBSD.org (Postfix) with SMTP id A809043F93 for ; Sun, 29 Jun 2003 16:41:53 -0700 (PDT) (envelope-from joan@grummit.biaix.org) Received: (qmail 1626 invoked by uid 1000); 29 Jun 2003 23:38:20 -0000 Date: Mon, 30 Jun 2003 01:38:20 +0200 From: Joan Picanyol i Puig To: freebsd-stable@freebsd.org Message-ID: <20030629233820.GA913@grummit.biaix.org> Mail-Followup-To: freebsd-stable@freebsd.org References: <20030629005708.GB599@grummit.biaix.org> <20030629012003.GN29066@wantadilla.lemis.com> <20030629012411.GA34797@grummit.biaix.org> <20030629020002.GO29066@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030629020002.GO29066@wantadilla.lemis.com> User-Agent: Mutt/1.4i Subject: Re: 'vinum list' wierd output (solved) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jun 2003 23:41:56 -0000 * Greg 'groggy' Lehey [20030629 03:57]: > > As I said, the computer just rebooted. Before that, it said I had -2 > > drives (?). > Ah, do you mean it crashed? Then you should get a dump. I can't. Coincidentally, I need to add this drive to get enough swap :o Besides, I'm not sure I could reproduce it anyway. > > Should I reboot it again before attaching the drive? > Reboot it now and see if you still have the anomaly after restarting > Vinum. Rebooting again has brought things back to normal. > > Will 'vinum attach storage bulk' just work? > I don't understand the question. 'vinum attach' creates relationships > between existing objects. OK (finally) understood it. I issued create with "subdisk length 0 drive storage plex bulk.p0" (Am I correct in assuming I could have done it in two steps, without specifying "plex bulk.p0" in the create file and issuing an 'attach' later?) many thanks -- pica From owner-freebsd-stable@FreeBSD.ORG Sun Jun 29 16:52:07 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D199A37B404; Sun, 29 Jun 2003 16:52:07 -0700 (PDT) Received: from cecov.masternet.it (cecov.masternet.it [194.184.65.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 26DF94400F; Sun, 29 Jun 2003 16:52:06 -0700 (PDT) (envelope-from gmarco@scotty.masternet.it) Received: from usul.scotty.masternet.it (freebsd.giovannelli.com [194.184.65.139]) by cecov.masternet.it (8.12.9/8.12.9) with ESMTP id h5TNrcto001917; Mon, 30 Jun 2003 01:53:43 +0200 (CEST) (envelope-from gmarco@scotty.masternet.it) Message-Id: <5.2.1.1.2.20030630014320.0419dc98@194.184.65.7> X-Sender: gmarco@194.184.65.7 (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.2.1 Date: Mon, 30 Jun 2003 01:51:50 +0200 To: rwatson@freebsd.org, stable@freebsd.org From: Gianmarco Giovannelli In-Reply-To: <5.2.1.1.2.20030630013114.0419dc98@194.184.65.7> References: <5.2.1.1.2.20030626212835.063e6950@194.184.65.4> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed cc: Luigi Rizzo cc: esperti@gufi.org Subject: Re: apache panics on a recent 4.8-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jun 2003 23:52:08 -0000 At 30/06/2003, you wrote: >I am organizing for the kernel debugging... >In the meantime I have isolated the problem. It starts happening with >cvsup of 2003.06.07.00.00.00, infact I have made some world/kernel using >the following cvsup date (the ok mean that apache is running fine, the ko >it panics the freebsd boxes I have) >The tests was made on a P4 -1.7, but the panics happened also on an epia >533, epia 933, 2 boxes with p4 - 2.4 (one with 1.024 ddr ram the other one >with 1.024 pc133 ram). > >01.06 --> ok > >15.06 --> ko >10.06 --> ko > >05.06 --> ok ( date=2003.06.05.00.00.00 ) > > Edit src/sys/modules/hifn/Makefile > Add delta 1.2.2.2 2003.06.05.04.13.47 sam > Edit src/sys/modules/ubsec/Makefile > Add delta 1.2.2.2 2003.06.05.04.13.48 sam > >06.06 --> ok ( date=2003.06.06.00.00.00 ) > > Edit src/lib/libfetch/common.c > Add delta 1.7.2.13 2003.06.06.06.45.25 des > Edit src/lib/libfetch/common.h > Add delta 1.7.2.10 2003.06.06.06.45.25 des > Edit src/lib/libfetch/fetch.3 > Add delta 1.11.2.28 2003.06.06.06.45.25 des > Edit src/lib/libfetch/fetch.c > Add delta 1.10.2.14 2003.06.06.06.45.25 des > Edit src/lib/libfetch/ftp.c > Add delta 1.16.2.31 2003.06.06.06.45.25 des > Edit src/lib/libfetch/http.c > Add delta 1.13.2.23 2003.06.06.06.45.25 des > Edit src/sbin/vinum/commands.c > Add delta 1.31.2.6 2003.06.06.05.13.29 grog > Edit src/sys/dev/ata/ata-pci.c > Add delta 1.32.2.15 2003.06.06.13.27.05 fjoe > Edit src/sys/kern/init_main.c > Add delta 1.134.2.8 2003.06.06.20.21.32 tegge > Edit src/sys/kern/kern_descrip.c > Add delta 1.81.2.17 2003.06.06.20.21.32 tegge > Edit src/sys/kern/kern_fork.c > Add delta 1.72.2.13 2003.06.06.20.21.32 tegge > Edit src/sys/sys/filedesc.h > Add delta 1.19.2.5 2003.06.06.20.21.32 tegge > Edit src/sys/sys/proc.h > Add delta 1.99.2.9 2003.06.06.20.21.32 tegge > Edit src/usr.bin/fetch/fetch.1 > Add delta 1.33.2.12 2003.06.06.06.48.42 des > Edit src/usr.bin/fetch/fetch.c > Add delta 1.10.2.21 2003.06.06.06.48.42 des > >06.07 --> KO ( date=2003.06.07.00.00.00 ) > >So I presume the panics are related to these changes, even if I can't say >why they happens ... >Any idea ? Ok digging any further. It is not apache that panics but "apachectl" and in particular it is the line (at least this line panics, dunno if there are others :-) : eval `limits -e -U www` >/dev/null 2>&1 Infact making a little script in this way: ---> begin <--- #!/bin/sh eval `limits -e -U www` >/dev/null 2>&1 ---> end <--- panics the box too ... Best Regards, Gianmarco Giovannelli , "Unix expert since yesterday" http://www.gufi.org/~gmarco From owner-freebsd-stable@FreeBSD.ORG Sun Jun 29 17:02:53 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6B5C937B401 for ; Sun, 29 Jun 2003 17:02:53 -0700 (PDT) Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB67C43FE0 for ; Sun, 29 Jun 2003 17:02:51 -0700 (PDT) (envelope-from grog@lemis.com) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 5EFAD526A0; Mon, 30 Jun 2003 09:32:49 +0930 (CST) Date: Mon, 30 Jun 2003 09:32:49 +0930 From: Greg 'groggy' Lehey To: freebsd-stable@freebsd.org Message-ID: <20030630000249.GF29066@wantadilla.lemis.com> References: <20030629005708.GB599@grummit.biaix.org> <20030629012003.GN29066@wantadilla.lemis.com> <20030629012411.GA34797@grummit.biaix.org> <20030629020002.GO29066@wantadilla.lemis.com> <20030629233820.GA913@grummit.biaix.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="2nmUZS6EBFTGcnEV" Content-Disposition: inline In-Reply-To: <20030629233820.GA913@grummit.biaix.org> User-Agent: Mutt/1.4i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 Subject: Re: 'vinum list' wierd output (solved) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jun 2003 00:02:53 -0000 --2nmUZS6EBFTGcnEV Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Monday, 30 June 2003 at 1:38:20 +0200, Joan Picanyol i Puig wrote: > * Greg 'groggy' Lehey [20030629 03:57]: >>> Will 'vinum attach storage bulk' just work? >> >> I don't understand the question. 'vinum attach' creates >> relationships between existing objects. > > OK (finally) understood it. I issued create with "subdisk length 0 > drive storage plex bulk.p0" (Am I correct in assuming I could have > done it in two steps, without specifying "plex bulk.p0" in the > create file and issuing an 'attach' later?) I've completely lost track of this question, which I didn't understand in the first place. But it looks as if the answer to your last question is "yes". If you want a real answer, please restate the original question. Greg -- See complete headers for address and phone numbers --2nmUZS6EBFTGcnEV Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (FreeBSD) iD8DBQE+/34pIubykFB6QiMRApOuAJ9URdoiygX9n+SKYKWn1g9sSgwbAQCeOliD M34FeBICqHKjTB5DZgkR0Vk= =lC5H -----END PGP SIGNATURE----- --2nmUZS6EBFTGcnEV-- From owner-freebsd-stable@FreeBSD.ORG Sun Jun 29 17:25:42 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D8F4F37B401 for ; Sun, 29 Jun 2003 17:25:42 -0700 (PDT) Received: from grummit.biaix.org (86.Red-213-97-212.pooles.rima-tde.net [213.97.212.86]) by mx1.FreeBSD.org (Postfix) with SMTP id 1B95144003 for ; Sun, 29 Jun 2003 17:25:41 -0700 (PDT) (envelope-from joan@grummit.biaix.org) Received: (qmail 445 invoked by uid 1000); 30 Jun 2003 00:22:07 -0000 Date: Mon, 30 Jun 2003 02:22:07 +0200 From: Joan Picanyol i Puig To: freebsd-stable@freebsd.org Message-ID: <20030630002207.GA247@grummit.biaix.org> Mail-Followup-To: freebsd-stable@freebsd.org References: <20030629005708.GB599@grummit.biaix.org> <20030629012003.GN29066@wantadilla.lemis.com> <20030629012411.GA34797@grummit.biaix.org> <20030629020002.GO29066@wantadilla.lemis.com> <20030629233820.GA913@grummit.biaix.org> <20030630000249.GF29066@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030630000249.GF29066@wantadilla.lemis.com> User-Agent: Mutt/1.4i Subject: Re: 'vinum list' wierd output (solved) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jun 2003 00:25:43 -0000 * Greg 'groggy' Lehey [20030630 02:00]: > If you want a real answer, please restate the > original question. Q: how do I add my new drive to an existing volume? A: create a drive object, a subdrive object on it and attach it to the volume's plex. Are these equivalent (bulk is the volume's name, storage the drive)? a) drive storage device /dev/ad0s1e subdrive length 0 drive storage name bulk.p0.s1 attach bulk.p0.s1 bulk.p0 b) drive storage device /dev/ad0s1e subdrive length 0 drive storage plex bulk.p0 tks -- pica From owner-freebsd-stable@FreeBSD.ORG Sun Jun 29 18:05:32 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ECFF537B401; Sun, 29 Jun 2003 18:05:32 -0700 (PDT) Received: from cecov.masternet.it (cecov.masternet.it [194.184.65.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id A25CF43FCB; Sun, 29 Jun 2003 18:05:31 -0700 (PDT) (envelope-from gmarco@scotty.masternet.it) Received: from usul.scotty.masternet.it (freebsd.giovannelli.com [194.184.65.139]) by cecov.masternet.it (8.12.9/8.12.9) with ESMTP id h5U17Nto002519; Mon, 30 Jun 2003 03:07:24 +0200 (CEST) (envelope-from gmarco@scotty.masternet.it) Message-Id: <5.2.1.1.2.20030630023229.02fb3eb8@194.184.65.7> X-Sender: gmarco@194.184.65.7 (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.2.1 Date: Mon, 30 Jun 2003 03:05:35 +0200 To: rwatson@freebsd.org, stable@freebsd.org From: Gianmarco Giovannelli In-Reply-To: <5.2.1.1.2.20030630014320.0419dc98@194.184.65.7> References: <5.2.1.1.2.20030630013114.0419dc98@194.184.65.7> <5.2.1.1.2.20030626212835.063e6950@194.184.65.4> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed cc: esperti@gufi.org cc: Luigi Rizzo Subject: Re: apache panics on a recent 4.8-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jun 2003 01:05:33 -0000 At 30/06/2003, Gianmarco Giovannelli wrote: >Infact making a little script in this way: >---> begin <--- >#!/bin/sh > >eval `limits -e -U www` >/dev/null 2>&1 >---> end <--- > >panics the box too ... If you use csh instead of sh it works ... This crashes... ---> begin <--- #!/bin/sh limits -e -U www --> end <--- This doesn't crash ---> begin <--- #!/bin/csh limits -e -U www ---> end <--- A little of kernel debugging: freebsd:/usr/obj/usr/src/sys/FREEBSD# gdb -k GNU gdb 4.18 (FreeBSD) Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd". (kgdb) symbol-file kernel.debug Reading symbols from kernel.debug...Deprecated bfd_read called at /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/dbxread.c line 2627 in elfstab_build_psymtabs Deprecated bfd_read called at /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/dbxread.c line 933 in fill_symbuf done. [...] orm0: