Thanks for the tips. I'm not sure if they will be relevant, though. We don't
talk directly with the AMS1000. We are using a USP-VM to virtualize all of our
storage and we didn't have to add anything to the drv configuration files to
see the new disk (mpxio was already turned on). We are
I think we found the choke point. The silver lining is that it isn't the T2000
or ZFS. We think it is the new SAN, an Hitachi AMS1000, which has 7200RPM SATA
disks with the cache turned off. This system has a very small cache, and when
we did turn it on for one of the replacement LUNs we saw
It's something we've considered here as well.
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
I had posted at the Sun forums, but it was recommended to me to try here as
well. For reference, please see
http://forums.sun.com/thread.jspa?threadID=5351916tstart=0.
In the process of a large SAN migration project we are moving many large
volumes from the old SAN to the new. We are making
We will be considering it in the new year, but that will not happen in time to
affect our current SAN migration.
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
