From owner-freebsd-fs@FreeBSD.ORG  Wed May 22 18:04:28 2013
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by hub.freebsd.org (Postfix) with ESMTP id C5BEC757
 for <freebsd-fs@FreeBSD.org>; Wed, 22 May 2013 18:04:28 +0000 (UTC)
 (envelope-from avg@FreeBSD.org)
Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140])
 by mx1.freebsd.org (Postfix) with ESMTP id 193CDAB8
 for <freebsd-fs@FreeBSD.org>; Wed, 22 May 2013 18:04:27 +0000 (UTC)
Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua
 [212.40.38.101])
 by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id VAA13579;
 Wed, 22 May 2013 21:04:22 +0300 (EEST)
 (envelope-from avg@FreeBSD.org)
Message-ID: <519D08A6.8020401@FreeBSD.org>
Date: Wed, 22 May 2013 21:04:22 +0300
From: Andriy Gapon <avg@FreeBSD.org>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
 rv:17.0) Gecko/20130517 Thunderbird/17.0.6
MIME-Version: 1.0
To: Leslie Jensen <leslie@eskk.nu>
Subject: Re: Upgrading from 8.3 to 9.1 zfs pool can't attach
References: <519CA3A5.3020109@eskk.nu>
 <CAOjFWZ5y0tr68++=VQzdp6bz=nsVcWXfeiy_d+8r92XBRc+Bnw@mail.gmail.com>
 <519D0428.8060800@eskk.nu>
In-Reply-To: <519D0428.8060800@eskk.nu>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: freebsd-fs@FreeBSD.org
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 22 May 2013 18:04:28 -0000

on 22/05/2013 20:45 Leslie Jensen said the following:
> 
> 
> 2013-05-22 17:33, Freddie Cash skrev:
[snip]
>> On Wed, May 22, 2013 at 3:53 AM, Leslie Jensen <leslie@eskk.nu
>> <mailto:leslie@eskk.nu>> wrote:
[snip]
>>     ada2 and ada3 are configured as raid/r0 holding the system.
>>
>>     ada0, ada1, ada4 and ada5 should be a zfs pool with  /home

If you look at the messages below you can see that  ada0, ada1, ada4 and ada5 are
also claimed by the raid driver.


> May 22 19:34:03 bagnerbsd kernel: GEOM_RAID: Intel-165267ff: Disk ada0 state
> changed from NONE to ACTIVE.
> May 22 19:34:03 bagnerbsd kernel: GEOM_RAID: Intel-165267ff: Subdisk
> Volume0:1-ada0 state changed from NONE to ACTIVE.
> May 22 19:34:03 bagnerbsd kernel: GEOM_RAID: Intel-165267ff: Disk ada1 state
> changed from NONE to ACTIVE.
> May 22 19:34:03 bagnerbsd kernel: GEOM_RAID: Intel-165267ff: Subdisk
> Volume0:3-ada1 state changed from NONE to ACTIVE.

> May 22 19:34:03 bagnerbsd kernel: GEOM_RAID: SiI-100311082330: Disk ada4 state
> changed from NONE to ACTIVE.
> May 22 19:34:03 bagnerbsd kernel: GEOM_RAID: SiI-100311082330: Subdisk SiI Raid5
> Set:0-ada4 state changed from NONE to STALE.
> May 22 19:34:03 bagnerbsd kernel: GEOM_RAID: SiI-100311082330: Disk ada5 state
> changed from NONE to ACTIVE.
> May 22 19:34:03 bagnerbsd kernel: GEOM_RAID: SiI-100311082330: Subdisk SiI Raid5
> Set:1-ada5 state changed from NONE to STALE.

Apparently they used to be in raid configurations and the metadata was never
properly cleared.

-- 
Andriy Gapon