From owner-freebsd-geom@FreeBSD.ORG Mon Jul 2 11:08:36 2007 Return-Path: X-Original-To: freebsd-geom@FreeBSD.org Delivered-To: freebsd-geom@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4169716A421 for ; Mon, 2 Jul 2007 11:08:36 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 19C5E13C480 for ; Mon, 2 Jul 2007 11:08:36 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l62B8Zs8082648 for ; Mon, 2 Jul 2007 11:08:35 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l62B8Yp4082644 for freebsd-geom@FreeBSD.org; Mon, 2 Jul 2007 11:08:34 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 2 Jul 2007 11:08:34 GMT Message-Id: <200707021108.l62B8Yp4082644@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-geom@FreeBSD.org Cc: Subject: Current problem reports assigned to you X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jul 2007 11:08:36 -0000 Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/73177 geom kldload geom_* causes panic due to memory exhaustion o kern/76538 geom [gbde] nfs-write on gbde partition stalls and continue o kern/83464 geom [geom] [patch] Unhandled malloc failures within libgeo o kern/84556 geom [geom] GBDE-encrypted swap causes panic at shutdown o kern/87544 geom [gbde] mmaping large files on a gbde filesystem deadlo o kern/89102 geom [geom_vfs] [panic] panic when forced unmount FS from u o bin/90093 geom fdisk(8) incapable of altering in-core geometry o kern/90582 geom [geom_mirror] [panic] Restore cause panic string (ffs_ o kern/98034 geom [geom] dereference of NULL pointer in acd_geom_detach o kern/104389 geom [geom] [patch] sys/geom/geom_dump.c doesn't encode XML o kern/113419 geom [geom] geom fox multipathing not failing back o misc/113543 geom [geom] [patch] geom(8) utilities don't work inside the o kern/113957 geom [gmirror] gmirror is intermittently reporting a degrad 13 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o bin/78131 geom gbde "destroy" not working. o kern/79251 geom [2TB] newfs fails on 2.6TB gbde device o kern/94632 geom [geom] Kernel output resets input while GELI asks for f kern/105390 geom [geli] filesystem on a md backed by sparse file with s o kern/107707 geom [geom] [patch] add new class geom_xbox360 to slice up p bin/110705 geom gmirror control utility does not exit with correct exi o kern/113790 geom [patch] enable the Camellia block cipher on GEOM ELI ( o kern/113837 geom [geom] unable to access 1024 sector size storage o kern/113885 geom [geom] [patch] improved gmirror balance algorithm 9 problems total. From owner-freebsd-geom@FreeBSD.ORG Mon Jul 2 19:24:16 2007 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5346D16A421 for ; Mon, 2 Jul 2007 19:24:16 +0000 (UTC) (envelope-from harry@yewbarrow.net) Received: from vm.yewbarrow.net (vm.yewbarrow.net [80.68.91.52]) by mx1.freebsd.org (Postfix) with ESMTP id EB18213C489 for ; Mon, 2 Jul 2007 19:24:15 +0000 (UTC) (envelope-from harry@yewbarrow.net) Received: by vm.yewbarrow.net (Postfix, from userid 1000) id 5EF4214A468; Mon, 2 Jul 2007 19:24:14 +0000 (GMT) To: freebsd-geom@freebsd.org References: <963281.43796.qm@web30315.mail.mud.yahoo.com> Organization: GAUDEAMUS X-Op.135: Muss es sein ? Es muss sein X-Attribution: HN From: Harry Newton Date: Mon, 02 Jul 2007 19:24:13 +0000 Message-ID: <87ved2zk0y.fsf@vm.yewbarrow.net> User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.4 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Arne =?iso-8859-1?q?W=F6rner?= Subject: Re: gmirror on a slice uncertainty X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jul 2007 19:24:16 -0000 Arne "W=F6rner" writes: [...] >> > 41929650 =3D=3D 41929587+63 >> > This is the beginning of slice 2 (see fdisk)... >> > I would guess, that slice 2 ends on the last sector of the disk, so th= at >> > gmirror is disturbed (it doesnt know if ad4 or ad4s2 (which share both= the >> > same last sector) is its underlying disk)... >>=20 >> I haven't followed this. If I look at the disk with sysinstall: >>=20 >> Disk name: ad4 FDISK Partiti= on >> Editor >> DISK Geometry: 38913 cyls/255 heads/63 sectors =3D 625137345 sectors >> (305242MB) >>=20=20=20=20=20 >> Offset Size(ST) End Name PType Desc Subty= pe=20 >> Flags >>=20=20=20=20=20 >> 0 63 62 - 12 unused 0 >> 63 41929587 41929649 ad4s1 8 freebsd 165 >> 41929650 583207695 625137344 ad4s2 8 freebsd 165= =20=20=20=20=20 >>=20=20=20=20=20 >> 625137345 5103 625142447 - 12 unused 0 >> > Ohoh... OK - so ad4 and ad4s2 do not share the last sector... > That makes my theory worthless... > >> I see there's space at the end of the disk. The code that produces the >> message is in geom_bsd.c and is: >>=20 >> if (rawoffset !=3D 0 && (off_t)rawoffset !=3D ms->mbroffset) >> printf("WARNING: Expected rawoffset %jd, found %jd\n", >> (intmax_t)ms->mbroffset/dl.d_secsize, >> (intmax_t)rawoffset/dl.d_secsize); >> > Hmm... Dont know what that might mean... I've reinstalled FreeBSD, but with the same slice values as given above. I'm following Arne's suggestion and putting no disklabel on the slice (the idea of having one lay in an abandoned partitioning scheme). What I did exactly was: gmirror label -v home ad4s2 ad6s2 Metadata value stored on ad4s2 Metadata value stored on ad6s2 gmirror load ... and then the machine froze. Looking in the logs, I see: Jul 2 19:23:48 hydra kernel: GEOM_MIRROR: Device home created (id=3D25= 10448576). Jul 2 19:23:48 hydra kernel: GEOM_MIRROR: Device home: provider ad6s2 = detected. Jul 2 19:23:48 hydra kernel: GEOM_MIRROR: Device home: provider ad4s2 = detected. Jul 2 19:23:48 hydra kernel: GEOM_MIRROR: Device home: provider ad6s2 = activated. Jul 2 19:23:48 hydra kernel: GEOM_MIRROR: Device home: provider ad4s2 = activated. Jul 2 19:23:48 hydra kernel: GEOM_MIRROR: Device home: provider mirror= /home launched. Jul 2 19:23:48 hydra kernel: WARNING: Expected rawoffset 0, found 4192= 9650 Jul 2 19:23:48 hydra last message repeated 13 times Jul 2 19:23:48 hydra kernel: GEOM_MIRROR: Cannot add disk mirror/homec= ccccccccccccc to home (error=3D17). Jul 2 19:23:48 hydra kernel: WARNING: Expected rawoffset 0, found 4192= 9650 Jul 2 19:23:48 hydra last message repeated 38 times Jul 2 19:23:48 hydra kernel: WARNING: Device name truncated! (mirror/h= omecccccccccccccccccccccccccccccccccccccccccccccccccccc) Jul 2 19:23:48 hydra kernel: WARNING: Expected rawoffset 0, found 4192= 9650 =20=20=20=20 with the last message repeated over 30 times before the reboot. I repeated this after rebooting and got exactly the same. I then tried: dd if=3D/dev/zero of=3D/dev/ad4s2 bs=3D512 count=3D79 dd if=3D/dev/zero of=3D/dev/ad6s2 bs=3D512 count=3D79 gmirror label -v home ad4s2 ad6s2 Metadata value stored on ad4s2 Metadata value stored on ad6s2 gmirror load GEOM_MIRROR: Device home created (id=3D1852978599). GEOM_MIRROR: Device home: provider ad6s2 detected. GEOM_MIRROR: Device home: provider ad4s2 detected. GEOM_MIRROR: Device home: provider ad6s2 activated. GEOM_MIRROR: Device home: provider ad4s2 activated. GEOM_MIRROR: Device home: provider mirror/home launched. =20=20=20=20 So I am now quite concerned, and cautious about putting any data onto this = machine. Does anyone have any ideas about this, and would you suggest this = is a software bug or faulty hardware ? Thanks - Harry From owner-freebsd-geom@FreeBSD.ORG Wed Jul 4 15:15:36 2007 Return-Path: X-Original-To: geom@freebsd.org Delivered-To: freebsd-geom@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4E94816A477 for ; Wed, 4 Jul 2007 15:15:36 +0000 (UTC) (envelope-from volker@vwsoft.com) Received: from frontmail.ipactive.de (frontmail.maindns.de [85.214.95.103]) by mx1.freebsd.org (Postfix) with ESMTP id DA84D13C465 for ; Wed, 4 Jul 2007 15:15:35 +0000 (UTC) (envelope-from volker@vwsoft.com) Received: from mail.vtec.ipme.de (Q7c8b.q.ppp-pool.de [89.53.124.139]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by frontmail.ipactive.de (Postfix) with ESMTP id 37E4012883F for ; Wed, 4 Jul 2007 16:56:49 +0200 (CEST) Received: from cesar.sz.vwsoft.com (cesar.sz.vwsoft.com [192.168.16.3]) by mail.vtec.ipme.de (Postfix) with ESMTP id EF0E03F468 for ; Wed, 4 Jul 2007 16:53:22 +0200 (CEST) Message-ID: <468BB473.304@vwsoft.com> Date: Wed, 04 Jul 2007 16:53:39 +0200 From: Volker User-Agent: Thunderbird 2.0.0.4 (X11/20070615) MIME-Version: 1.0 To: geom@freebsd.org X-Enigmail-Version: 0.95.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-VWSoft-MailScanner: Found to be clean X-MailScanner-From: volker@vwsoft.com X-ipactive-MailScanner-Information: Please contact the ISP for more information X-ipactive-MailScanner: Found to be clean X-ipactive-MailScanner-From: volker@vwsoft.com Cc: Subject: gjournal size reservation? X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jul 2007 15:15:36 -0000 hej, I've never played with gjournal before and would like to try it to get protection of the root-fs, var and tmp. I'm wondering if someone can answer these simple questions: 1) As I understand, gjournal does not need to run on a filesystem but is also able to journal a whole slice. What are the pro's and con's for running gjournal on a whole slice or per filesystem? 1a) if journaling per filesystem, is gjournal able to use just one journaling area for more than one filesystem? 2) How much space is required for journaling? I'm having space to get the journal into it's own slice or at least a bsd label. The fsys layout is quite simple: slice 1 (10g) / 2G /tmp 2G /var 4G slice 2 (8g) can be used for spare space and for gjournal but I'm unsure how much space to give gjournal. Thanks! Volker From owner-freebsd-geom@FreeBSD.ORG Thu Jul 5 18:44:29 2007 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2F71216A46C for ; Thu, 5 Jul 2007 18:44:29 +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 05C4113C457 for ; Thu, 5 Jul 2007 18:44:28 +0000 (UTC) (envelope-from sbruno@miralink.com) Received: from localhost (localhost.localdomain [127.0.0.1]) by plato.miralink.com (Postfix) with ESMTP id AE13D619E79 for ; Thu, 5 Jul 2007 11:44:28 -0700 (PDT) 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 03185-02 for ; Thu, 5 Jul 2007 11:44:27 -0700 (PDT) Received: from [10.0.0.40] (iago.office.miralink.com [10.0.0.40]) by plato.miralink.com (Postfix) with ESMTP id C818A619E44 for ; Thu, 5 Jul 2007 11:44:27 -0700 (PDT) Message-ID: <468D3C0B.8070203@miralink.com> Date: Thu, 05 Jul 2007 11:44:27 -0700 From: Sean Bruno User-Agent: Thunderbird 1.5.0.12 (X11/20070530) MIME-Version: 1.0 To: freebsd-geom@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DSPAM-Result: Innocent X-DSPAM-Processed: Thu Jul 5 11:44:28 2007 X-DSPAM-Confidence: 0.9997 X-DSPAM-Probability: 0.0000 X-DSPAM-Signature: 468d3c0c102101337958704 X-DSPAM-Factors: 27, X-Virus-Scanned: amavisd-new at X-Spam-Status: No, score=-4.47 tagged_above=-10 required=6.6 autolearn=ham tests=[ALL_TRUSTED=-1.8, AWL=0.029, BAYES_00=-2.599, DSPAM_HAM=-0.1] X-Spam-Score: -4.47 X-Spam-Level: Subject: RAID 1 configuration failure(Provider Too Small) X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jul 2007 18:44:29 -0000 I'm trying to setup a 2 disk RAID 1 on my Dell PE 1850 between two identical Seagate SCSI drives with the howto at: http://www.onlamp.com/pub/a/bsd/2005/11/10/FreeBSD_Basics.html I am able to convert my root drive(da0) to geom and reboot just fine. I am failing when I run: |*gmirror insert gm0 /dev/da1*| The second step of converting the mirror drive of my RAID1 (da1) fails with the same "Provider da1 too small" error no matter what I attempt to do. The drives are reporting exactly the same size according to fdisk(see below). Any ideas here? desdemona# fdisk /dev/da1 ******* Working on device /dev/da1 ******* parameters extracted from in-core disklabel are: cylinders=8924 heads=255 sectors/track=63 (16065 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=8924 heads=255 sectors/track=63 (16065 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: The data for partition 2 is: The data for partition 3 is: The data for partition 4 is: desdemona# fdisk /dev/da0 ******* Working on device /dev/da0 ******* parameters extracted from in-core disklabel are: cylinders=8924 heads=255 sectors/track=63 (16065 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=8924 heads=255 sectors/track=63 (16065 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 143363997 (70001 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 1023/ head 254/ sector 63 The data for partition 2 is: The data for partition 3 is: The data for partition 4 is: From owner-freebsd-geom@FreeBSD.ORG Thu Jul 5 18:47:30 2007 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 05BFB16A400 for ; Thu, 5 Jul 2007 18:47:30 +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 CB16313C44C for ; Thu, 5 Jul 2007 18:47:29 +0000 (UTC) (envelope-from sbruno@miralink.com) Received: from localhost (localhost.localdomain [127.0.0.1]) by plato.miralink.com (Postfix) with ESMTP id A86CF619E79 for ; Thu, 5 Jul 2007 11:47:29 -0700 (PDT) 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 20465-08 for ; Thu, 5 Jul 2007 11:47:28 -0700 (PDT) Received: from [10.0.0.40] (iago.office.miralink.com [10.0.0.40]) by plato.miralink.com (Postfix) with ESMTP id 88218619E44 for ; Thu, 5 Jul 2007 11:47:28 -0700 (PDT) Message-ID: <468D3CC0.4020708@miralink.com> Date: Thu, 05 Jul 2007 11:47:28 -0700 From: Sean Bruno User-Agent: Thunderbird 1.5.0.12 (X11/20070530) MIME-Version: 1.0 To: freebsd-geom@freebsd.org References: <468D3C0B.8070203@miralink.com> In-Reply-To: <468D3C0B.8070203@miralink.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DSPAM-Result: Innocent X-DSPAM-Processed: Thu Jul 5 11:47:29 2007 X-DSPAM-Confidence: 0.9997 X-DSPAM-Probability: 0.0000 X-DSPAM-Signature: 468d3cc1110493219765590 X-DSPAM-Factors: 27, X-Virus-Scanned: amavisd-new at X-Spam-Status: No, score=-4.499 tagged_above=-10 required=6.6 autolearn=ham tests=[ALL_TRUSTED=-1.8, BAYES_00=-2.599, DSPAM_HAM=-0.1] X-Spam-Score: -4.499 X-Spam-Level: Subject: Re: RAID 1 configuration failure(Provider Too Small) X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jul 2007 18:47:30 -0000 Sean Bruno wrote: > > I'm trying to setup a 2 disk RAID 1 on my Dell PE 1850 between two > identical Seagate SCSI drives with the howto at: > http://www.onlamp.com/pub/a/bsd/2005/11/10/FreeBSD_Basics.html > > I am able to convert my root drive(da0) to geom and reboot just fine. > I am failing when I run: > > |*gmirror insert gm0 /dev/da1*| > > > The second step of converting the mirror drive of my RAID1 (da1) fails > with the same "Provider da1 too small" error no matter what I attempt > to do. The drives are reporting exactly the same size according to > fdisk(see below). Any ideas here? > > desdemona# fdisk /dev/da1 > ******* Working on device /dev/da1 ******* > parameters extracted from in-core disklabel are: > cylinders=8924 heads=255 sectors/track=63 (16065 blks/cyl) > > Figures below won't work with BIOS for partitions not in cyl 1 > parameters to be used for BIOS calculations are: > cylinders=8924 heads=255 sectors/track=63 (16065 blks/cyl) > > Media sector size is 512 > Warning: BIOS sector numbering starts with sector 1 > Information from DOS bootblock is: > The data for partition 1 is: > > The data for partition 2 is: > > The data for partition 3 is: > > The data for partition 4 is: > > desdemona# fdisk /dev/da0 > ******* Working on device /dev/da0 ******* > parameters extracted from in-core disklabel are: > cylinders=8924 heads=255 sectors/track=63 (16065 blks/cyl) > > Figures below won't work with BIOS for partitions not in cyl 1 > parameters to be used for BIOS calculations are: > cylinders=8924 heads=255 sectors/track=63 (16065 blks/cyl) > > Media sector size is 512 > Warning: BIOS sector numbering starts with sector 1 > Information from DOS bootblock is: > The data for partition 1 is: > sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) > start 63, size 143363997 (70001 Meg), flag 80 (active) > beg: cyl 0/ head 1/ sector 1; > end: cyl 1023/ head 254/ sector 63 > The data for partition 2 is: > > The data for partition 3 is: > > The data for partition 4 is: > > > _______________________________________________ > freebsd-geom@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-geom > To unsubscribe, send any mail to "freebsd-geom-unsubscribe@freebsd.org" Adding the output of 'gmirror list' desdemona# gmirror list Geom name: gm0 State: COMPLETE Components: 1 Balance: round-robin Slice: 4096 Flags: NONE GenID: 0 SyncID: 1 ID: 1639059843 Providers: 1. Name: mirror/gm0 Mediasize: 73407868416 (68G) Sectorsize: 512 Mode: r6w6e7 Consumers: 1. Name: da0 Mediasize: 73407868928 (68G) Sectorsize: 512 Mode: r1w1e1 State: ACTIVE Priority: 0 Flags: DIRTY GenID: 0 SyncID: 1 ID: 3049063106 From owner-freebsd-geom@FreeBSD.ORG Thu Jul 5 18:48:26 2007 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9DF4816A41F for ; Thu, 5 Jul 2007 18:48:26 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.freebsd.org (Postfix) with ESMTP id 42E3113C45B for ; Thu, 5 Jul 2007 18:48:25 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id D0E3F45696; Thu, 5 Jul 2007 20:48:23 +0200 (CEST) Received: from localhost (axn162.internetdsl.tpnet.pl [83.18.91.162]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 706DB45681; Thu, 5 Jul 2007 20:48:17 +0200 (CEST) Date: Thu, 5 Jul 2007 20:48:11 +0200 From: Pawel Jakub Dawidek To: Sean Bruno Message-ID: <20070705184811.GA950@garage.freebsd.pl> References: <468D3C0B.8070203@miralink.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="rwEMma7ioTxnRzrJ" Content-Disposition: inline In-Reply-To: <468D3C0B.8070203@miralink.com> X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 User-Agent: mutt-ng/devel-r804 (FreeBSD) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-2.5 required=3.0 tests=BAYES_00,RCVD_IN_NJABL_DUL autolearn=no version=3.0.4 Cc: freebsd-geom@freebsd.org Subject: Re: RAID 1 configuration failure(Provider Too Small) X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jul 2007 18:48:26 -0000 --rwEMma7ioTxnRzrJ Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jul 05, 2007 at 11:44:27AM -0700, Sean Bruno wrote: >=20 > I'm trying to setup a 2 disk RAID 1 on my Dell PE 1850 between two identi= cal Seagate SCSI drives with the howto at:=20 > http://www.onlamp.com/pub/a/bsd/2005/11/10/FreeBSD_Basics.html >=20 > I am able to convert my root drive(da0) to geom and reboot just fine. I = am failing when I run: >=20 > |*gmirror insert gm0 /dev/da1*| >=20 >=20 > The second step of converting the mirror drive of my RAID1 (da1) fails wi= th the same "Provider da1 too small" error no matter what I attempt to do. = The drives are=20 > reporting exactly the same size according to fdisk(see below). Any ideas= here? fdisk? You are operating on raw disks, so it doesn't matter what fdisk(8) reports. Compare disk sizes with diskinfo(8). --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --rwEMma7ioTxnRzrJ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFGjTzrForvXbEpPzQRAnNLAKDBEMGzqnhMTtp/pv8Qn1OZ3L7q4wCeMc+/ pNB2hxGMTtkixUsEeL5Rem8= =osND -----END PGP SIGNATURE----- --rwEMma7ioTxnRzrJ-- From owner-freebsd-geom@FreeBSD.ORG Thu Jul 5 19:06:07 2007 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0B2B416A400 for ; Thu, 5 Jul 2007 19:06:07 +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 DB65113C487 for ; Thu, 5 Jul 2007 19:06:06 +0000 (UTC) (envelope-from sbruno@miralink.com) Received: from localhost (localhost.localdomain [127.0.0.1]) by plato.miralink.com (Postfix) with ESMTP id 9372A619B57 for ; Thu, 5 Jul 2007 12:06:06 -0700 (PDT) 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 19918-10 for ; Thu, 5 Jul 2007 12:06:05 -0700 (PDT) Received: from [10.0.0.40] (iago.office.miralink.com [10.0.0.40]) by plato.miralink.com (Postfix) with ESMTP id 831196199BA for ; Thu, 5 Jul 2007 12:06:05 -0700 (PDT) Message-ID: <468D411D.8070400@miralink.com> Date: Thu, 05 Jul 2007 12:06:05 -0700 From: Sean Bruno User-Agent: Thunderbird 1.5.0.12 (X11/20070530) MIME-Version: 1.0 To: freebsd-geom@freebsd.org References: <468D3C0B.8070203@miralink.com> <20070705184811.GA950@garage.freebsd.pl> In-Reply-To: <20070705184811.GA950@garage.freebsd.pl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DSPAM-Result: Innocent X-DSPAM-Processed: Thu Jul 5 12:06:06 2007 X-DSPAM-Confidence: 0.6768 X-DSPAM-Probability: 0.0000 X-DSPAM-Signature: 468d411e186191336712104 X-DSPAM-Factors: 27, X-Virus-Scanned: amavisd-new at X-Spam-Status: No, score=-4.499 tagged_above=-10 required=6.6 autolearn=ham tests=[ALL_TRUSTED=-1.8, BAYES_00=-2.599, DSPAM_HAM=-0.1] X-Spam-Score: -4.499 X-Spam-Level: Subject: Re: RAID 1 configuration failure(Provider Too Small) X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jul 2007 19:06:07 -0000 Pawel Jakub Dawidek wrote: > On Thu, Jul 05, 2007 at 11:44:27AM -0700, Sean Bruno wrote: > >> I'm trying to setup a 2 disk RAID 1 on my Dell PE 1850 between two identical Seagate SCSI drives with the howto at: >> http://www.onlamp.com/pub/a/bsd/2005/11/10/FreeBSD_Basics.html >> >> I am able to convert my root drive(da0) to geom and reboot just fine. I am failing when I run: >> >> |*gmirror insert gm0 /dev/da1*| >> >> >> The second step of converting the mirror drive of my RAID1 (da1) fails with the same "Provider da1 too small" error no matter what I attempt to do. The drives are >> reporting exactly the same size according to fdisk(see below). Any ideas here? >> > > fdisk? You are operating on raw disks, so it doesn't matter what > fdisk(8) reports. Compare disk sizes with diskinfo(8). > > Ah...thanks! That makes more sense. I guess I'll re-install on the smaller drive and then mirror to the larger one? Does that sound reasonable? desdemona# diskinfo da0 da1 da0 512 73407868928 143374744 8924 255 63 da1 512 73407820800 143374650 8924 255 63 Sean From owner-freebsd-geom@FreeBSD.ORG Thu Jul 5 23:53:54 2007 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 42A4716A421 for ; Thu, 5 Jul 2007 23:53:54 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.freebsd.org (Postfix) with ESMTP id D799413C45D for ; Thu, 5 Jul 2007 23:53:53 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 151A645B26; Fri, 6 Jul 2007 01:53:52 +0200 (CEST) Received: from localhost (axn162.internetdsl.tpnet.pl [83.18.91.162]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 5153545696; Fri, 6 Jul 2007 01:53:38 +0200 (CEST) Date: Fri, 6 Jul 2007 01:53:22 +0200 From: Pawel Jakub Dawidek To: Sean Bruno Message-ID: <20070705235322.GB950@garage.freebsd.pl> References: <468D3C0B.8070203@miralink.com> <20070705184811.GA950@garage.freebsd.pl> <468D411D.8070400@miralink.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="hQiwHBbRI9kgIhsi" Content-Disposition: inline In-Reply-To: <468D411D.8070400@miralink.com> X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 User-Agent: mutt-ng/devel-r804 (FreeBSD) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-2.5 required=3.0 tests=BAYES_00,RCVD_IN_NJABL_DUL autolearn=no version=3.0.4 Cc: freebsd-geom@freebsd.org Subject: Re: RAID 1 configuration failure(Provider Too Small) X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jul 2007 23:53:54 -0000 --hQiwHBbRI9kgIhsi Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jul 05, 2007 at 12:06:05PM -0700, Sean Bruno wrote: > Pawel Jakub Dawidek wrote: > >On Thu, Jul 05, 2007 at 11:44:27AM -0700, Sean Bruno wrote: > > =20 > >>I'm trying to setup a 2 disk RAID 1 on my Dell PE 1850 between two iden= tical Seagate SCSI drives with the howto at:=20 > >>http://www.onlamp.com/pub/a/bsd/2005/11/10/FreeBSD_Basics.html > >> > >>I am able to convert my root drive(da0) to geom and reboot just fine. = I am failing when I run: > >> > >>|*gmirror insert gm0 /dev/da1*| > >> > >> > >>The second step of converting the mirror drive of my RAID1 (da1) fails = with the same "Provider da1 too small" error no matter what I attempt to do= =2E The drives are=20 > >>reporting exactly the same size according to fdisk(see below). Any ide= as here? > >> =20 > > > >fdisk? You are operating on raw disks, so it doesn't matter what > >fdisk(8) reports. Compare disk sizes with diskinfo(8). > > > > =20 > Ah...thanks! That makes more sense. I guess I'll re-install on the smal= ler drive and then mirror to the larger one? Does that sound reasonable? >=20 > desdemona# diskinfo da0 da1 > da0 512 73407868928 143374744 8924 255 63 > da1 512 73407820800 143374650 8924 255 63 Yes, you can always insert bigger disk. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --hQiwHBbRI9kgIhsi Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFGjYRyForvXbEpPzQRAp8BAJwJmTGzcGI4lZ3u0LYP8mufCUpq/wCfcFW/ OIb9lm1NHg2vIKk3Qb07JlE= =jFIl -----END PGP SIGNATURE----- --hQiwHBbRI9kgIhsi-- From owner-freebsd-geom@FreeBSD.ORG Fri Jul 6 09:25:26 2007 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7E26816A46D for ; Fri, 6 Jul 2007 09:25:26 +0000 (UTC) (envelope-from gcubfg-freebsd-geom@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 0AE0313C4AD for ; Fri, 6 Jul 2007 09:25:25 +0000 (UTC) (envelope-from gcubfg-freebsd-geom@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1I6k41-0005dH-OV for freebsd-geom@freebsd.org; Fri, 06 Jul 2007 11:25:21 +0200 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 ; Fri, 06 Jul 2007 11:25:21 +0200 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 06 Jul 2007 11:25:21 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-geom@freebsd.org From: Ivan Voras Date: Fri, 06 Jul 2007 11:25:13 +0200 Lines: 54 Message-ID: References: <468BB473.304@vwsoft.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig30FB7E062D6BCD30B90D44F5" X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Thunderbird 1.5.0.12 (X11/20060911) In-Reply-To: <468BB473.304@vwsoft.com> X-Enigmail-Version: 0.94.2.0 Sender: news Subject: Re: gjournal size reservation? X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jul 2007 09:25:26 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig30FB7E062D6BCD30B90D44F5 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Volker wrote: > hej, >=20 > I've never played with gjournal before and would like to try it to get > protection of the root-fs, var and tmp. I'm wondering if someone can > answer these simple questions: >=20 > 1) As I understand, gjournal does not need to run on a filesystem but > is also able to journal a whole slice. What are the pro's and con's > for running gjournal on a whole slice or per filesystem? In either case the journaling is "per slice", the "on a filesystem" mode = is mostly just a convenience shortcut for the users so they don't need=20 to set a gjournal slice separately. > 1a) if journaling per filesystem, is gjournal able to use just one > journaling area for more than one filesystem? Almose certainly no. > 2) How much space is required for journaling? I'm having space to get > the journal into it's own slice or at least a bsd label. > slice 2 (8g) can be used for spare space and for gjournal but I'm > unsure how much space to give gjournal. The calculation for this involves disk bandwidth multiplied by the=20 "journal flush interval", multiplied by two because there are two=20 journal areas, and it's usually recommended that it should be at least 1 = GB. --------------enig30FB7E062D6BCD30B90D44F5 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.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGjgp5ldnAQVacBcgRAp2+AKC7c49cpiGxJ8dVRww7/W99AQSMKwCeJgsp 1zr2+h7Dzh1NnBnAZeQJ4TU= =eGVP -----END PGP SIGNATURE----- --------------enig30FB7E062D6BCD30B90D44F5-- From owner-freebsd-geom@FreeBSD.ORG Sat Jul 7 22:11:16 2007 Return-Path: X-Original-To: geom@freebsd.org Delivered-To: freebsd-geom@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 84EF716A41F for ; Sat, 7 Jul 2007 22:11:16 +0000 (UTC) (envelope-from volker@vwsoft.com) Received: from frontmail.ipactive.de (frontmail.maindns.de [85.214.95.103]) by mx1.freebsd.org (Postfix) with ESMTP id 212AF13C45B for ; Sat, 7 Jul 2007 22:11:15 +0000 (UTC) (envelope-from volker@vwsoft.com) Received: from mail.vtec.ipme.de (Q7c4d.q.ppp-pool.de [89.53.124.77]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by frontmail.ipactive.de (Postfix) with ESMTP id EB1DB12883F for ; Sun, 8 Jul 2007 00:11:08 +0200 (CEST) Received: from cesar.sz.vwsoft.com (unknown [192.168.18.3]) by mail.vtec.ipme.de (Postfix) with ESMTP id 38C1E3F45B; Sun, 8 Jul 2007 00:08:08 +0200 (CEST) Message-ID: <46900ED9.1060206@vwsoft.com> Date: Sun, 08 Jul 2007 00:08:25 +0200 From: Volker User-Agent: Thunderbird 2.0.0.4 (X11/20070615) MIME-Version: 1.0 To: Ivan Voras X-Enigmail-Version: 0.95.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-VWSoft-MailScanner: Found to be clean X-MailScanner-From: volker@vwsoft.com X-ipactive-MailScanner-Information: Please contact the ISP for more information X-ipactive-MailScanner: Found to be clean X-ipactive-MailScanner-From: volker@vwsoft.com Cc: geom@freebsd.org Subject: Re: gjournal size reservation? X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Jul 2007 22:11:16 -0000 Ivan, thanks for your answer. Much appreciated. I initially thought this goes into my fabulous series of never been answered questions... ;) >> > I've never played with gjournal before and would like to try it to get >> > protection of the root-fs, var and tmp. I'm wondering if someone can >> > answer these simple questions: >> > >> > 1) As I understand, gjournal does not need to run on a filesystem but >> > is also able to journal a whole slice. What are the pro's and con's >> > for running gjournal on a whole slice or per filesystem? > > In either case the journaling is "per slice", the "on a filesystem" mode > is mostly just a convenience shortcut for the users so they don't need > to set a gjournal slice separately. > >> > 1a) if journaling per filesystem, is gjournal able to use just one >> > journaling area for more than one filesystem? > > Almose certainly no. Ok, short after asking my questions, I figured it out myself. gjournal is responding with an error message when trying to use the same area for more than one journal. Will this change one time in the future? >> > 2) How much space is required for journaling? I'm having space to get >> > the journal into it's own slice or at least a bsd label. > >> > slice 2 (8g) can be used for spare space and for gjournal but I'm >> > unsure how much space to give gjournal. > > The calculation for this involves disk bandwidth multiplied by the > "journal flush interval", multiplied by two because there are two > journal areas, and it's usually recommended that it should be at least 1 > GB. hmm, this calculation sounds like it's valid for busy server machines but is it valid as a general rule of thumb? On my typical desktop (and even on my typical router/proxy/mailserver etc), there's not that much traffic on the disk bus so I would tend to use a smaller size (< 1GB). Do you generally recommend to use data + journal on one single provider and let gjournal take care of all the calculations? Thx, Volker