I've not seen the disconnects and can't imagine why you'd be getting
them unless there's network problem. I'm not saying you have network
problems, it's just the only reason that I can think of that would
cause what you're seeing.
Out of curiosity is there a core file on /? Or does the PID of the
iscsitgtd keep changing? Thinking about the problem this would be the
other most logical cause. The daemon is getting a segv or something
and SMF is restarting it.
I'll work on trying to reproduce your problem.
On Sep 18, 2006, at 12:11 PM, Ed Plese wrote:
On Mon, Sep 18, 2006 at 09:12:59AM -0600, Rick McNeal wrote:
I'd like to get a little more information regarding your trouble with
format on Windows. You state that Windows can see the volume, but not
format it. Are you able to attempt to format the drive, but the
format command fails? Or is it a case of format not willing to run on
the drive? Previously in my testing I never did the long format since
the underlying drive is already formated and just needs the Windows
label. It turns out the during the long format Windows uses the
optional SCSI command VERIFY. I didn't support that previously and
have now added the code (the latest OpenSolaris nightly builds would
have it). If it a case of not being able to run format could you give
me some more information about what version of Windows you're running
and that platform?
I'm not sure if this is related, but every time I've tried to setup
the
iSCSI target and connect to it with the Microsoft iSCSI Software
Initiator, it continually drops the connection. Most recently I tried
this with Solaris Express build 46.
In Windows XP I am able to see the volume, connect to it, and see
it show
up in the Disk Management program, however once connected to it, the
Event Viewer shows the following information event in the System log
every 1-2 seconds:
Source: iScsiPrt
Category: None
Type: Information
Event ID: 34
A connection to the target was lost, but Initiator successfully
reconnected to the target. Dump data contains the target name.
Most operations will work on this volume such as formatting and then
reading and writing data, however they are extremely slow due to the
disconnects and will frequently fail.
Both systems are 32 bit x86. On the Solaris side of things here's
the volume:
# iscsitadm list target -v
Target: wintgt
iSCSI Name: iqn.1986-03.com.sun:02:70d96a85-5aba-436b-dd8f-
abc36faa14df.wintgt
Connections: 1
Initiator:
iSCSI Name: iqn.1991-05.com.microsoft:vmxp
Alias: unknown
ACL list:
TPGT list:
LUN information:
LUN: 0
GUID: 0100000c294b752400002a0044fe1e3d
VID: SUN
PID: SOLARIS
Type: disk
Size: 256M
Status: online
Is there any way to prevent these disconnects? Is this a known issue?
Thanks,
Ed Plese
_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
----
Rick McNeal
A good friend will come and bail you out of jail ... but, a true
friend will be sitting next to you saying, "Damn ... that was fun!"
_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
