From owner-freebsd-fs@FreeBSD.ORG Fri May 6 06:30:04 2011 Return-Path: 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 4C1091065672 for ; Fri, 6 May 2011 06:30:04 +0000 (UTC) (envelope-from toasty@dragondata.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id DEEB58FC17 for ; Fri, 6 May 2011 06:30:01 +0000 (UTC) Received: by iwn33 with SMTP id 33so3398993iwn.13 for ; Thu, 05 May 2011 23:30:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dragondata.com; s=google; h=domainkey-signature:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=DjXDjVWUjuAzLLchb6K/E+cQ+5M2VxkhGvA+/4pgUfw=; b=nZBMT34w2PbQStFWMugQEd9jWY0XWiz/qSBT3jdO0en3eSCuaP4XagTnSU2sxd3i9P fD6ZthMuTpqbiJ/gp4r1EfeULXxtcNCLZrQ90gvUaB7x3yZYBev1qitd6nt7UA3UJ0Or WGLn8Br0EotADn7jz3IPr32KIrbTUEHkpN2cs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=dragondata.com; s=google; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=PBBzyf6/qxU+PJYpEMbBl0yV3WMGSSQAI/kJzMcK91trH0Rmznh0y07BdsC9qSA11e WSzV+mnmgcM5MGqijo8Z2FBcZSREXWYUj+cZ2CqICQBpst0fNZs1Bb7JiuKwatiRT/ij tjaq8svbW/Qgzy6fWcp27hh4JxxDyZ/pRN4Do= Received: by 10.42.159.65 with SMTP id k1mr2161427icx.174.1304663401225; Thu, 05 May 2011 23:30:01 -0700 (PDT) Received: from vpn168.ord02.your.org (vpn168.ord02.your.org [204.9.55.168]) by mx.google.com with ESMTPS id u17sm1229948ibm.28.2011.05.05.23.29.59 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 05 May 2011 23:29:59 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Kevin Day In-Reply-To: <6B7B3E48-08D5-47D1-85B4-FAA1EEE6764C@xcllnt.net> Date: Fri, 6 May 2011 01:29:57 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: <4A043649-429E-4CAC-8DB2-2275ECF552A0@dragondata.com> References: <6B7B3E48-08D5-47D1-85B4-FAA1EEE6764C@xcllnt.net> To: Marcel Moolenaar X-Mailer: Apple Mail (2.1084) Cc: freebsd-fs@freebsd.org Subject: Re: "gpart show" stuck in loop X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 May 2011 06:30:04 -0000 On May 5, 2011, at 10:11 PM, Marcel Moolenaar wrote: > Hi Kevin, >=20 > I reproduced the problem: >=20 Yay! > The first problem you have is that the MBR has overflows. > As you can see from my initial MBR, only 2.0TB out of the > 2.7T can be addressed, whereas yours addresses the whole > 2.7T. There must be an overflow condition. >=20 > The second problem is that more than 1 slice is marked > active. Yeah, I'm not exactly sure how the previous user of this storage array = ended up with this MBR. I believe he was using it in FreeBSD, but = probably something much older (6.x?). I don't know if it was actually = working or not with all the partitions, but I honestly can't see how. > I think we should do things: > 1. Protect the gpart tool against this, > 2. Fix the kernel to simply reject partitions that > fall outside of the addressable space (as determined > by the limitations of the scheme). >=20 > In your case it would mean that slice 3 would result > in slice 3 being inaccessable. >=20 > Given that you've been hit by this: do you feel that such > a change would be a better failure mode? Definitely. As it stands now, slice 3 isn't accessible anyway: # dd if=3D/dev/da0s3 of=3D/dev/null=20 dd: /dev/da0s3: Input/output error 0+0 records in 0+0 records out 0 bytes transferred in 0.000233 secs (0 bytes/sec) So allowing the rc startup to finish without hanging would be much = improved. Thanks for the speedy answer. :) -- Kevin