Matthew Flanagan wrote:
Matt,
Matthew Flanagan wrote:
mkfile 100m /data
zpool create tank /data
...
rm /data
...
panic[cpu0]/thread=2a1011d3cc0: ZFS: I/O failure
(write on <unknown> off 0: zio 60007432bc0 [L0
unallocated] 4000L/400P DVA[0]=<0:b000:400>
DVA[1]=<0:120a000:400> fletcher4 lzjb BE contiguous
birth=6 fill=0
cksum=672165b9e7:328e78ae25fd:ed007c9008f5f:34c05b1090
0b668): error 6
...
is there a fix for this?
Um, don't do that?
This is a known bug that we're working on.
What is the bugid for this an ETA for fix?
6417779 ZFS: I/O failure (write on ...) -- need to reallocate writes
and
6322646 ZFS should gracefully handle all devices failing (when writing)
These bugs are actively being worked on, but it will probably be a while
before fixes appear.
-Mark
I'm extremely surprised that this kind of bug can make it into a Solaris
release. This is the second zfs related panic that I've found in testing it in
our labs. The first was caused to the system to panic when the ZFS volume got
close to 100% full (Sun case id #10914593).
I've just replicated this panic with a USB flash drive as well by creating the
zpool and then yanking the drive out. This is probably a common situation for
desktop/laptop users who would not be impressed that their otherwise robust
Solaris system crashed.
regards
matthew
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
