So I was back on it again today and I was following this thread
http://opensolaris.org/jive/thread.jspa?threadID=70205tstart=15
and got the following error when I ran this command
zdb -e -bb rpool
Traversing all blocks to verify nothing leaked ...
Assertion failed: c SPA_MAXBLOCKSIZE
I redirected the console to the serial port and managed to capture the panic
information below:
SunOS Release 5.11 Version snv_111b 64-bit
Copyright 1983-2009 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
panic[cpu0]/thread=ff0007c39c60: mutex_enter: bad
When I boot from a snv133 live cd and attempt to import the rpool it panics
with this output:
Sun Microsystems Inc. SunOS 5.11 snv_133 February 2010
j...@opensolaris:~$ pfexec su
Mar 9 03:11:37 opensolaris su: 'su root' succeeded for jack on /dev/console
j...@opensolaris:~# zpool import
Found a site that recommended setting the following system file entries
set zfs:zfs_recover=1
set aok=1
and running this command
zdb -e -bcsvL rpool
but I get the following error:
Traversing all blocks to verify checksums ...
out of memory -- generating core dump
Abort
The laptop has 4GB of
Hi D,
Is this a 32-bit system?
We were looking at your panic messages and they seem to indicate a
problem with memory and not necessarily a problem with the pool or
the disk. Your previous zpool status output also indicates that the
disk is okay.
Maybe someone with similar recent memory
On 03/ 9/10 10:53 AM, Cindy Swearingen wrote:
Hi D,
Is this a 32-bit system?
We were looking at your panic messages and they seem to indicate a
problem with memory and not necessarily a problem with the pool or
the disk. Your previous zpool status output also indicates that the
disk is okay.
My Laptop is a 64bit system
Dell Latitude D630
Intel Core2 Duo Processor T7100
4GB RAM
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
