ZFS will currently panic on a write failure to a non replicated pool.
In the case below the Intent Log (though it could have been any module)
could not write an intent log block. Here's a previous response from Eric
Schrock explaining how ZFS intends to handle this:
Yes,
Hi,
No, I can't offer insight, but I do have some questions
that are not really on topic.
What version of solaris are you running? Is this
the console output at time of panic? When did the
panic code (or mdb) learn about frame recycling?
Or are you using scat to get this output?
thanks,
max
On
