Definitely not a silly question. And no, we create the pool on node1 then set up the cluster resources. Once setup, sun cluster manages importing/exporting the pool into only the active cluster node. Sorry for the lack of clarity.. not much sleep has been had recently.
When connecting to our SAS tray with a single box and with the pool configuration as stated and SSD's in the pool as slog devices everything works as it should. When connecting the second box AND when the SSDs are in the pool, there are tons of SCSI resets and even some panics on the nodes. With the sas tray connected to both nodes and no ssds everything works as it should. Sorry for the confusion, Steve Jost > Silly question - you're not trying to have the ZFS pool imported on > both hosts at the same time, are you? Maybe I misread, had a hard > time following the full description of what exact configuration caused > the scsi resets. > > > > On Jun 1, 2010, at 2:22 PM, Steve Jost wrote: > > > Hello All, > > We are currently testing a NFS+Sun Cluster solution with ZFS in our > > environment. Currently we have 2 HP DL360s each with a 2-port LSI > > SAS 9200-8e controller (mpt_sas driver) connected to a Xyratex > > OneStor SP1224s 24-bay sas tray. The xyratex sas tray has 2 ports > > on the controller which can connect to each server. We have a zpool > > of 2x (8+2) drives and 1 hot spare and also 3 intel X25-E ssds in > > the tray. We were hoping to have the ssds work as slog/cache > > devices however when we add them to the pool (as cache or log) we > > start to get an insane number of scsi resets. When the storage is > > connected to a single node the resets do not happen. > > > > scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ > > d...@g50015179591cdd18 (sd24): > > Error for Command: write(10) Error Level: Retryable > > scsi: [ID 107833 kern.notice] ASC: 0x29 (power on, reset, or > > bus reset occurred), ASCQ: 0x0, FRU: 0x0 > > > > Could this error be because the Intel SSDs are sata and we need a > > real SAS interface for multi-initiator support or is it a bug in the > > firmware somewhere that needs to be addressed? Where can we go from > > here to troubleshoot this oddity? Thanks! > > > > Steve Jost > > -- > > This message posted from opensolaris.org > > _______________________________________________ > > zfs-discuss mailing list > > zfs-discuss@opensolaris.org > > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
