From owner-freebsd-geom@FreeBSD.ORG Mon Nov 11 08:24:14 2013 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 615ABEB3 for ; Mon, 11 Nov 2013 08:24:14 +0000 (UTC) (envelope-from erich@alogt.com) Received: from alogt.com (alogt.com [69.36.191.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 3B69922FE for ; Mon, 11 Nov 2013 08:24:14 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com; s=default; h=Content-Transfer-Encoding:Content-Type:Mime-Version:Message-ID:Subject:To:From:Date; bh=2RVkPGnVtUjWgqa+4v9KNW8bV5Hbao8u24R2mwuXh3I=; b=DM/rnX7oC9NpxY0yEbdsO39+rwyATlUTBlAqlvpGLzOKKs8yUdMQVD8QibDUfhk+i6z9R27ODlPc7TgpNotH0F1UYQUo7ZVjcGPJ1mOYWS84WzO0+hQ8R7Ks5hAq4dtnmcQ5dCPQM9EzcoRmpXRDTKgwEkxLQM6+hvE3z1pApdY=; Received: from [182.5.85.198] (port=31189 helo=X220.ovitrap.com) by sl-508-2.slc.westdc.net with esmtpsa (SSLv3:DHE-RSA-AES128-SHA:128) (Exim 4.80.1) (envelope-from ) id 1Vfmn6-000Ya5-Ey for freebsd-geom@freebsd.org; Mon, 11 Nov 2013 01:24:13 -0700 Date: Mon, 11 Nov 2013 16:24:00 +0800 From: Erich Dollansky To: freebsd-geom@freebsd.org Subject: documentation of GEOM data structures needed Message-ID: <20131111162400.0bc7dfef@X220.ovitrap.com> Organization: ALO Green Technologies X-Mailer: Claws Mail 3.9.2 (GTK+ 2.24.19; amd64-portbld-freebsd10.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alogt.com X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id: erich@alogt.com X-Source: X-Source-Args: X-Source-Dir: X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.14 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 Nov 2013 08:24:14 -0000 Hi, I would need a documentation of the GEOM data structure. A disk got damages in a strange way during the process of backing up data. It was partitioned with gpart as all my disks using the MBR schema. When creating the backup, the system crashed. The disk was not usable anymore. I found out that the MBR was overwritten before the backup was started while the beginning of the first partition seems to be ok. I hope to be able to recover the data saving me one week of work. Erich From owner-freebsd-geom@FreeBSD.ORG Mon Nov 11 09:18:39 2013 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 74F4B434 for ; Mon, 11 Nov 2013 09:18:39 +0000 (UTC) (envelope-from symbolics@gmx.com) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 122B02614 for ; Mon, 11 Nov 2013 09:18:39 +0000 (UTC) Received: from lemon ([80.7.17.14]) by mail.gmx.com (mrgmx101) with ESMTPSA (Nemesis) id 0MYKGj-1WAvPQ2121-00V9uv for ; Mon, 11 Nov 2013 10:18:37 +0100 Received: by lemon (Postfix, from userid 1001) id D8CA8EB2F2; Mon, 11 Nov 2013 09:18:36 +0000 (GMT) Date: Mon, 11 Nov 2013 09:18:36 +0000 From: symbolics@gmx.com To: freebsd-geom@freebsd.org Subject: Re: documentation of GEOM data structures needed Message-ID: <20131111091836.GA83261@lemon> References: <20131111162400.0bc7dfef@X220.ovitrap.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20131111162400.0bc7dfef@X220.ovitrap.com> X-Provags-ID: V03:K0:diDduCkeDMf6XpfEzOkLFdPw5SLx8PrEDuWdwvIw6hFj00L//dH qV+NeLP1CiFVG9UFH7GRwrDYjjdZ80EsvgX6yPK3UVrIykIRFaOWLglxMrlywuIxsCePFSM UUqfUfgIfcFAunXtCmF4BAzzZA88QHFIKLmYdBnHK/Sju1E159c1OgNm0EQ37qEwywpVfC0 67aQw3zeIto3VIK7Qj3Mw== X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.14 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 Nov 2013 09:18:39 -0000 On Mon, Nov 11, 2013 at 04:24:00PM +0800, Erich Dollansky wrote: > Hi, > > I would need a documentation of the GEOM data structure. A disk got > damages in a strange way during the process of backing up data. It was > partitioned with gpart as all my disks using the MBR schema. When > creating the backup, the system crashed. The disk was not usable > anymore. I found out that the MBR was overwritten before the backup was > started while the beginning of the first partition seems to be ok. > > I hope to be able to recover the data saving me one week of work. Hi Erich, As I understand things, you believe that your filesystems are okay and you just want to recreate the MBR so you can try to fsck and mount them? How did you set the disc MBR up in the first place? If you used the automatic scheme in the installer and you know the size of the disc, you could reconstruct things that way. What does `gpart show' look like at the moment? --sym From owner-freebsd-geom@FreeBSD.ORG Mon Nov 11 10:32:26 2013 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 22BA4869 for ; Mon, 11 Nov 2013 10:32:26 +0000 (UTC) (envelope-from erich@alogt.com) Received: from alogt.com (alogt.com [69.36.191.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id EB0E92A4A for ; Mon, 11 Nov 2013 10:32:25 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com; s=default; h=Content-Transfer-Encoding:Content-Type:Mime-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date; bh=TKK+pFaLW8YAsK0EN97lYVv477xdwTxDE5fKpOrXHG8=; b=yK4DYJFSPslOLmb9761jmbDcIE4jkbInK0Fk382ivegDQMWUK2Wk3SFbRI2GSN7uuofFiYhOHLOsjhhxFHjTOsRSkjRjC0wtn3LapAYKj84w29XWDkb3VVfGXz6fT7wAdNWyrsPryudSnURRZmzz7CdOYNLO6a1FOge9bynCE0c=; Received: from [182.5.85.198] (port=49975 helo=X220.ovitrap.com) by sl-508-2.slc.westdc.net with esmtpsa (SSLv3:DHE-RSA-AES128-SHA:128) (Exim 4.80.1) (envelope-from ) id 1Vfon9-001IHm-3K; Mon, 11 Nov 2013 03:32:24 -0700 Date: Mon, 11 Nov 2013 18:32:16 +0800 From: Erich Dollansky To: symbolics@gmx.com Subject: Re: documentation of GEOM data structures needed Message-ID: <20131111183216.5ec80e9e@X220.ovitrap.com> In-Reply-To: <20131111091836.GA83261@lemon> References: <20131111162400.0bc7dfef@X220.ovitrap.com> <20131111091836.GA83261@lemon> Organization: ALO Green Technologies X-Mailer: Claws Mail 3.9.2 (GTK+ 2.24.19; amd64-portbld-freebsd10.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alogt.com X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id: erich@alogt.com X-Source: X-Source-Args: X-Source-Dir: Cc: freebsd-geom@freebsd.org X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.14 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 Nov 2013 10:32:26 -0000 Hi Sym, On Mon, 11 Nov 2013 09:18:36 +0000 symbolics@gmx.com wrote: > On Mon, Nov 11, 2013 at 04:24:00PM +0800, Erich Dollansky wrote: > > Hi, > > > > I would need a documentation of the GEOM data structure. A disk got > > damages in a strange way during the process of backing up data. It > > was partitioned with gpart as all my disks using the MBR schema. > > When creating the backup, the system crashed. The disk was not > > usable anymore. I found out that the MBR was overwritten before the > > backup was started while the beginning of the first partition seems > > to be ok. > > > > I hope to be able to recover the data saving me one week of work. > > Hi Erich, > > As I understand things, you believe that your filesystems are okay and > you just want to recreate the MBR so you can try to fsck and mount this is the basic idea. > them? How did you set the disc MBR up in the first place? If you used > the automatic scheme in the installer and you know the size of the I used the manual way creating 6 partitions. > disc, you could reconstruct things that way. What does `gpart show' > look like at the moment? It does not come that far gpart list da0 gpart: No such geom: da0. is all I get. My luck is that I have three disks which are the type but manufactured with some months between. But their sizes differ a bit. I think that I should be able to recover much by just comparing the entries. Erich > > --sym > _______________________________________________ > 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 Mon Nov 11 11:06:49 2013 Return-Path: Delivered-To: freebsd-geom@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 0639491D for ; Mon, 11 Nov 2013 11:06:49 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E826D2CB0 for ; Mon, 11 Nov 2013 11:06:48 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id rABB6mJf082021 for ; Mon, 11 Nov 2013 11:06:48 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id rABB6mLX082019 for freebsd-geom@FreeBSD.org; Mon, 11 Nov 2013 11:06:48 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 11 Nov 2013 11:06:48 GMT Message-Id: <201311111106.rABB6mLX082019@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-geom@FreeBSD.org Subject: Current problem reports assigned to freebsd-geom@FreeBSD.org X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.14 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 Nov 2013 11:06:49 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/181900 geom [geom] [patch] Line breaks missing in geli's kern.geom o kern/181704 geom [geom] ggatec crash the system when I write something o kern/179889 geom [geli] geli stopped work after updating RELEASE 9.* so o kern/178684 geom gpart(8) cannot get my GEOM tree o kern/178359 geom [geom] [patch] geom_eli: support external metadata o kern/176744 geom [geom] [patch] BIO_FLUSH not recorded by devstats o kern/170038 geom [geom] geom_mirror always starts degraded after reboot o kern/169539 geom [geom] [patch] fix ability to run gmirror on MSI MegaR a bin/169077 geom bsdinstall(8) does not use partition labels in /etc/fs f kern/165745 geom [geom] geom_multipath page fault on removed drive o kern/165428 geom [glabel][patch] Add xfs support to glabel o kern/164254 geom [geom] gjournal not stopping on GPT partitions o kern/164252 geom [geom] gjournal overflow o kern/164143 geom [geom] Partition table not recognized after upgrade R8 a kern/163020 geom [geli] [patch] enable the Camellia-XTS on GEOM ELI o kern/162690 geom [geom] gpart label changes only take effect after a re o kern/162010 geom [geli] panic: Provider's error should be set (error=0) o kern/161979 geom [geom] glabel doesn't update after newfs, and glabel s o bin/161807 geom [patch] add option for explicitly specifying metadata o kern/161752 geom [geom] glabel(8) doesn't get gpt label change o bin/161677 geom gpart(8) Probably bug in gptboot o kern/160409 geom [geli] failed to attach provider f kern/159595 geom [geom] [panic] panic on gmirror unload in vbox [regres f kern/159414 geom [isp] isp(4)+gmultipath(8) : removing active fiber pat p kern/158398 geom [headers] [patch] includes o kern/158197 geom [geom] geom_cache with size>1000 leads to panics o kern/157879 geom [libgeom] [regression] ABI change without version bump o kern/157863 geom [geli] kbdmux prevents geli passwords from being enter o kern/157739 geom [geom] GPT labels with geom_multipath o kern/157724 geom [geom] gpart(8) 'add' command must preserve gap for sc o kern/157723 geom [geom] GEOM should not process 'c' (raw) partitions fo o kern/157108 geom [gjournal] dumpon(8) fails on gjournal providers o kern/155994 geom [geom] Long "Suspend time" when reading large files fr o bin/154570 geom [patch] gvinum(8) can't be built as part of the kernel o kern/154226 geom [geom] GEOM label does not change when you modify them o kern/150858 geom [geom] [geom_label] [patch] glabel(8) is not compatibl o kern/150626 geom [geom] [gjournal] gjournal(8) destroys label o kern/150555 geom [geom] gjournal unusable on GPT partitions o kern/150334 geom [geom] [udf] [patch] geom label does not support UDF o kern/149762 geom volume labels with rogue characters o bin/149215 geom [panic] [geom_part] gpart(8): Delete linux's slice via o kern/147667 geom [gmirror] Booting with one component of a gmirror, the o kern/145818 geom [geom] geom_stat_open showing cached information for n o kern/145042 geom [geom] System stops booting after printing message "GE o kern/143455 geom gstripe(8) in RELENG_8 (31st Jan 2010) broken o kern/142563 geom [geom] [hang] ioctl freeze in zpool o kern/141740 geom [geom] gjournal(8): g_journal_destroy concurrent error o kern/140352 geom [geom] gjournal + glabel not working o kern/135898 geom [geom] Severe filesystem corruption - large files or l o kern/134113 geom [geli] Problem setting secondary GELI key o kern/133931 geom [geli] [request] intentionally wrong password to destr o bin/132845 geom [geom] [patch] ggated(8) does not close files opened a o bin/131415 geom [geli] keystrokes are unregulary sent to Geli when typ o kern/131353 geom [geom] gjournal(8) kernel lock o kern/129674 geom [geom] gjournal root did not mount on boot o kern/129645 geom gjournal(8): GEOM_JOURNAL causes system to fail to boo o kern/129245 geom [geom] gcache is more suitable for suffix based provid o kern/127420 geom [geom] [gjournal] [panic] Journal overflow on gmirrore o kern/124973 geom [gjournal] [patch] boot order affects geom_journal con o kern/124969 geom gvinum(8): gvinum raid5 plex does not detect missing s o kern/123962 geom [panic] [gjournal] gjournal (455Gb data, 8Gb journal), o kern/123122 geom [geom] GEOM / gjournal kernel lock o kern/122738 geom [geom] gmirror list "losts consumers" after gmirror de o kern/122067 geom [geom] [panic] Geom crashed during boot o kern/121364 geom [gmirror] Removing all providers create a "zombie" mir o kern/120091 geom [geom] [geli] [gjournal] geli does not prompt for pass o kern/115856 geom [geli] ZFS thought it was degraded when it should have o kern/115547 geom [geom] [patch] [request] let GEOM Eli get password fro o kern/113837 geom [geom] unable to access 1024 sector size storage o kern/113419 geom [geom] geom fox multipathing not failing back o kern/107707 geom [geom] [patch] [request] add new class geom_xbox360 to o kern/94632 geom [geom] Kernel output resets input while GELI asks for o kern/90582 geom [geom] [panic] Restore cause panic string (ffs_blkfree o bin/90093 geom fdisk(8) incapable of altering in-core geometry o kern/87544 geom [gbde] mmaping large files on a gbde filesystem deadlo o bin/86388 geom [geom] [geom_part] periodic(8) daily should backup gpa o kern/84556 geom [geom] [panic] GBDE-encrypted swap causes panic at shu o kern/79251 geom [2TB] newfs fails on 2.6TB gbde device o kern/79035 geom [vinum] gvinum unable to create a striped set of mirro o bin/78131 geom gbde(8) "destroy" not working. 80 problems total. From owner-freebsd-geom@FreeBSD.ORG Mon Nov 11 11:15:06 2013 Return-Path: Delivered-To: freebsd-geom@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id E4E3656D; Mon, 11 Nov 2013 11:15:06 +0000 (UTC) (envelope-from ae@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id BB3232EC4; Mon, 11 Nov 2013 11:15:06 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id rABBF6p2088979; Mon, 11 Nov 2013 11:15:06 GMT (envelope-from ae@freefall.freebsd.org) Received: (from ae@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id rABBF68S088978; Mon, 11 Nov 2013 11:15:06 GMT (envelope-from ae) Date: Mon, 11 Nov 2013 11:15:06 GMT Message-Id: <201311111115.rABBF68S088978@freefall.freebsd.org> To: fk@fabiankeil.de, ae@FreeBSD.org, freebsd-geom@FreeBSD.org, ae@FreeBSD.org From: ae@FreeBSD.org Subject: Re: kern/181900: [geom] [patch] Line breaks missing in geli's kern.geom.confxml entries X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.14 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 Nov 2013 11:15:07 -0000 Synopsis: [geom] [patch] Line breaks missing in geli's kern.geom.confxml entries State-Changed-From-To: open->patched State-Changed-By: ae State-Changed-When: Mon Nov 11 11:14:27 UTC 2013 State-Changed-Why: Patched in head/. Responsible-Changed-From-To: freebsd-geom->ae Responsible-Changed-By: ae Responsible-Changed-When: Mon Nov 11 11:14:27 UTC 2013 Responsible-Changed-Why: Take it. http://www.freebsd.org/cgi/query-pr.cgi?pr=181900 From owner-freebsd-geom@FreeBSD.ORG Mon Nov 11 14:41:07 2013 Return-Path: Delivered-To: freebsd-geom@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 85443BCF; Mon, 11 Nov 2013 14:41:07 +0000 (UTC) (envelope-from ae@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 5A6202BF1; Mon, 11 Nov 2013 14:41:07 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id rABEf7fS039409; Mon, 11 Nov 2013 14:41:07 GMT (envelope-from ae@freefall.freebsd.org) Received: (from ae@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id rABEf6sQ039408; Mon, 11 Nov 2013 14:41:06 GMT (envelope-from ae) Date: Mon, 11 Nov 2013 14:41:06 GMT Message-Id: <201311111441.rABEf6sQ039408@freefall.freebsd.org> To: kena@vodka-pomme.net, ae@FreeBSD.org, freebsd-geom@FreeBSD.org, ae@FreeBSD.org From: ae@FreeBSD.org Subject: Re: kern/121364: [gmirror] Removing all providers create a "zombie" mirror X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.14 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 Nov 2013 14:41:07 -0000 Synopsis: [gmirror] Removing all providers create a "zombie" mirror State-Changed-From-To: open->closed State-Changed-By: ae State-Changed-When: Mon Nov 11 14:39:41 UTC 2013 State-Changed-Why: This is already fixed with r235600 and merged to stable branches. Thanks! Responsible-Changed-From-To: freebsd-geom->ae Responsible-Changed-By: ae Responsible-Changed-When: Mon Nov 11 14:39:41 UTC 2013 Responsible-Changed-Why: Take it. http://www.freebsd.org/cgi/query-pr.cgi?pr=121364 From owner-freebsd-geom@FreeBSD.ORG Mon Nov 11 15:11:45 2013 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 3EDDB71D for ; Mon, 11 Nov 2013 15:11:45 +0000 (UTC) (envelope-from symbolics@gmx.com) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B37512E4E for ; Mon, 11 Nov 2013 15:11:44 +0000 (UTC) Received: from lemon ([80.7.17.14]) by mail.gmx.com (mrgmx102) with ESMTPSA (Nemesis) id 0MJmcS-1Vgzc23IBg-0016C8 for ; Mon, 11 Nov 2013 16:11:43 +0100 Received: by lemon (Postfix, from userid 1001) id 3B454EB2F2; Mon, 11 Nov 2013 15:11:41 +0000 (GMT) Date: Mon, 11 Nov 2013 15:11:41 +0000 From: symbolics@gmx.com To: freebsd-geom@freebsd.org Subject: Re: documentation of GEOM data structures needed Message-ID: <20131111151141.GA1381@lemon> References: <20131111162400.0bc7dfef@X220.ovitrap.com> <20131111091836.GA83261@lemon> <20131111183216.5ec80e9e@X220.ovitrap.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20131111183216.5ec80e9e@X220.ovitrap.com> X-Provags-ID: V03:K0:wN56HbFOi1vBuq+iyScwQ1IlzK32XohOHc6crFyeuhq4+kiURuT tP3V1Q9WnWxAHfjO3hgN6GJtH7OgSwDeD3D1aCrETkNg/anJEFgEHprFD9EsUussLCGloXX vxsyv9lUzmNtTPzWuixpbvW849fZpqc6nMsk+ZP82c7bd1iZGK6qHiIe8EHxi7vAjnOTchl Qkfuy+gyUnOHzqOQt36Cw== X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.14 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 Nov 2013 15:11:45 -0000 On Mon, Nov 11, 2013 at 06:32:16PM +0800, Erich Dollansky wrote: > Hi Sym, > > On Mon, 11 Nov 2013 09:18:36 +0000 > symbolics@gmx.com wrote: > > > On Mon, Nov 11, 2013 at 04:24:00PM +0800, Erich Dollansky wrote: > > > Hi, > > > > > > I would need a documentation of the GEOM data structure. A disk got > > > damages in a strange way during the process of backing up data. It > > > was partitioned with gpart as all my disks using the MBR schema. > > > When creating the backup, the system crashed. The disk was not > > > usable anymore. I found out that the MBR was overwritten before the > > > backup was started while the beginning of the first partition seems > > > to be ok. > > > > > > I hope to be able to recover the data saving me one week of work. > > > > Hi Erich, > > > > As I understand things, you believe that your filesystems are okay and > > you just want to recreate the MBR so you can try to fsck and mount > > this is the basic idea. > > > them? How did you set the disc MBR up in the first place? If you used > > the automatic scheme in the installer and you know the size of the > > I used the manual way creating 6 partitions. Do you know the sizes and order of how they were set up? They're all UFS2 or a mixture of other things too? > > disc, you could reconstruct things that way. What does `gpart show' > > look like at the moment? > > It does not come that far > > gpart list da0 > gpart: No such geom: da0. > > is all I get. > > My luck is that I have three disks which are the type but manufactured > with some months between. But their sizes differ a bit. I think that I > should be able to recover much by just comparing the entries. > You can try looking at diskinfo -v da0 to see the numbers. I had a little play around making a test disc and mdconfig. If I get some more time this evening I'll see if I can write a tool to scan the disc and recover the partition data, it'd be a good exercise. There are a few programmes in ports/sysutils you should try in the meantime. I didn't find them useful in my tests but that might not be indicative of anything. --sym From owner-freebsd-geom@FreeBSD.ORG Mon Nov 11 15:20:02 2013 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id AAFC9987 for ; Mon, 11 Nov 2013 15:20:02 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 5FD5E2EE1 for ; Mon, 11 Nov 2013 15:20:02 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.7/8.14.7) with ESMTP id rABFJvr9099616; Mon, 11 Nov 2013 08:19:57 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.7/8.14.7/Submit) with ESMTP id rABFJv1C099613; Mon, 11 Nov 2013 08:19:57 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Mon, 11 Nov 2013 08:19:57 -0700 (MST) From: Warren Block To: Erich Dollansky Subject: Re: documentation of GEOM data structures needed In-Reply-To: <20131111162400.0bc7dfef@X220.ovitrap.com> Message-ID: References: <20131111162400.0bc7dfef@X220.ovitrap.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Mon, 11 Nov 2013 08:19:57 -0700 (MST) Cc: freebsd-geom@freebsd.org X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.14 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 Nov 2013 15:20:02 -0000 On Mon, 11 Nov 2013, Erich Dollansky wrote: > I would need a documentation of the GEOM data structure. A disk got > damages in a strange way during the process of backing up data. It was > partitioned with gpart as all my disks using the MBR schema. When > creating the backup, the system crashed. The disk was not usable > anymore. I found out that the MBR was overwritten before the backup was > started while the beginning of the first partition seems to be ok. MBR does not have any specific GEOM structure. It's just a standard MBR: http://en.wikipedia.org/wiki/Master_boot_record See the end of the mdconfig(8) man page for an example of using it and gnop(8) to skip over an arbitrary length of data at the start of a disk. With that and file -s, you can attempt to find mountable filesystems on the whole disk. A script would be the fastest way. The first one should be relatively easy. After that, guessing approximate locations would speed it up a lot. From owner-freebsd-geom@FreeBSD.ORG Mon Nov 11 15:32:58 2013 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 7411CFC6 for ; Mon, 11 Nov 2013 15:32:58 +0000 (UTC) (envelope-from erich@alogt.com) Received: from alogt.com (alogt.com [69.36.191.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4BE032FED for ; Mon, 11 Nov 2013 15:32:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com; s=default; h=Content-Transfer-Encoding:Content-Type:Mime-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date; bh=ZwmK/BWPabvxdkhekZJaI6F38zQ991WbatnoKM3tMtk=; b=PxuJ4ORRnTTTxD+gG0X/IpQlXD89JUa7LBzdc3SVVurqfoRmfgtK82qPJSCjmL5drvzioicPcYdOw5tYGNY39R9k1FzPTNNQSn9WQxwoSvxYtOlKNvOTXPWFWNzPWWNV7giNHKW832GWCtkNr53bUXJuW1dvlrOPN20WDbnNa/o=; Received: from [182.5.85.198] (port=61836 helo=X220.ovitrap.com) by sl-508-2.slc.westdc.net with esmtpsa (SSLv3:DHE-RSA-AES128-SHA:128) (Exim 4.80.1) (envelope-from ) id 1VftTv-00320j-FQ; Mon, 11 Nov 2013 08:32:52 -0700 Date: Mon, 11 Nov 2013 23:32:43 +0800 From: Erich Dollansky To: Warren Block Subject: Re: documentation of GEOM data structures needed Message-ID: <20131111233243.0ee485be@X220.ovitrap.com> In-Reply-To: References: <20131111162400.0bc7dfef@X220.ovitrap.com> Organization: ALO Green Technologies X-Mailer: Claws Mail 3.9.2 (GTK+ 2.24.19; amd64-portbld-freebsd10.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alogt.com X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id: erich@alogt.com X-Source: X-Source-Args: X-Source-Dir: Cc: freebsd-geom@freebsd.org X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.14 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 Nov 2013 15:32:58 -0000 Hi, On Mon, 11 Nov 2013 08:19:57 -0700 (MST) Warren Block wrote: > On Mon, 11 Nov 2013, Erich Dollansky wrote: > > > I would need a documentation of the GEOM data structure. A disk got > > damages in a strange way during the process of backing up data. It > > was partitioned with gpart as all my disks using the MBR schema. > > When creating the backup, the system crashed. The disk was not > > usable anymore. I found out that the MBR was overwritten before the > > backup was started while the beginning of the first partition seems > > to be ok. > > MBR does not have any specific GEOM structure. It's just a standard > MBR: http://en.wikipedia.org/wiki/Master_boot_record this I knew. It points then to the container for the FreeBSD slices. > > See the end of the mdconfig(8) man page for an example of using it > and gnop(8) to skip over an arbitrary length of data at the start of > a disk. > I did not tell you the other effect I have with this disk. It boots until FreeBSD wants to mount /. So, the loaders somehow find the kernel etc. All seems to be there except the proper entries in the data structures defining the container and the individual partitions. > With that and file -s, you can attempt to find mountable filesystems > on the whole disk. A script would be the fastest way. The first one > should be relatively easy. After that, guessing approximate > locations would speed it up a lot. This is the alternative if my assumptions are wrong. Erich From owner-freebsd-geom@FreeBSD.ORG Mon Nov 11 15:50:46 2013 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id C3120886 for ; Mon, 11 Nov 2013 15:50:46 +0000 (UTC) (envelope-from erichsfreebsdlist@alogt.com) Received: from alogt.com (alogt.com [69.36.191.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9FEB7217C for ; Mon, 11 Nov 2013 15:50:46 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com; s=default; h=Content-Transfer-Encoding:Content-Type:Mime-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date; bh=Q+LAUrMzSUTT1QPSmwcQhglyzMF+MGNmGPYGZmVq+uA=; b=o2gnr9bDjQfitTxTB+/8kEYUxCeRA3vidb1EYkYZbxyDR4qDaDlldYZ5EknAC3GWqnucSaGwowhMWo5i3FPkFpHwx5UllYrnvgGMu9deMrqzUPYWbTX5FoZuiul3n+gHRsp5lwhJqKfsJpdgC8yaKw+zuwijTt/7CYvcMxKq52s=; Received: from [182.5.85.198] (port=25267 helo=X220.ovitrap.com) by sl-508-2.slc.westdc.net with esmtpsa (SSLv3:DHE-RSA-AES128-SHA:128) (Exim 4.80.1) (envelope-from ) id 1VftlE-0039Sy-Sb; Mon, 11 Nov 2013 08:50:46 -0700 Date: Mon, 11 Nov 2013 23:50:32 +0800 From: Erich Dollansky To: symbolics@gmx.com Subject: Re: documentation of GEOM data structures needed Message-ID: <20131111235032.6a6f26f7@X220.ovitrap.com> In-Reply-To: <20131111151141.GA1381@lemon> References: <20131111162400.0bc7dfef@X220.ovitrap.com> <20131111091836.GA83261@lemon> <20131111183216.5ec80e9e@X220.ovitrap.com> <20131111151141.GA1381@lemon> X-Mailer: Claws Mail 3.9.2 (GTK+ 2.24.19; amd64-portbld-freebsd10.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alogt.com X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id: erichsfreebsdlist@alogt.com X-Source: X-Source-Args: X-Source-Dir: Cc: freebsd-geom@freebsd.org X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.14 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 Nov 2013 15:50:46 -0000 Hi, On Mon, 11 Nov 2013 15:11:41 +0000 symbolics@gmx.com wrote: > On Mon, Nov 11, 2013 at 06:32:16PM +0800, Erich Dollansky wrote: > > > > On Mon, 11 Nov 2013 09:18:36 +0000 > > symbolics@gmx.com wrote: > > > > > On Mon, Nov 11, 2013 at 04:24:00PM +0800, Erich Dollansky wrote: > > > > > > > > I would need a documentation of the GEOM data structure. A disk > > > > got damages in a strange way during the process of backing up > > > > data. It was partitioned with gpart as all my disks using the > > > > MBR schema. When creating the backup, the system crashed. The > > > > disk was not usable anymore. I found out that the MBR was > > > > overwritten before the backup was started while the beginning > > > > of the first partition seems to be ok. > > > > > > > > I hope to be able to recover the data saving me one week of > > > > work. > > > > > > As I understand things, you believe that your filesystems are > > > okay and you just want to recreate the MBR so you can try to fsck > > > and mount > > > > this is the basic idea. > > > > > them? How did you set the disc MBR up in the first place? If you > > > used the automatic scheme in the installer and you know the size > > > of the > > > > I used the manual way creating 6 partitions. > > Do you know the sizes and order of how they were set up? They're all > UFS2 or a mixture of other things too? they are all UFS plus one swap. I have two other which should have the same partitioning with the exception that the size of the disk differ by a few sectors. This should only affect the end of the size of the last partition. > > > > disc, you could reconstruct things that way. What does `gpart > > > show' look like at the moment? > > > > It does not come that far > > > > gpart list da0 > > gpart: No such geom: da0. > > > > is all I get. > > > > My luck is that I have three disks which are the type but > > manufactured with some months between. But their sizes differ a > > bit. I think that I should be able to recover much by just > > comparing the entries. > > > > You can try looking at diskinfo -v da0 to see the numbers. > 512 # sectorsize 500107860480 # mediasize in bytes (466G) 976773165 # mediasize in sectors 0 # stripesize 0 # stripeoffset 60801 # Cylinders according to firmware. 255 # Heads according to firmware. 63 # Sectors according to firmware. 0000000000006121 # Disk ident. One other disk shows the same data while the third one shows this: 512 # sectorsize 500107862016 # mediasize in bytes (466G) 976773168 # mediasize in sectors 4096 # stripesize 0 # stripeoffset 15504336 # Cylinders according to firmware. 1 # Heads according to firmware. 63 # Sectors according to firmware. TF0504YS02ZPBP # Disk ident. > I had a little play around making a test disc and mdconfig. If I get > some more time this evening I'll see if I can write a tool to scan the > disc and recover the partition data, it'd be a good exercise. > > There are a few programmes in ports/sysutils you should try in the > meantime. I didn't find them useful in my tests but that might not be > indicative of anything. > This I will do tomorrow. Erich From owner-freebsd-geom@FreeBSD.ORG Mon Nov 11 16:48:08 2013 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 3D52BDF3 for ; Mon, 11 Nov 2013 16:48:08 +0000 (UTC) (envelope-from symbolics@gmx.com) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C2F622572 for ; Mon, 11 Nov 2013 16:48:07 +0000 (UTC) Received: from lemon ([80.7.17.14]) by mail.gmx.com (mrgmx001) with ESMTPSA (Nemesis) id 0LzKmP-1VbUu701Sb-014Pg7 for ; Mon, 11 Nov 2013 17:48:06 +0100 Received: by lemon (Postfix, from userid 1001) id 54966EB2F2; Mon, 11 Nov 2013 16:48:05 +0000 (GMT) Date: Mon, 11 Nov 2013 16:48:05 +0000 From: symbolics@gmx.com To: freebsd-geom@freebsd.org Subject: Re: documentation of GEOM data structures needed Message-ID: <20131111164805.GB1381@lemon> References: <20131111162400.0bc7dfef@X220.ovitrap.com> <20131111091836.GA83261@lemon> <20131111183216.5ec80e9e@X220.ovitrap.com> <20131111151141.GA1381@lemon> <20131111235032.6a6f26f7@X220.ovitrap.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20131111235032.6a6f26f7@X220.ovitrap.com> X-Provags-ID: V03:K0:6zhbR8OvSP0eMamMUeUnTaElGCIsBBtaLAei8vSqTKKSjhNjnzW FR3M6fpYX5xtqdrJCjIkxtILh69s1RYaUqU4fXZMmrIv/g3hf0Ib6m6VkxBtId5KA9NCdHA NqPVco0ekJjfaNM3A0Jd1Au8/lb4HS0botIj6xMBctDiVsggJNpyrK9D66Jxe5/V3Zj5rcq oalr+Qe7Qc9dIFJDphPRA== X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.14 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 Nov 2013 16:48:08 -0000 On Mon, Nov 11, 2013 at 11:50:32PM +0800, Erich Dollansky wrote: > Hi, > > On Mon, 11 Nov 2013 15:11:41 +0000 > symbolics@gmx.com wrote: > > > On Mon, Nov 11, 2013 at 06:32:16PM +0800, Erich Dollansky wrote: > > > > > > On Mon, 11 Nov 2013 09:18:36 +0000 > > > symbolics@gmx.com wrote: > > > > > > > On Mon, Nov 11, 2013 at 04:24:00PM +0800, Erich Dollansky wrote: > > > > > > > > > > I would need a documentation of the GEOM data structure. A disk > > > > > got damages in a strange way during the process of backing up > > > > > data. It was partitioned with gpart as all my disks using the > > > > > MBR schema. When creating the backup, the system crashed. The > > > > > disk was not usable anymore. I found out that the MBR was > > > > > overwritten before the backup was started while the beginning > > > > > of the first partition seems to be ok. > > > > > > > > > > I hope to be able to recover the data saving me one week of > > > > > work. > > > > > > > > As I understand things, you believe that your filesystems are > > > > okay and you just want to recreate the MBR so you can try to fsck > > > > and mount > > > > > > this is the basic idea. > > > > > > > them? How did you set the disc MBR up in the first place? If you > > > > used the automatic scheme in the installer and you know the size > > > > of the > > > > > > I used the manual way creating 6 partitions. > > > > Do you know the sizes and order of how they were set up? They're all > > UFS2 or a mixture of other things too? > > they are all UFS plus one swap. I have two other which should have the > same partitioning with the exception that the size of the disk differ > by a few sectors. This should only affect the end of the size of the > last partition. In which case run `gpart backup da1' (assuming da1 is the name of one of the intact discs). You can store the output text to a file and then edit it to fit. Then use `gpart restore da0' to apply it to the new disc. First of all, take backups of your existing MBRs, just in case: # gpart backup da1 > ~/da1.gpart ... If you like you can try to fit the first five partitions first and then worry about the last one later. If da1 is an intact disc then running the following piped command should reset all but the last partiton on da0: # gpart backup da1 | sed \$d | gpart restore da0 Try fscking and mounting the first five partitions and see how you get on. Hopefully they'll just work. > > > > disc, you could reconstruct things that way. What does `gpart > > > > show' look like at the moment? > > > > > > It does not come that far > > > > > > gpart list da0 > > > gpart: No such geom: da0. > > > > > > is all I get. > > > > > > My luck is that I have three disks which are the type but > > > manufactured with some months between. But their sizes differ a > > > bit. I think that I should be able to recover much by just > > > comparing the entries. > > > > > > > You can try looking at diskinfo -v da0 to see the numbers. > > > 512 # sectorsize > 500107860480 # mediasize in bytes (466G) > 976773165 # mediasize in sectors > 0 # stripesize > 0 # stripeoffset > 60801 # Cylinders according to firmware. > 255 # Heads according to firmware. > 63 # Sectors according to firmware. > 0000000000006121 # Disk ident. > > One other disk shows the same data while the third one shows this: > > 512 # sectorsize > 500107862016 # mediasize in bytes (466G) > 976773168 # mediasize in sectors > 4096 # stripesize > 0 # stripeoffset > 15504336 # Cylinders according to firmware. > 1 # Heads according to firmware. > 63 # Sectors according to firmware. > TF0504YS02ZPBP # Disk ident. > These look really different. Are you using other GEOM classes? What else is different about these discs? --sym From owner-freebsd-geom@FreeBSD.ORG Tue Nov 12 03:17:06 2013 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 59F9661A for ; Tue, 12 Nov 2013 03:17:06 +0000 (UTC) Received: from alogt.com (alogt.com [69.36.191.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 380B13AA1 for ; Tue, 12 Nov 2013 03:17:06 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com; s=default; h=Content-Transfer-Encoding:Content-Type:Mime-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date; bh=di3djeZx0Hmx2tyIt0PmKI7AJDf/RucOBYLf4Vull1U=; b=OXCX4CKvQGMx996rY+X9oaaNJ9nGcNqVR8Cc+rCpMuQ0eQfbA8R4UjTwOVKIcSbFkC182Op7PuzsKsXsW4IrlF/8iLNOrmJOqXLvy761c1qE4pm+2jwS05S07ZpBjc67xvCHCUXTh4aEC+6Usw1QwsxuUjA3jTGxMyoKSRZZfls=; Received: from [182.14.132.28] (port=31769 helo=X220.ovitrap.com) by sl-508-2.slc.westdc.net with esmtpsa (SSLv3:DHE-RSA-AES128-SHA:128) (Exim 4.80.1) (envelope-from ) id 1Vg4TP-00301R-Rt; Mon, 11 Nov 2013 20:17:05 -0700 Date: Tue, 12 Nov 2013 11:16:58 +0800 From: Erich Dollansky To: symbolics@gmx.com Subject: Re: documentation of GEOM data structures needed Message-ID: <20131112111658.4cb1ef95@X220.ovitrap.com> In-Reply-To: <20131111164805.GB1381@lemon> References: <20131111162400.0bc7dfef@X220.ovitrap.com> <20131111091836.GA83261@lemon> <20131111183216.5ec80e9e@X220.ovitrap.com> <20131111151141.GA1381@lemon> <20131111235032.6a6f26f7@X220.ovitrap.com> <20131111164805.GB1381@lemon> Organization: ALO Green Technologies X-Mailer: Claws Mail 3.9.2 (GTK+ 2.24.19; amd64-portbld-freebsd10.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alogt.com X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id: erich@alogt.com X-Source: X-Source-Args: X-Source-Dir: Cc: freebsd-geom@freebsd.org X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.16 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 Nov 2013 03:17:06 -0000 Hi, On Mon, 11 Nov 2013 16:48:05 +0000 symbolics@gmx.com wrote: > On Mon, Nov 11, 2013 at 11:50:32PM +0800, Erich Dollansky wrote: > > > > On Mon, 11 Nov 2013 15:11:41 +0000 > > symbolics@gmx.com wrote: > > > > > On Mon, Nov 11, 2013 at 06:32:16PM +0800, Erich Dollansky wrote: > > > > > > > > On Mon, 11 Nov 2013 09:18:36 +0000 > > > > symbolics@gmx.com wrote: > > > > > > > > > On Mon, Nov 11, 2013 at 04:24:00PM +0800, Erich Dollansky > > > > > wrote: > > > > > > > > > > > > I would need a documentation of the GEOM data structure. A > > > > > > disk got damages in a strange way during the process of > > > > > > backing up data. It was partitioned with gpart as all my > > > > > > disks using the MBR schema. When creating the backup, the > > > > > > system crashed. The disk was not usable anymore. I found > > > > > > out that the MBR was overwritten before the backup was > > > > > > started while the beginning of the first partition seems to > > > > > > be ok. > > > > > > > > > > > > I hope to be able to recover the data saving me one week of > > > > > > work. > > > > > > > > > > As I understand things, you believe that your filesystems are > > > > > okay and you just want to recreate the MBR so you can try to > > > > > fsck and mount > > > > > > > > this is the basic idea. > > > > > > > > > them? How did you set the disc MBR up in the first place? If > > > > > you used the automatic scheme in the installer and you know > > > > > the size of the > > > > > > > > I used the manual way creating 6 partitions. > > > > > > Do you know the sizes and order of how they were set up? They're > > > all UFS2 or a mixture of other things too? > > > > they are all UFS plus one swap. I have two other which should have > > the same partitioning with the exception that the size of the disk > > differ by a few sectors. This should only affect the end of the > > size of the last partition. > > In which case run `gpart backup da1' (assuming da1 is the name of one > of the intact discs). You can store the output text to a file and > then edit it to fit. Then use `gpart restore da0' to apply it to the > new disc. > > First of all, take backups of your existing MBRs, just in case: > I copied already the identified data structures into files. > # gpart backup da1 > ~/da1.gpart This is what I would like to avoid. I would like to understand how it works and do it manually. > ... > > If you like you can try to fit the first five partitions first and > then worry about the last one later. If da1 is an intact disc then > running the following piped command should reset all but the last > partiton on da0: > > # gpart backup da1 | sed \$d | gpart restore da0 > > Try fscking and mounting the first five partitions and see how you get > on. Hopefully they'll just work. > The hopefully is the point why I would like to do it by hand. I do not think that there is a huge secret behind. It is just that I did not find the documentation. Or doesn't it exist? > > > > > disc, you could reconstruct things that way. What does `gpart > > > > > show' look like at the moment? > > > > > > > > It does not come that far > > > > > > > > gpart list da0 > > > > gpart: No such geom: da0. > > > > > > > > is all I get. > > > > > > > > My luck is that I have three disks which are the type but > > > > manufactured with some months between. But their sizes differ a > > > > bit. I think that I should be able to recover much by just > > > > comparing the entries. > > > > > > > > > > You can try looking at diskinfo -v da0 to see the numbers. > > > > > 512 # sectorsize > > 500107860480 # mediasize in bytes (466G) > > 976773165 # mediasize in sectors > > 0 # stripesize > > 0 # stripeoffset > > 60801 # Cylinders according to firmware. > > 255 # Heads according to firmware. > > 63 # Sectors according to firmware. > > 0000000000006121 # Disk ident. > > > > One other disk shows the same data while the third one shows this: > > > > 512 # sectorsize > > 500107862016 # mediasize in bytes (466G) > > 976773168 # mediasize in sectors > > 4096 # stripesize > > 0 # stripeoffset > > 15504336 # Cylinders according to firmware. > > 1 # Heads according to firmware. > > 63 # Sectors according to firmware. > > TF0504YS02ZPBP # Disk ident. > > > > These look really different. Are you using other GEOM classes? What > else is different about these discs? The media size is already different. The drives are all Hitachi's with 4k sectors. They should be all from the same factory but obviously there is a difference. Erich From owner-freebsd-geom@FreeBSD.ORG Tue Nov 12 09:40:55 2013 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 27746C8 for ; Tue, 12 Nov 2013 09:40:55 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C39182D5E for ; Tue, 12 Nov 2013 09:40:54 +0000 (UTC) Received: from lemon ([80.7.17.14]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0LqQTl-1VAwFf48R7-00e1EI for ; Tue, 12 Nov 2013 10:40:51 +0100 Received: by lemon (Postfix, from userid 1001) id 6EC10EB300; Tue, 12 Nov 2013 09:40:50 +0000 (GMT) Date: Tue, 12 Nov 2013 09:40:50 +0000 From: symbolics@gmx.com To: freebsd-geom@freebsd.org Subject: Re: documentation of GEOM data structures needed Message-ID: <20131112094050.GA1808@lemon> References: <20131111162400.0bc7dfef@X220.ovitrap.com> <20131111091836.GA83261@lemon> <20131111183216.5ec80e9e@X220.ovitrap.com> <20131111151141.GA1381@lemon> <20131111235032.6a6f26f7@X220.ovitrap.com> <20131111164805.GB1381@lemon> <20131112111658.4cb1ef95@X220.ovitrap.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20131112111658.4cb1ef95@X220.ovitrap.com> X-Provags-ID: V03:K0:EWvMhK1PZ2aDNn8tCcWKgTWWt7HorKlc5E0qEp5MG31iL1ExG9w gb8isSQW4Y1fUE67qzUvL8R5Z6a/NUC3SgWRszeWR2Y5fxeGxFBcws4FxaeaZTDBd8mwesV HhgCRyAwUJzNsb+YKa4hmmkqJ45IkZM1K8VsocKGsc7nE+K9g2OE/oo9TkiXkqm6Cbp7N22 1ziMviFHeSY+yJIvXWXQg== X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.16 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 Nov 2013 09:40:55 -0000 On Tue, Nov 12, 2013 at 11:16:58AM +0800, Erich Dollansky wrote: > Hi, > [...] > > > > In which case run `gpart backup da1' (assuming da1 is the name of one > > of the intact discs). You can store the output text to a file and > > then edit it to fit. Then use `gpart restore da0' to apply it to the > > new disc. > > > > First of all, take backups of your existing MBRs, just in case: > > > I copied already the identified data structures into files. > > > # gpart backup da1 > ~/da1.gpart > > This is what I would like to avoid. I would like to understand how it > works and do it manually. The code is in sys/geom and sbin/geom. The structure definitions can be found in the header files in sys/geom. The backup command itself can be found in sbin/geom/class/part/geom_part.c. > > > > If you like you can try to fit the first five partitions first and > > then worry about the last one later. If da1 is an intact disc then > > running the following piped command should reset all but the last > > partiton on da0: > > > > # gpart backup da1 | sed \$d | gpart restore da0 > > > > Try fscking and mounting the first five partitions and see how you get > > on. Hopefully they'll just work. > > > The hopefully is the point why I would like to do it by hand. I do not > think that there is a huge secret behind. It is just that I did not > find the documentation. Or doesn't it exist? It depends on what you mean by documentation I suppose. Quite a lot of the GEOM API is documented to varying levels (something I intend to improve as my time allows). You can look at the sys/sys/diskmbr.h header file for some useful information though. The MBR format is documented on Wikipedia. > > > > > > disc, you could reconstruct things that way. What does `gpart > > > > > > show' look like at the moment? > > > > > > > > > > It does not come that far > > > > > > > > > > gpart list da0 > > > > > gpart: No such geom: da0. > > > > > > > > > > is all I get. > > > > > > > > > > My luck is that I have three disks which are the type but > > > > > manufactured with some months between. But their sizes differ a > > > > > bit. I think that I should be able to recover much by just > > > > > comparing the entries. > > > > > > > > > > > > > You can try looking at diskinfo -v da0 to see the numbers. > > > > > > > 512 # sectorsize > > > 500107860480 # mediasize in bytes (466G) > > > 976773165 # mediasize in sectors > > > 0 # stripesize > > > 0 # stripeoffset > > > 60801 # Cylinders according to firmware. > > > 255 # Heads according to firmware. > > > 63 # Sectors according to firmware. > > > 0000000000006121 # Disk ident. > > > > > > One other disk shows the same data while the third one shows this: > > > > > > 512 # sectorsize > > > 500107862016 # mediasize in bytes (466G) > > > 976773168 # mediasize in sectors > > > 4096 # stripesize > > > 0 # stripeoffset > > > 15504336 # Cylinders according to firmware. > > > 1 # Heads according to firmware. > > > 63 # Sectors according to firmware. > > > TF0504YS02ZPBP # Disk ident. > > > > > > > These look really different. Are you using other GEOM classes? What > > else is different about these discs? > > The media size is already different. The drives are all Hitachi's with > 4k sectors. They should be all from the same factory but obviously > there is a difference. > Ok, good luck. --sym From owner-freebsd-geom@FreeBSD.ORG Tue Nov 12 10:10:03 2013 Return-Path: Delivered-To: freebsd-geom@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B2446FB0 for ; Tue, 12 Nov 2013 10:10:03 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 889972F61 for ; Tue, 12 Nov 2013 10:10:03 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id rACAA2Zr086176 for ; Tue, 12 Nov 2013 10:10:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id rACAA2cY086175; Tue, 12 Nov 2013 10:10:02 GMT (envelope-from gnats) Date: Tue, 12 Nov 2013 10:10:02 GMT Message-Id: <201311121010.rACAA2cY086175@freefall.freebsd.org> To: freebsd-geom@FreeBSD.org Cc: From: Ivan Klymenko Subject: Re: kern/158197: [geom] geom_cache with size>1000 leads to panics X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list Reply-To: Ivan Klymenko List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Nov 2013 10:10:03 -0000 The following reply was made to PR kern/158197; it has been noted by GNATS. From: Ivan Klymenko To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/158197: [geom] geom_cache with size>1000 leads to panics Date: Tue, 12 Nov 2013 12:07:39 +0200 I have a similar situation but on the 10.0-BETA3 http://docs.freebsd.org/cgi/mid.cgi?20131112112825.0be85aee From owner-freebsd-geom@FreeBSD.ORG Wed Nov 13 04:55:50 2013 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 992BC4DA for ; Wed, 13 Nov 2013 04:55:50 +0000 (UTC) Received: from alogt.com (alogt.com [69.36.191.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 77AE32244 for ; Wed, 13 Nov 2013 04:55:50 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com; s=default; h=Content-Transfer-Encoding:Content-Type:Mime-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date; bh=t/Ztiqak/Qyf3OtMI7bQuQtBk6ehpFqlrH32LsSK+Po=; b=nYjVfPVjUimPWp0ZVBd1xgBHlSgYzuYN0rit1oYExlwgqN/H6Pe67M1Z6TpyaHnj38LFjuTYLu4P8UEQsY7SDLS0bqXkdZD7kyqrQL1sAIsdiLA7e8BoYycDxyPs5oC7XIDRlfG0OfNe3tGvnfMJ/KPpy1ZdPRgncpSnkEp8SAQ=; Received: from [182.11.142.138] (port=49221 helo=X220.ovitrap.com) by sl-508-2.slc.westdc.net with esmtpsa (SSLv3:DHE-RSA-AES128-SHA:128) (Exim 4.80.1) (envelope-from ) id 1VgSUP-003JfR-Ng; Tue, 12 Nov 2013 21:55:43 -0700 Date: Wed, 13 Nov 2013 12:55:36 +0800 From: Erich Dollansky To: symbolics@gmx.com Subject: Re: documentation of GEOM data structures needed Message-ID: <20131113125536.01a43e4b@X220.ovitrap.com> In-Reply-To: <20131112094050.GA1808@lemon> References: <20131111162400.0bc7dfef@X220.ovitrap.com> <20131111091836.GA83261@lemon> <20131111183216.5ec80e9e@X220.ovitrap.com> <20131111151141.GA1381@lemon> <20131111235032.6a6f26f7@X220.ovitrap.com> <20131111164805.GB1381@lemon> <20131112111658.4cb1ef95@X220.ovitrap.com> <20131112094050.GA1808@lemon> X-Mailer: Claws Mail 3.9.2 (GTK+ 2.24.19; amd64-portbld-freebsd10.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alogt.com X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id: erichsfreebsdlist@alogt.com X-Source: X-Source-Args: X-Source-Dir: Cc: freebsd-geom@freebsd.org X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Nov 2013 04:55:50 -0000 Hi, On Tue, 12 Nov 2013 09:40:50 +0000 symbolics@gmx.com wrote: > On Tue, Nov 12, 2013 at 11:16:58AM +0800, Erich Dollansky wrote: > > > > > > In which case run `gpart backup da1' (assuming da1 is the name of > > > one of the intact discs). You can store the output text to a file > > > and then edit it to fit. Then use `gpart restore da0' to apply it > > > to the new disc. > > > > > > First of all, take backups of your existing MBRs, just in case: > > > > > I copied already the identified data structures into files. > > > > > # gpart backup da1 > ~/da1.gpart > > > > This is what I would like to avoid. I would like to understand how > > it works and do it manually. > > The code is in sys/geom and sbin/geom. The structure definitions can > be found in the header files in sys/geom. The backup command itself I missed the header files in sys/geom. The rest I have had found. > can be found in sbin/geom/class/part/geom_part.c. > > > > > > > If you like you can try to fit the first five partitions first and > > > then worry about the last one later. If da1 is an intact disc then > > > running the following piped command should reset all but the last > > > partiton on da0: > > > > > > # gpart backup da1 | sed \$d | gpart restore da0 > > > > > > Try fscking and mounting the first five partitions and see how > > > you get on. Hopefully they'll just work. > > > > > The hopefully is the point why I would like to do it by hand. I do > > not think that there is a huge secret behind. It is just that I did > > not find the documentation. Or doesn't it exist? > > It depends on what you mean by documentation I suppose. Quite a lot of > the GEOM API is documented to varying levels (something I intend to > improve as my time allows). You can look at the sys/sys/diskmbr.h > header file for some useful information though. The MBR format is > documented on Wikipedia. > I noticed that in FreeBSD data structures are hardly documented. When I was still programming, the first step during development was the documentation of the data structures. I kept this documentation in the header files. I must also say that I was massively influenced by Modula-2 and its creators. > > > > > > > disc, you could reconstruct things that way. What does > > > > > > > `gpart show' look like at the moment? > > > > > > > > > > > > It does not come that far > > > > > > > > > > > > gpart list da0 > > > > > > gpart: No such geom: da0. > > > > > > > > > > > > is all I get. > > > > > > > > > > > > My luck is that I have three disks which are the type but > > > > > > manufactured with some months between. But their sizes > > > > > > differ a bit. I think that I should be able to recover much > > > > > > by just comparing the entries. > > > > > > > > > > > > > > > > You can try looking at diskinfo -v da0 to see the numbers. > > > > > > > > > 512 # sectorsize > > > > 500107860480 # mediasize in bytes (466G) > > > > 976773165 # mediasize in sectors > > > > 0 # stripesize > > > > 0 # stripeoffset > > > > 60801 # Cylinders according to firmware. > > > > 255 # Heads according to firmware. > > > > 63 # Sectors according to firmware. > > > > 0000000000006121 # Disk ident. > > > > > > > > One other disk shows the same data while the third one shows > > > > this: > > > > > > > > 512 # sectorsize > > > > 500107862016 # mediasize in bytes (466G) > > > > 976773168 # mediasize in sectors > > > > 4096 # stripesize > > > > 0 # stripeoffset > > > > 15504336 # Cylinders according to firmware. > > > > 1 # Heads according to firmware. > > > > 63 # Sectors according to firmware. > > > > TF0504YS02ZPBP # Disk ident. > > > > > > > > > > These look really different. Are you using other GEOM classes? > > > What else is different about these discs? > > > > The media size is already different. The drives are all Hitachi's > > with 4k sectors. They should be all from the same factory but > > obviously there is a difference. > > > > Ok, good luck. Thank you. Erich From owner-freebsd-geom@FreeBSD.ORG Wed Nov 13 09:32:16 2013 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D6059BA1 for ; Wed, 13 Nov 2013 09:32:16 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 70F02218F for ; Wed, 13 Nov 2013 09:32:16 +0000 (UTC) Received: from lemon ([80.7.17.14]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0MLvLE-1VoFV62tUC-007nve for ; Wed, 13 Nov 2013 10:32:08 +0100 Received: by lemon (Postfix, from userid 1001) id CD8A3EB27E; Wed, 13 Nov 2013 09:32:07 +0000 (GMT) Date: Wed, 13 Nov 2013 09:32:07 +0000 From: symbolics@gmx.com To: freebsd-geom@freebsd.org Subject: Re: documentation of GEOM data structures needed Message-ID: <20131113093207.GA60246@lemon> References: <20131111162400.0bc7dfef@X220.ovitrap.com> <20131111091836.GA83261@lemon> <20131111183216.5ec80e9e@X220.ovitrap.com> <20131111151141.GA1381@lemon> <20131111235032.6a6f26f7@X220.ovitrap.com> <20131111164805.GB1381@lemon> <20131112111658.4cb1ef95@X220.ovitrap.com> <20131112094050.GA1808@lemon> <20131113125536.01a43e4b@X220.ovitrap.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20131113125536.01a43e4b@X220.ovitrap.com> X-Provags-ID: V03:K0:6GsZxtIWSpuQnjdF/UQR5tcXg5E4d9DlCQRPlvDZJIDb0Rq6pZD HXfFihkQjimdxEnCpgGzYtcDdm6z4TLMcimYXzaPF4v3cekKVpAZ5yfFTV/NpNjTX44NSke Ipwe+LmYN8ROyKrGHMsqJJYzLVVZEYOdOUJpbtQQdgG53yDOKWiFIway+6ZN6UUS5Hg7QqJ pYrU0Sf76kjBhll85aukw== X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Nov 2013 09:32:16 -0000 On Wed, Nov 13, 2013 at 12:55:36PM +0800, Erich Dollansky wrote: [...] > I noticed that in FreeBSD data structures are hardly documented. When I > was still programming, the first step during development was the > documentation of the data structures. I kept this documentation in the > header files. Hi, I agree, I would like more comprehensive documentation too. --sym From owner-freebsd-geom@FreeBSD.ORG Wed Nov 13 16:47:25 2013 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D35E3548 for ; Wed, 13 Nov 2013 16:47:25 +0000 (UTC) Received: from filter2.win.net (filter2.win.net [216.24.27.102]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2106F2E6E for ; Wed, 13 Nov 2013 16:47:25 +0000 (UTC) Received: from nb-202.win.net (nb-202.win.net [216.24.27.202]) by filter2.win.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id rADGlIjD022020 for ; Wed, 13 Nov 2013 11:47:18 -0500 Received: from Gantry (pool245.office.win.net [216.24.33.245]) by nb-202.win.net (Postfix) with SMTP id C8AD3228EA for ; Wed, 13 Nov 2013 11:47:17 -0500 (EST) Message-ID: From: "Joseph Mays" To: Subject: Expanding a partition in gpart after increasing the size of an array. Date: Wed, 13 Nov 2013 11:47:19 -0500 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 15.4.3538.513 X-MimeOLE: Produced By Microsoft MimeOLE V15.4.3538.513 X-Spam-Score: undef - mays@win.net is whitelisted. X-CanIt-Geo: ip=216.24.27.202; country=US; region=KY; city=Louisville; postalcode=40204; latitude=38.2390; longitude=-85.7174; metrocode=529; areacode=502; http://maps.google.com/maps?q=38.2390,-85.7174&z=6 X-CanItPRO-Stream: Outbound:default (inherits from base:default) X-Canit-Stats-ID: 01KN4Lio3 - 8556382802cb - 20131113 X-Antispam-Training-Forget: http://filter.win.net/canit/b.php?i=01KN4Lio3&m=8556382802cb&t=20131113&c=f X-Antispam-Training-Nonspam: http://filter.win.net/canit/b.php?i=01KN4Lio3&m=8556382802cb&t=20131113&c=n X-Antispam-Training-Spam: http://filter.win.net/canit/b.php?i=01KN4Lio3&m=8556382802cb&t=20131113&c=s X-Scanned-By: CanIt (www . roaringpenguin . com) on 216.24.27.102 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.16 X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Nov 2013 16:47:25 -0000 I have a freebsd box with an LSI Raid controller in it. It had 4 = 3-terabyte drives configured in an 8TB array. I added a 5th drive and = built that into the array. Of course, the amount of drive space that = shows in operation in FreeBSD did not change, presumably because I need = to resize the partition. I was trying to follow the partition resizing instructions shown here = --- http://www.unibia.com/unibianet/freebsd/resize-your-existing-freebsd-root= -partitionslice-safely-without-re-installing but when I do the =E2=80=9Cgpart show =E2=80=9D I don=E2=80=99t see the = free space. What I do see is a change in the apparent overall size of = the disk and a set of parititions that don=E2=80=99t add up to the new = size of the disk. Is there a way to tell gpart that the size of the drive has changed? From owner-freebsd-geom@FreeBSD.ORG Wed Nov 13 17:07:13 2013 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8021AF9B for ; Wed, 13 Nov 2013 17:07:13 +0000 (UTC) Received: from filter2.win.net (filter2.win.net [216.24.27.102]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 43B682FEC for ; Wed, 13 Nov 2013 17:07:13 +0000 (UTC) Received: from nb-201.win.net (nb-201.win.net [216.24.27.201]) by filter2.win.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id rADH7Ckg030369 for ; Wed, 13 Nov 2013 12:07:12 -0500 Received: from Gantry (pool245.office.win.net [216.24.33.245]) by nb-201.win.net (Postfix) with SMTP id 457F661C08 for ; Wed, 13 Nov 2013 12:07:12 -0500 (EST) Message-ID: <690085F62D0F44DBAED44EB2604D948F@Gantry> From: "Joseph Mays" To: Subject: Re: Expanding a partition in gpart after increasing the size of an array. Date: Wed, 13 Nov 2013 12:07:14 -0500 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 15.4.3538.513 X-MimeOLE: Produced By Microsoft MimeOLE V15.4.3538.513 X-Spam-Score: undef - mays@win.net is whitelisted. X-CanIt-Geo: ip=216.24.27.201; country=US; region=KY; city=Louisville; postalcode=40204; latitude=38.2390; longitude=-85.7174; metrocode=529; areacode=502; http://maps.google.com/maps?q=38.2390,-85.7174&z=6 X-CanItPRO-Stream: Outbound:default (inherits from base:default) X-Canit-Stats-ID: 01KN57cpX - 3fbf7282527c - 20131113 X-Antispam-Training-Forget: http://filter.win.net/canit/b.php?i=01KN57cpX&m=3fbf7282527c&t=20131113&c=f X-Antispam-Training-Nonspam: http://filter.win.net/canit/b.php?i=01KN57cpX&m=3fbf7282527c&t=20131113&c=n X-Antispam-Training-Spam: http://filter.win.net/canit/b.php?i=01KN57cpX&m=3fbf7282527c&t=20131113&c=s X-Scanned-By: CanIt (www . roaringpenguin . com) on 216.24.27.102 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.16 X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Nov 2013 17:07:13 -0000 I was originally attaching the results of "gpart show" as a screenshot = because I was working through an internet kvm module on a system several = states away that was booted in standalone mode. But the mailing list = seems to strip off attachments, so I ssh'd into the system in normal = operation to get output of "gpart show" that I can cut and paste here. root@warehouse:/root # gpart show mfid0 =3D> 34 17578327997 mfid0 GPT (10T) [CORRUPT] 34 128 1 freebsd-boot (64k) 162 1048576000 2 freebsd-ufs (500G) 1048576162 16521363328 4 freebsd-ufs (7.7T) 17569939490 8388540 3 freebsd-swap (4G) 17578328030 1 - free - (512B) From: Joseph Mays=20 Sent: Wednesday, November 13, 2013 11:47 AM To: freebsd-geom@freebsd.org=20 Subject: Expanding a partition in gpart after increasing the size of an = array. I have a freebsd box with an LSI Raid controller in it. It had 4 = 3-terabyte drives configured in an 8TB array. I added a 5th drive and = built that into the array. Of course, the amount of drive space that = shows in operation in FreeBSD did not change, presumably because I need = to resize the partition. I was trying to follow the partition resizing instructions shown here = --- http://www.unibia.com/unibianet/freebsd/resize-your-existing-freebsd-root= -partitionslice-safely-without-re-installing but when I do the =E2=80=9Cgpart show =E2=80=9D I don=E2=80=99t see the = free space. What I do see is a change in the apparent overall size of = the disk and a set of parititions that don=E2=80=99t add up to the new = size of the disk. Is there a way to tell gpart that the size of the drive has changed? From owner-freebsd-geom@FreeBSD.ORG Wed Nov 13 18:45:30 2013 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4F51134D for ; Wed, 13 Nov 2013 18:45:30 +0000 (UTC) Received: from forward18.mail.yandex.net (forward18.mail.yandex.net [IPv6:2a02:6b8:0:1402::3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 02BB826FA for ; Wed, 13 Nov 2013 18:45:30 +0000 (UTC) Received: from smtp18.mail.yandex.net (smtp18.mail.yandex.net [95.108.252.18]) by forward18.mail.yandex.net (Yandex) with ESMTP id 44B3917827EF; Wed, 13 Nov 2013 22:45:17 +0400 (MSK) Received: from smtp18.mail.yandex.net (localhost [127.0.0.1]) by smtp18.mail.yandex.net (Yandex) with ESMTP id 0BD6018A02D8; Wed, 13 Nov 2013 22:45:16 +0400 (MSK) Received: from v3-150-120.yandex.net (v3-150-120.yandex.net [84.201.150.120]) by smtp18.mail.yandex.net (nwsmtp/Yandex) with ESMTP id Yp36Y5FQEI-jG2qMvgX; Wed, 13 Nov 2013 22:45:16 +0400 (using TLSv1 with cipher CAMELLIA256-SHA (256/256 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1384368316; bh=BL31jcWXy5IUd4rXOkRYROnuK8nwIsGOcVR9EDfmm9k=; h=Message-ID:Date:From:User-Agent:MIME-Version:To:Subject: References:In-Reply-To:X-Enigmail-Version:Content-Type: Content-Transfer-Encoding; b=k0ruCWJZEBwlecRJGjcJTTvgcgkKCbZ5Vs46dtIPd9Z3vpEgRfADNoUj8An+FwxY9 eF4irZ0RYz+S3dqyrRN+DeVOVXENzOVUZRo+Mjs43UP0C9Yj9duDsW35vNFh2U7/oi Tu7x6sIzEzPm8EIGWkY+glAPu8nhhFBznjUp/vXk= Authentication-Results: smtp18.mail.yandex.net; dkim=pass header.i=@yandex.ru Message-ID: <5283C7AD.2020103@yandex.ru> Date: Wed, 13 Nov 2013 22:40:45 +0400 From: "Andrey V. Elsukov" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1 MIME-Version: 1.0 To: Joseph Mays , freebsd-geom@freebsd.org Subject: Re: Expanding a partition in gpart after increasing the size of an array. References: <690085F62D0F44DBAED44EB2604D948F@Gantry> In-Reply-To: <690085F62D0F44DBAED44EB2604D948F@Gantry> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Nov 2013 18:45:30 -0000 On 13.11.2013 21:07, Joseph Mays wrote: > I was originally attaching the results of "gpart show" as a > screenshot because I was working through an internet kvm module on a > system several states away that was booted in standalone mode. But > the mailing list seems to strip off attachments, so I ssh'd into the > system in normal operation to get output of "gpart show" that I can > cut and paste here. > > root@warehouse:/root # gpart show mfid0 > => 34 17578327997 mfid0 GPT (10T) [CORRUPT] > 34 128 1 freebsd-boot (64k) > 162 1048576000 2 freebsd-ufs (500G) > 1048576162 16521363328 4 freebsd-ufs (7.7T) > 17569939490 8388540 3 freebsd-swap (4G) > 17578328030 1 - free - (512B) > Hi, you just need to do `gpart recover mfid0`. -- WBR, Andrey V. Elsukov From owner-freebsd-geom@FreeBSD.ORG Thu Nov 14 13:20:02 2013 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 78D9FA06 for ; Thu, 14 Nov 2013 13:20:02 +0000 (UTC) Received: from alogt.com (alogt.com [69.36.191.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 526F12A45 for ; Thu, 14 Nov 2013 13:20:02 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com; s=default; h=Content-Transfer-Encoding:Content-Type:Mime-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date; bh=qmbeN/rFoU57xnFOLcSREYwoUCDxXhYjQhLySx5jJsE=; b=UgW/vJ1uWKqB9PSCtTnXz3E3p/6tYcLvIFdc9SUBXkfQKMW+M0zFu9bGvUzN+G62Kh46ik1fLtK1vcV7QoKL9I7pdmekqbzTxfS9snwn1sOXAH2FCIGcqi9Zf2NI1Yue6AFTLSFbCWiKV1duUZvKn0bODjbsELAy3pLzsX3vZWc=; Received: from [182.8.41.140] (port=39858 helo=X220.ovitrap.com) by sl-508-2.slc.westdc.net with esmtpsa (SSLv3:DHE-RSA-AES128-SHA:128) (Exim 4.80.1) (envelope-from ) id 1Vgwpu-0017cx-CB; Thu, 14 Nov 2013 06:19:55 -0700 Date: Thu, 14 Nov 2013 21:19:44 +0800 From: Erich Dollansky To: symbolics@gmx.com Subject: Re: documentation of GEOM data structures needed Message-ID: <20131114211944.627cb247@X220.ovitrap.com> In-Reply-To: <20131113093207.GA60246@lemon> References: <20131111162400.0bc7dfef@X220.ovitrap.com> <20131111091836.GA83261@lemon> <20131111183216.5ec80e9e@X220.ovitrap.com> <20131111151141.GA1381@lemon> <20131111235032.6a6f26f7@X220.ovitrap.com> <20131111164805.GB1381@lemon> <20131112111658.4cb1ef95@X220.ovitrap.com> <20131112094050.GA1808@lemon> <20131113125536.01a43e4b@X220.ovitrap.com> <20131113093207.GA60246@lemon> X-Mailer: Claws Mail 3.9.2 (GTK+ 2.24.19; amd64-portbld-freebsd10.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alogt.com X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id: erichsfreebsdlist@alogt.com X-Source: X-Source-Args: X-Source-Dir: Cc: freebsd-geom@freebsd.org X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.16 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 Nov 2013 13:20:02 -0000 Hi, On Wed, 13 Nov 2013 09:32:07 +0000 symbolics@gmx.com wrote: > On Wed, Nov 13, 2013 at 12:55:36PM +0800, Erich Dollansky wrote: > [...] > > I noticed that in FreeBSD data structures are hardly documented. > > When I was still programming, the first step during development was > > the documentation of the data structures. I kept this documentation > > in the header files. > > > I agree, I would like more comprehensive documentation too. > I got meanwhile all data back. The MBR was overwritten with some other boot loader. I set the pointer in the MBR to the BSD label and was able to mount the disk. Irony is now that I still got the integrity check failed error message but all partitions have been mountable and the file system could be read. I did not run an fsck on the file systems. As the files in question all have been plain ASCII files, it was very easy to check if they got damaged. Your hint where to find the documentation of the BSD label was the key. Thanks! Erich From owner-freebsd-geom@FreeBSD.ORG Thu Nov 14 14:11:05 2013 Return-Path: Delivered-To: freebsd-geom@FreeBSD.org Received: from mx2.freebsd.org (mx2.freebsd.org [8.8.178.116]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0D7D75E0; Thu, 14 Nov 2013 14:11:05 +0000 (UTC) Received: from butcher-nb.yandex.net (hub.freebsd.org [IPv6:2001:1900:2254:206c::16:88]) by mx2.freebsd.org (Postfix) with ESMTP id 1762152FA; Thu, 14 Nov 2013 14:11:03 +0000 (UTC) Message-ID: <5284D8E1.6000104@FreeBSD.org> Date: Thu, 14 Nov 2013 18:06:25 +0400 From: "Andrey V. Elsukov" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1 MIME-Version: 1.0 To: freebsd-geom@FreeBSD.org Subject: [RFC/CFT] Resize support for geom_mirror X-Enigmail-Version: 1.6 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="fHjJt6or2l89KoUajA3NghHkCQoSxDgAW" Cc: Pawel Jakub Dawidek , trasz@FreeBSD.org X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.16 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 Nov 2013 14:11:05 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --fHjJt6or2l89KoUajA3NghHkCQoSxDgAW Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi All, I prepared the patch, that adds new verb "resize" to the gmirror(8) and such functionality to the geom_mirror(4). The main idea is to be able expand the mirror size after replacing all its components. But reducing the size also is possible. Also I added g_resize method, and now it automatically writes gmirror's metadata in the new last sector, when the parent provider changes the siz= e. Several notes about implementation: * `gmirror resize gm0` without exactly specified size will automatically calculate the maximum possible size for this mirror. * Reduce the size of the mirror when it is in use is possible only with debugflags=3D16. Pawel, please look at the case, when the size of the mirror reduced when synchronization is in progress. I guess it is enough to change the condition in g_mirror_sync_request? The patch is here: http://people.freebsd.org/~ae/g_mirror_resize.diff --=20 WBR, Andrey V. Elsukov --fHjJt6or2l89KoUajA3NghHkCQoSxDgAW Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQEcBAEBAgAGBQJShNjlAAoJEAHF6gQQyKF6EKcH/0UFJOP7b2M8DvoGXso7v3fk cZrXp3xo2yYCxeougVdXunRz1LYFbX5kJsP4ZIp/pH83BOhm72FkrCjoqFxhM7XX 0RfVgJYUuownLMFiShFSBZnkyCZAiuE14XSr7utdL8nupOz9vu2pxg+eB3kOUTi4 JkI9j+gtdXWDDVKasFD57Ax+HsJxM1w/MlxeysIW+7gaBTWppu4PIHvWLngJPh6z tJLsMYQoE4Ke+MFUrrqvrB3byDyAi5bY0H7G8Uh1ZBS9bYJAoYUANzH0mAw05kPD 6LLOJXibDBzN3Z2kV+yswhwiL566gaUZzDirSU4UecF7y51zSuyjxew4iNV0vHQ= =xhLr -----END PGP SIGNATURE----- --fHjJt6or2l89KoUajA3NghHkCQoSxDgAW--