From owner-freebsd-fs@FreeBSD.ORG Mon Jul 19 00:39:17 2010 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 E6ADD1065672 for ; Mon, 19 Jul 2010 00:39:17 +0000 (UTC) (envelope-from freebsd-fs@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id A4E038FC0A for ; Mon, 19 Jul 2010 00:39:17 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1OaeO3-0004Ib-T2 for freebsd-fs@freebsd.org; Mon, 19 Jul 2010 02:39:15 +0200 Received: from 193.33.173.33 ([193.33.173.33]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 19 Jul 2010 02:39:15 +0200 Received: from c.kworr by 193.33.173.33 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 19 Jul 2010 02:39:15 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-fs@freebsd.org From: Volodymyr Kostyrko Date: Mon, 19 Jul 2010 03:39:06 +0300 Lines: 25 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: 193.33.173.33 User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; uk-UA; rv:1.9.1.10) Gecko/20100713 Thunderbird/3.0.5 Subject: zfs corruption 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: Mon, 19 Jul 2010 00:39:18 -0000 Hi all. I have trouble accessing one zpool. It's set as bootable an it even manages to load and start kernel, so I suppose I can rip some files off it. Yet after loading kernel it spits out: panic: solaris asser: sm->sm_space + size <= sm->sm_size, file: /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/space_map.c, line:96 Line number is incorrect, I have added some extra code to obtain values: sm->sm_space = 2147483648 size = 34304 sm->sm_size = 2147483648 Yes, sm_space is equal to sm_size here, and this leads to panic. I'm still trying to page the code to understand where I can patch the driver to obtain a read only access. Have anyone saw that before? If so could someone spare some bits of knowledge? -- Sphinx of black quartz judge my vow.