Hi,
Aaron Stranberg wrote:
Hello All,
New OF user here, I have a question about IETD and lun 0's. My
environment is a dual opteron server with 3ware raid card, connecting
to vmware ESX server hosts. I have noticed that it seems whenever you
manipulate volum
groups in the GUI, the ietd.conf file changes all luns to 0.
As they should be. A each target is designed in OF currently to export
only one lun therefore the lun id is 0 since it's the first lun for that
target.
I have also read that one way to fix this is by pulling down the
iscsi-target svn and compiling it. So my question is, is that the
best way to fix this problem, and if so, what are the dependencies
that I need to install to successfully compile iscsi-target from svn
and any additional instructions would be great?
That's a really painful way of fixing it.
Of note, I attempted a conary updateall and the problem did not
resolve its self. Thanks in advance and apologies if this has already
been addressed, please point me in the right direction.
IIRC ESX should work with unique scsi serial numbers assigned to each
lun (even if lun id is 0 for all luns). If you've updated to latest
Openfiler release (via updateall or the GUI), you should create a new
iSCSI target. That will update all existing targets as well with a
unique scsi device serial number for their respective luns. That ought
to fix your problem.
R.
_______________________________________________
Openfiler-users mailing list
[email protected]
https://lists.openfiler.com/mailman/listinfo/openfiler-users
