From owner-freebsd-geom@FreeBSD.ORG Sun May 6 02:46:49 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 6AF2A16A403 for ; Sun, 6 May 2007 02:46:49 +0000 (UTC) (envelope-from ivoras@fer.hr) Received: from palunko.srce.hr (palunko.srce.hr [161.53.2.67]) by mx1.freebsd.org (Postfix) with ESMTP id ED53713C45B for ; Sun, 6 May 2007 02:46:48 +0000 (UTC) (envelope-from ivoras@fer.hr) Received: from [193.198.134.42] (cmung1566.cmu.carnet.hr [193.198.134.42]) by palunko.srce.hr (8.13.8/8.13.8) with ESMTP id l4614aXf017432; Sun, 6 May 2007 03:04:37 +0200 (CEST) Message-ID: <463D2997.2050207@fer.hr> Date: Sun, 06 May 2007 03:04:23 +0200 From: Ivan Voras User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: =?UTF-8?B?RGFnLUVybGluZyBTbcO4cmdyYXY=?= References: <171980743.20070504223126@uzvik.kiev.ua> <125507.38194.qm@web30304.mail.mud.yahoo.com> <86fy6bqocr.fsf@dwp.des.no> In-Reply-To: <86fy6bqocr.fsf@dwp.des.no> X-Enigmail-Version: 0.94.1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigB051F796716AD8B02D55F406" X-Scanned-By: MIMEDefang 2.55 on 161.53.2.67 Cc: freebsd-geom@freebsd.org Subject: Re: graid5 after-reboot problem 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: Sun, 06 May 2007 02:46:49 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigB051F796716AD8B02D55F406 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Dag-Erling Sm=C3=B8rgrav wrote: > Ivan Voras writes: >> Is the write cache in graid5 aware of what happens on the VFS / UFS >> layers (something like gjournal does)? Otherwise, how can you guarante= e >> consistency with write caching at the GEOM layer when there's a power >> outage or some other system interruption? >=20 > You can't. Google for "RAID 5 write hole" for an explanation. It was a rhetorical question :) --------------enigB051F796716AD8B02D55F406 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 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGPSmXldnAQVacBcgRAgk6AKCfoUPOm1TmzicxoGEE5LsgRCNcVQCgtLyh 7EfkINylR0hIyhjrtsGpIVU= =ky+m -----END PGP SIGNATURE----- --------------enigB051F796716AD8B02D55F406-- From owner-freebsd-geom@FreeBSD.ORG Sun May 6 09:26:33 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 AA73C16A400 for ; Sun, 6 May 2007 09:26:33 +0000 (UTC) (envelope-from wilkinsa@obelix.dsto.defence.gov.au) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by mx1.freebsd.org (Postfix) with ESMTP id 18DB713C44B for ; Sun, 6 May 2007 09:26:32 +0000 (UTC) (envelope-from wilkinsa@obelix.dsto.defence.gov.au) Received: from ednmsw510.dsto.defence.gov.au (ednmsw510.dsto.defence.gov.au [131.185.68.11]) by digger1.defence.gov.au (8.13.8/8.13.8) with ESMTP id l469H69F023571 for ; Sun, 6 May 2007 18:47:06 +0930 (CST) Received: from ednex510.dsto.defence.gov.au (ednex510.dsto.defence.gov.au) by ednmsw510.dsto.defence.gov.au (Clearswift SMTPRS 5.2.5) with ESMTP id for ; Sun, 6 May 2007 18:56:24 +0930 Received: from obelix.dsto.defence.gov.au ([203.6.60.208]) by ednex510.dsto.defence.gov.au with Microsoft SMTPSVC(6.0.3790.1830); Sun, 6 May 2007 18:56:23 +0930 Received: from obelix.dsto.defence.gov.au (localhost [127.0.0.1]) by obelix.dsto.defence.gov.au (8.13.8/8.13.8) with ESMTP id l469QBsp034574 for ; Sun, 6 May 2007 17:26:11 +0800 (WST) (envelope-from wilkinsa@obelix.dsto.defence.gov.au) Received: (from wilkinsa@localhost) by obelix.dsto.defence.gov.au (8.13.8/8.13.8/Submit) id l469QAtY034573 for freebsd-geom@freebsd.org; Sun, 6 May 2007 17:26:10 +0800 (WST) (envelope-from wilkinsa) Date: Sun, 6 May 2007 17:26:10 +0800 From: "Wilkinson, Alex" To: freebsd-geom@freebsd.org Message-ID: <20070506092610.GB34390@obelix.dsto.defence.gov.au> Mail-Followup-To: freebsd-geom@freebsd.org References: <171980743.20070504223126@uzvik.kiev.ua> <125507.38194.qm@web30304.mail.mud.yahoo.com> <86fy6bqocr.fsf@dwp.des.no> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <86fy6bqocr.fsf@dwp.des.no> User-Agent: Mutt/1.5.14 (2007-02-12) X-OriginalArrivalTime: 06 May 2007 09:26:24.0052 (UTC) FILETIME=[9D658F40:01C78FC0] X-TM-AS-Product-Ver: SMEX-7.0.0.1526-3.6.1039-15156.001 X-TM-AS-Result: No-6.786900-8.000000-31 Content-Transfer-Encoding: 7bit Subject: Re: graid5 after-reboot problem 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: Sun, 06 May 2007 09:26:33 -0000 0n Sat, May 05, 2007 at 05:31:00PM +0200, Dag-Erling Smrgrav wrote: >Ivan Voras writes: >> Is the write cache in graid5 aware of what happens on the VFS / UFS >> layers (something like gjournal does)? Otherwise, how can you guarantee >> consistency with write caching at the GEOM layer when there's a power >> outage or some other system interruption? > >You can't. Google for "RAID 5 write hole" for an explanation. > >The way this is handled by hardware RAID 5 controllers is that they >keep a journal in the controller's memory (which has its own battery >backup) and replay it when the power returns. If the controller is >fried, you're SOL. > >ZFS uses copy-on-write, so its raidz and raidz2 do not have a "write >hole". "ZFS uses its end-to-end checksums to detect and correct silent data corruption. If a disk returns bad data transiently, ZFS will detect it and retry the read. If the disk is part of a mirror or RAID-Z group, ZFS will both detect and correct the error: it will use the checksum to determine which copy is correct, provide good data to the application, and repair the damaged copy." A good read about this exact issue by sun kernel-fs wizard Jeff Bonwick: [http://blogs.sun.com/bonwick/entry/zfs_end_to_end_data] -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email. From owner-freebsd-geom@FreeBSD.ORG Sun May 6 09:54:49 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 4719916A400; Sun, 6 May 2007 09:54:49 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 0521B13C45D; Sun, 6 May 2007 09:54:48 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 8FE1620A7; Sun, 6 May 2007 11:54:45 +0200 (CEST) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: 0.0/3.0 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on tim.des.no Received: from dwp.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id 8302F208C; Sun, 6 May 2007 11:54:45 +0200 (CEST) Received: by dwp.des.no (Postfix, from userid 1001) id 6AED24A19; Sun, 6 May 2007 11:54:45 +0200 (CEST) From: des@des.no (Dag-Erling =?utf-8?Q?Sm=C3=B8rgrav?=) To: Pawel Jakub Dawidek References: <171980743.20070504223126@uzvik.kiev.ua> <125507.38194.qm@web30304.mail.mud.yahoo.com> <86fy6bqocr.fsf@dwp.des.no> <20070505233053.GE16398@garage.freebsd.pl> Date: Sun, 06 May 2007 11:54:45 +0200 In-Reply-To: <20070505233053.GE16398@garage.freebsd.pl> (Pawel Jakub Dawidek's message of "Sun, 6 May 2007 01:30:53 +0200") Message-ID: <867irmqntm.fsf@dwp.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: Ivan Voras , freebsd-geom@freebsd.org Subject: Re: graid5 after-reboot problem 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: Sun, 06 May 2007 09:54:49 -0000 Pawel Jakub Dawidek writes: > RAID3 is also write-hole safe, btw. How? Any write to a RAID3 requires writing the data to one of the data disks *and* updating the parity disk. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-geom@FreeBSD.ORG Sun May 6 13:01:21 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 8F1AF16A402 for ; Sun, 6 May 2007 13:01:21 +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 EB7B513C483 for ; Sun, 6 May 2007 13:01:18 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 33901456AB; Sun, 6 May 2007 15:01:17 +0200 (CEST) Received: from localhost (154.81.datacomsa.pl [195.34.81.154]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id ECEF145681; Sun, 6 May 2007 15:01:10 +0200 (CEST) Date: Sun, 6 May 2007 15:00:40 +0200 From: Pawel Jakub Dawidek To: Dag-Erling Sm??rgrav Message-ID: <20070506130040.GB2138@garage.freebsd.pl> References: <171980743.20070504223126@uzvik.kiev.ua> <125507.38194.qm@web30304.mail.mud.yahoo.com> <86fy6bqocr.fsf@dwp.des.no> <20070505233053.GE16398@garage.freebsd.pl> <867irmqntm.fsf@dwp.des.no> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="kXdP64Ggrk/fb43R" Content-Disposition: inline In-Reply-To: <867irmqntm.fsf@dwp.des.no> 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.6 required=3.0 tests=BAYES_00 autolearn=ham version=3.0.4 Cc: Ivan Voras , freebsd-geom@freebsd.org Subject: Re: graid5 after-reboot problem 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: Sun, 06 May 2007 13:01:21 -0000 --kXdP64Ggrk/fb43R Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, May 06, 2007 at 11:54:45AM +0200, Dag-Erling Sm??rgrav wrote: > Pawel Jakub Dawidek writes: > > RAID3 is also write-hole safe, btw. >=20 > How? Any write to a RAID3 requires writing the data to one of the > data disks *and* updating the parity disk. The "write hole" problem is so important in RAID5, because RAID5 parity block to update data block. There are few stages of writting a block in RAID5: 1. Read old content of the block you want to write. 2. Read corresponding parity block. 3. XOR parity with old content. 4. XOR parity with new content. 5. Write new content. 6. Write parity. (This could be done by avoiding parity and reading all corresponding data block, but it's way too inefficient, so this short-cut is most popular.) When you lose the power between 5 and 6, you parity will be corrupted and will stay corrupted forever, because none of the further writes will update it correctly (the only exception is when you do full stripe write, then you don't read old parity, just calculate it, because you have all data blocks needed). This is so much different in RAID3. In RAID3 you always do full stripe writes, so it looks like this: 1. Write data to all data disks and parity disk at once. Of course 1 is not atomic, but when you have a power failure, graid3 will synchronize parity component, but even if you decide not to do it, next write to this block will fix inconsistency, which is not the case for RAID5. RAIDZ also does full stripe writes, just like RAID3, but its COW model is what gives always consistent data and not full stripe writes. Also note, that using gjournal on top of graid3 will fix non-atomicity, but gjournal on top of RAID5 won't fix RAID5 non-atomicity. All in all, write hole is not that dangerous if you remember to synchronize parity on unclean shutdown and this is need for RAID5, RAID3, RAID1, RAID4, RAID6, etc. for RAID5 it is just most visible and you can't avoid resynchronization even when you use things like gjournal. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --kXdP64Ggrk/fb43R Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFGPdF4ForvXbEpPzQRAiacAJwOTjE7x85KElucTySsIlGeWwiZPACglyB1 7Nj1cE5shScEvCIhtxufcv8= =g7c8 -----END PGP SIGNATURE----- --kXdP64Ggrk/fb43R-- From owner-freebsd-geom@FreeBSD.ORG Sun May 6 17:56:55 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 97AA516A400 for ; Sun, 6 May 2007 17:56:55 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [82.208.36.70]) by mx1.freebsd.org (Postfix) with ESMTP id 5B51413C4C6 for ; Sun, 6 May 2007 17:56:55 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from localhost (localhost.codelab.cz [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 4564019E02A for ; Sun, 6 May 2007 19:38:30 +0200 (CEST) Received: from [192.168.1.2] (grimm.quip.cz [213.220.192.218]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTP id 6B33A19E027 for ; Sun, 6 May 2007 19:38:27 +0200 (CEST) Message-ID: <463E1296.5060506@quip.cz> Date: Sun, 06 May 2007 19:38:30 +0200 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.12) Gecko/20050915 X-Accept-Language: cz, cs, en, en-us MIME-Version: 1.0 To: freebsd-geom@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: geom command with nonexistent class 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: Sun, 06 May 2007 17:56:55 -0000 Hi, if I try geom command with nonexistent class, geom prints its usage: root@grimm2 ~/# geom blahblah usage: geom blahblah help geom blahblah list [name ...] geom blahblah status [-s] [name ...] geom blahblah load [-v] geom blahblah unload [-v] So it leads to confusing typing errors if somebody write bad class name, but geom prints it's usage instead of error message. Is there any chance to fix it or is it "a feature"? Can geom find all available classes and print error if command is used with nonexistent one? (FreeBSD 6.2-RELEASE-p4) Miroslav Lachman From owner-freebsd-geom@FreeBSD.ORG Mon May 7 11:08:27 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 C5ECD16A4CA for ; Mon, 7 May 2007 11:08:27 +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 B5E1D13C455 for ; Mon, 7 May 2007 11:08:27 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l47B8Q57078638 for ; Mon, 7 May 2007 11:08:26 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l47B8PI5078634 for freebsd-geom@FreeBSD.org; Mon, 7 May 2007 11:08:25 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 7 May 2007 11:08:25 GMT Message-Id: <200705071108.l47B8PI5078634@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: linimon 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, 07 May 2007 11:08:27 -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 10 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 6 problems total. From owner-freebsd-geom@FreeBSD.ORG Wed May 9 15:13:06 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 F0EDB16A402 for ; Wed, 9 May 2007 15:13:06 +0000 (UTC) (envelope-from jonathan_dobbie@mcad.edu) Received: from cliff.mcad.edu (cliff.mcad.edu [150.253.10.35]) by mx1.freebsd.org (Postfix) with ESMTP id BB12713C455 for ; Wed, 9 May 2007 15:13:06 +0000 (UTC) (envelope-from jonathan_dobbie@mcad.edu) Received: from 42.247.mcad.edu (unknown [150.253.42.247]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jdobbie) by cliff.mcad.edu (Postfix) with ESMTP id 601722F6C0 for ; Wed, 9 May 2007 09:43:19 -0500 (CDT) Message-ID: <4641DE02.3000706@mcad.edu> Date: Wed, 09 May 2007 09:43:14 -0500 From: Jonathan Dobbie User-Agent: Thunderbird 2.0.0.0 (Macintosh/20070326) MIME-Version: 1.0 To: freebsd-geom@freebsd.org X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Nesting gvinum? 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, 09 May 2007 15:13:07 -0000 Greetings list (hopefully the correct one). I'm installing my first FreeBSD server in two versions (I think 4.10 was the last one) and I've gotten myself a bit confused by geom. The box is an 850MHz PE Dell with 3 36GB u320 drives, but no RAID card, that will be a syslog server. I was hoping to have something like md+LVM where I could change the size of RAID 5 volumes. Could I have a large gvinum raid-5 volume and then make 3 gvinum volumes on top that could be resized? Also, is there a better fs to use on top of gvinum? Unlinks and file creation "feel" slow to me. I thought about reiser, but my coworker was burned the last time he put it on a production box and we've been rather cautious since. Didn't UFS2 come out for freeBSD a while ago? I'm using the generic kernel right now, as I just installed the box yesterday, so hopefully that will help a bit, but I'm not expecting it to do much for disk access. I know that shelling out the 250$ for a raid card is the best option, but no one with a budget wants to put any money into the box. It's nice to be back working on FreeBSD again. I've been doing 90% OSX and 10% Linux for the past few years, and it is wonderful to be on an OS that is designed as opposed to grown. There are too many things on linux that are just "weird" that people deal without questioning. And OSX... I like OSX, it is a wonderful desktop OS. It's innards make me want to cry. Thanks in advance for the help, relevant config files below: Here is what I set up: /etc/fstab: /dev/mirror/swap none swap sw 0 0 /dev/mirror/root / ufs rw 1 1 /dev/gvinum/logs /var/log ufs rw 1 1 /dev/gvinum/var /var ufs rw 1 1 /dev/gvinum/usr /usr ufs rw 1 1 The mirrors are on s1: a: 508352 2560000 4.2BSD 0 0 0 b: 2560000 0 swap c: 3068352 0 unused 0 0 # "raw" part, don't edit and the gvinum is RAID 5 on s2 # /dev/da1s2: 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 68051340 3068415 vinum c: 68051340 3068415 unused 0 0 # "raw" part, don't edit partition a: partition extends past end of unit partition c: partition extends past end of unit bsdlabel: partition c doesn't start at 0! bsdlabel: An incorrect partition c may cause problems for standard system utilities my config file is: drive Left device /dev/da0s2a drive Center device /dev/da1s2a drive Right device /dev/da2s2a volume logs plex org raid5 256k sd length 10G drive Left sd length 10G drive Center sd length 10G drive Right volume var plex org raid5 256k sd length 50M drive Left sd length 50M drive Center sd length 50M drive Right volume usr plex org raid5 256k sd length 0 drive Left sd length 0 drive Center sd length 0 drive Right From owner-freebsd-geom@FreeBSD.ORG Wed May 9 16:00:12 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 9A25416A400 for ; Wed, 9 May 2007 16:00:12 +0000 (UTC) (envelope-from rick@kiwi-computer.com) Received: from kiwi-computer.com (keira.kiwi-computer.com [63.224.10.3]) by mx1.freebsd.org (Postfix) with SMTP id 2888513C455 for ; Wed, 9 May 2007 16:00:12 +0000 (UTC) (envelope-from rick@kiwi-computer.com) Received: (qmail 22829 invoked by uid 2001); 9 May 2007 16:00:18 -0000 Date: Wed, 9 May 2007 11:00:18 -0500 From: "Rick C. Petty" To: Jonathan Dobbie Message-ID: <20070509160018.GB22504@keira.kiwi-computer.com> References: <4641DE02.3000706@mcad.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4641DE02.3000706@mcad.edu> User-Agent: Mutt/1.4.2.1i Cc: freebsd-geom@freebsd.org Subject: Re: Nesting gvinum? X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rick-freebsd@kiwi-computer.com List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 May 2007 16:00:12 -0000 On Wed, May 09, 2007 at 09:43:14AM -0500, Jonathan Dobbie wrote: > > I was hoping to have something like md+LVM where I could change the size > of RAID 5 volumes. Could I have a large gvinum raid-5 volume and then > make 3 gvinum volumes on top that could be resized? Except for the nesting, this is precisely what gvinum does. Why do you need nesting? Resizing volumes is something gvinum is supposed to be able to do. > Also, is there a better fs to use on top of gvinum? Unlinks and file > creation "feel" slow to me. I thought about reiser, but my coworker was UFS2. It's incredibly fast, even with RAID5 underneath. > burned the last time he put it on a production box and we've been rather > cautious since. I wasn't aware that FreeBSD supported reiser. > Didn't UFS2 come out for freeBSD a while ago? I'm as of 5.0, in the 2002-2003 timeframe. > I know that shelling out the 250$ for a raid card is the best option, > but no one with a budget wants to put any money into the box. Not really. Software RAID has been proven to be faster than hardware numerous times. I read somewhere that this has to do with the transfer blocksize or something. I haven't witnessed this myself, but I've seen gstripe & gmirror outperform RAID0/1 cards. -- Rick C. Petty From owner-freebsd-geom@FreeBSD.ORG Wed May 9 16:22:17 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 7984F16A409 for ; Wed, 9 May 2007 16:22:17 +0000 (UTC) (envelope-from jonathan_dobbie@mcad.edu) Received: from cliff.mcad.edu (cliff.mcad.edu [150.253.10.35]) by mx1.freebsd.org (Postfix) with ESMTP id 41B6713C487 for ; Wed, 9 May 2007 16:22:17 +0000 (UTC) (envelope-from jonathan_dobbie@mcad.edu) Received: from 42.247.mcad.edu (unknown [150.253.42.247]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jdobbie) by cliff.mcad.edu (Postfix) with ESMTP id C5B082F6A2 for ; Wed, 9 May 2007 11:22:16 -0500 (CDT) Message-ID: <4641F533.4000101@mcad.edu> Date: Wed, 09 May 2007 11:22:11 -0500 From: Jonathan Dobbie User-Agent: Thunderbird 2.0.0.0 (Macintosh/20070326) MIME-Version: 1.0 To: freebsd-geom@freebsd.org References: <4641DE02.3000706@mcad.edu> <20070509160018.GB22504@keira.kiwi-computer.com> In-Reply-To: <20070509160018.GB22504@keira.kiwi-computer.com> X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Subject: Re: Nesting gvinum? 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, 09 May 2007 16:22:17 -0000 Rick C. Petty wrote: > On Wed, May 09, 2007 at 09:43:14AM -0500, Jonathan Dobbie wrote: > >> I was hoping to have something like md+LVM where I could change the size >> of RAID 5 volumes. Could I have a large gvinum raid-5 volume and then >> make 3 gvinum volumes on top that could be resized? >> > > Except for the nesting, this is precisely what gvinum does. Why do you > need nesting? Resizing volumes is something gvinum is supposed to be able > to do. > > I thought that it could only resize striped volumes? Would you happen to have a guide handy? If I, say, wanted to resize usr and log to add 20GB to log, could I drop the s0 subdisk from both, resize, readd, sync and then repeat for s1 and s2? >> Also, is there a better fs to use on top of gvinum? Unlinks and file >> creation "feel" slow to me. I thought about reiser, but my coworker was >> > > UFS2. It's incredibly fast, even with RAID5 underneath. > > I used newfs and sysinstall to create all of the partitions, so they should be UFS2, no? >> burned the last time he put it on a production box and we've been rather >> cautious since. >> > > I wasn't aware that FreeBSD supported reiser. > > I was a but surprised as well. *HISTORY* The *mount*/_/*reiserfs* utility first appeared in FreeBSD 6.0. *AUTHORS* The *mount*/_/*reiserfs* utility and manual were written by Jean-Sébastien Pédron >. >> Didn't UFS2 come out for freeBSD a while ago? I'm >> > > as of 5.0, in the 2002-2003 timeframe. > > >> I know that shelling out the 250$ for a raid card is the best option, >> but no one with a budget wants to put any money into the box. >> > > Not really. Software RAID has been proven to be faster than hardware > numerous times. I read somewhere that this has to do with the transfer > blocksize or something. I haven't witnessed this myself, but I've seen > gstripe & gmirror outperform RAID0/1 cards. > > > I'm definitely sold on software RAID for 0 and 1, but it is nice to boot off of RAID 5 and forget that it is there until a drive dies. From owner-freebsd-geom@FreeBSD.ORG Wed May 9 17:11:51 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 7554316A402 for ; Wed, 9 May 2007 17:11:51 +0000 (UTC) (envelope-from rick@kiwi-computer.com) Received: from kiwi-computer.com (keira.kiwi-computer.com [63.224.10.3]) by mx1.freebsd.org (Postfix) with SMTP id 178A213C4B8 for ; Wed, 9 May 2007 17:11:50 +0000 (UTC) (envelope-from rick@kiwi-computer.com) Received: (qmail 24646 invoked by uid 2001); 9 May 2007 17:11:56 -0000 Date: Wed, 9 May 2007 12:11:56 -0500 From: "Rick C. Petty" To: Jonathan Dobbie Message-ID: <20070509171156.GB24152@keira.kiwi-computer.com> References: <4641DE02.3000706@mcad.edu> <20070509160018.GB22504@keira.kiwi-computer.com> <4641F533.4000101@mcad.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4641F533.4000101@mcad.edu> User-Agent: Mutt/1.4.2.1i Cc: freebsd-geom@freebsd.org Subject: Re: Nesting gvinum? X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rick-freebsd@kiwi-computer.com List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 May 2007 17:11:51 -0000 On Wed, May 09, 2007 at 11:22:11AM -0500, Jonathan Dobbie wrote: > Rick C. Petty wrote: > > > > Except for the nesting, this is precisely what gvinum does. Why do you > > need nesting? Resizing volumes is something gvinum is supposed to be able > > to do. > > > I thought that it could only resize striped volumes? Would you happen > to have a guide handy? If I, say, wanted to resize usr and log to add > 20GB to log, could I drop the s0 subdisk from both, resize, readd, sync > and then repeat for s1 and s2? I'm pretty sure you can. If not, Ulf (lulf@) is working on improvements this summer. Now, you weren't expecting to be able to resize the filesystem automatically, were you? If so, I think growfs(1) might work. What I've done with gvinum is move around and "resize" volumes while the system is up. By "resize" I mean I always do a copy to a new volume, then delete the old volume. I'm not sure if gvinum has a "resize" command, although IIRC the plain vinum did. > > UFS2. It's incredibly fast, even with RAID5 underneath. > > > I used newfs and sysinstall to create all of the partitions, so they > should be UFS2, no? If you did a newfs or usied sysinstall from 5.x or later, yes. Read the "-O" option to newfs(8). > > I wasn't aware that FreeBSD supported reiser. > > > I was a but surprised as well. > > *HISTORY* > The *mount*/_/*reiserfs* utility first appeared in FreeBSD 6.0. Well what do you know... scary! > > Not really. Software RAID has been proven to be faster than hardware > > numerous times. I read somewhere that this has to do with the transfer > > blocksize or something. I haven't witnessed this myself, but I've seen > > gstripe & gmirror outperform RAID0/1 cards. > > > I'm definitely sold on software RAID for 0 and 1, but it is nice to boot > off of RAID 5 and forget that it is there until a drive dies. And you can do this with software RAID5 as well. But I understand your argument-- sacrifice speed, flexibility, and price to let the card do all the work. But also, it matters where you decide to put your trust-- some company who made a custom ASIC where I can't view or change the code versus well-written, documented, opensource software... Sure, gvinum has a ways to go to support all the old vinum commands, but it's saved me on a number of occasions already. -- Rick C. Petty From owner-freebsd-geom@FreeBSD.ORG Wed May 9 20:19:06 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 572E416A406 for ; Wed, 9 May 2007 20:19:06 +0000 (UTC) (envelope-from le@freebsd.org) Received: from grace.univie.ac.at (grace.univie.ac.at [131.130.3.115]) by mx1.freebsd.org (Postfix) with ESMTP id 1ADE613C45D for ; Wed, 9 May 2007 20:19:05 +0000 (UTC) (envelope-from le@freebsd.org) Received: from justin.univie.ac.at ([131.130.3.111] helo=justin.univie.ac.at) by grace.univie.ac.at with esmtp (Exim 4.67) (envelope-from ) id 1HlsMs-0005td-8K; Wed, 09 May 2007 22:02:34 +0200 Received: from korben.prv.univie.ac.at ([131.130.7.98]) by justin.univie.ac.at with esmtps (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1HlsMs-0005Zf-3I; Wed, 09 May 2007 22:02:34 +0200 Message-ID: <464228D8.1040806@freebsd.org> Date: Wed, 09 May 2007 22:02:32 +0200 From: Lukas Ertl User-Agent: Thunderbird 2.0.0.0 (X11/20070420) MIME-Version: 1.0 To: Jonathan Dobbie References: <4641DE02.3000706@mcad.edu> In-Reply-To: <4641DE02.3000706@mcad.edu> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-geom@freebsd.org Subject: Re: Nesting gvinum? 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, 09 May 2007 20:19:06 -0000 Jonathan Dobbie wrote: > I was hoping to have something like md+LVM where I could change the size > of RAID 5 volumes. Could I have a large gvinum raid-5 volume and then > make 3 gvinum volumes on top that could be resized? Theoretically, yes, but I've never tried it, and you're likely to run into problems. cheers, le -- Lukas Ertl http://mailbox.univie.ac.at/~le/ le@FreeBSD.org http://people.freebsd.org/~le/ From owner-freebsd-geom@FreeBSD.ORG Wed May 9 20:24:47 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 D137616A400 for ; Wed, 9 May 2007 20:24:47 +0000 (UTC) (envelope-from le@freebsd.org) Received: from grace.univie.ac.at (grace.univie.ac.at [131.130.3.115]) by mx1.freebsd.org (Postfix) with ESMTP id 923BC13C447 for ; Wed, 9 May 2007 20:24:47 +0000 (UTC) (envelope-from le@freebsd.org) Received: from justin.univie.ac.at ([131.130.3.111] helo=justin.univie.ac.at) by grace.univie.ac.at with esmtp (Exim 4.67) (envelope-from ) id 1HlsQp-0006OJ-1a; Wed, 09 May 2007 22:06:39 +0200 Received: from korben.prv.univie.ac.at ([131.130.7.98]) by justin.univie.ac.at with esmtps (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1HlsQo-0005gh-Tq; Wed, 09 May 2007 22:06:39 +0200 Message-ID: <464229CD.9030901@freebsd.org> Date: Wed, 09 May 2007 22:06:37 +0200 From: Lukas Ertl User-Agent: Thunderbird 2.0.0.0 (X11/20070420) MIME-Version: 1.0 To: rick-freebsd@kiwi-computer.com References: <4641DE02.3000706@mcad.edu> <20070509160018.GB22504@keira.kiwi-computer.com> <4641F533.4000101@mcad.edu> <20070509171156.GB24152@keira.kiwi-computer.com> In-Reply-To: <20070509171156.GB24152@keira.kiwi-computer.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Jonathan Dobbie , freebsd-geom@freebsd.org Subject: Re: Nesting gvinum? 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, 09 May 2007 20:24:47 -0000 Rick C. Petty wrote: > And you can do this with software RAID5 as well. You can't boot from a RAID5 gvinum plex currently, and probably never will, as the loader would need to understand all the RAID5 transformations to locate the kernel. cheers, le -- Lukas Ertl http://mailbox.univie.ac.at/~le/ le@FreeBSD.org http://people.freebsd.org/~le/ From owner-freebsd-geom@FreeBSD.ORG Wed May 9 20:28:02 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 5802A16A400 for ; Wed, 9 May 2007 20:28:02 +0000 (UTC) (envelope-from le@freebsd.org) Received: from grace.univie.ac.at (grace.univie.ac.at [131.130.3.115]) by mx1.freebsd.org (Postfix) with ESMTP id 1972C13C45B for ; Wed, 9 May 2007 20:28:01 +0000 (UTC) (envelope-from le@freebsd.org) Received: from justin.univie.ac.at ([131.130.3.111] helo=justin.univie.ac.at) by grace.univie.ac.at with esmtp (Exim 4.67) (envelope-from ) id 1HlsOe-00068e-N6; Wed, 09 May 2007 22:04:24 +0200 Received: from korben.prv.univie.ac.at ([131.130.7.98]) by justin.univie.ac.at with esmtps (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1HlsOe-0005c3-JI; Wed, 09 May 2007 22:04:24 +0200 Message-ID: <46422947.3090301@freebsd.org> Date: Wed, 09 May 2007 22:04:23 +0200 From: Lukas Ertl User-Agent: Thunderbird 2.0.0.0 (X11/20070420) MIME-Version: 1.0 To: rick-freebsd@kiwi-computer.com References: <4641DE02.3000706@mcad.edu> <20070509160018.GB22504@keira.kiwi-computer.com> In-Reply-To: <20070509160018.GB22504@keira.kiwi-computer.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Jonathan Dobbie , freebsd-geom@freebsd.org Subject: Re: Nesting gvinum? 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, 09 May 2007 20:28:02 -0000 Rick C. Petty wrote: > On Wed, May 09, 2007 at 09:43:14AM -0500, Jonathan Dobbie wrote: >> I was hoping to have something like md+LVM where I could change the size >> of RAID 5 volumes. Could I have a large gvinum raid-5 volume and then >> make 3 gvinum volumes on top that could be resized? > > Except for the nesting, this is precisely what gvinum does. Why do you > need nesting? Resizing volumes is something gvinum is supposed to be able > to do. RAID5 plexes (as striped plexes) can't be resized without destroying all the data, although it would be a nice feature, I agree. :-) cheers, le -- Lukas Ertl http://mailbox.univie.ac.at/~le/ le@FreeBSD.org http://people.freebsd.org/~le/ From owner-freebsd-geom@FreeBSD.ORG Wed May 9 20:57:25 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 9F7FD16A404 for ; Wed, 9 May 2007 20:57:25 +0000 (UTC) (envelope-from rick@kiwi-computer.com) Received: from kiwi-computer.com (keira.kiwi-computer.com [63.224.10.3]) by mx1.freebsd.org (Postfix) with SMTP id DCF3413C43E for ; Wed, 9 May 2007 20:57:24 +0000 (UTC) (envelope-from rick@kiwi-computer.com) Received: (qmail 29869 invoked by uid 2001); 9 May 2007 20:57:33 -0000 Date: Wed, 9 May 2007 15:57:33 -0500 From: "Rick C. Petty" To: Lukas Ertl Message-ID: <20070509205733.GA29809@keira.kiwi-computer.com> References: <4641DE02.3000706@mcad.edu> <20070509160018.GB22504@keira.kiwi-computer.com> <4641F533.4000101@mcad.edu> <20070509171156.GB24152@keira.kiwi-computer.com> <464229CD.9030901@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <464229CD.9030901@freebsd.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-geom@freebsd.org Subject: Re: Nesting gvinum? X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rick-freebsd@kiwi-computer.com List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 May 2007 20:57:25 -0000 On Wed, May 09, 2007 at 10:06:37PM +0200, Lukas Ertl wrote: > Rick C. Petty wrote: > > > And you can do this with software RAID5 as well. > > You can't boot from a RAID5 gvinum plex currently, and probably never > will, as the loader would need to understand all the RAID5 > transformations to locate the kernel. Oops, I was thinking of booting from gvinum mirrors, which it can do. -- Rick C. Petty From owner-freebsd-geom@FreeBSD.ORG Wed May 9 21:14: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 8923016A402 for ; Wed, 9 May 2007 21:14:54 +0000 (UTC) (envelope-from jonathan_dobbie@mcad.edu) Received: from cliff.mcad.edu (cliff.mcad.edu [150.253.10.35]) by mx1.freebsd.org (Postfix) with ESMTP id 51FE913C43E for ; Wed, 9 May 2007 21:14:54 +0000 (UTC) (envelope-from jonathan_dobbie@mcad.edu) Received: from 42.247.mcad.edu (unknown [150.253.42.247]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jdobbie) by cliff.mcad.edu (Postfix) with ESMTP id 9BE5C2DAF7 for ; Wed, 9 May 2007 16:14:53 -0500 (CDT) Message-ID: <464239C7.7000606@mcad.edu> Date: Wed, 09 May 2007 16:14:47 -0500 From: Jonathan Dobbie User-Agent: Thunderbird 2.0.0.0 (Macintosh/20070326) MIME-Version: 1.0 To: freebsd-geom@freebsd.org References: <4641DE02.3000706@mcad.edu> <20070509160018.GB22504@keira.kiwi-computer.com> <4641F533.4000101@mcad.edu> <20070509205943.GA850@twoflower.idi.ntnu.no> In-Reply-To: <20070509205943.GA850@twoflower.idi.ntnu.no> X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: Nesting gvinum? 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, 09 May 2007 21:14:54 -0000 Ulf Lilleengen wrote: > On Wed, May 09, 2007 at 11:22:11AM -0500, Jonathan Dobbie wrote: > >> Rick C. Petty wrote: >> >>> On Wed, May 09, 2007 at 09:43:14AM -0500, Jonathan Dobbie wrote: >>> >>> >>>> I was hoping to have something like md+LVM where I could change the size >>>> of RAID 5 volumes. Could I have a large gvinum raid-5 volume and then >>>> make 3 gvinum volumes on top that could be resized? >>>> >>>> >>> Except for the nesting, this is precisely what gvinum does. Why do you >>> need nesting? Resizing volumes is something gvinum is supposed to be able >>> to do. >>> >>> >>> >> I thought that it could only resize striped volumes? Would you happen >> to have a guide handy? If I, say, wanted to resize usr and log to add >> 20GB to log, could I drop the s0 subdisk from both, resize, readd, sync >> and then repeat for s1 and s2? >> > > You can only make them bigger. I wouldn't bet on it to work for raid5 in gvinum, > but it should work for simple plex organisations, although I really need to test > this better to find out what works and don't. But making gvinum handle this > properly is one of my goals this summer. > > To grow the volume, you can add new subdisks to gvinum, and the plex and volume > of that uses that subdisk will be larger. However, you need to run growfs to > grow the _filesystem_ on top of it. > > To shrink gvinum volumes is not possible, but shouldn't be that difficult to > implement in gvinum for the simplest plex organisations. However, you need to > be able to shrink UFS, and that is not supported. > > If you're looking for another fs, you might want to try ZFS, but remember that > it is quite experimental compared to UFS. > > There are some guides on gvinum out there that isn't completely outdated, and > google are able to find most of them. The handbook also gives a more general > guide to gvinum and vinum. > > Thanks, this confirms what I was thinking. I'm not the adventuresome sort when it comes to servers, so UFS will work fine. We're pretty small, so 20GB will probably be enough for our logs for quite a while. If not, it won't be that hard to back things up for a resize. It'd be awesome if you were able to get things to grow. We could then at least put larger drives in one at a time and then grow the arrays. Good luck on your summer projects, geom seems well thought out. I'm looking forward to seeing where it goes. From owner-freebsd-geom@FreeBSD.ORG Wed May 9 21:20:53 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 23A9816A400 for ; Wed, 9 May 2007 21:20:53 +0000 (UTC) (envelope-from lulf@FreeBSD.org) Received: from signal.itea.ntnu.no (signal.itea.ntnu.no [129.241.190.231]) by mx1.freebsd.org (Postfix) with ESMTP id A74C513C455 for ; Wed, 9 May 2007 21:20:52 +0000 (UTC) (envelope-from lulf@FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by signal.itea.ntnu.no (Postfix) with ESMTP id 294B734205; Wed, 9 May 2007 22:59:44 +0200 (CEST) Received: from twoflower.idi.ntnu.no (twoflower.idi.ntnu.no [129.241.104.169]) by signal.itea.ntnu.no (Postfix) with ESMTP; Wed, 9 May 2007 22:59:43 +0200 (CEST) Received: by twoflower.idi.ntnu.no (Postfix, from userid 1002) id D314D1701F; Wed, 9 May 2007 22:59:43 +0200 (CEST) Date: Wed, 9 May 2007 22:59:43 +0200 From: Ulf Lilleengen To: Jonathan Dobbie Message-ID: <20070509205943.GA850@twoflower.idi.ntnu.no> Mail-Followup-To: Jonathan Dobbie , freebsd-geom@freebsd.org References: <4641DE02.3000706@mcad.edu> <20070509160018.GB22504@keira.kiwi-computer.com> <4641F533.4000101@mcad.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4641F533.4000101@mcad.edu> User-Agent: Mutt/1.5.15 (2007-04-06) X-Content-Scanned: with sophos and spamassassin at mailgw.ntnu.no. Cc: freebsd-geom@freebsd.org Subject: Re: Nesting gvinum? X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "..."@twoflower.idi.ntnu.no List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 May 2007 21:20:53 -0000 On Wed, May 09, 2007 at 11:22:11AM -0500, Jonathan Dobbie wrote: > Rick C. Petty wrote: > > On Wed, May 09, 2007 at 09:43:14AM -0500, Jonathan Dobbie wrote: > > > >> I was hoping to have something like md+LVM where I could change the size > >> of RAID 5 volumes. Could I have a large gvinum raid-5 volume and then > >> make 3 gvinum volumes on top that could be resized? > >> > > > > Except for the nesting, this is precisely what gvinum does. Why do you > > need nesting? Resizing volumes is something gvinum is supposed to be able > > to do. > > > > > I thought that it could only resize striped volumes? Would you happen > to have a guide handy? If I, say, wanted to resize usr and log to add > 20GB to log, could I drop the s0 subdisk from both, resize, readd, sync > and then repeat for s1 and s2? You can only make them bigger. I wouldn't bet on it to work for raid5 in gvinum, but it should work for simple plex organisations, although I really need to test this better to find out what works and don't. But making gvinum handle this properly is one of my goals this summer. To grow the volume, you can add new subdisks to gvinum, and the plex and volume of that uses that subdisk will be larger. However, you need to run growfs to grow the _filesystem_ on top of it. To shrink gvinum volumes is not possible, but shouldn't be that difficult to implement in gvinum for the simplest plex organisations. However, you need to be able to shrink UFS, and that is not supported. If you're looking for another fs, you might want to try ZFS, but remember that it is quite experimental compared to UFS. There are some guides on gvinum out there that isn't completely outdated, and google are able to find most of them. The handbook also gives a more general guide to gvinum and vinum. -- Ulf Lilleengen From owner-freebsd-geom@FreeBSD.ORG Fri May 11 08:14: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 5B73116A403 for ; Fri, 11 May 2007 08:14:07 +0000 (UTC) (envelope-from eike@unorganized.net) Received: from segfault.0xC0DE.de (0xc0de.de [81.169.134.74]) by mx1.freebsd.org (Postfix) with ESMTP id 2514113C480 for ; Fri, 11 May 2007 08:14:07 +0000 (UTC) (envelope-from eike@unorganized.net) Received: from localhost (localhost [127.0.0.1]) by segfault.0xC0DE.de (Postfix) with ESMTP id 49C3A49FD for ; Fri, 11 May 2007 09:55:38 +0200 (CEST) X-Virus-Scanned: amavisd-new at 0xC0DE.de Received: from segfault.0xC0DE.de ([127.0.0.1]) by localhost (segfault.0xC0DE.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JcigpdBQ4QYM for ; Fri, 11 May 2007 09:55:36 +0200 (CEST) Received: from [192.168.100.29] (p54812539.dip0.t-ipconnect.de [84.129.37.57]) by segfault.0xC0DE.de (Postfix) with ESMTP id 29B744988 for ; Fri, 11 May 2007 09:55:36 +0200 (CEST) Message-ID: <46442175.60508@unorganized.net> Date: Fri, 11 May 2007 09:55:33 +0200 From: Eike Bernhardt User-Agent: Thunderbird 2.0.0.0 (Macintosh/20070326) MIME-Version: 1.0 To: freebsd-geom@freebsd.org X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Growing a graid3? 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, 11 May 2007 08:14:07 -0000 Hello, is it possible to expand a existing graid3? I have a graid3 consisting of 3x 250GB drives, which is nearly full. My idea would be to swap out each disk one after one with a bigger disk, let the graid3 rebuild itself between swaps, and then use growfs to resize the filesystem to the new availiabale maximum size. Is this possible? Has anyone tried this? Thanks, Eike From owner-freebsd-geom@FreeBSD.ORG Fri May 11 08:40:27 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 4C07F16A403 for ; Fri, 11 May 2007 08:40:27 +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 DC20013C46C for ; Fri, 11 May 2007 08:40:26 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 4317A48809; Fri, 11 May 2007 10:40:25 +0200 (CEST) Received: from localhost (pjd.wheel.pl [10.0.1.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 5B3B845696; Fri, 11 May 2007 10:40:20 +0200 (CEST) Date: Fri, 11 May 2007 10:40:18 +0200 From: Pawel Jakub Dawidek To: Eike Bernhardt Message-ID: <20070511084018.GA38860@garage.freebsd.pl> References: <46442175.60508@unorganized.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ew6BAiZeqk4r7MaW" Content-Disposition: inline In-Reply-To: <46442175.60508@unorganized.net> 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=-5.9 required=3.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-geom@freebsd.org Subject: Re: Growing a graid3? 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, 11 May 2007 08:40:27 -0000 --ew6BAiZeqk4r7MaW Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, May 11, 2007 at 09:55:33AM +0200, Eike Bernhardt wrote: > Hello, >=20 > is it possible to expand a existing graid3? >=20 > I have a graid3 consisting of 3x 250GB drives, which is nearly full. >=20 > My idea would be to swap out each disk one after one with a bigger disk, > let the graid3 rebuild itself between swaps, and then use growfs to > resize the filesystem to the new availiabale maximum size. >=20 > Is this possible? Has anyone tried this? It should be possible. First you swap one disk after another waiting for synchronization. Once you have all new disks in place, you need to relabel your graid3 (it won't touch your data) and then growfs(8) it. You can try it with md(4) devices, eg: # truncate -s 8m /tmp/disk{0,1,2} # mdconfig -a -f /tmp/disk0 -u 0 # mdconfig -a -f /tmp/disk1 -u 1 # mdconfig -a -f /tmp/disk2 -u 2 # graid3 label test md{0,1,2} # newfs /dev/raid3/test # mount /dev/raid3/test /mnt/test # dd if=3D/dev/random of=3D/mnt/test/rand bs=3D1m count=3D12 # dd if=3D/mnt/test/rand bs=3D1m count=3D12 | md5 # umount /mnt/test # truncate -s 16m /tmp/disk{3,4,5} # mdconfig -a -f /tmp/disk3 -u 3 # mdconfig -a -f /tmp/disk4 -u 4 # mdconfig -a -f /tmp/disk5 -u 5 # graid3 remove -n 0 test # graid3 insert -n 0 test md3 [wait] # graid3 remove -n 1 test # graid3 insert -n 1 test md4 [wait] # graid3 remove -n 2 test # graid3 insert -n 2 test md5 [wait] # graid3 stop test # graid3 label test md{3,4,5} # order is very important # mount -o ro /dev/raid3/test /mnt/test # dd if=3D/mnt/test/rand bs=3D1m count=3D12 | md5 # verify if file is ok # umount /mnt/test # growfs /dev/raid3/test # mount -o ro /dev/raid3/test /mnt/test # dd if=3D/mnt/test/rand bs=3D1m count=3D12 | md5 # verify if file is ok a= gain Something like this. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --ew6BAiZeqk4r7MaW Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFGRCvyForvXbEpPzQRAmNDAJ98sfrRhCJfPVT4oECTo/+plHxEaQCfewWe zj1ww19//1ZHbfj3iA6+/IY= =/AGG -----END PGP SIGNATURE----- --ew6BAiZeqk4r7MaW-- From owner-freebsd-geom@FreeBSD.ORG Fri May 11 10:09:12 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 6BAFC16A402; Fri, 11 May 2007 10:09:12 +0000 (UTC) (envelope-from eike@unorganized.net) Received: from physnet.physik.uni-oldenburg.de (physnet.physik.uni-oldenburg.de [134.106.31.103]) by mx1.freebsd.org (Postfix) with ESMTP id 2C45213C459; Fri, 11 May 2007 10:09:12 +0000 (UTC) (envelope-from eike@unorganized.net) Received: by physnet.physik.uni-oldenburg.de (Postfix, from userid 65534) id 6BC6C4080; Fri, 11 May 2007 11:51:15 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on physnet.physik.uni-oldenburg.de X-Spam-Level: X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.8 Received: from [134.106.31.105] (knote.physik.uni-oldenburg.de [134.106.31.105]) by physnet.physik.uni-oldenburg.de (Postfix) with ESMTP id E6A45A8A90; Fri, 11 May 2007 11:51:10 +0200 (CEST) In-Reply-To: <20070511084018.GA38860@garage.freebsd.pl> References: <46442175.60508@unorganized.net> <20070511084018.GA38860@garage.freebsd.pl> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Eike Bernhardt Date: Fri, 11 May 2007 11:51:15 +0200 To: Pawel Jakub Dawidek X-Mailer: Apple Mail (2.752.3) Cc: freebsd-geom@freebsd.org Subject: Re: Growing a graid3? 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, 11 May 2007 10:09:12 -0000 On 11.05.2007, at 10:40, Pawel Jakub Dawidek wrote: > It should be possible. First you swap one disk after another > waiting for > synchronization. Once you have all new disks in place, you need to > relabel your graid3 (it won't touch your data) and then growfs(8) it. > You can try it with md(4) devices, eg: *snip* > # growfs /dev/raid3/test > # mount -o ro /dev/raid3/test /mnt/test > # dd if=/mnt/test/rand bs=1m count=12 | md5 # verify if file is ok > again > > Something like this. Well, I just tried this with md devices, this works fine up to the growfs step: # growfs /dev/raid3/test growfs: we are not growing (8191->8191) # graid3 list test Geom name: test State: COMPLETE Components: 3 Flags: NONE GenID: 0 SyncID: 1 ID: 2225454830 Zone64kFailed: 0 Zone64kRequested: 0 Zone16kFailed: 0 Zone16kRequested: 2 Zone4kFailed: 0 Zone4kRequested: 50 Providers: 1. Name: raid3/test Mediasize: 33553408 (32M) Sectorsize: 1024 Mode: r0w0e0 *snip* So something seems to be missing? Thanks, Eike -- Eike Bernhardt ___ ___ _ _ Institute for Science Networking Oldenburg GmbH |_ _/ __| \| | email: eike.bernhardt@isn-oldenburg.de | |\__ \ .` | http://www.isn-oldenburg.de/ |___|___/_|\_| From owner-freebsd-geom@FreeBSD.ORG Fri May 11 10:50:25 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 EB17216A406 for ; Fri, 11 May 2007 10:50:25 +0000 (UTC) (envelope-from V.Konrad@lse.ac.uk) Received: from mail66.messagelabs.com (mail66.messagelabs.com [193.109.254.35]) by mx1.freebsd.org (Postfix) with SMTP id 3E07113C4B7 for ; Fri, 11 May 2007 10:50:25 +0000 (UTC) (envelope-from V.Konrad@lse.ac.uk) X-VirusChecked: Checked X-Env-Sender: V.Konrad@lse.ac.uk X-Msg-Ref: server-2.tower-66.messagelabs.com!1178879021!10517410!1 X-StarScan-Version: 5.5.10.7.1; banners=-,-,- X-Originating-IP: [158.143.216.143] Received: (qmail 32176 invoked from network); 11 May 2007 10:23:41 -0000 Received: from exchic3.lse.ac.uk (HELO exchic3.lse.ac.uk) (158.143.216.143) by server-2.tower-66.messagelabs.com with SMTP; 11 May 2007 10:23:41 -0000 Received: from EXCHIC2.lse.ac.uk ([158.143.216.142]) by exchic3.lse.ac.uk with Microsoft SMTPSVC(6.0.3790.1830); Fri, 11 May 2007 11:23:34 +0100 Received: from exic4.lse.ac.uk ([158.143.216.121]) by EXCHIC2.lse.ac.uk with Microsoft SMTPSVC(6.0.3790.3959); Fri, 11 May 2007 11:23:34 +0100 Received: from exic6.lse.ac.uk ([158.143.216.123]) by exic4.lse.ac.uk with Microsoft SMTPSVC(5.0.2195.6713); Fri, 11 May 2007 11:23:34 +0100 Received: from whirpool.lse.ac.uk ([158.143.201.19]) by exic6.lse.ac.uk with Microsoft SMTPSVC(5.0.2195.6713); Fri, 11 May 2007 11:23:33 +0100 Date: Fri, 11 May 2007 11:23:35 +0100 From: vladimir konrad To: freebsd-geom@freebsd.org Message-ID: <20070511112335.698620bf@whirpool.lse.ac.uk> In-Reply-To: References: <46442175.60508@unorganized.net> <20070511084018.GA38860@garage.freebsd.pl> Organization: lse X-Mailer: Claws Mail 2.9.2 (GTK+ 2.8.20; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: multipart/signed; boundary=Sig_NQA8UDUZ2zHzcSSLuJr4Ff6; protocol="application/pgp-signature"; micalg=PGP-SHA1 X-OriginalArrivalTime: 11 May 2007 10:23:33.0761 (UTC) FILETIME=[6DBA5F10:01C793B6] Subject: Re: Growing a graid3? 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, 11 May 2007 10:50:26 -0000 --Sig_NQA8UDUZ2zHzcSSLuJr4Ff6 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable > growfs: we are not growing (8191->8191) is there a disk label on the raid? vlad --Sig_NQA8UDUZ2zHzcSSLuJr4Ff6 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGREQs5mQ6ItFTZ8gRAlqtAJ9Xf011OJbhFsuoTjfFzA7twaqclQCdH4w2 /8ATMZYLUR1id3sp9ty8scE= =AA76 -----END PGP SIGNATURE----- --Sig_NQA8UDUZ2zHzcSSLuJr4Ff6-- From owner-freebsd-geom@FreeBSD.ORG Fri May 11 12:14:15 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 D5D3416A400 for ; Fri, 11 May 2007 12:14:15 +0000 (UTC) (envelope-from eike@unorganized.net) Received: from physnet.physik.uni-oldenburg.de (physnet.physik.uni-oldenburg.de [134.106.31.103]) by mx1.freebsd.org (Postfix) with ESMTP id 95D8B13C45D for ; Fri, 11 May 2007 12:14:15 +0000 (UTC) (envelope-from eike@unorganized.net) Received: by physnet.physik.uni-oldenburg.de (Postfix, from userid 65534) id BEEB0E7019; Fri, 11 May 2007 14:14:13 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on physnet.physik.uni-oldenburg.de X-Spam-Level: X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.8 Received: from [134.106.31.105] (knote.physik.uni-oldenburg.de [134.106.31.105]) by physnet.physik.uni-oldenburg.de (Postfix) with ESMTP id 4FD9EE7017 for ; Fri, 11 May 2007 14:14:10 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v752.3) In-Reply-To: <20070511112335.698620bf@whirpool.lse.ac.uk> References: <46442175.60508@unorganized.net> <20070511084018.GA38860@garage.freebsd.pl> <20070511112335.698620bf@whirpool.lse.ac.uk> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Eike Bernhardt Date: Fri, 11 May 2007 14:14:15 +0200 To: freebsd-geom@freebsd.org X-Mailer: Apple Mail (2.752.3) Subject: Re: Growing a graid3? 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, 11 May 2007 12:14:15 -0000 On 11.05.2007, at 12:23, vladimir konrad wrote: >> growfs: we are not growing (8191->8191) > > is there a disk label on the raid? I haven't added one explicitly, just did a graid3 label test md{0,1,2} newfs /dev/raid3/test as stated in Pawel's example and the one in graid3(8) -- Eike Bernhardt ___ ___ _ _ Institute for Science Networking Oldenburg GmbH |_ _/ __| \| | email: eike.bernhardt@isn-oldenburg.de | |\__ \ .` | http://www.isn-oldenburg.de/ |___|___/_|\_| From owner-freebsd-geom@FreeBSD.ORG Fri May 11 16:12:38 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 32CAD16A404 for ; Fri, 11 May 2007 16:12:38 +0000 (UTC) (envelope-from eike@unorganized.net) Received: from segfault.0xC0DE.de (0xc0de.de [81.169.134.74]) by mx1.freebsd.org (Postfix) with ESMTP id E797713C447 for ; Fri, 11 May 2007 16:12:37 +0000 (UTC) (envelope-from eike@unorganized.net) Received: from localhost (localhost [127.0.0.1]) by segfault.0xC0DE.de (Postfix) with ESMTP id 4A19B49FF for ; Fri, 11 May 2007 18:12:36 +0200 (CEST) X-Virus-Scanned: amavisd-new at 0xC0DE.de Received: from segfault.0xC0DE.de ([127.0.0.1]) by localhost (segfault.0xC0DE.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 04h1P0xhVkMd for ; Fri, 11 May 2007 18:12:34 +0200 (CEST) Received: from [192.168.100.29] (p54812539.dip0.t-ipconnect.de [84.129.37.57]) by segfault.0xC0DE.de (Postfix) with ESMTP id 81C934988 for ; Fri, 11 May 2007 18:12:34 +0200 (CEST) Message-ID: <464495F1.4080108@unorganized.net> Date: Fri, 11 May 2007 18:12:33 +0200 From: Eike Bernhardt User-Agent: Thunderbird 2.0.0.0 (Macintosh/20070326) MIME-Version: 1.0 To: freebsd-geom@freebsd.org References: <46442175.60508@unorganized.net> <20070511084018.GA38860@garage.freebsd.pl> <20070511112335.698620bf@whirpool.lse.ac.uk> In-Reply-To: X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: Growing a graid3? 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, 11 May 2007 16:12:38 -0000 On 11.05.2007 14:14 Uhr, Eike Bernhardt wrote: > > On 11.05.2007, at 12:23, vladimir konrad wrote: > >>> growfs: we are not growing (8191->8191) >> >> is there a disk label on the raid? > > I haven't added one explicitly, just did a > > graid3 label test md{0,1,2} > newfs /dev/raid3/test > > as stated in Pawel's example and the one in graid3(8) I just testet this with md devices and gmirror, without adding a disk label -- there growfs works as expected .. ie. resizes the filesystem successfully.