Nigel,
I have sent you an email with the output that you were looking for.
Once a solution has been discovered I'll post it on here so everyone can see.
Tano
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensola
ns> I will raise this as a bug, but first please would you run
'/usr/X11/bin/scanpci'
to indentify the exact 'vendor id' and 'device id' for the Broadcom network
chipset,
and report that back here
Primary network interface Embedded NIC:
pci bus 0x0005 cardnum 0x00 function 0x00: vendor 0x14e4
> "ns" == Nigel Smith <[EMAIL PROTECTED]> writes:
ns> the bnx driver is closed source :-(
The GPL'd Linux driver is contributed by Broadcom:
http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.27.y.git;a=blob;f=drivers/net/bnx2.c;h=2486a656f12d9f47ff27ead587e084a3c337a1a3;hb=HE
Hi Tano
Great to hear that you've now got this working!!
I understand you are using a Broadcom network card,
from your previous posts I can see you are using the 'bnx' driver.
I will raise this as a bug, but first please would you run
'/usr/X11/bin/scanpci'
to indentify the exact 'vendor id' and
So it's finally working: nothing special was done to get it working either
which is extremely vexing!
I disabled the I/OAT DMA feature from the BIOS that apparently assists the
network card and enabled the TPGT option on the iscsi target. I have two
iscsitargets, one 100G on a mirror on the int
Hi Tano
Please check out my post on the storage-forum for another idea
to try which may give further clues:
http://mail.opensolaris.org/pipermail/storage-discuss/2008-October/006458.html
Best Regards
Nigel Smith
--
This message posted from opensolaris.org
__
around 30 to 40% it really starts to slow down, but no disconnection or timeout
yet. The speed is unacceptable and therefore will continue to with the notion
that something is wrong in the tcp stack/iscsi.
Following the snoop logs, it shows that the Windows size on the iscsi end is 0,
and the o
so I found some more information and have been at it diligently.
Checking my hardware bios, Dell likes to share a lot of it's IRQs with other
peripherals.
back in the old days when we were limited to just 15 IRQs it was imperative
that certain critical hardware had it's own IRQ. It may seem to
Well the '/var/svc/log/system-iscsitgt\:default.log'
is NOT showing any core dumps, which is good, but
means that we need to look & think deeper for the answer.
The 'iscsisnoop.d' output does looks similar to that
captured by Eugene over on the storage forum, but
Eugene only showed a short sequen
[EMAIL PROTECTED]:/tmp# cat /var/svc/log/system-iscsitgt\:default.log
[ Oct 21 09:17:49 Enabled. ]
[ Oct 21 09:17:49 Executing start method ("/lib/svc/method/svc-iscsitgt
start"). ]
[ Oct 21 09:17:49 Method "start" exited with status 0. ]
[ Oct 21 17:02:12 Disabled. ]
[ Oct 21 17:02:12 Rereading
Hi tano
I hope you can try with the 'iscsisnoop.d' script, so
we can see if your problem is the same as what Eugene is seeing.
Please can you also check the contents of the file:
/var/svc/log/system-iscsitgt\:default.log
.. just to make sure that the iscsi target is not core dumping & restarting.
one more update:
common hardware between all my machines soo far has been the PERC (Poweredge
Raid Controllers) or also known as the LSI MEGA RAID controller.
The 1850 has a PERC 4d/i
the 1900 has a PERC 5/i
I'll be testing the iscsitarget with a SATA controller to test my hypothesis.
--
This
The poweredge 1850 has an intel etherexpress pro 1000 internal cards in it.
However, some new updates, even the microsoft initiator hung writing a 1.5
gigabyte file to the iscsitarget on the opensolaris box.
I've installed linux iscsitarget on the same box and will reattempt the iscsi
targets
I have a very similar problem with SNV_(( and Virtual Iron
(http://www.opensolaris.org/jive/thread.jspa?threadID=79831&tstart=0)
I am using IBM x3650 Server with 6 SAS drives. And what we have in common is
Broadcomm network cards (BNX driver). From previous experiance I know this
cards had a dr
Well, my colleague & myself have recently had a basic Vmare ESX cluster working,
with the Solaris iscsi target, in the Lab at work, so I know it does work.
We used ESX 3.5i on two Dell Precision 390 workstations,
booted from USB memory sticks.
We used snv_97 and no special tweaks required.
We used
A couple of updates:
Installed Opensolaris on a Poweredge 1850 with a single network card, default
iscsitarget configuration (no special tweaks or tpgt settings), vmotion was
about 10 percent successful before I received write errors on disk.
10 percent better than the Poweredge 1900 iscsitarge
Ciao,
Your GUID's must not be the same an NAA is already established on the targets
and if you previously tried to initialize the LUN with VMware it would have
assigned the value in the VMFS header wich is now stored on your raw ZFS
backing store. This will confuse VMware and it will remember i
According to the svccfg(1M) man page:
http://docs.sun.com/app/docs/doc/819-2240/svccfg-1m?a=view
...it should be just 'export' without a leading '-' or '--'.
I've been googling on NAA and this is the 'Network Address Authority',
It seems to be yet another way of uniquely identifying a target & Lun
Hi,
I rebooted the server after I submitted the information to release the locks
set up on my ESX host.
After the reboot: I reran the iscsitadm list target -v and the GUIDs showed up.
Only interesting problem: the GUID's are identical (any problems with that?)
[EMAIL PROTECTED]:~# iscsitadm li
Hello Tano,
The issue here is not the target or VMware but a missing GUID on the target as
the issue.
Observe the target smf properties using
iscsitadm list target -v
You have
iSCSI Name: iqn.1986-03.com.sun:02:35ec26d8-f173-6dd5-b239-93a9690ffe46.vscsi
Connections: 0
ACL list:
TPGT list:
TPG
>Do you have an active interface on the OpenSolaris box that is configured for
>>0.0.0.0 right now?
Not anymore:
>By default, since you haven't configured the tpgt on the iscsi target, solaris
>will >broadcast all active interfaces in its SendTargets response. On the ESX
>side, >ESX will att
Nigel Smith wrote:
> I googled on some sub-strings from your ESX logs
> and found these threads on the VmWare forum
> which lists similar error messages,
> & suggests some actions to try on the ESX server:
>
> http://communities.vmware.com/message/828207
>
> Also, see this thread:
>
> http://commu
I googled on some sub-strings from your ESX logs
and found these threads on the VmWare forum
which lists similar error messages,
& suggests some actions to try on the ESX server:
http://communities.vmware.com/message/828207
Also, see this thread:
http://communities.vmware.com/thread/131923
Are
Also I had read your blog post previously.
I will be taking advantage of the cloning/snapshot section of your blog once I
am successful writing to the Targets.
Thanks again!
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-d
Thank you Ryan for your response, I have included all the information you
requested in line to this document:
I will be testing SNV_86 again to see whether the problem persists, maybe it's
my hardware. I will confirm that soon enough.
On Thu, October 16, 2008 10:31 am, Ryan Arneson wrote:
> Tan
Tano wrote:
> I'm not sure if this is a problem with the iscsitarget or zfs. I'd greatly
> appreciate it if it gets moved to the proper list.
>
> Well I'm just about out of ideas on what might be wrong..
>
> Quick history:
>
> I installed OS 2008.05 when it was SNV_86 to try out ZFS with VMWare. F
26 matches
Mail list logo
