search for: snv_97

I''ve recently upgraded my x4500 to Nevada build 97, and am having problems with the iscsi target. Background: this box is used to serve NFS underlying a VMware ESX environment (zfs filesystem-type datasets) and presents iSCSI targets (zfs zvol datasets) for a Windows host and to act as zoneroots for Solaris 10 hosts. For optimal random-read performance, I''ve configured a single

Hi all, got this every time: Error: Device 5632 (vbd) could not be connected. Backend device not found. didn''t have any problem in b95 Any idea? thanks Philip xm info host : snv release : 5.11 version : snv_97 machine : i86pc nr_cpus : 2 nr_nodes : 1 sockets_per_node : 1 cores_per_socket : 2 threads_per_core : 1 cpu_mhz : 1997 hw_caps : bfebfbff:20100800:00000000:00000140:0000e3bd:00000000:00000001 total_memory...

Hi all, I''ve got a lot of video files on a zfs/cifs fileserver running SXCE. A little while ago the dual onboard NICs died and I had to replace them with a PCI 10/100 NIC. The system was fine for a couple of weeks but now the performance when viewing a video file from the cifs share is appauling. Videos stop and jerk with audio distortion. I have tried this from several client machines

...eate target -u 0 -b /dev/zvol/rdsk/tank/disk1 LABEL1 6) iscsitadm create target -u 1 -b /dev/zvol/rdsk/tank/disk2 LABEL1 VMWARE discovers the seperate LUNs on the Device identifier, but still unable to write to the iscsi luns. Why is it that the steps I''ve conducted in SNV_94 work but in SNV_97,98, or 99 don''t. Any ideas?? any log files I can check? I am still an ignorant linux user so I only know to look in /var/log :) -- This message posted from opensolaris.org