Date: Sun, 10 Mar 2013 02:15:10 +0900 From: Stephane LAPIE <stephane.lapie@darkbsd.org> To: freebsd-fs@freebsd.org Subject: Re: Panic loop on ZFS with 9.1-RELEASE Message-ID: <513B6E1E.6080805@darkbsd.org> In-Reply-To: <513B58B6.2090903@darkbsd.org> References: <513B58B6.2090903@darkbsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --]
Posting a quick update.
I ran a "zdb -emm" command to figure out what was going on, and it blew
up in my face with an abort trap here :
- vdev 0 has 145 metaslabs, which are cleared without any problems.
- vdev 1 has 145 metaslabs, but fails in the middle :
metaslab 32 offset 20000000000 spacemap 289 free 1.64G
segments 19509 maxsize 41.7M freepct 2%
metaslab 33 offset 21000000000 spacemap 303 free 11.9G
error: zfs: allocating allocated segment(offset=2335563722752 size=1024)
Abort trap(core dumped)
Converting offset 2335563722752 from earlier kernel panic messages gives
: 21fca723000, which matches the broken metaslab found by zdb.
Is there anything I can do at this point, using zdb?
It just sounds surrealistic I have ONE broken metaslab (seemingly?) and
that I can't recover anything...
Cheers,
On 03/10/2013 12:43 AM, Stephane LAPIE wrote:
> Hello list,
>
> I currently am faced with a sudden death case I can't understand at all,
> and I would be very appreciating of any explanation or assistance :(
>
> Here is my current kernel version :
> FreeBSD 9.1-STABLE FreeBSD 9.1-STABLE #5 r245055: Thu Jan 17 13:12:59
> JST 2013
> darksoul@eirei-no-za.yomi.darkbsd.org:/usr/obj/usr/storage/tech/eirei-no-za.yomi.darkbsd.org/usr/src/sys/DARK-2012KERN
> amd64
> (Kernel is basically a lightened GENERIC kernel without VESA options and
> unneeded controllers removed)
>
> The pool is a set of 3x raidz1 (5 drives), + 2 cache devices + mirrored
> transaction log
>
> Booting and trying to import the pool is met with :
> Solaris(panic): zfs: panic: allocating allocated
> segment(offset=2335563722752 size=1024)
>
> Booting single mode on my emergency flash card with a base OS and zpool
> import -o readonly=on is met with :
> panic: solaris assert: zio->io_type != ZIO_TYPE_WRITE ||
> spa_writeable(spa), file:
> /usr/storage/tech/eirei-no-za.yomi.darkbsd.org/usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c,
> line: 2461
>
> I tried zpool import -F -f, zpool import -F -f -m after removing the
> mirrored transaction log devices, but after 40s of trying to import, it
> just blows up.
>
> I am currently running "zdb -emm" as per the procedure suggested here :
> http://simplex.swordsaint.net/?p=199 if only to get some debug information.
>
> Thanks in advance for your time.
>
> Cheers,
>
>
> --
> Stephane LAPIE, EPITA SRS, Promo 2005
> "Even when they have digital readouts, I can't understand them."
> --MegaTokyo
[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/
iF4EAREIAAYFAlE7bh4ACgkQDJ4OK7D3FWSh6AEAjXH57LB79EthHQDPtaJkbLKt
VgyGWQoa2mAgw2qPMagBAMvBfS2roNM0mC8eQq/v4mejgGNi5KJ0IvmB2xUTyYzC
=H/PJ
-----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?513B6E1E.6080805>