I'm seeing this too. Nothing unusual happened before the panic.
Just a shutdown (init 5) and later startup. I have the crashdump
and copy of the problem zpool (on swan). Here's the stack trace:
$C
ff0004463680 vpanic()
ff00044636b0 vcmn_err+0x28(3, f792ecf0, ff0004463778)
space_map_add+0xdb(ff014c1a21b8, 472785000, 1000)
space_map_load+0x1fc(ff014c1a21b8, fbd52568, 1,
ff014c1a1e88, ff0149c88c30)
running snv79.
hmm.. did you spend any time in snv_74 or snv_75 that might
have gotten
Hi,
On 09/29/07 22:00, Gavin Maltby wrote:
Hi,
Our zfs nfs build server running snv_73 (pool created back before
zfs integrated to ON) paniced I guess from zfs the first time
and now panics on attempted boot every time as below. Is this
a known issue and, more importantly (2TB of data in the
T3 comment below...
Gavin Maltby wrote:
Hi,
On 09/29/07 22:00, Gavin Maltby wrote:
Hi,
Our zfs nfs build server running snv_73 (pool created back before
zfs integrated to ON) paniced I guess from zfs the first time
and now panics on attempted boot every time as below. Is this
a known
On 10/01/07 17:01, Richard Elling wrote:
T3 comment below...
[cut]
A scrub is only 20% complete, but has found no errors thus far. I check
the T3 pair and no complaints there either - I did reboot them just for
luck (last reboot was 2 years ago, apparently!).
Living on the edge...
The T3
Hi,
Our zfs nfs build server running snv_73 (pool created back before
zfs integrated to ON) paniced I guess from zfs the first time
and now panics on attempted boot every time as below. Is this
a known issue and, more importantly (2TB of data in the pool),
any suggestions on how to recover
