|
From: Ross S. W. W. <RW...@me...> - 2013-02-14 16:50:33
|
I have been running IET 1.4.20 release in one of our data centers for years without issue. Post your storage configuration and IET configuration. The phantom LUN issue tends to mean there is a configuration problem somewhere. -Ross On Feb 14, 2013, at 10:18 AM, "Caspar Smit" <c....@tr...> wrote: > Hi all, > > We have an ESXi 4.1 machine connected to an IET (1.4.20.2 stable) server (debian 6 stable) which has some issues now and then. > > Sometimes (can take a week, other times half a year) all VM's running on the iSCSI datastore hang and the only way to resolve is to reboot the ESXi host. > > We see logging on the iet server like: > > iscsi_trgt: Abort Task (01) issued on tid:1 lun:1 by sid:7320548421730816 (Unknown LUN) > > Repeated every few seconds. > > Since the stable version of IET is not updated for two and a half years, i was wondering if these kind of issues are resolved in the trunk version? > Can anyone confirm the trunk version is stable enough for everyday use? > > Furthermore, is IET still developed and is there any ETA for a new stable release? > > Kind regards, > Caspar Smit > ------------------------------------------------------------------------------ > Free Next-Gen Firewall Hardware Offer > Buy your Sophos next-gen firewall before the end March 2013 > and get the hardware for free! Learn more. > http://p.sf.net/sfu/sophos-d2d-feb > _______________________________________________ > Iscsitarget-devel mailing list > Isc...@li... > https://lists.sourceforge.net/lists/listinfo/iscsitarget-devel ______________________________________________________________________ This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender and permanently delete the original and any copy or printout thereof. |