HOW TO MAKE EASY MONEY IN HOME BASED
ALL TIPS IS HERE FREE JUST GOTHROUGH IT
http://worlddtechnology.blogspot.com/
http://worlddtechnology.blogspot.com/
http://worlddtechnology.blogspot.com/
--~--~-~--~~~---~--~~
You received this message because you are subscr
Or Gerlitz wrote:
> Mike Christie wrote:
>> I am not sure what you are asking. Did you look at the patches?
>
> I gave it quick look before asking, I looked now again and I think
> to understand this better - lets see if I'm in the correct direction:
>
> The I/OAT related kernel code serves the
dave wrote:
>
>
> On Mar 19, 10:56 am, Mike Christie wrote:
>> dave wrote:
>>> Can anyone tell me why the SCSI layer says the device is not ready
>>> when iscsiadm reports it is logged in?
>>> Can I manually online the device? How should I recover from here?
>> You can do
>>
>> echo running > /
On Mar 19, 10:56 am, Mike Christie wrote:
> dave wrote:
> > Can anyone tell me why the SCSI layer says the device is not ready
> > when iscsiadm reports it is logged in?
>
> > Can I manually online the device? How should I recover from here?
>
> You can do
>
> echo running > /sys/block/sdX/devi
bigcatxjs wrote:
>>> Mar 17 18:27:59 MYHOST53 kernel: scsi 2:0:0:0: rejecting I/O to dead
>>> device
>> It looks like one of the following is happening:
>>
>> 1. were using RHEL 5.2 and the target logged us out or dropped the
>> session and when we tried to login we got what we thought was a fatal
dave wrote:
> Can anyone tell me why the SCSI layer says the device is not ready
> when iscsiadm reports it is logged in?
>
> Can I manually online the device? How should I recover from here?
>
You can do
echo running > /sys/block/sdX/device/state
but you might not want to because the device
Mike Christie wrote:
> Mike Christie wrote:
>> We should not have to call stop_event_loop if the event_loop is
>> already stopped. What I am wondering is how the event loop is stopped
>> by anyone other than the call to stop_event_loop? It looks like it
>> could happen if there was a signal or
Thanks Mike...
On Mar 18, 5:45 pm, Mike Christie wrote:
> bigcatxjs wrote:
> > Hi,
> > We have encountered this error below. This is the first time I have
> > seen this before;
>
> This is with the noop settings set to 0 right? Was this the RHEL 5.3 or
> 5.2 setup?
It is our RHEL 5.3 host.
>
Mike Christie wrote:
> I am not sure what you are asking. Did you look at the patches?
I gave it quick look before asking, I looked now again and I think
to understand this better - lets see if I'm in the correct direction:
The I/OAT related kernel code serves the TCP stack for coping data
from
