Today we lost an other zpool!
Fortunately it was only a backup repository.
SERVER144@/# zpool import zpool3
internal error: unexpected error 5 at line 773 of ../common/libzfs_pool.c
this zpool was a RAID10 from 4 HDS LUN.
trying to import it into snv_60 (recovery mode) doesn't work.
gino
Two conflicting answers to the same question? I guess we need someone to break
the tie :)
Hello,
I have been reading alot of good things about Raid-z,
but before I jump into it I have one unanswered
question i can't find a clear answer for.
Is it possible to enlarge the initial RAID
I was considering the same thing (but with 250GB drives)
and instead decided to start with 5*250GB
so that I could do raid-z2 instead
thinking that once you add one more drive
you'd rather have raidz2 than raidz
On 4/7/07, MC [EMAIL PROTECTED] wrote:
Two conflicting answers to the same
I'm running Nevada build 60 inside VMWare, it is a test rig with no data of
value.
SunOS b60 5.11 snv_60 i86pc i386 i86pc
I wanted to check out the FMA handling of a serious zpool error, so I did the
following:
2007-04-07.08:46:31 zpool create tank mirror c0d1 c1d1
2007-04-07.15:21:37 zpool
Hi All,
here is an other kind of kernel panic caused by ZFS that we found.
I have dumps if needed.
#zpool import
pool: zpool8
id: 7382567111495567914
state: ONLINE
status: The pool is formatted using an older on-disk version.
action: The pool can be imported using its name or numeric
In a recent message, I detailed the excessive checksum errors that
occurred after replacing a disk. It seems that after a resilver
completes, it leaves a large number of blocks in the pool which fail
to checksum properly. Afterward, it is necessary to scrub the pool in
order to correct these
