From owner-freebsd-fs@FreeBSD.ORG  Mon Dec 12 21:08:18 2011
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 05AEA1065672
	for <freebsd-fs@freebsd.org>; Mon, 12 Dec 2011 21:08:18 +0000 (UTC)
	(envelope-from Lee@Dilkie.com)
Received: from spock.dilkie.com (spock.dilkie.com [IPv6:2001:470:8900::40])
	by mx1.freebsd.org (Postfix) with ESMTP id 6338D8FC08
	for <freebsd-fs@freebsd.org>; Mon, 12 Dec 2011 21:08:16 +0000 (UTC)
Received: from [10.39.164.100] ([216.191.234.70]) (authenticated bits=0)
	by spock.dilkie.com (8.14.5/8.14.5) with ESMTP id pBCL89Qn040381
	(version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO);
	Mon, 12 Dec 2011 16:08:13 -0500 (EST) (envelope-from Lee@Dilkie.com)
X-DKIM: Sendmail DKIM Filter v2.8.3 spock.dilkie.com pBCL89Qn040381
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dilkie.com; s=mail;
	t=1323724095; bh=6bcED00MTSSaaEx8H84vQUMQFAHwmOoJ4NU03WbI4Nw=;
	h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References:
	In-Reply-To:Content-Type;
	b=RPy3Wm08xPEKgiRvR0atzg8nj82bDKC7PGzS3qIeRcT1vcrr+tJJcTcAwkRhFVJdt
	lxt9+PB+O48ypu17RvuuJVy5UELbX2Flv1XVrmViRMFZAal9K3zgxdiEM8eIujG
Message-ID: <4EE66D35.2060602@Dilkie.com>
Date: Mon, 12 Dec 2011 16:08:05 -0500
From: Lee Dilkie <Lee@Dilkie.com>
User-Agent: Mozilla/5.0 (Windows NT 5.2; WOW64;
	rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Diego Arias <dak.col@gmail.com>
References: <CANFKmJ+=_=PtzjY-6iw3Mc92U6XG_0ZYupRRg-rsJUZwe4FSUQ@mail.gmail.com>
	<CAGwmmWUxwAkfdjV4j2+Ot=o8-AxRkrU+7WTwVA6Zo2O3jX_erQ@mail.gmail.com>
In-Reply-To: <CAGwmmWUxwAkfdjV4j2+Ot=o8-AxRkrU+7WTwVA6Zo2O3jX_erQ@mail.gmail.com>
X-Enigmail-Version: 1.3.4
OpenPGP: id=9C23E113
X-Scanned-By: MIMEDefang 2.72 on 142.46.160.214
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
Cc: freebsd-fs@freebsd.org
Subject: Re: epic UFS crash
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/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: Mon, 12 Dec 2011 21:08:18 -0000



On 12/12/2011 2:35 PM, Diego Arias wrote:
> Hi:
>
> Maybe the other drive have the info updated, do you check that?

That's what occurred to me, the system was running with the other drive
as the only one with this drive as degraded and then things got reversed
on the re-boot.

If so, the other drive should be up to date.

-lee