On 12/6/06, Jason J. W. Williams [EMAIL PROTECTED] wrote:
We've been using MPXIO (STMS) with ZFS quite solidly for the past few
months. Failover is instantaneous when a write operations occurs
after a path is pulled. Our environment is similar to yours, dual-FC
ports on the host, and 4 FC ports
On 12/6/06, Jason J. W. Williams [EMAIL PROTECTED] wrote:
The configuration is a T2000 connected to a StorageTek FLX210 array
via Qlogic QLA2342 HBAs and Brocade 3850 switches. We currently RAID-Z
the LUNs across 3 array volume groups. For performance reasons we're
in the process of changing to
On 12/5/06, Peter Eriksson [EMAIL PROTECTED] wrote:
Hmm... I just noticed this qla2100.conf option:
# During link down conditions enable/disable the reporting of
# errors.
#0 = disabled, 1 = enable
hba0-link-down-error=1;
hba1-link-down-error=1;
This is the driver the we are using in this
Last Friday, one of our V880s kernel panicked with the following
message.This is a SAN connected ZFS pool attached to one LUN. From
this, it appears that the SAN 'disappeared' and then there was a panic
shortly after.
Am I reading this correctly?
Is this normal behavior for ZFS?
This is a
On 12/4/06, James C. McPherson [EMAIL PROTECTED] wrote:
Is this normal behavior for ZFS?
Yes. You have no redundancy (from ZFS' point of view at least),
so ZFS has no option except panicing in order to maintain the
integrity of your data.
This is interesting from a implementation point of
In reading the list archives, am I right to conclude that disks larger than
1 TB need to support EFI? I one of my projects the SAN does not support EFI
labels under Solaris. Does this mean I would have to create a pool with
disks 1 TB?
TIA.
-Doug
___
