From owner-freebsd-geom@FreeBSD.ORG Sat Jan 28 23:40:40 2012 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 869CA106566C for ; Sat, 28 Jan 2012 23:40:40 +0000 (UTC) (envelope-from lee@dilkie.com) Received: from data.snhdns.com (data.snhdns.com [208.76.82.136]) by mx1.freebsd.org (Postfix) with ESMTP id 4DEF88FC14 for ; Sat, 28 Jan 2012 23:40:39 +0000 (UTC) Received: from borg.dilkie.com ([142.46.160.216] helo=[206.51.1.11]) by data.snhdns.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1RrGra-00083l-VG for freebsd-geom@freebsd.org; Sat, 28 Jan 2012 17:35:15 -0500 Message-ID: <4F24785F.20607@dilkie.com> Date: Sat, 28 Jan 2012 17:36:15 -0500 From: Lee Dilkie User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 MIME-Version: 1.0 To: freebsd-geom X-Enigmail-Version: 1.3.5 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - data.snhdns.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - dilkie.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: gmirror question, drive missing 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, 28 Jan 2012 23:40:40 -0000 Hi Folks, I'm hoping freebsd-goem is the correct place for this question. I had a server crash that had a gmirror array of two drives. It was my bootable disk and it failed in such a way that it wouldn't recover without swapping cables. So the original gmirror, gm0, had /dev/ad10 and /dev/ad11 as providers. Now, gmirror shows. $ gmirror status gm0 Name Status Components mirror/gm0 DEGRADED ad10 $ gmirror list gm0 Geom name: gm0 State: DEGRADED Components: 2 Balance: round-robin Slice: 4096 Flags: NONE GenID: 1 SyncID: 2 ID: 1837199655 Providers: 1. Name: mirror/gm0 Mediasize: 1000204885504 (931G) Sectorsize: 512 Mode: r5w5e6 Consumers: 1. Name: ad10 Mediasize: 1000204886016 (931G) Sectorsize: 512 Mode: r1w1e1 State: ACTIVE Priority: 0 Flags: DIRTY GenID: 1 SyncID: 2 ID: 3835414526 no mention of /dev/ad11 at all. however, I can dump the metadata and it's there, as far as I can tell. $ gmirror dump /dev/ad11 Metadata on /dev/ad11: magic: GEOM::MIRROR version: 4 name: gm0 mid: 1837199655 did: 1856327785 all: 2 genid: 0 syncid: 2 priority: 0 slice: 4096 balance: round-robin mediasize: 1000204885504 sectorsize: 512 syncoffset: 0 mflags: NONE dflags: DIRTY hcprovider: provsize: 1000204886016 MD5 hash: 5ac5a19c7e0b99b4852ba535297d413a and the working, ad10... $ gmirror dump /dev/ad10 Metadata on /dev/ad10: magic: GEOM::MIRROR version: 4 name: gm0 mid: 1837199655 did: 3835414526 all: 2 genid: 1 syncid: 2 priority: 0 slice: 4096 balance: round-robin mediasize: 1000204885504 sectorsize: 512 syncoffset: 0 mflags: NONE dflags: DIRTY hcprovider: provsize: 1000204886016 MD5 hash: 13cc9220591eb360cbdaea72edbe87d9 so what's happened? Do I simply perform a "gmirror insert gmo /dev/ad11" to re-setup the mirror or should something else be done? BTW, when I performed all my failure mode tests before, I never saw a provider disappear, gmirror simply rebuilt the array when the disk was plugged in. And I did move disks around the sata cables so they were both masters instead of the master/slave I had originally used with the mirror was set up, so I don't *think* swapping the sata cables did this but.... TIA, -lee