Hello,
I've been looking into trying to optimise SFS related tunables and found that
one of the previously tunable parameters, ssd_retry_count, is not available in
Solaris 10 update2. When I try to set this parameter in /etc/system I get a
message during boot saying that ssd_retry_count is
I have an alua capable array which allows me to turn alua on or off for a
specific initiator or group of initiators. When my Solaris 10 U3 system, a
280r, discovered it's luns I had neglected to enable alua on my array for the
server's initiators. As a result no scsi_vhci devices were created
Just a quick question. I recall in years past that if sd.conf was
pre-populated with entries that a boot time delay penalty would occur
which was supposed to be something like 3 seconds per lun for luns
that really weren't available.
My question is does solaris and the sd driver still behave this
I have a script that I use for labeling luns. So if I add 100 luns from my SAN
I run the script and it runs devfsadm or cfgadm where appropriate and then gets
a list of unlabeled luns via the format command and then iterates over the list
and issues the following command...
format -f
Hi,
Could anyone comment on any recommended TCP tuning specific to the solaris
iscsi initiator? The tcp_keepalive_interval default seems to be 2 hours.
[EMAIL PROTECTED]]ndd -get /dev/tcp tcp_keepalive_interval
720
Assuming that this parameter is in milliseconds then this works out to
Usually on the host side all that is required is to use format to re-type the
lun; choose type then Auto Configure then label the lun. That usually
updates the disk geometry to reflect the new lun size. I seem to recall that
after this you end up with a default label on the lun but if you make
Has there been any discussion here about the idea integrating a virtual IP into
ZFS. It makes sense to me because of the integration of NFS and iSCSI with the
sharenfs and shareiscsi properties. Since these are both dependent on an IP it
would be pretty cool if there was also a virtual IP that
Are the non-Sun Asymmetrical disk arrays supported by Solaris multipathing S/W
documented anywhere?
Thanks,
Vic
From - http://docs.sun.com/source/819-0139/ch_1_prod_oview.html
Symmetrical/Asymmetrical Device Support - The Solaris FC and Storage
Multipathing software support the following
I installed snv_75 recently and noticed that the scsi_vhci.conf file no longer
has the following section...
# device-type-scsi-options-list =
# SUN SENA, symmetric-option;
Instead it has this new section...
# scsi-vhci-failover-override =
# STK FLEXLINE 400, f_asym_lsi,
#
The emlxdrv utility may be used to configure a host to use either emlxs or lpfc
for Emulex HBAs. The emlxs driver is used by default. What does emlxdrv do to
configure one driver or the other? Is it possible to script this change so that
a jumpstart finish script could configure a host being
Just curious about progress being made with this project. Any estimates as to
availability of the target and initiator?
Thanks,
Vic
This message posted from opensolaris.org
___
storage-discuss mailing list
storage-discuss@opensolaris.org
11 matches
Mail list logo
