On Fri, Nov 21, 2008 at 12:13 PM, Mike Christie <[EMAIL PROTECTED]> wrote:
>
> Mike McGrath wrote:
>> What tarball was this patch against? I tried it against 6.2.0.870 and
>> it failed to apply. Should I grab what's in HEAD?
>>
>
>
> Is this the 870 from open-iscsi.org or fedora?
>
> HEAD and 87
Mike McGrath wrote:
> What tarball was this patch against? I tried it against 6.2.0.870 and
> it failed to apply. Should I grab what's in HEAD?
>
Is this the 870 from open-iscsi.org or fedora?
HEAD and 870 on open-iscis.org are the same right now. I just tried to
apply it and it worked for
What tarball was this patch against? I tried it against 6.2.0.870 and
it failed to apply. Should I grab what's in HEAD?
-Mike
On Fri, Nov 21, 2008 at 11:44 AM, Mike Christie <[EMAIL PROTECTED]> wrote:
> Mike Christie wrote:
>> So just wait a sec for the patch. I need to retest for reg
Mike Christie wrote:
> So just wait a sec for the patch. I need to retest for regressions. I
> should have it out today and pushed in fedora this evening.
>
Here is the patch I am thinking about. It works here.
I want to take some time to make sure it is ok, so instead of today, I
am going to
Mike Christie wrote:
> Mike Christie wrote:
>> Mike McGrath wrote:
>>> On Thu, Nov 20, 2008 at 1:39 PM, Mike Christie <[EMAIL PROTECTED]> wrote:
Mike Christie wrote:
> Could you send the /var/log/messages output when you start the iscsi
> service? It should be something like:
>
>>
Mike Christie wrote:
> Mike McGrath wrote:
>> On Thu, Nov 20, 2008 at 1:39 PM, Mike Christie <[EMAIL PROTECTED]> wrote:
>>> Mike Christie wrote:
Could you send the /var/log/messages output when you start the iscsi
service? It should be something like:
>>> Ignore this. I think I foun
Mike McGrath wrote:
> On Thu, Nov 20, 2008 at 1:39 PM, Mike Christie <[EMAIL PROTECTED]> wrote:
>> Mike Christie wrote:
>>> Could you send the /var/log/messages output when you start the iscsi
>>> service? It should be something like:
>>>
>> Ignore this. I think I found the bug.
>>
>
> Is there a
On Thu, Nov 20, 2008 at 1:39 PM, Mike Christie <[EMAIL PROTECTED]> wrote:
>
> Mike Christie wrote:
>> Could you send the /var/log/messages output when you start the iscsi
>> service? It should be something like:
>>
>
> Ignore this. I think I found the bug.
>
Is there a previous version I could ru
[EMAIL PROTECTED] wrote:
>
>
> On Nov 20, 12:52 pm, Mike Christie <[EMAIL PROTECTED]> wrote:
>> [EMAIL PROTECTED] wrote:
>>> I've got a replacement timeout set to 86400 but after losing
>>> connection to the iscsi device it will fail typically in a minute or
>>> so:
>>> Nov 19 17:03:43 desktop k
Mike Christie wrote:
> Could you send the /var/log/messages output when you start the iscsi
> service? It should be something like:
>
Ignore this. I think I found the bug.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
On Nov 20, 12:52 pm, Mike Christie <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
> > I've got a replacement timeout set to 86400 but after losing
> > connection to the iscsi device it will fail typically in a minute or
> > so:
>
> > Nov 19 17:03:43 desktop kernel: connection4:0: detected
[EMAIL PROTECTED] wrote:
> I've got a replacement timeout set to 86400 but after losing
> connection to the iscsi device it will fail typically in a minute or
> so:
>
> Nov 19 17:03:43 desktop kernel: connection4:0: detected conn error
> (1011)
> Nov 19 17:03:44 desktop iscsid: Kernel reported iS
I've got a replacement timeout set to 86400 but after losing
connection to the iscsi device it will fail typically in a minute or
so:
Nov 19 17:03:43 desktop kernel: connection4:0: detected conn error
(1011)
Nov 19 17:03:44 desktop iscsid: Kernel reported iSCSI connection 4:0
error (1011) state (
13 matches
Mail list logo
