From owner-freebsd-fs@FreeBSD.ORG Wed Jun 26 13:08:53 2013 Return-Path: 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 CC8247CC for ; Wed, 26 Jun 2013 13:08:53 +0000 (UTC) (envelope-from skeletor@lissyara.su) Received: from mx.lissyara.su (mx.lissyara.su [91.227.18.11]) by mx1.freebsd.org (Postfix) with ESMTP id 8ABEE169D for ; Wed, 26 Jun 2013 13:08:53 +0000 (UTC) Received: from [195.234.69.50] (port=41525 helo=[10.5.5.55]) by mx.lissyara.su with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1 (FreeBSD)) (envelope-from ) id 1UrpSu-000PCc-MT for freebsd-fs@freebsd.org; Wed, 26 Jun 2013 17:08:52 +0400 Message-ID: <51CAE7E6.8000708@lissyara.su> Date: Wed, 26 Jun 2013 16:08:54 +0300 From: skeletor User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6 MIME-Version: 1.0 To: freebsd-fs@freebsd.org Subject: Re: panic: Solaris(panic): zfs: allocating allocated segment References: <51CABB87.2020408@lissyara.su> In-Reply-To: <51CABB87.2020408@lissyara.su> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Description: if spam count > 60 - this is spam X-Spam-Count: 0 X-Descriptions: powered by www.lissyara.su X-Bounce-ID: mx.lissyara.su X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: skeletor@lissyara.su List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Jun 2013 13:08:53 -0000 26.06.2013 12:59, skeletor пишет: > Hello all. > > I have the same trouble, that this > http://lists.freebsd.org/pipermail/freebsd-current/2009-February/003039.html > > > Does it already fised or no? > > OS FreeBSD 9.1 Release amd64 From Solaris this pool successfully accessed, but in degraded state: # zpool status pool: dpool state: DEGRADED status: One or more devices are unavailable in response to persistent errors. Sufficient replicas exist for the pool to continue functioning in a degraded state. action: Determine if the device needs to be replaced, and clear the errors using 'zpool clear' or 'fmadm repaired', or replace the device with 'zpool replace'. Run 'zpool status -v' to see device specific details. scan: scrub repaired 64K in 0h3m with 0 errors on Sat Jun 22 17:10:17 2013 config: NAME STATE READ WRITE CKSUM dpool DEGRADED 0 0 0 raidz1-0 DEGRADED 0 0 0 c7t1d0p0 ONLINE 0 0 0 7844172536082216995 UNAVAIL 0 0 0 c7t3d0p0 ONLINE 0 0 0 errors: No known data errors