From owner-freebsd-geom@FreeBSD.ORG Sun Sep 10 17:36:52 2006 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4D6CA16A47E for ; Sun, 10 Sep 2006 17:36:52 +0000 (UTC) (envelope-from matled@gmx.net) Received: from moooo.ath.cx (moooo.ath.cx [85.116.203.178]) by mx1.FreeBSD.org (Postfix) with ESMTP id BAB1D43D70 for ; Sun, 10 Sep 2006 17:36:45 +0000 (GMT) (envelope-from matled@gmx.net) Date: Sun, 10 Sep 2006 19:36:43 +0200 From: Matthias Lederhofer To: freebsd-geom@freebsd.org Message-ID: <20060910173643.GA22815@moooo.ath.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: [PATCH] geli: command to set the boot flag 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, 10 Sep 2006 17:36:52 -0000 I did not find any way to set the boot flag other than init. Here is a patch adding a new command setboot which shows the current value when only a provider is passed or sets it to the value specified on the command line. Probably this should have another name and/or another way to pass the parameters, I can also change this if someone tells me how this should be done. --- geom_eli.c | 109 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 files changed, 109 insertions(+), 0 deletions(-) diff --git a/geom_eli.c b/geom_eli.c index 07026fc..f90e974 100644 --- a/geom_eli.c +++ b/geom_eli.c @@ -71,6 +71,7 @@ static void eli_backup(struct gctl_req * static void eli_restore(struct gctl_req *req); static void eli_clear(struct gctl_req *req); static void eli_dump(struct gctl_req *req); +static void eli_setboot(struct gctl_req *req); /* * Available commands: @@ -191,6 +192,9 @@ struct g_command class_commands[] = { { "dump", G_FLAG_VERBOSE, eli_main, G_NULL_OPTS, "[-v] prov ..." }, + { "setboot", G_FLAG_VERBOSE, eli_main, G_NULL_OPTS, + "[-v] prov [value]" + }, G_CMD_SENTINEL }; @@ -251,6 +255,8 @@ eli_main(struct gctl_req *req, unsigned eli_dump(req); else if (strcmp(name, "clear") == 0) eli_clear(req); + else if (strcmp(name, "setboot") == 0) + eli_setboot(req); else gctl_error(req, "Unknown command: %s.", name); } @@ -1129,3 +1135,106 @@ eli_dump(struct gctl_req *req) printf("\n"); } } + +static void +eli_setboot(struct gctl_req *req) +{ + struct g_eli_metadata md; + const char *prov; + unsigned secsize; + unsigned char *sector; + off_t mediasize; + int nargs, provfd, value; + + value = -1; + nargs = gctl_get_int(req, "nargs"); + if (nargs == 2) { + const char *arg = gctl_get_ascii(req, "arg1"); + if (!strcmp(arg, "0")) { + value = 0; + } else if (!strcmp(arg, "1")) { + value = 1; + } else { + gctl_error(req, "Invalid argument for the new value."); + return; + } + } else if (nargs != 1) { + gctl_error(req, "Invalid number of arguments."); + return; + } + prov = gctl_get_ascii(req, "arg0"); + + provfd = -1; + sector = NULL; + secsize = 0; + + provfd = open(prov, (value == -1) ? O_RDONLY : O_RDWR); + if (provfd == -1 && errno == ENOENT && prov[0] != '/') { + char devprov[MAXPATHLEN]; + + snprintf(devprov, sizeof(devprov), "%s%s", _PATH_DEV, prov); + provfd = open(devprov, (value == -1) ? O_RDONLY : O_RDWR); + } + if (provfd == -1) { + gctl_error(req, "Cannot open %s: %s.", prov, strerror(errno)); + return; + } + + mediasize = g_get_mediasize(prov); + secsize = g_get_sectorsize(prov); + if (mediasize == 0 || secsize == 0) { + gctl_error(req, "Cannot get informations about %s: %s.", prov, + strerror(errno)); + return; + } + + sector = malloc(secsize); + if (sector == NULL) { + gctl_error(req, "Cannot allocate memory."); + return; + } + + /* Read metadata from the provider. */ + if (pread(provfd, sector, secsize, mediasize - secsize) != + (ssize_t)secsize) { + gctl_error(req, "Cannot read metadata: %s.", strerror(errno)); + goto out; + } + /* Check if this is geli provider. */ + if (eli_metadata_decode(sector, &md) != 0) { + gctl_error(req, "MD5 hash mismatch: not a geli provider?"); + goto out; + } + /* Show current value. */ + if (value == -1) { + printf("boot flag: %d\n", !!(md.md_flags & G_ELI_FLAG_BOOT)); + goto out; + } + /* Don't actually rewrite the metadata, nothing to change. */ + if ((value && (md.md_flags & G_ELI_FLAG_BOOT)) || + (!value && !(md.md_flags & G_ELI_FLAG_BOOT))) { + printf("boot flag: %d -> %d\n", + !!(md.md_flags & G_ELI_FLAG_BOOT), + !!(md.md_flags & G_ELI_FLAG_BOOT)); + goto out; + } + /* Toggle bootflag. */ + printf("boot flag: %d -> %d\n", + !!(md.md_flags & G_ELI_FLAG_BOOT), + !(md.md_flags & G_ELI_FLAG_BOOT)); + md.md_flags ^= G_ELI_FLAG_BOOT; + eli_metadata_encode(&md, sector); + /* Write metadata to the provider. */ + if (pwrite(provfd, sector, secsize, mediasize - secsize) != + (ssize_t)secsize) { + gctl_error(req, "Cannot write metadata: %s.", strerror(errno)); + goto out; + } +out: + if (provfd > 0) + close(provfd); + if (sector != NULL) { + bzero(sector, secsize); + free(sector); + } +} -- 1.4.1 From owner-freebsd-geom@FreeBSD.ORG Sun Sep 10 17:49:14 2006 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BEF1316A407 for ; Sun, 10 Sep 2006 17:49:14 +0000 (UTC) (envelope-from matled@gmx.net) Received: from moooo.ath.cx (moooo.ath.cx [85.116.203.178]) by mx1.FreeBSD.org (Postfix) with ESMTP id 545B043D76 for ; Sun, 10 Sep 2006 17:49:10 +0000 (GMT) (envelope-from matled@gmx.net) Date: Sun, 10 Sep 2006 19:49:08 +0200 From: Matthias Lederhofer To: freebsd-geom@freebsd.org Message-ID: <20060910174908.GA26715@moooo.ath.cx> References: <20060910173643.GA22815@moooo.ath.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060910173643.GA22815@moooo.ath.cx> Subject: Re: [PATCH] geli: command to set the boot flag 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, 10 Sep 2006 17:49:14 -0000 Matthias Lederhofer wrote: > diff --git a/geom_eli.c b/geom_eli.c This is for src/sbin/geam/class/eli. And here is another patch for a comment I found while reading the source, probably this was copied 'n' pasted. :) --- geom_eli.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/geom_eli.c b/geom_eli.c index f90e974..489e212 100644 --- a/geom_eli.c +++ b/geom_eli.c @@ -1058,7 +1058,7 @@ eli_restore(struct gctl_req *req) gctl_error(req, "MD5 hash mismatch: not a geli backup file?"); goto out; } - /* Read metadata from the provider. */ + /* Write metadata to the provider. */ if (pwrite(provfd, sector, secsize, mediasize - secsize) != (ssize_t)secsize) { gctl_error(req, "Cannot write metadata: %s.", strerror(errno)); -- 1.4.1 From owner-freebsd-geom@FreeBSD.ORG Mon Sep 11 11:08:03 2006 Return-Path: X-Original-To: freebsd-geom@FreeBSD.org Delivered-To: freebsd-geom@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8064A16A415 for ; Mon, 11 Sep 2006 11:08:03 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2610043D53 for ; Mon, 11 Sep 2006 11:08:03 +0000 (GMT) (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 k8BB833J063165 for ; Mon, 11 Sep 2006 11:08:03 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k8BB810i063161 for freebsd-geom@FreeBSD.org; Mon, 11 Sep 2006 11:08:01 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 11 Sep 2006 11:08:01 GMT Message-Id: <200609111108.k8BB810i063161@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, 11 Sep 2006 11:08:03 -0000 Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/76538 geom [gbde] nfs-write on gbde partition stalls and continue 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/95771 geom [geom] geom mirror provider destroyed (machine crashed o kern/98034 geom [geom] dereference of NULL pointer in acd_geom_detach o kern/99256 geom [geli] kernel panic/freeze with geli and ufs (maybe re 9 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 3 problems total. From owner-freebsd-geom@FreeBSD.ORG Tue Sep 12 14:22:33 2006 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6C55E16A47B for ; Tue, 12 Sep 2006 14:22:33 +0000 (UTC) (envelope-from mark@gaiahost.coop) Received: from biodiesel.gaiahost.coop (biodiesel.gaiahost.coop [64.95.78.120]) by mx1.FreeBSD.org (Postfix) with ESMTP id D475C43D7D for ; Tue, 12 Sep 2006 14:22:28 +0000 (GMT) (envelope-from mark@gaiahost.coop) Received: from gaiahost.coop (host-64-65-195-19.spr.choiceone.net [::ffff:64.65.195.19]) (AUTH: LOGIN mark@hubcapconsulting.com) by biodiesel.gaiahost.coop with esmtp; Tue, 12 Sep 2006 10:22:26 -0400 id 00794091.4506C2A3.000019BC Received: by gaiahost.coop (sSMTP sendmail emulation); Tue, 12 Sep 2006 10:22:33 -0400 Date: Tue, 12 Sep 2006 10:22:33 -0400 From: Mark Bucciarelli To: freebsd-geom@FreeBSD.org Message-ID: <20060912142232.GB440@rabbit> Mail-Followup-To: freebsd-geom@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Cc: Subject: gvinum raid5 in production 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: Tue, 12 Sep 2006 14:22:33 -0000 Is anybody using gvinum raid5 in production with 6.1-release? How is it going? Have you every had any instances where a kernel panic caused the raid-array not to rebuild properly on reboot and you had data loss? Has your array been robust to SCSI errors from your drives? I reviewed all problem reports I could find and only 89660 looked serious. Dec. 2005 (6.0): kernel panic (perhaps due to low memory) caused by code in geom perhaps. Looks like raid rebuilds properly, only b/c poster didn't mention any problem. Patch included. (Hmmm, gvinum code doesn't check for null pointers returned by malloc.) [1] Sep. 2005 (6.0): probably not geom-related (according to poster). Kernel panic when copying large file (2 Gb). [2] Feb. 2005 (5.3): A newfs bug caused by an integer overflow when entering stupidly large values when creating a new file system. No risk. [3] Nov. 2005 (5.3): Pulls a drive from raid 5 (w/o turning off machine, I _think_), get's SCSI errors, and kernel panics. Older machine? (Pentium Pro) [4] As a followup question, in case of kernel panic, coredump and subsequent savecore, is it safe to have swap on a gmirror raid1? How about on gvinum raid 5? m [1] http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/89660 [2] http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/85728 [3] http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/77181 [4] http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/73830 From owner-freebsd-geom@FreeBSD.ORG Tue Sep 12 17:03:38 2006 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D328016A407 for ; Tue, 12 Sep 2006 17:03:38 +0000 (UTC) (envelope-from dragonx@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1373843D45 for ; Tue, 12 Sep 2006 17:03:37 +0000 (GMT) (envelope-from dragonx@gmail.com) Received: by nf-out-0910.google.com with SMTP id n29so1599903nfc for ; Tue, 12 Sep 2006 10:03:36 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=tenROh8wKBkxbO4D/DIohFHAEVg1nsh5AcpXZvmGldiK9VtJQH/d/mmctJqKyPuOBx6OHDTP/CAiKVdq5tI43llTwOwuoLgb7fMA7SzJuNPRGIWq/QY+io9jdZyqvRaInWXyGDLE1/qYeYgJqxJAWJOt6xY2LCTlTkSj3jwbDLM= Received: by 10.49.55.13 with SMTP id h13mr9880988nfk; Tue, 12 Sep 2006 10:03:36 -0700 (PDT) Received: by 10.49.12.14 with HTTP; Tue, 12 Sep 2006 10:03:36 -0700 (PDT) Message-ID: <1f3e40760609121003q70088f56g68e5c3f6d80b3314@mail.gmail.com> Date: Tue, 12 Sep 2006 10:03:36 -0700 From: "D X" To: freebsd-geom@freebsd.org In-Reply-To: <20060912142232.GB440@rabbit> MIME-Version: 1.0 References: <20060912142232.GB440@rabbit> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: gvinum raid5 in production 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: Tue, 12 Sep 2006 17:03:38 -0000 I know the FreeNAS project has been using 6.1-release. A number of people have complained about problems with gvinum running RAID 5. I haven't been following up on this in the past couple of months, but if you're looking for bugs, you might want to contact Olivier Cochard, the lead of the freenas project. http://www.freenas.org/ On 9/12/06, Mark Bucciarelli wrote: > > Is anybody using gvinum raid5 in production with 6.1-release? How is it > going? > > Have you every had any instances where a kernel panic caused the > raid-array > not to rebuild properly on reboot and you had data loss? > > Has your array been robust to SCSI errors from your drives? > > I reviewed all problem reports I could find and only 89660 looked serious. > > Dec. 2005 (6.0): kernel panic (perhaps due to low memory) > caused by code in geom perhaps. Looks like raid rebuilds > properly, only b/c poster didn't mention any problem. Patch > included. (Hmmm, gvinum code doesn't check for null pointers > returned by malloc.) [1] > > Sep. 2005 (6.0): probably not geom-related (according to > poster). Kernel panic when copying large file (2 Gb). [2] > > Feb. 2005 (5.3): A newfs bug caused by an integer overflow > when entering stupidly large values when creating a new file > system. No risk. [3] > > Nov. 2005 (5.3): Pulls a drive from raid 5 (w/o turning off > machine, I _think_), get's SCSI errors, and kernel panics. > Older machine? (Pentium Pro) [4] > > As a followup question, in case of kernel panic, coredump and subsequent > savecore, is it safe to have swap on a gmirror raid1? How about on gvinum > raid 5? > > m > > [1] http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/89660 > > [2] http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/85728 > > [3] http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/77181 > > [4] http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/73830 > _______________________________________________ > 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" > From owner-freebsd-geom@FreeBSD.ORG Tue Sep 12 18:37:36 2006 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 178B316A501 for ; Tue, 12 Sep 2006 18:37:36 +0000 (UTC) (envelope-from lulf@stud.ntnu.no) Received: from merke.itea.ntnu.no (merke.itea.ntnu.no [129.241.7.61]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9AD7B43D45 for ; Tue, 12 Sep 2006 18:37:35 +0000 (GMT) (envelope-from lulf@stud.ntnu.no) Received: from localhost (localhost [127.0.0.1]) by merke.itea.ntnu.no (Postfix) with ESMTP id A57AF13C5C9; Tue, 12 Sep 2006 20:37:33 +0200 (CEST) Received: from localhost (textus5.itea.ntnu.no [129.241.56.155]) by merke.itea.ntnu.no (Postfix) with ESMTP; Tue, 12 Sep 2006 20:37:33 +0200 (CEST) Received: from m044h.studby.ntnu.no (m044h.studby.ntnu.no [129.241.135.44]) by webmail.ntnu.no (IMP) with HTTP for ; Tue, 12 Sep 2006 20:37:33 +0200 Message-ID: <1158086253.4506fe6d6d6fe@webmail.ntnu.no> Date: Tue, 12 Sep 2006 20:37:33 +0200 From: Ulf Lilleengen To: Mark Bucciarelli References: <20060912142232.GB440@rabbit> In-Reply-To: <20060912142232.GB440@rabbit> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2.8 X-Content-Scanned: with sophos and spamassassin at mailgw.ntnu.no. Cc: freebsd-geom@freebsd.org Subject: Re: gvinum raid5 in production 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: Tue, 12 Sep 2006 18:37:36 -0000 Quoting Mark Bucciarelli : > Is anybody using gvinum raid5 in production with 6.1-release? How is > it > going? > I run gvinum raid5 in 6.1 Release on a light production server, and I've not encountered any problems so far, but it _should_ work :) About the PR's you found I'm not sure of what's a gvinum bug or not of them, but at the thing about not checking NULL pointers for g_malloc is because when passing the M_WAITOK flag to g_malloc (or kernel malloc for instance), it is guaranteed to not return NULL because the flag tells malloc to wait for resources to be freed. -- Ulf Lilleengen From owner-freebsd-geom@FreeBSD.ORG Tue Sep 12 18:44:56 2006 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 099A916A403 for ; Tue, 12 Sep 2006 18:44:56 +0000 (UTC) (envelope-from arne_woerner@yahoo.com) Received: from web30313.mail.mud.yahoo.com (web30313.mail.mud.yahoo.com [209.191.69.75]) by mx1.FreeBSD.org (Postfix) with SMTP id 8469D43D45 for ; Tue, 12 Sep 2006 18:44:55 +0000 (GMT) (envelope-from arne_woerner@yahoo.com) Received: (qmail 33679 invoked by uid 60001); 12 Sep 2006 18:44:53 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=34ntHe+SfPutpw+pkWNf2C5NBbgH3plqb3o4e/VKn3hrUjdhsKSGGFU2dhp6XdmftFc/07Bff19SI1dpwIczwk+RG27QMnYd0ukr35ll+5UcY9mMkRGbaCdzO1f7MFkc/JHdi1WBFcDLVUTZkhiB0b2oIUztPlTAEMUGXujqpEM= ; Message-ID: <20060912184453.33677.qmail@web30313.mail.mud.yahoo.com> Received: from [213.54.69.36] by web30313.mail.mud.yahoo.com via HTTP; Tue, 12 Sep 2006 11:44:53 PDT Date: Tue, 12 Sep 2006 11:44:53 -0700 (PDT) From: "R. B. Riddick" To: Ulf Lilleengen , Mark Bucciarelli In-Reply-To: <1158086253.4506fe6d6d6fe@webmail.ntnu.no> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: freebsd-geom@freebsd.org Subject: Re: gvinum raid5 in production 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: Tue, 12 Sep 2006 18:44:56 -0000 --- Ulf Lilleengen wrote: > Quoting Mark Bucciarelli : > > Is anybody using gvinum raid5 in production with 6.1-release? How is > > it going? > > About the PR's you found I'm not sure of what's a gvinum bug or not of > them, but at the thing about not checking NULL pointers for g_malloc is > because when passing the M_WAITOK flag to g_malloc (or kernel malloc > for instance), it is guaranteed to not return NULL because the flag > tells malloc to wait for resources to be freed. > As far as I understood GEOM it does not like to sleep in g_up or g_down threads... So we cannot use M_WAITOK in gv_down()... I personally do it in my geom_raid5 class (downloadable tar-ball: http://home.tiscali.de/cmdr_faako/geom_raid5.tbz and .../geom_cache.tbz) different: I just put the pointer to the bio into a worker queue (that does not need any malloc's; just bending some pointer attributes) and then in the worker thread I process those requests... Maybe we should create a queue for that purpose for gvinum, too? -Arne __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From owner-freebsd-geom@FreeBSD.ORG Tue Sep 12 19:18:16 2006 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 254EE16A417 for ; Tue, 12 Sep 2006 19:18:16 +0000 (UTC) (envelope-from lulf@stud.ntnu.no) Received: from fri.itea.ntnu.no (fri.itea.ntnu.no [129.241.7.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9DC1343D76 for ; Tue, 12 Sep 2006 19:18:12 +0000 (GMT) (envelope-from lulf@stud.ntnu.no) Received: from localhost (localhost [127.0.0.1]) by fri.itea.ntnu.no (Postfix) with ESMTP id 7244F8671; Tue, 12 Sep 2006 21:18:11 +0200 (CEST) Received: from gaupe.stud.ntnu.no (gaupe.stud.ntnu.no [129.241.56.184]) by fri.itea.ntnu.no (Postfix) with ESMTP; Tue, 12 Sep 2006 21:18:11 +0200 (CEST) Received: by gaupe.stud.ntnu.no (Postfix, from userid 2312) id 6FCD4CFF19; Tue, 12 Sep 2006 21:18:14 +0200 (CEST) Date: Tue, 12 Sep 2006 21:18:14 +0200 From: Ulf Lilleengen To: "R. B. Riddick" Message-ID: <20060912191744.GA28858@stud.ntnu.no> References: <1158086253.4506fe6d6d6fe@webmail.ntnu.no> <20060912184453.33677.qmail@web30313.mail.mud.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060912184453.33677.qmail@web30313.mail.mud.yahoo.com> User-Agent: Mutt/1.5.9i X-Content-Scanned: with sophos and spamassassin at mailgw.ntnu.no. Cc: freebsd-geom@freebsd.org Subject: Re: gvinum raid5 in production 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: Tue, 12 Sep 2006 19:18:16 -0000 On tir, sep 12, 2006 at 11:44:53 -0700, R. B. Riddick wrote: > --- Ulf Lilleengen wrote: > > Quoting Mark Bucciarelli : > > > Is anybody using gvinum raid5 in production with 6.1-release? How is > > > it going? > > > > About the PR's you found I'm not sure of what's a gvinum bug or not of > > them, but at the thing about not checking NULL pointers for g_malloc is > > because when passing the M_WAITOK flag to g_malloc (or kernel malloc > > for instance), it is guaranteed to not return NULL because the flag > > tells malloc to wait for resources to be freed. > > > As far as I understood GEOM it does not like to sleep in g_up or g_down > threads... So we cannot use M_WAITOK in gv_down()... What do you mean gv_down()? Gvinum does not use g_up or g_down as far as i can tell? -- Ulf Lilleengen From owner-freebsd-geom@FreeBSD.ORG Tue Sep 12 19:22:14 2006 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4A66B16A407 for ; Tue, 12 Sep 2006 19:22:14 +0000 (UTC) (envelope-from mark@gaiahost.coop) Received: from biodiesel.gaiahost.coop (biodiesel.gaiahost.coop [64.95.78.120]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A61743D46 for ; Tue, 12 Sep 2006 19:22:13 +0000 (GMT) (envelope-from mark@gaiahost.coop) Received: from gaiahost.coop (host-64-65-195-19.spr.choiceone.net [::ffff:64.65.195.19]) (AUTH: LOGIN mark@hubcapconsulting.com) by biodiesel.gaiahost.coop with esmtp; Tue, 12 Sep 2006 15:21:04 -0400 id 00794085.450708B2.000075F9 Received: by gaiahost.coop (sSMTP sendmail emulation); Tue, 12 Sep 2006 15:17:53 -0400 Date: Tue, 12 Sep 2006 15:17:52 -0400 From: Mark Bucciarelli To: Ulf Lilleengen Message-ID: <20060912191752.GB3164@rabbit> Mail-Followup-To: Ulf Lilleengen , freebsd-geom@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Cc: freebsd-geom@freebsd.org Subject: Re: gvinum raid5 in production 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: Tue, 12 Sep 2006 19:22:14 -0000 On Tue, Sep 12, 2006 at 08:37:33PM +0200, Ulf Lilleengen wrote: > Quoting Mark Bucciarelli : > > > Is anybody using gvinum raid5 in production with 6.1-release? How is > > it > > going? > > > > I run gvinum raid5 in 6.1 Release on a light production server, and I've > not encountered any problems so far, but it _should_ work :) > > About the PR's you found I'm not sure of what's a gvinum bug or not of > them, but at the thing about not checking NULL pointers for g_malloc is > because when passing the M_WAITOK flag to g_malloc (or kernel malloc > for instance), it is guaranteed to not return NULL because the flag > tells malloc to wait for resources to be freed. Guaranteed to either return non-NULL or produce a KASSERT failure. From the backtrace it look like the latter happened to bug reporter. So not a geom bug. RW's fxr is handy. :) m From owner-freebsd-geom@FreeBSD.ORG Tue Sep 12 19:32:26 2006 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0CD6D16A40F for ; Tue, 12 Sep 2006 19:32:26 +0000 (UTC) (envelope-from arne_woerner@yahoo.com) Received: from web30310.mail.mud.yahoo.com (web30310.mail.mud.yahoo.com [209.191.69.72]) by mx1.FreeBSD.org (Postfix) with SMTP id 89E8043D46 for ; Tue, 12 Sep 2006 19:32:25 +0000 (GMT) (envelope-from arne_woerner@yahoo.com) Received: (qmail 75862 invoked by uid 60001); 12 Sep 2006 19:32:25 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=ZifKqY7tlJa7AZn9LjUb/3AneIIjSmosrZF/v4wnQiCmb4qioENqJ8NIr7RAMpgDtx/abF4epEWools/q5q0SYvKqvt+IgF++NTiGkoQJ/q3TPAHXSgN3mVq46CBfSeXX6KhrbdTqpb5NK8GxRj9Iuqjk4bRX6FYuTzop3fkB2g= ; Message-ID: <20060912193225.75860.qmail@web30310.mail.mud.yahoo.com> Received: from [213.54.69.36] by web30310.mail.mud.yahoo.com via HTTP; Tue, 12 Sep 2006 12:32:25 PDT Date: Tue, 12 Sep 2006 12:32:25 -0700 (PDT) From: "R. B. Riddick" To: Ulf Lilleengen In-Reply-To: <20060912191744.GA28858@stud.ntnu.no> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: freebsd-geom@freebsd.org Subject: Re: gvinum raid5 in production 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: Tue, 12 Sep 2006 19:32:26 -0000 --- Ulf Lilleengen wrote: > > As far as I understood GEOM it does not like to sleep in g_up or g_down > > threads... So we cannot use M_WAITOK in gv_down()... > What do you mean gv_down()? Gvinum does not use g_up or g_down as far as i > can tell? > Ohoh... Tubby "typo"... "gv_down" is wrong... I meant "gv_drive_done()" As far as I understood GEOM it work as follows: 1. A geom class provides a drive and several functions, that r needed to operate that drive... 2. Thread g_down hands down a new read/write/... request to an instance of a geom class by using those functions (often called: ..._start()) 3. Thread g_up hands up a completed/aborted request to the caller (a geom or so) by using those functions (often called: ..._done()) It is a little bit like "function overloading" in OO... -Arne --- Arne likes Teletubbies... __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From owner-freebsd-geom@FreeBSD.ORG Tue Sep 12 19:39:42 2006 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5541E16A607 for ; Tue, 12 Sep 2006 19:39:42 +0000 (UTC) (envelope-from lulf@stud.ntnu.no) Received: from fri.itea.ntnu.no (fri.itea.ntnu.no [129.241.7.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA5B643D55 for ; Tue, 12 Sep 2006 19:39:41 +0000 (GMT) (envelope-from lulf@stud.ntnu.no) Received: from localhost (localhost [127.0.0.1]) by fri.itea.ntnu.no (Postfix) with ESMTP id 90F8C7F65 for ; Tue, 12 Sep 2006 21:39:40 +0200 (CEST) Received: from gaupe.stud.ntnu.no (gaupe.stud.ntnu.no [129.241.56.184]) by fri.itea.ntnu.no (Postfix) with ESMTP for ; Tue, 12 Sep 2006 21:39:40 +0200 (CEST) Received: by gaupe.stud.ntnu.no (Postfix, from userid 2312) id 936CFCFF19; Tue, 12 Sep 2006 21:39:43 +0200 (CEST) Resent-From: lulf@stud.ntnu.no Resent-Date: Tue, 12 Sep 2006 21:39:43 +0200 Resent-Message-ID: <20060912193943.GA466@stud.ntnu.no> Resent-To: freebsd-geom@freebsd.org Date: Tue, 12 Sep 2006 21:38:17 +0200 From: Ulf Lilleengen To: "R. B. Riddick" Message-ID: <20060912193816.GA32402@stud.ntnu.no> References: <20060912191744.GA28858@stud.ntnu.no> <20060912193225.75860.qmail@web30310.mail.mud.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060912193225.75860.qmail@web30310.mail.mud.yahoo.com> User-Agent: Mutt/1.5.9i X-Content-Scanned: with sophos and spamassassin at mailgw.ntnu.no. Cc: Subject: Re: gvinum raid5 in production 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: Tue, 12 Sep 2006 19:39:42 -0000 On tir, sep 12, 2006 at 12:32:25 -0700, R. B. Riddick wrote: > --- Ulf Lilleengen wrote: > > > As far as I understood GEOM it does not like to sleep in g_up or g_down > > > threads... So we cannot use M_WAITOK in gv_down()... > > What do you mean gv_down()? Gvinum does not use g_up or g_down as far as i > > can tell? > > > Ohoh... Tubby "typo"... > > "gv_down" is wrong... I meant "gv_drive_done()" > > As far as I understood GEOM it work as follows: > 1. A geom class provides a drive and several functions, that r needed to > operate that drive... > 2. Thread g_down hands down a new read/write/... request to an instance of a > geom class by using those functions (often called: ..._start()) > 3. Thread g_up hands up a completed/aborted request to the caller (a geom or > so) by using those functions (often called: ..._done()) Have a look at the CURRENT branch instead. It uses a worker queue. In RELENG_6 i can see that it used g_malloc. -- Ulf Lilleengen From owner-freebsd-geom@FreeBSD.ORG Tue Sep 12 19:47:43 2006 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5372916A417 for ; Tue, 12 Sep 2006 19:47:43 +0000 (UTC) (envelope-from arne_woerner@yahoo.com) Received: from web30309.mail.mud.yahoo.com (web30309.mail.mud.yahoo.com [209.191.69.71]) by mx1.FreeBSD.org (Postfix) with SMTP id 2ED6E43D5E for ; Tue, 12 Sep 2006 19:47:37 +0000 (GMT) (envelope-from arne_woerner@yahoo.com) Received: (qmail 90448 invoked by uid 60001); 12 Sep 2006 19:47:37 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=Il6p4oDHaGtw2YbutSBLhEW6+PQPdCpOwka2VrvkyWTxnarjccMQ1n53I8xxqGosiwgIDVmC2n0Q9GRY+1knREW52id1gQmVLELqvt6YEJyLUWP0gkPn8CCG0mbUIHWUPKD66mHL/o3nCrv4BTc7F0Uj9f/O6IQXEOqHzu3a5Q8= ; Message-ID: <20060912194737.90446.qmail@web30309.mail.mud.yahoo.com> Received: from [213.54.69.36] by web30309.mail.mud.yahoo.com via HTTP; Tue, 12 Sep 2006 12:47:37 PDT Date: Tue, 12 Sep 2006 12:47:37 -0700 (PDT) From: "R. B. Riddick" To: Ulf Lilleengen In-Reply-To: <20060912193816.GA32402@stud.ntnu.no> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: freebsd-geom@freebsd.org Subject: Re: gvinum raid5 in production 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: Tue, 12 Sep 2006 19:47:43 -0000 --- Ulf Lilleengen wrote: > Have a look at the CURRENT branch instead. It uses a worker queue. In > RELENG_6 i can see that it used g_malloc. > Oh yes... I looked via the CVS web interface... Currently it is like I would do it, too... Maybe the originator of this thread should try to update to CURRENT? -Arne __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From owner-freebsd-geom@FreeBSD.ORG Tue Sep 12 19:48:52 2006 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8F03F16A40F for ; Tue, 12 Sep 2006 19:48:52 +0000 (UTC) (envelope-from lulf@stud.ntnu.no) Received: from merke.itea.ntnu.no (merke.itea.ntnu.no [129.241.7.61]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1CCB543D46 for ; Tue, 12 Sep 2006 19:48:52 +0000 (GMT) (envelope-from lulf@stud.ntnu.no) Received: from localhost (localhost [127.0.0.1]) by merke.itea.ntnu.no (Postfix) with ESMTP id E0F2B13D797 for ; Tue, 12 Sep 2006 21:48:50 +0200 (CEST) Received: from gaupe.stud.ntnu.no (gaupe.stud.ntnu.no [129.241.56.184]) by merke.itea.ntnu.no (Postfix) with ESMTP for ; Tue, 12 Sep 2006 21:48:50 +0200 (CEST) Received: by gaupe.stud.ntnu.no (Postfix, from userid 2312) id DE2E5CFF19; Tue, 12 Sep 2006 21:48:53 +0200 (CEST) Date: Tue, 12 Sep 2006 21:48:53 +0200 From: Ulf Lilleengen To: freebsd-geom@freebsd.org Message-ID: <20060912194853.GA1263@stud.ntnu.no> References: <20060912191744.GA28858@stud.ntnu.no> <20060912193225.75860.qmail@web30310.mail.mud.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060912193225.75860.qmail@web30310.mail.mud.yahoo.com> User-Agent: Mutt/1.5.9i X-Content-Scanned: with sophos and spamassassin at mailgw.ntnu.no. Subject: Re: gvinum raid5 in production 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: Tue, 12 Sep 2006 19:48:52 -0000 On tir, sep 12, 2006 at 12:32:25 -0700, R. B. Riddick wrote: > --- Ulf Lilleengen wrote: > > > As far as I understood GEOM it does not like to sleep in g_up or g_down > > > threads... So we cannot use M_WAITOK in gv_down()... > > What do you mean gv_down()? Gvinum does not use g_up or g_down as far as i > > can tell? > > > Ohoh... Tubby "typo"... > > "gv_down" is wrong... I meant "gv_drive_done()" > > As far as I understood GEOM it work as follows: > 1. A geom class provides a drive and several functions, that r needed to > operate that drive... > 2. Thread g_down hands down a new read/write/... request to an instance of a > geom class by using those functions (often called: ..._start()) > 3. Thread g_up hands up a completed/aborted request to the caller (a geom or > so) by using those functions (often called: ..._done()) > Have a look at the CURRENT branch instead. It uses a worker queue. In RELENG_6 i can see that it used g_malloc. -- Mvh Ulf Lilleengen From owner-freebsd-geom@FreeBSD.ORG Tue Sep 12 20:04:18 2006 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 979E516A4A0 for ; Tue, 12 Sep 2006 20:04:18 +0000 (UTC) (envelope-from lulf@stud.ntnu.no) Received: from signal.itea.ntnu.no (signal.itea.ntnu.no [129.241.190.231]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4B12143DDA for ; Tue, 12 Sep 2006 20:02:52 +0000 (GMT) (envelope-from lulf@stud.ntnu.no) Received: from localhost (localhost [127.0.0.1]) by signal.itea.ntnu.no (Postfix) with ESMTP id B1C9934A76; Tue, 12 Sep 2006 22:02:48 +0200 (CEST) Received: from gaupe.stud.ntnu.no (gaupe.stud.ntnu.no [129.241.56.184]) by signal.itea.ntnu.no (Postfix) with ESMTP; Tue, 12 Sep 2006 22:02:48 +0200 (CEST) Received: by gaupe.stud.ntnu.no (Postfix, from userid 2312) id B42CFCFF19; Tue, 12 Sep 2006 22:02:51 +0200 (CEST) Date: Tue, 12 Sep 2006 22:02:51 +0200 From: Ulf Lilleengen To: "R. B. Riddick" Message-ID: <20060912200251.GA3098@stud.ntnu.no> References: <20060912193816.GA32402@stud.ntnu.no> <20060912194737.90446.qmail@web30309.mail.mud.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060912194737.90446.qmail@web30309.mail.mud.yahoo.com> User-Agent: Mutt/1.5.9i X-Content-Scanned: with sophos and spamassassin at mailgw.ntnu.no. Cc: freebsd-geom@freebsd.org Subject: Re: gvinum raid5 in production 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: Tue, 12 Sep 2006 20:04:18 -0000 On tir, sep 12, 2006 at 12:47:37 -0700, R. B. Riddick wrote: > --- Ulf Lilleengen wrote: > > Have a look at the CURRENT branch instead. It uses a worker queue. In > > RELENG_6 i can see that it used g_malloc. > > > Oh yes... I looked via the CVS web interface... Currently it is like I would do > it, too... > > Maybe the originator of this thread should try to update to CURRENT? I would not recommend using CURRENT in production :) -- Ulf Lilleengen From owner-freebsd-geom@FreeBSD.ORG Tue Sep 12 20:29:26 2006 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BE94F16A5A1 for ; Tue, 12 Sep 2006 20:29:26 +0000 (UTC) (envelope-from arne_woerner@yahoo.com) Received: from web30313.mail.mud.yahoo.com (web30313.mail.mud.yahoo.com [209.191.69.75]) by mx1.FreeBSD.org (Postfix) with SMTP id 466DA43E20 for ; Tue, 12 Sep 2006 20:27:25 +0000 (GMT) (envelope-from arne_woerner@yahoo.com) Received: (qmail 77967 invoked by uid 60001); 12 Sep 2006 20:27:24 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=eBf4speViylQEdaHCD7YvS1dgCenreMopWpoKcS42MSigkjKSo8pR3DWjE8WAteN72A3CgslwGKnmCebQcYBLss7vNUREj06334zOsWDZsVkqYEQI/sZV0W8JPXm9wfnctAfU3/qXl1vdXiWK8JwdumARPoiB+GQ4h07SZs5CMg= ; Message-ID: <20060912202724.77965.qmail@web30313.mail.mud.yahoo.com> Received: from [213.54.69.36] by web30313.mail.mud.yahoo.com via HTTP; Tue, 12 Sep 2006 13:27:24 PDT Date: Tue, 12 Sep 2006 13:27:24 -0700 (PDT) From: "R. B. Riddick" To: Ulf Lilleengen In-Reply-To: <20060912200251.GA3098@stud.ntnu.no> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: freebsd-geom@freebsd.org Subject: Re: gvinum raid5 in production 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: Tue, 12 Sep 2006 20:29:26 -0000 --- Ulf Lilleengen wrote: > On tir, sep 12, 2006 at 12:47:37 -0700, R. B. Riddick wrote: > > Maybe the originator of this thread should try to update to CURRENT? > > I would not recommend using CURRENT in production :) > I meant: Just for gvinum... :-) Since it seems to be already quite bad for him or her... -Arne __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From owner-freebsd-geom@FreeBSD.ORG Tue Sep 12 20:51:18 2006 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EB13416A40F for ; Tue, 12 Sep 2006 20:51:18 +0000 (UTC) (envelope-from mark@gaiahost.coop) Received: from biodiesel.gaiahost.coop (biodiesel.gaiahost.coop [64.95.78.120]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3EB2443D6B for ; Tue, 12 Sep 2006 20:51:15 +0000 (GMT) (envelope-from mark@gaiahost.coop) Received: from gaiahost.coop (host-64-65-195-19.spr.choiceone.net [::ffff:64.65.195.19]) (AUTH: LOGIN mark@hubcapconsulting.com) by biodiesel.gaiahost.coop with esmtp; Tue, 12 Sep 2006 16:51:13 -0400 id 007740B6.45071DC2.00005699 Received: by gaiahost.coop (sSMTP sendmail emulation); Tue, 12 Sep 2006 16:51:20 -0400 Date: Tue, 12 Sep 2006 16:51:20 -0400 From: Mark Bucciarelli To: "R. B. Riddick" Message-ID: <20060912205120.GD3164@rabbit> Mail-Followup-To: "R. B. Riddick" , Ulf Lilleengen , freebsd-geom@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Cc: Ulf Lilleengen , freebsd-geom@freebsd.org Subject: Re: gvinum raid5 in production 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: Tue, 12 Sep 2006 20:51:19 -0000 On Tue, Sep 12, 2006 at 01:27:24PM -0700, R. B. Riddick wrote: > --- Ulf Lilleengen wrote: > > On tir, sep 12, 2006 at 12:47:37 -0700, R. B. Riddick wrote: > > > Maybe the originator of this thread should try to update to CURRENT? > > > > I would not recommend using CURRENT in production :) > > > I meant: Just for gvinum... :-) > Since it seems to be already quite bad for him or her... > Just having a hard time deciding between Net/OpenBSD Raidframe and some gmirror/gvinum combo. m From owner-freebsd-geom@FreeBSD.ORG Thu Sep 14 16:00:00 2006 Return-Path: X-Original-To: freebsd-geom@FreeBSD.ORG Delivered-To: freebsd-geom@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 215E316A412 for ; Thu, 14 Sep 2006 16:00:00 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE28C43D46 for ; Thu, 14 Sep 2006 15:59:58 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (fgjajc@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id k8EFxpIZ056653 for ; Thu, 14 Sep 2006 17:59:57 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id k8EFxp2P056652; Thu, 14 Sep 2006 17:59:51 +0200 (CEST) (envelope-from olli) Date: Thu, 14 Sep 2006 17:59:51 +0200 (CEST) Message-Id: <200609141559.k8EFxp2P056652@lurza.secnetix.de> From: Oliver Fromme To: freebsd-geom@FreeBSD.ORG X-Newsgroups: list.freebsd-geom User-Agent: tin/1.8.0-20051224 ("Ronay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Thu, 14 Sep 2006 17:59:57 +0200 (CEST) Cc: Subject: gmirror size question X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-geom@FreeBSD.ORG List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Sep 2006 16:00:00 -0000 Hi, I've read the gmirror manpage and the Handbook section, and even had a short look at the source, but couldn't find an answer ... I plan to setup gmirror for a production server with two identical disks (Fujitsu U160 SCSI); they have exactly the same number of blocks. Now I wonder what will happen if one drive fails and I won't be able to get a drive with exactly the same size. The problem is that not all 74GB drives have exactly the same number of blocks, not even those from the same vendor. Using the next larger size (147GB) would be a waste. If the new disk is sligtly larger, I guess there shouldn't be a problem. When adding the new drive, gmirror will simply ignore the excess blocks, right? However, I guess I'll run into trouble if the new drive is slightly smaller. Therefore, it came to my mind that it might make sense to make the mirror slightly smaller from the beginning, i.e. let gmirror use only the first 73GB of the 74GB available. That should be enough of a safety margin. However, how do I do that? gmirror(8) doesn't provide an option to specify the size of the consumer, or to let it ignore a certain amount of space at the end of it. My next thought was to create separate slice tables on both disks, with one slices of 73GB each (letting 1GB stay unused), and then put gmirror onto the slices (da0s1 + da1s1) instead of the whole disks (da0 + da1). I guess that would work, but in that case the MBR and slice tables wouldn't be mirrored, which could lead to trouble if one drive fails and GEOM (or anything else) tried to access the MBR for whatever reason. So ... what's the best solution to the problem? Any comments and ideas are appreciated. Best regards Oliver PS: No need to Cc me; I'm reading the list. -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "Documentation is like sex; when it's good, it's very, very good, and when it's bad, it's better than nothing." -- Dick Brandon From owner-freebsd-geom@FreeBSD.ORG Thu Sep 14 16:11:50 2006 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ECB0116A416 for ; Thu, 14 Sep 2006 16:11:50 +0000 (UTC) (envelope-from peter_giessel@dot.state.ak.us) Received: from jnumail1.state.ak.us (jnumail1.state.ak.us [146.63.81.86]) by mx1.FreeBSD.org (Postfix) with ESMTP id 07DF443D81 for ; Thu, 14 Sep 2006 16:11:41 +0000 (GMT) (envelope-from peter_giessel@dot.state.ak.us) Received: from smtpj.state.ak.us (localhost [127.0.0.1]) by jnumail1.state.ak.us (iPlanet Messaging Server 5.2 HotFix 2.04 (built Feb 8 2005)) with ESMTP id <0J5L00N8MBNH4P@jnumail1.state.ak.us> for freebsd-geom@freebsd.org; Thu, 14 Sep 2006 08:11:41 -0800 (AKDT) Received: from [192.168.0.193] ([158.145.111.132]) by smtpj.state.ak.us (iPlanet Messaging Server 5.2 HotFix 2.04 (built Feb 8 2005)) with ESMTP id <0J5L00519BNGN0@smtpj.state.ak.us> for freebsd-geom@freebsd.org; Thu, 14 Sep 2006 08:11:40 -0800 (AKDT) Date: Thu, 14 Sep 2006 08:11:39 -0800 From: "Peter A. Giessel" To: freebsd-geom@freebsd.org Message-id: <45097F3B.2060606@dot.state.ak.us> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7BIT User-Agent: Thunderbird 1.5.0.5 (Macintosh/20060719) Subject: Replacing failed drive in gvinum causes panic 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, 14 Sep 2006 16:11:51 -0000 I'm getting the same thing as Ludo was getting about 9 months ago with both 5.4 and 6.1 http://docs.freebsd.org/cgi/getmsg.cgi?fetch=55224+0+/usr/local/www/db/text/2005/freebsd-geom/20051225.freebsd-geom I'm using a raid5: --------------------------------- 4 drives: D five State: up /dev/ad10s1 A: 47/190779 MB (0%) D four State: up /dev/ad11s1 A: 47/190779 MB (0%) D three State: up /dev/ad12s1 A: 47/190779 MB (0%) D two State: up /dev/ad14s1 A: 0/190732 MB (0%) D eleven State: up /dev/ad16s1 A: 47/190779 MB (0%) 1 volume: V array State: up Plexes: 1 Size: 745 GB 1 plex: P array.p0 R5 State: degraded Subdisks: 5 Size: 745 GB 6 subdisks: S array.p0.s5 State: up D: eleven Size: 186 GB S array.p0.s4 State: up D: five Size: 186 GB S array.p0.s3 State: up D: four Size: 186 GB S array.p0.s2 State: up D: three Size: 186 GB S array.p0.s1 State: up D: two Size: 186 GB S array.p0.s0 State: down D: one Size: 186 GB --------------------------------- Drive one failed, so we took it out, put a new one in, repartitioned, created the config file "driveone": ----------driveone--------- drive one device /dev/ad18s1h --------------------------- now, "gvinum create driveone" results in an immediate panic. Sometimes gvinum will print: "array.p0 degraded -> up" just before the panic. This seems odd to me since it should take a while for array.p0.s0 to come back online, so its like its skipping the rebuild, coming up in an odd state, and immediately panic'ing. Any advice that you could give would be very much appreciated. From owner-freebsd-geom@FreeBSD.ORG Thu Sep 14 16:28:22 2006 Return-Path: X-Original-To: freebsd-geom@FreeBSD.ORG Delivered-To: freebsd-geom@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9A00E16A59B for ; Thu, 14 Sep 2006 16:28:22 +0000 (UTC) (envelope-from arne_woerner@yahoo.com) Received: from web30306.mail.mud.yahoo.com (web30306.mail.mud.yahoo.com [209.191.69.68]) by mx1.FreeBSD.org (Postfix) with SMTP id B555043D78 for ; Thu, 14 Sep 2006 16:28:18 +0000 (GMT) (envelope-from arne_woerner@yahoo.com) Received: (qmail 74001 invoked by uid 60001); 14 Sep 2006 16:28:17 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=q0JoJz5GUkr7P66cpRbSNcJhfuzBuQ9Q0iNylrJGgDqfmYRHcshI24LDXv3csGnxw5PNPEtlCdK2hbE/II5SyyUvI6bSVf056rIvpTeO+xHP0aPJJ25EciIqqtb8S6Pa/a5L+bfRMbGjEBMQ3aYNoISEbOZDK8UiPll66hn+iq8= ; Message-ID: <20060914162817.73998.qmail@web30306.mail.mud.yahoo.com> Received: from [213.54.79.187] by web30306.mail.mud.yahoo.com via HTTP; Thu, 14 Sep 2006 09:28:17 PDT Date: Thu, 14 Sep 2006 09:28:17 -0700 (PDT) From: "R. B. Riddick" To: freebsd-geom@FreeBSD.ORG In-Reply-To: <200609141559.k8EFxp2P056652@lurza.secnetix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: Subject: Re: gmirror size question 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, 14 Sep 2006 16:28:22 -0000 Hi! --- Oliver Fromme wrote: > If the new disk is sligtly larger, I guess there shouldn't > be a problem. When adding the new drive, gmirror will > simply ignore the excess blocks, right? > Yup! > However, I guess I'll run into trouble if the new drive > is slightly smaller. Therefore, it came to my mind that > it might make sense to make the mirror slightly smaller > from the beginning, i.e. let gmirror use only the first > 73GB of the 74GB available. That should be enough of a > safety margin. > g_mirror.c says in g_mirror_check_metadata(): if (sc->sc_mediasize > pp->mediasize) { G_MIRROR_DEBUG(1, "Invalid size of disk %s (device %s), skipping.", pp->name, sc->sc_name); return (EINVAL); } > However, how do I do that? gmirror(8) doesn't provide > an option to specify the size of the consumer, or to > let it ignore a certain amount of space at the end of > it. > It is important to care about that before IT happens... :-) Because: The file system might expect the last few sectors to exist... I would use gnop during the "gmirror label" command in the hope, that gmirror stores the mediasize permanently without further future checking... But that is just a quick shot... > My next thought was to create separate slice tables on > both disks, with one slices of 73GB each (letting 1GB > stay unused), and then put gmirror onto the slices > (da0s1 + da1s1) instead of the whole disks (da0 + da1). > I guess that would work, but in that case the MBR and > slice tables wouldn't be mirrored, which could lead to > trouble if one drive fails and GEOM (or anything else) > tried to access the MBR for whatever reason. > Gah! :-) -Arne __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From owner-freebsd-geom@FreeBSD.ORG Thu Sep 14 16:30:25 2006 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 83D7E16A531 for ; Thu, 14 Sep 2006 16:30:25 +0000 (UTC) (envelope-from arne_woerner@yahoo.com) Received: from web30314.mail.mud.yahoo.com (web30314.mail.mud.yahoo.com [209.191.69.76]) by mx1.FreeBSD.org (Postfix) with SMTP id E0B2F43DDE for ; Thu, 14 Sep 2006 16:30:07 +0000 (GMT) (envelope-from arne_woerner@yahoo.com) Received: (qmail 93105 invoked by uid 60001); 14 Sep 2006 16:30:07 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=csNdUDeKAXTMhw72HNqvW/Os6UCxA31k2WcefgzB0o6kFHWvab0r0F+DAjIf0fHRaMwkmjYOeOH5oOMM6Dz7CSlY6KKElsisHPByOtkrt2E1h0iugp6Ff4PWumXkAhiAPBlqhKFlHIM3Mkar9GNCgsKjqD3VfjN+jxXwcC0Pxj8= ; Message-ID: <20060914163007.93103.qmail@web30314.mail.mud.yahoo.com> Received: from [213.54.79.187] by web30314.mail.mud.yahoo.com via HTTP; Thu, 14 Sep 2006 09:30:07 PDT Date: Thu, 14 Sep 2006 09:30:07 -0700 (PDT) From: "R. B. Riddick" To: "Peter A. Giessel" , freebsd-geom@freebsd.org In-Reply-To: <45097F3B.2060606@dot.state.ak.us> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: Subject: Re: Replacing failed drive in gvinum causes panic 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, 14 Sep 2006 16:30:25 -0000 Try geom_raid5... http://home.tiscali.de/cmdr_faako/geom_raid5.tbz :-) -Arne --- "Peter A. Giessel" wrote: > I'm getting the same thing as Ludo was getting about 9 months ago with > both 5.4 and 6.1 > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=55224+0+/usr/local/www/db/text/2005/freebsd-geom/20051225.freebsd-geom > > I'm using a raid5: > --------------------------------- > 4 drives: > D five State: up /dev/ad10s1 A: 47/190779 MB (0%) > D four State: up /dev/ad11s1 A: 47/190779 MB (0%) > D three State: up /dev/ad12s1 A: 47/190779 MB (0%) > D two State: up /dev/ad14s1 A: 0/190732 MB (0%) > D eleven State: up /dev/ad16s1 A: 47/190779 MB (0%) > > 1 volume: > V array State: up Plexes: 1 Size: 745 GB > > 1 plex: > P array.p0 R5 State: degraded Subdisks: 5 Size: 745 GB > > 6 subdisks: > S array.p0.s5 State: up D: eleven Size: 186 GB > S array.p0.s4 State: up D: five Size: 186 GB > S array.p0.s3 State: up D: four Size: 186 GB > S array.p0.s2 State: up D: three Size: 186 GB > S array.p0.s1 State: up D: two Size: 186 GB > S array.p0.s0 State: down D: one Size: 186 GB > --------------------------------- > > Drive one failed, so we took it out, put a new one in, repartitioned, > created the config file "driveone": > ----------driveone--------- > drive one device /dev/ad18s1h > --------------------------- > > now, "gvinum create driveone" results in an immediate panic. Sometimes > gvinum will print: > "array.p0 degraded -> up" just before the panic. > > This seems odd to me since it should take a while for array.p0.s0 to > come back online, so its like its skipping the rebuild, coming up in > an odd state, and immediately panic'ing. > > Any advice that you could give would be very much appreciated. > _______________________________________________ > 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" > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From owner-freebsd-geom@FreeBSD.ORG Thu Sep 14 16:42:30 2006 Return-Path: X-Original-To: freebsd-geom@FreeBSD.ORG Delivered-To: freebsd-geom@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C3CF416A492 for ; Thu, 14 Sep 2006 16:42:30 +0000 (UTC) (envelope-from arne_woerner@yahoo.com) Received: from web30309.mail.mud.yahoo.com (web30309.mail.mud.yahoo.com [209.191.69.71]) by mx1.FreeBSD.org (Postfix) with SMTP id 4D67643D77 for ; Thu, 14 Sep 2006 16:42:26 +0000 (GMT) (envelope-from arne_woerner@yahoo.com) Received: (qmail 36455 invoked by uid 60001); 14 Sep 2006 16:42:25 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=kqNQJrGSROS6tLH0xRbH/P2n2ycv8eHFZ8kkrwM/pndZUe+D8TisdyavD5WPB0ivlgeMB3Vyv2k+2HXVWgTPt57C2oTkEdbGEY+7G7vylmKaRPLqqnsdbzhXu8YJygUYw02lYlCABtceKnkFJvh/qqeDQSYED1n0mfoWOqgJYPw= ; Message-ID: <20060914164225.36453.qmail@web30309.mail.mud.yahoo.com> Received: from [213.54.79.187] by web30309.mail.mud.yahoo.com via HTTP; Thu, 14 Sep 2006 09:42:25 PDT Date: Thu, 14 Sep 2006 09:42:25 -0700 (PDT) From: "R. B. Riddick" To: freebsd-geom@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: Subject: Re: gmirror size question 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, 14 Sep 2006 16:42:30 -0000 --- "R. B. Riddick" wrote: > I would use gnop during the "gmirror label" command in the hope, that gmirror > stores the mediasize permanently without further future checking... But that > is just a quick shot... > Because I found the question so interesting here is the plan (it is my plan; I invented it on my own; and I have a second plan about bands playing songs of David Hasselhoff): # diskinfo /dev/md? /dev/md0 512 33554432 65536 /dev/md1 512 16777216 32768 # gnop create -v -s 10485760 md0 # gmirror label fook md0.nop md1 # gmirror stop fook # gnop destroy md0.nop # gmirror forget fook # gmirror insert fook md0 # gmirror list Geom name: fook State: COMPLETE Components: 2 Balance: split Slice: 4096 Flags: NONE GenID: 0 SyncID: 1 ID: 395302241 Providers: 1. Name: mirror/fook Mediasize: 10485248 (10M) Sectorsize: 512 Mode: r0w0e0 Consumers: 1. Name: md0 Mediasize: 33554432 (32M) Sectorsize: 512 Mode: r1w1e1 State: ACTIVE Priority: 0 Flags: NONE GenID: 0 SyncID: 1 ID: 864954146 2. Name: md1 Mediasize: 16777216 (16M) Sectorsize: 512 Mode: r1w1e1 State: ACTIVE Priority: 0 Flags: NONE GenID: 0 SyncID: 1 ID: 3713132874 [or similar] quod erat fackiendum -Arne __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From owner-freebsd-geom@FreeBSD.ORG Fri Sep 15 08:49:24 2006 Return-Path: X-Original-To: freebsd-geom@FreeBSD.ORG Delivered-To: freebsd-geom@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 460B516A40F for ; Fri, 15 Sep 2006 08:49:24 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 835B943D46 for ; Fri, 15 Sep 2006 08:49:23 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (ojuzmj@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id k8F8nGwQ004732 for ; Fri, 15 Sep 2006 10:49:22 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id k8F8nGBa004731; Fri, 15 Sep 2006 10:49:16 +0200 (CEST) (envelope-from olli) Date: Fri, 15 Sep 2006 10:49:16 +0200 (CEST) Message-Id: <200609150849.k8F8nGBa004731@lurza.secnetix.de> From: Oliver Fromme To: freebsd-geom@FreeBSD.ORG In-Reply-To: <20060914164225.36453.qmail@web30309.mail.mud.yahoo.com> X-Newsgroups: list.freebsd-geom User-Agent: tin/1.8.0-20051224 ("Ronay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Fri, 15 Sep 2006 10:49:22 +0200 (CEST) Cc: Subject: Re: gmirror size question 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, 15 Sep 2006 08:49:24 -0000 R. B. Riddick wrote: > # diskinfo /dev/md? > /dev/md0 512 33554432 65536 > /dev/md1 512 16777216 32768 > # gnop create -v -s 10485760 md0 > # gmirror label fook md0.nop md1 > # gmirror stop fook > # gnop destroy md0.nop > # gmirror forget fook > # gmirror insert fook md0 > # gmirror list > [...] > Providers: > 1. Name: mirror/fook > Mediasize: 10485248 (10M) > [...] > Consumers: > 1. Name: md0 > Mediasize: 33554432 (32M) > [...] > 2. Name: md1 > Mediasize: 16777216 (16M) Ah, that's cool. Thanks for the suggestion, I didn't think of using gnop for that purpose. I was rather looking for a "size" option to gmirror(8), but that doesn't exist. I've just successfully reproduced your "plan" with several md devices of various sizes, for testing purposes. Now going to do it with the "real" disks. :-) Thanks! Best regards Oliver PS: I think that hint should be mentioned in the Handbook section about gmirror. It could prevent major foot-shoting. Comments? -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "It combines all the worst aspects of C and Lisp: a billion different sublanguages in one monolithic executable. It combines the power of C with the readability of PostScript." -- Jamie Zawinski, when asked: "What's wrong with perl?" From owner-freebsd-geom@FreeBSD.ORG Fri Sep 15 09:05:15 2006 Return-Path: X-Original-To: freebsd-geom@FreeBSD.ORG Delivered-To: freebsd-geom@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A8ECD16A407 for ; Fri, 15 Sep 2006 09:05:15 +0000 (UTC) (envelope-from arne_woerner@yahoo.com) Received: from web30314.mail.mud.yahoo.com (web30314.mail.mud.yahoo.com [209.191.69.76]) by mx1.FreeBSD.org (Postfix) with SMTP id C1BDA43D46 for ; Fri, 15 Sep 2006 09:05:14 +0000 (GMT) (envelope-from arne_woerner@yahoo.com) Received: (qmail 90095 invoked by uid 60001); 15 Sep 2006 09:05:14 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=59PBbUZ/JuBuUTxYMoU/QQAGGp6qya+v4Vm6vF4uyVIT2P5vvBmn4XIgaIbejZigKaIX03ZfAzg3oucVjymiyB6gwGDJXQMFQwi7Y+nPol2U5oVv16GBTqxA/+hgzauFALvUYYhr0m4JWOktVSE82bTHqJtrt8tZUjaosv7Bvy4= ; Message-ID: <20060915090514.90093.qmail@web30314.mail.mud.yahoo.com> Received: from [213.54.78.159] by web30314.mail.mud.yahoo.com via HTTP; Fri, 15 Sep 2006 02:05:14 PDT Date: Fri, 15 Sep 2006 02:05:14 -0700 (PDT) From: "R. B. Riddick" To: Oliver Fromme , freebsd-geom@FreeBSD.ORG In-Reply-To: <200609150849.k8F8nGBa004731@lurza.secnetix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: Subject: Re: gmirror size question 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, 15 Sep 2006 09:05:15 -0000 --- Oliver Fromme wrote: > PS: I think that hint should be mentioned in the Handbook > section about gmirror. It could prevent major foot-shoting. > Comments? > Hmm... I would say, if one buys a new disk, that is 1 sector too short *giggle*, one could still try the following plan: 0. single user mode 1. Make a new file system on the shorter&new disk 2. Move the data from the old disk to the new disk (MBR with dd, the rest with cpio or so) 3. Create a new gmirror just with the new disk as the only disk 4. Add the old disk to the new gmirror 5. Change the configuration in order to reflect the changed name of the gmirror. QEF (reboot inbetween whenever it seems necessary) -Arne __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From owner-freebsd-geom@FreeBSD.ORG Fri Sep 15 09:45:47 2006 Return-Path: X-Original-To: freebsd-geom@FreeBSD.ORG Delivered-To: freebsd-geom@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3E9F516A40F for ; Fri, 15 Sep 2006 09:45:47 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B3D543D45 for ; Fri, 15 Sep 2006 09:45:45 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (varonk@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id k8F9jdWe007298 for ; Fri, 15 Sep 2006 11:45:44 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id k8F9jdU6007297; Fri, 15 Sep 2006 11:45:39 +0200 (CEST) (envelope-from olli) Date: Fri, 15 Sep 2006 11:45:39 +0200 (CEST) Message-Id: <200609150945.k8F9jdU6007297@lurza.secnetix.de> From: Oliver Fromme To: freebsd-geom@FreeBSD.ORG In-Reply-To: <20060915090514.90093.qmail@web30314.mail.mud.yahoo.com> X-Newsgroups: list.freebsd-geom User-Agent: tin/1.8.0-20051224 ("Ronay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Fri, 15 Sep 2006 11:45:44 +0200 (CEST) Cc: Subject: Re: gmirror size question X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-geom@FreeBSD.ORG List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Sep 2006 09:45:47 -0000 R. B. Riddick wrote: > Oliver Fromme wrote: > > PS: I think that hint should be mentioned in the Handbook > > section about gmirror. It could prevent major foot-shoting. > > Comments? > > > Hmm... > > I would say, if one buys a new disk, that is 1 sector too short *giggle*, one > could still try the following plan: > 0. single user mode > 1. Make a new file system on the shorter&new disk > 2. Move the data from the old disk to the new disk (MBR with dd, the rest with > cpio or so) > 3. Create a new gmirror just with the new disk as the only disk > 4. Add the old disk to the new gmirror > 5. Change the configuration in order to reflect the changed name of the > gmirror. > QEF (reboot inbetween whenever it seems necessary) Yes, but that takes quite a lot of work and time. If you use RAID1, you don't want any downtime in the first place. Also, it might not be obvious to the person repairing the mirror that the new disk is too small. The EINVAL errno code isn't really very verbose about the root of the problem. If you use the gnop trick at the beginning, so the gmirror is somewhat smaller, then you can simply plug in the new drive, gmirror insert, and you're done. No downtime at all. You don't even have to remember anything special. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "[...] one observation we can make here is that Python makes an excellent pseudocoding language, with the wonderful attribute that it can actually be executed." -- Bruce Eckel From owner-freebsd-geom@FreeBSD.ORG Fri Sep 15 12:56:10 2006 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5F74716A47B for ; Fri, 15 Sep 2006 12:56:10 +0000 (UTC) (envelope-from lulf@stud.ntnu.no) Received: from signal.itea.ntnu.no (signal.itea.ntnu.no [129.241.190.231]) by mx1.FreeBSD.org (Postfix) with ESMTP id E7AB843D49 for ; Fri, 15 Sep 2006 12:56:09 +0000 (GMT) (envelope-from lulf@stud.ntnu.no) Received: from localhost (localhost [127.0.0.1]) by signal.itea.ntnu.no (Postfix) with ESMTP id 49BBC34282; Fri, 15 Sep 2006 14:56:06 +0200 (CEST) Received: from gaupe.stud.ntnu.no (gaupe.stud.ntnu.no [129.241.56.184]) by signal.itea.ntnu.no (Postfix) with ESMTP; Fri, 15 Sep 2006 14:56:04 +0200 (CEST) Received: by gaupe.stud.ntnu.no (Postfix, from userid 2312) id DDF1FD0009; Fri, 15 Sep 2006 14:56:07 +0200 (CEST) Date: Fri, 15 Sep 2006 14:56:07 +0200 From: Ulf Lilleengen To: "Peter A. Giessel" Message-ID: <20060915125607.GA2722@stud.ntnu.no> References: <45097F3B.2060606@dot.state.ak.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45097F3B.2060606@dot.state.ak.us> User-Agent: Mutt/1.5.9i X-Content-Scanned: with sophos and spamassassin at mailgw.ntnu.no. Cc: freebsd-geom@freebsd.org Subject: Re: Replacing failed drive in gvinum causes panic 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, 15 Sep 2006 12:56:10 -0000 On tor, sep 14, 2006 at 08:11:39 -0800, Peter A. Giessel wrote: > I'm getting the same thing as Ludo was getting about 9 months ago with > both 5.4 and 6.1 > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=55224+0+/usr/local/www/db/text/2005/freebsd-geom/20051225.freebsd-geom *snip* > > now, "gvinum create driveone" results in an immediate panic. Sometimes > gvinum will print: > "array.p0 degraded -> up" just before the panic. > > This seems odd to me since it should take a while for array.p0.s0 to > come back online, so its like its skipping the rebuild, coming up in > an odd state, and immediately panic'ing. Do you also have a different sized drive as Ludo had? The thing is, that a subdisk has a drive_offset that indicates where on the drive that a subdisk begin. Gvinum may not actually handle this. -- Mvh Ulf Lilleengen From owner-freebsd-geom@FreeBSD.ORG Fri Sep 15 15:49:19 2006 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BA35D16A403 for ; Fri, 15 Sep 2006 15:49:19 +0000 (UTC) (envelope-from peter_giessel@dot.state.ak.us) Received: from jnumail1.state.ak.us (jnumail1.state.ak.us [146.63.81.86]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7258043DA6 for ; Fri, 15 Sep 2006 15:49:01 +0000 (GMT) (envelope-from peter_giessel@dot.state.ak.us) Received: from smtpj.state.ak.us (localhost [127.0.0.1]) by jnumail1.state.ak.us (iPlanet Messaging Server 5.2 HotFix 2.04 (built Feb 8 2005)) with ESMTP id <0J5N001XF59MTB@jnumail1.state.ak.us> for freebsd-geom@freebsd.org; Fri, 15 Sep 2006 07:48:58 -0800 (AKDT) Received: from [192.168.0.193] ([158.145.111.132]) by smtpj.state.ak.us (iPlanet Messaging Server 5.2 HotFix 2.04 (built Feb 8 2005)) with ESMTP id <0J5N005D059K92@smtpj.state.ak.us>; Fri, 15 Sep 2006 07:48:57 -0800 (AKDT) Date: Fri, 15 Sep 2006 07:48:57 -0800 From: "Peter A. Giessel" In-reply-to: <20060915125607.GA2722@stud.ntnu.no> To: Ulf Lilleengen Message-id: <450ACB69.3090704@dot.state.ak.us> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7BIT User-Agent: Thunderbird 1.5.0.5 (Macintosh/20060719) References: <45097F3B.2060606@dot.state.ak.us> <20060915125607.GA2722@stud.ntnu.no> Cc: freebsd-geom@freebsd.org Subject: Re: Replacing failed drive in gvinum causes panic 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, 15 Sep 2006 15:49:19 -0000 On 2006/09/15 4:56, Ulf Lilleengen seems to have typed: > Do you also have a different sized drive as Ludo had? > The thing is, that a subdisk has a drive_offset that indicates where on the > drive that a subdisk begin. Gvinum may not actually handle this. > *slightly* Original configuration: ------------------------------- 6 drives: D one State: up /dev/ad18s1 A: 0/190732 MB (0%) D eleven State: up /dev/ad16s1 A: 47/190779 MB (0%) D two State: up /dev/ad14s1 A: 0/190732 MB (0%) D three State: up /dev/ad12s1 A: 47/190779 MB (0%) D four State: up /dev/ad11s1 A: 47/190779 MB (0%) D five State: up /dev/ad10s1 A: 47/190779 MB (0%) -------------------------------- As you can see, they vary from 190732 MB to 190779 MB, a difference of 47 MB. Am I understanding you correctly to say that I should adjust the slices so that all their slices are the same? instead of: ************************** # /dev/ad16s1: 8 partitions: # size offset fstype [fsize bsize bps/cpg] c: 390716802 0 unused 0 0 # "raw" part, don't edit h: 390716802 0 vinum # /dev/ad18s1: 8 partitions: # size offset fstype [fsize bsize bps/cpg] c: 390620412 0 unused 0 0 # "raw" part, don't edit h: 390620412 0 vinum ************************** Do something more like: ************************** # /dev/ad16s1: 8 partitions: # size offset fstype [fsize bsize bps/cpg] c: 390716802 0 unused 0 0 # "raw" part, don't edit h: 390620412 0 vinum # /dev/ad18s1: 8 partitions: # size offset fstype [fsize bsize bps/cpg] c: 390620412 0 unused 0 0 # "raw" part, don't edit h: 390620412 0 vinum ************************** Will that help problems in the future? From owner-freebsd-geom@FreeBSD.ORG Fri Sep 15 19:00:49 2006 Return-Path: X-Original-To: freebsd-geom@hub.freebsd.org Delivered-To: freebsd-geom@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EC5FC16A593 for ; Fri, 15 Sep 2006 19:00:48 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B54943D72 for ; Fri, 15 Sep 2006 19:00:43 +0000 (GMT) (envelope-from gnats@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 k8FJ0hIN089766 for ; Fri, 15 Sep 2006 19:00:43 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k8FJ0hNX089765; Fri, 15 Sep 2006 19:00:43 GMT (envelope-from gnats) Date: Fri, 15 Sep 2006 19:00:43 GMT Message-Id: <200609151900.k8FJ0hNX089765@freefall.freebsd.org> To: freebsd-geom@FreeBSD.org From: clemens fischer Cc: Subject: Re: kern/89102:[geom_vfs] [panic] panic when forced unmount FS from unplugged device X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: clemens fischer List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Sep 2006 19:00:49 -0000 The following reply was made to PR kern/89102; it has been noted by GNATS. From: clemens fischer To: bug-followup@FreeBSD.org, bu7cher@yandex.ru Cc: Subject: Re: kern/89102:[geom_vfs] [panic] panic when forced unmount FS from unplugged device Date: Fri, 15 Sep 2006 20:53:59 +0200 i had a crash related to this topic, but at another location. it happened after using umount(8) on a card-reader, but this time _without_ using the `-f' flag. the messages "(CTRL-C to abort)" were not shown on the screen, instead the machine just rebooted. here's the backtrace: --- start of dump --- /usr/obj/usr/src/sys/spott 0 # kgdb kernel.debug /var/crash/vmcore.2 kgdb: kvm_nlist(_stopped_cpus): kgdb: kvm_nlist(_stoppcbs): [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] GNU gdb 6.1.1 [FreeBSD] This GDB was configured as "i386-marcel-freebsd". Unread portion of the kernel message buffer: panic: vinvalbuf: dirty bufs Uptime: 1h12m4s (da0:dead_sim0:0:0:0): Synchronize cache failed, status == 0x8, scsi status == 0x0 Dumping 383 MB (2 chunks) chunk 0: 1MB (159 pages) ... ok chunk 1: 383MB (98048 pages) 368 352 336 320 304 288 272 (CTRL-C to abort) 256 (CTRL-C to abort) 240 (CTRL-C to abort) 224 208 192 176 160 144 128 112 96 80 64 48 32 (CTRL-C to abort) 16 (CTRL-C to abort) #0 doadump () at pcpu.h:165 165 __asm __volatile("movl %%fs:0,%0" : "=r" (td)); (kgdb) bt full #0 doadump () at pcpu.h:165 No locals. #1 0xc052d27c in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409 first_buf_printf = 1 #2 0xc052d589 in panic (fmt=0xc06cc79b "vinvalbuf: dirty bufs") at /usr/src/sys/kern/kern_shutdown.c:565 td = (struct thread *) 0xc2b8bd80 bootopt = 260 newpanic = 0 ap = 0xc2b8bd80 "\f\022@�\200�x�" buf = "vinvalbuf: dirty bufs", '\0' #3 0xc05984a0 in bufobj_invalbuf (bo=0xc3213e90, flags=1, td=0x0, slpflag=0, slptimeo=0) at /usr/src/sys/kern/vfs_subr.c:1015 error = 0 #4 0xc0598802 in vinvalbuf (vp=0xc3213dd0, flags=0, td=0x0, slpflag=0, slptimeo=0) at /usr/src/sys/kern/vfs_subr.c:1082 No locals. #5 0xc059baf4 in vgonel (vp=0xc3213dd0) at /usr/src/sys/kern/vfs_subr.c:2436 td = (struct thread *) 0xc2b8bd80 oweinact = 0 active = 1 mp = (struct mount *) 0xc270f400 #6 0xc059b9c8 in vgone (vp=0xc3213dd0) at /usr/src/sys/kern/vfs_subr.c:2391 No locals. #7 0xc04da8b6 in devfs_delete (dm=0xc27a4880, de=0xc32afb80) at /usr/src/sys/fs/devfs/devfs_devs.c:244 No locals. #8 0xc04dab2a in devfs_populate_loop (dm=0xc27a4880, cleanup=0) at /usr/src/sys/fs/devfs/devfs_devs.c:352 cdp = (struct cdev_priv *) 0xc2b8e600 de = (struct devfs_dirent *) 0xc32afb80 dd = (struct devfs_dirent *) 0x0 pdev = (struct cdev *) 0xc27aa000 j = 0 q = 0x0 s = 0xc27aa000 "\002" #9 0xc04dadd5 in devfs_populate (dm=0xc27a4880) at /usr/src/sys/fs/devfs/devfs_devs.c:448 No locals. #10 0xc04dd02f in devfs_lookupx (ap=0x0) at /usr/src/sys/fs/devfs/devfs_vnops.c:512 cnp = (struct componentname *) 0xd5d19be8 dvp = (struct vnode *) 0xc27aa000 vpp = (struct vnode **) 0xd5d19bd4 td = (struct thread *) 0xc2b8bd80 de = (struct devfs_dirent *) 0x2002 dd = (struct devfs_dirent *) 0xc27a4600 dde = (struct devfs_dirent **) 0x0 dmp = (struct devfs_mount *) 0xc27a4880 cdev = (struct cdev *) 0xc05ab1ac error = -1032173424 flags = 18923588 nameiop = 0 specname = "$\231��\000\000\000\000�\230��\"�X�\b\234z�\006\000\000\000,\234z�\200����\230�հ\233z��\230��إY�\233z°\233z�@\231��\016�Y�" pname = 0xc27ab805 "tty" #11 0xc04dd1ce in devfs_lookup (ap=0xd5d19998) at /usr/src/sys/fs/devfs/devfs_vnops.c:576 j = -707683944 dmp = (struct devfs_mount *) 0xc27a4890 #12 0xc06a7194 in VOP_LOOKUP_APV (vop=0xc06efbe0, a=0xd5d19998) at vnode_if.c:99 rc = -1066468384 #13 0xc05911fb in lookup (ndp=0xd5d19bc0) at vnode_if.h:56 cp = 0xc27ab808 "" dp = (struct vnode *) 0xc27aa000 tdp = (struct vnode *) 0xc27aa000 mp = (struct mount *) 0x0 docache = 32 wantparent = 0 rdonly = 0 trailing_slash = 0 error = 0 dpunlocked = 0 cnp = (struct componentname *) 0xd5d19be8 td = (struct thread *) 0xc2b8bd80 vfslocked = 0 dvfslocked = 0 tvfslocked = 0 #14 0xc0590968 in namei (ndp=0xd5d19bc0) at /usr/src/sys/kern/vfs_lookup.c:203 fdp = (struct filedesc *) 0xc32b1500 cp = 0xc32b1500 "" dp = (struct vnode *) 0xc27a9bb0 aiov = {iov_base = 0x0, iov_len = 0} auio = {uio_iov = 0xc01e0, uio_iovcnt = 0, uio_offset = 16384, uio_resid = 0, uio_segflg = 3273065636, uio_rw = UIO_READ, uio_td = 0x0} error = -1032152144 linklen = -1032152144 cnp = (struct componentname *) 0xd5d19be8 td = (struct thread *) 0xc2b8bd80 p = (struct proc *) 0x0 vfslocked = 0 #15 0xc05a9cd7 in vn_open_cred (ndp=0xd5d19bc0, flagp=0xd5d19cc0, cmode=2504, cred=0xc2bad780, fdidx=3) at /usr/src/sys/kern/vfs_vnops.c:182 vp = (struct vnode *) 0x0 mp = (struct mount *) 0x2 td = (struct thread *) 0xc2b8bd80 vat = {va_type = 3266887040, va_mode = 0, va_nlink = 0, va_uid = 3587283628, va_gid = 3226451657, va_fsid = 4294967280, va_fileid = 0, va_size = 15407266001175183363, va_blocksize = -1068515300, va_atime = { tv_sec = -1020586752, tv_nsec = 3}, va_mtime = {tv_sec = 256, tv_nsec = 3}, va_ctime = { tv_sec = -1020586752, tv_nsec = -1019211252}, va_birthtime = {tv_sec = -707683592, tv_nsec = -1068500313}, va_gen = 3274380544, va_flags = 3, va_rdev = 256, va_bytes = 3587283724, va_filerev = 17179874663, va_vaflags = 3275756044, va_spare = -1029671664} mode = -707683720 fmode = 1 error = -707683068 vfslocked = 0 #16 0xc05a99b3 in vn_open (ndp=0x0, flagp=0x0, cmode=0, fdidx=0) at /usr/src/sys/kern/vfs_vnops.c:91 td = (struct thread *) 0x0 #17 0xc05a05e8 in kern_open (td=0xc2b8bd80, path=0x0, pathseg=UIO_USERSPACE, flags=1, mode=-1077945896) at /usr/src/sys/kern/vfs_syscalls.c:1002 p = (struct proc *) 0x0 fdp = (struct filedesc *) 0xc32b1500 fp = (struct file *) 0xc2a07510 vp = (struct vnode *) 0xc2713800 vat = {va_type = 3275756044, va_mode = 40008, va_nlink = -10799, va_uid = 3226741305, va_gid = 3228675648, va_fsid = 3261295572, va_fileid = 0, va_size = 13858750082021694556, va_blocksize = 0, va_atime = {tv_sec = 0, tv_nsec = -1028080256}, va_mtime = {tv_sec = 6, tv_nsec = -1068226384}, va_ctime = { tv_sec = -1028080256, tv_nsec = -1033672064}, va_birthtime = {tv_sec = -1066434944, tv_nsec = 60211073}, va_gen = 3275756212, va_flags = 3275756044, va_rdev = 3587284176, va_bytes = 14031172999752930889, va_filerev = 8589934592, va_vaflags = 3119171692, va_spare = -134132641} mp = (struct mount *) 0xc31a9aa0 cmode = 0 nfp = (struct file *) 0xc2a07510 type = 0 indx = 3 error = -707683068 lf = {l_start = -4415571073916420396, l_len = -3039476491986403325, l_pid = -1068226135, l_type = -17024, l_whence = -15688} nd = {ni_dirp = 0x806120a
, ni_segflg = UIO_USERSPACE, ni_startdir = 0x0, ni_rootdir = 0xc27a9bb0, ni_topdir = 0x0, ni_vp = 0x0, ni_dvp = 0xc27aa000, ni_pathlen = 1, ni_next = 0xc27ab808 "", ni_loopcnt = 0, ni_cnd = {cn_nameiop = 0, cn_flags = 18923588, cn_thread = 0xc2b8bd80, cn_cred = 0xc2bad780, cn_lkflags = 2, cn_pnbuf = 0xc27ab800 "/dev/tty", cn_nameptr = 0xc27ab805 "tty", cn_namelen = 3, cn_consume = 0}} vfslocked = -1028080256 #18 0xc05a04d6 in open (td=0x0, uap=0xd5d19d04) at /usr/src/sys/kern/vfs_syscalls.c:968 error = -1028080256 #19 0xc0692c30 in syscall (frame= {tf_fs = 59, tf_es = 59, tf_ds = 59, tf_edi = 134599286, tf_esi = 134668416, tf_ebp = -1077945944, tf_isp = -707682972, tf_ebx = -1077945836, tf_edx = 53, tf_ecx = 134668416, tf_eax = 5, tf_trapno = 0, tf_err = 2, tf_eip = 672773295, tf_cs = 51, tf_eflags = 646, tf_esp = -1077945956, tf_ss = 59}) at /usr/src/sys/i386/i386/trap.c:981 params = 0xbfbfd9a0
callp = (struct sysent *) 0xc06f1b9c td = (struct thread *) 0xc2b8bd80 p = (struct proc *) 0xc340120c orig_tf_eflags = 646 sticks = 1 error = 0 narg = 3 args = {134615562, 0, -1077945896, -707683028, -1066837953, -1066330208, -707683020, 134629856} code = 5 #20 0xc067e03f in Xint0x80_syscall () at /usr/src/sys/i386/i386/exception.s:200 No locals. #21 0x00000033 in ?? () No symbol table info available. Previous frame inner to this frame (corrupt stack?) (kgdb) l layout list load (kgdb) l 200 call syscall 201 MEXITCOUNT 202 jmp doreti 203 204 ENTRY(fork_trampoline) 205 pushl %esp /* trapframe pointer */ 206 pushl %ebx /* arg1 */ 207 pushl %esi /* function */ 208 call fork_exit 209 addl $12,%esp --- end of dump --- i have two questions regarding this backtrace: [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] what does this mean? also: #20 0xc067e03f in Xint0x80_syscall () at /usr/src/sys/i386/i386/exception.s:200 No locals. #21 0x00000033 in ?? () No symbol table info available. Previous frame inner to this frame (corrupt stack?) you guys always post such beautiful kgdb usages with complete backtraces, why do i have a funny frame 21 (IP = 0x33)? regards, clemens From owner-freebsd-geom@FreeBSD.ORG Sat Sep 16 10:46:23 2006 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 831E416A40F for ; Sat, 16 Sep 2006 10:46:23 +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 9D7D443D45 for ; Sat, 16 Sep 2006 10:46:22 +0000 (GMT) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id ED9F7487F5; Sat, 16 Sep 2006 12:46:20 +0200 (CEST) Received: from localhost (dle44.neoplus.adsl.tpnet.pl [83.24.34.44]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 36EDE4569A; Sat, 16 Sep 2006 12:46:15 +0200 (CEST) Date: Sat, 16 Sep 2006 12:45:56 +0200 From: Pawel Jakub Dawidek To: Matthias Lederhofer Message-ID: <20060916104556.GD2874@garage.freebsd.pl> References: <20060910173643.GA22815@moooo.ath.cx> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="GpGaEY17fSl8rd50" Content-Disposition: inline In-Reply-To: <20060910173643.GA22815@moooo.ath.cx> 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=-0.5 required=3.0 tests=BAYES_00,RCVD_IN_NJABL_DUL, RCVD_IN_SORBS_DUL autolearn=no version=3.0.4 Cc: freebsd-geom@freebsd.org Subject: Re: [PATCH] geli: command to set the boot flag 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, 16 Sep 2006 10:46:23 -0000 --GpGaEY17fSl8rd50 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Sep 10, 2006 at 07:36:43PM +0200, Matthias Lederhofer wrote: > I did not find any way to set the boot flag other than init. Here is > a patch adding a new command setboot which shows the current value > when only a provider is passed or sets it to the value specified on > the command line. >=20 > Probably this should have another name and/or another way to pass the > parameters, I can also change this if someone tells me how this should > be done. I implemented functionality you asked for under 'configure' subcommand to be consistent with other GEOM classes. It allows to both set and remove the BOOT flag and it works for attached and detached providers. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --GpGaEY17fSl8rd50 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFFC9XkForvXbEpPzQRApoeAJ45Qq1wlZRGfK8VM/MLSBNjANHR5QCdECwz J0XwurRIoSKYcGkKR7l36rE= =AoZS -----END PGP SIGNATURE----- --GpGaEY17fSl8rd50-- From owner-freebsd-geom@FreeBSD.ORG Sat Sep 16 10:47:45 2006 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3BDF616A602 for ; Sat, 16 Sep 2006 10:47:45 +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 95E5243D4C for ; Sat, 16 Sep 2006 10:47:44 +0000 (GMT) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 5FD90487F5; Sat, 16 Sep 2006 12:47:43 +0200 (CEST) Received: from localhost (dle44.neoplus.adsl.tpnet.pl [83.24.34.44]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id DAE0B4569A; Sat, 16 Sep 2006 12:47:38 +0200 (CEST) Date: Sat, 16 Sep 2006 12:47:20 +0200 From: Pawel Jakub Dawidek To: Matthias Lederhofer Message-ID: <20060916104720.GE2874@garage.freebsd.pl> References: <20060910173643.GA22815@moooo.ath.cx> <20060910174908.GA26715@moooo.ath.cx> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="VUDLurXRWRKrGuMn" Content-Disposition: inline In-Reply-To: <20060910174908.GA26715@moooo.ath.cx> 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=-0.5 required=3.0 tests=BAYES_00,RCVD_IN_NJABL_DUL, RCVD_IN_SORBS_DUL autolearn=no version=3.0.4 Cc: freebsd-geom@freebsd.org Subject: Re: [PATCH] geli: command to set the boot flag 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, 16 Sep 2006 10:47:45 -0000 --VUDLurXRWRKrGuMn Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Sep 10, 2006 at 07:49:08PM +0200, Matthias Lederhofer wrote: > Matthias Lederhofer wrote: > > diff --git a/geom_eli.c b/geom_eli.c > This is for src/sbin/geam/class/eli. >=20 > And here is another patch for a comment I found while reading the > source, probably this was copied 'n' pasted. :) > --- > geom_eli.c | 2 +- > 1 files changed, 1 insertions(+), 1 deletions(-) >=20 > diff --git a/geom_eli.c b/geom_eli.c > index f90e974..489e212 100644 > --- a/geom_eli.c > +++ b/geom_eli.c > @@ -1058,7 +1058,7 @@ eli_restore(struct gctl_req *req) > gctl_error(req, "MD5 hash mismatch: not a geli backup file?"); > goto out; > } > - /* Read metadata from the provider. */ > + /* Write metadata to the provider. */ > if (pwrite(provfd, sector, secsize, mediasize - secsize) !=3D > (ssize_t)secsize) { > gctl_error(req, "Cannot write metadata: %s.", strerror(errno)); Committed, thanks. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --VUDLurXRWRKrGuMn Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFFC9Y4ForvXbEpPzQRAvjXAJsGFdJtXVXso8hPiwQ5bs0YpkVh5QCeLdbv gyhFpm/KFsTXJCRIMAx4Id8= =LSDL -----END PGP SIGNATURE----- --VUDLurXRWRKrGuMn-- From owner-freebsd-geom@FreeBSD.ORG Sat Sep 16 11:27:16 2006 Return-Path: X-Original-To: freebsd-geom@hub.freebsd.org Delivered-To: freebsd-geom@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CF58616A415; Sat, 16 Sep 2006 11:27:16 +0000 (UTC) (envelope-from pjd@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B80243D49; Sat, 16 Sep 2006 11:27:16 +0000 (GMT) (envelope-from pjd@FreeBSD.org) Received: from freefall.freebsd.org (pjd@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k8GBRGN9078837; Sat, 16 Sep 2006 11:27:16 GMT (envelope-from pjd@freefall.freebsd.org) Received: (from pjd@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k8GBRGVK078833; Sat, 16 Sep 2006 11:27:16 GMT (envelope-from pjd) Date: Sat, 16 Sep 2006 11:27:16 GMT From: Pawel Jakub Dawidek Message-Id: <200609161127.k8GBRGVK078833@freefall.freebsd.org> To: pjd@FreeBSD.org, pjd@FreeBSD.org, freebsd-geom@FreeBSD.org Cc: Subject: Re: kern/73177: kldload geom_* causes panic due to memory exhaustion 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, 16 Sep 2006 11:27:16 -0000 Synopsis: kldload geom_* causes panic due to memory exhaustion Responsible-Changed-From-To: pjd->freebsd-geom Responsible-Changed-By: pjd Responsible-Changed-When: Sat Sep 16 11:25:55 UTC 2006 Responsible-Changed-Why: I wasn't able to reproduce it. Maybe someone else will have more luck. http://www.freebsd.org/cgi/query-pr.cgi?pr=73177 From owner-freebsd-geom@FreeBSD.ORG Sat Sep 16 18:58:01 2006 Return-Path: X-Original-To: freebsd-geom@FreeBSD.ORG Delivered-To: freebsd-geom@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E132816A40F for ; Sat, 16 Sep 2006 18:58:01 +0000 (UTC) (envelope-from arne_woerner@yahoo.com) Received: from web30302.mail.mud.yahoo.com (web30302.mail.mud.yahoo.com [209.191.69.64]) by mx1.FreeBSD.org (Postfix) with SMTP id 6B8D243D55 for ; Sat, 16 Sep 2006 18:58:01 +0000 (GMT) (envelope-from arne_woerner@yahoo.com) Received: (qmail 81223 invoked by uid 60001); 16 Sep 2006 18:58:00 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=yVrKzX05v7SjzR+CdePDDkJpCRgcYZxmEQDK7UdH1+RdpGa5n1n4l4Qvoz6qHxlVxsoRILhojANCaMVIm+tUQcM9yUsjgyaiEWxjswOKaz96Ed0XD8+Bu6D9nsIy6ZQ2NVxosUtgNNPaBjgYTD1eSfaT41IZQIT3iGkkYrw05hc= ; Message-ID: <20060916185800.81221.qmail@web30302.mail.mud.yahoo.com> Received: from [213.54.67.190] by web30302.mail.mud.yahoo.com via HTTP; Sat, 16 Sep 2006 11:58:00 PDT Date: Sat, 16 Sep 2006 11:58:00 -0700 (PDT) From: "R. B. Riddick" To: freebsd-geom@FreeBSD.ORG In-Reply-To: <200609150945.k8F9jdU6007297@lurza.secnetix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: Subject: Re: gmirror size question 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, 16 Sep 2006 18:58:02 -0000 --- Oliver Fromme wrote: > R. B. Riddick wrote: > Yes, but that takes quite a lot of work and time. If you > Yup! Right! > use RAID1, you don't want any downtime in the first place. > Also, it might not be obvious to the person repairing the > mirror that the new disk is too small. The EINVAL errno > code isn't really very verbose about the root of the > problem. > Yup! Maybe the G_RAID5_DEBUG should use 0 as its first argument and not 1, so that at least syslog mentions the reason why it failed... And the gmirror front end could try to be more context sensitive with its error messages... :-) Who writes the change request? I can do, if nobody else wants to do it... > If you use the gnop trick at the beginning, so the gmirror > is somewhat smaller, then you can simply plug in the new > drive, gmirror insert, and you're done. No downtime at > all. You don't even have to remember anything special. > Yup! Right! -Arne __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com