I'm attempting to follow-up on this bug ID and the seemingly related bug
6539587. In the Bugster db neither appear to be fixed. There was some
improvement with IEEE support in or around SNV_105, such that the patch was no
longer necessary to prevent panic on boot with an attached firewire drive.
However, using snv_109 I have only intermittent success with ZFS on a firewire
drive. I was initially able to restore my system from the firewire back-up.
Later I received a hang at the terminal prompt after issuing a command to the
firewire ZFS filesystem. Since that time I get this message when attempting to
query the zpool on the firewire drive:
r...@solenv ~ 16:11:06 # zpool status -v firewire
pool: firewire
state: UNAVAIL
status: One or more devices could not be opened. There are insufficient
replicas for the pool to continue functioning.
action: Attach the missing device and online it using 'zpool online'.
see: http://www.sun.com/msg/ZFS-8000-3C
scrub: none requested
config:
NAME STATE READ WRITE CKSUM
firewire UNAVAIL 0 0 0 insufficient replicas
c2t0d0 UNAVAIL 0 0 0 cannot open
r...@solenv ~ 16:12:15 # zpool online firewire c2t0d0
cannot open 'firewire': pool is unavailable
So once again this drive is of little use. Me thinks there remains an issue
with firewire support and snv_109. Would it be possible to get an update on the
status of bugs 6560174 and 6539587?
Thanks, Aric
--
This message posted from opensolaris.org
_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
