I was really hoping for some option other than ZIL_DISABLE, but finally gave up
the fight. Some people suggested NFSv4 helping over NFSv3 but it didn't... at
least not enough to matter.
ZIL_DISABLE was the solution, sadly. I'm running B43/X86 and hoping to get up
to 48 or so soonish (I BFU'd
On Tue, eric kustarz wrote:
Ben Rockwood wrote:
I was really hoping for some option other than ZIL_DISABLE, but finally
gave up the fight. Some people suggested NFSv4 helping over NFSv3 but it
didn't... at least not enough to matter.
ZIL_DISABLE was the solution, sadly. I'm running
Could someone offer insight into this panic, please?
panic string: ZFS: I/O failure (write on unknown off 0: zio
6000c5fbc0
0 [L0 ZIL intent log] 1000L/1000P DVA[0]=1:249b68000:1000 zilog uncompre
ssed BE contiguous birth=318892 fill=0 cksum=3b8f19730caa4327:9e102
panic kernel thread:
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
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:
Michael Phua - PTS wrote:
Hi,
Our customer has an Sun Fire X4100 with Solaris 10 using ZFS and a HW RAID
array (STK D280).
He has extended a LUN on the storage array and want to make this new size
known to ZFS and Solaris.
Does anyone know if this can be done and how it can be done.
