Re: LIO - the broken iSCSI target implementation

2013-01-19 Thread Fubo Chen
On Fri, Jan 18, 2013 at 9:21 PM, wrote: > Please don't start another "SCST Vs. LIO" holy war here. We all know why LIO > belongs to Linux kernel and SCST does not. SCST is not familiar to me. Does this mean that SCST is competition for the StarWind products but LIO not ? Fubo. -- To unsubscrib

Re: LIO - the broken iSCSI target implementation

2013-01-19 Thread Ritesh Raj Sarraf
On Fri, Jan 18, 2013 at 4:01 AM, Andy Grover wrote: > On 01/17/2013 12:56 PM, Nicholas A. Bellinger wrote: >> On Thu, 2013-01-17 at 02:19 +0100, Andreas Steinmetz wrote: >>> This is not a technical point of view. This is a more or less political >>> and user point of view. And for any replies, I'm

Re: LIO - the broken iSCSI target implementation

2013-01-18 Thread promo
Please don't start another "SCST Vs. LIO" holy war here. We all know why LIO belongs to Linux kernel and SCST does not. On Friday, January 18, 2013 3:54:18 AM UTC+2, Vladislav Bolkhovitin wrote: > Andreas Steinmetz, on 01/16/2013 08:19 PM wrote: > > > Thus, lio (http://www.linux-iscsi.org/) seem

Re: LIO - the broken iSCSI target implementation

2013-01-17 Thread Vladislav Bolkhovitin
Andreas Steinmetz, on 01/16/2013 08:19 PM wrote: Thus, lio (http://www.linux-iscsi.org/) seemed to be the politically and technically favoured solution. [...] The fun part of it was that I finally ended up using SCST - which was refrained from kernel inclusion for technical reasons beyond my

Re: LIO - the broken iSCSI target implementation

2013-01-17 Thread Nicholas A. Bellinger
On Thu, 2013-01-17 at 14:31 -0800, Andy Grover wrote: > On 01/17/2013 12:56 PM, Nicholas A. Bellinger wrote: > > On Thu, 2013-01-17 at 02:19 +0100, Andreas Steinmetz wrote: > >> This is not a technical point of view. This is a more or less political > >> and user point of view. And for any replies,

Re: LIO - the broken iSCSI target implementation

2013-01-17 Thread Linus Torvalds
On Thu, Jan 17, 2013 at 2:31 PM, Andy Grover wrote: > > No... actually upstream targetcli/rtslib are not very well maintained. > Around 5 patches each in the last year. > > Meanwhile, I have been actively maintaining branches at > github.com/agrover/targetcli-fb and github.com/agrover/rtslib-fb. W

Re: LIO - the broken iSCSI target implementation

2013-01-17 Thread Andy Grover
On 01/17/2013 12:56 PM, Nicholas A. Bellinger wrote: > On Thu, 2013-01-17 at 02:19 +0100, Andreas Steinmetz wrote: >> This is not a technical point of view. This is a more or less political >> and user point of view. And for any replies, I'm not subscribed (haven't >> been now for years). >> >> As

Re: LIO - the broken iSCSI target implementation

2013-01-17 Thread Nicholas A. Bellinger
On Thu, 2013-01-17 at 12:56 -0800, Nicholas A. Bellinger wrote: > Hi Andreas, > > On Thu, 2013-01-17 at 02:19 +0100, Andreas Steinmetz wrote: > > This is not a technical point of view. This is a more or less political > > and user point of view. And for any replies, I'm not subscribed (haven't > >

Re: LIO - the broken iSCSI target implementation

2013-01-17 Thread Nicholas A. Bellinger
Hi Andreas, On Thu, 2013-01-17 at 02:19 +0100, Andreas Steinmetz wrote: > This is not a technical point of view. This is a more or less political > and user point of view. And for any replies, I'm not subscribed (haven't > been now for years). > > As a user, I was in need for an iSCSI target. Act

LIO - the broken iSCSI target implementation

2013-01-16 Thread Andreas Steinmetz
This is not a technical point of view. This is a more or less political and user point of view. And for any replies, I'm not subscribed (haven't been now for years). As a user, I was in need for an iSCSI target. Actually, I needed to export a SAS tape device (Ultrium 5) - which is one of the devic