> How did you get those other kernel messages? If you can just get the
> iscsid log info that is sent after lines like this
I'm able to issue the "dmesg" command after the drive is lost and
still retrieve some logging info. Unfortunately, what I sent was all
that I can get. If the drive ever succe
>> >>> Sean S schrieb am 28.07.2010 um 16:34 in
> Nachricht
com>:
How did you get those other kernel messages? If you can just get the
> > iscsid log info that is sent after lines like this
>
> I'm able to issue the "dmesg" command after the drive is lost and
> still retrieve some logging info
>> "Ulrich Windl" schrieb am
>> 28.07.2010
> um
16:46 in Nachricht <4c505ef502a1e...@gwsmtp1.uni-regensburg.de>
> :
>>> Sean S schrieb am 28.07.2010 um 16:34 in
> > Nachricht
> > com>:
> How did you get those other kernel messages? If you can just get the
> > > iscsid log
I've attached the file indirect_io.txt which contains my block device
driver code that does the IO. I dont know if I am allowed to request
anyone in here to see if something is wrong in that...sorry, If i'm
not allowed. You can just delete the file. But, if there is some
developer who can take a lo
On 07/28/2010 09:34 AM, Sean S wrote:
What version of open-iscsi-871 are you using is it 871.1 or .2 .3?
I downloaded the "current semi-stable release":
http://www.open-iscsi.org/bits/open-iscsi-2.0-871.tar.gz
It doesn't appear to have a minor version number. Should I be using
something else?
>>> Anil schrieb am 27.07.2010 um 19:35 in Nachricht
<21e0403d-aa3d-42e6-b274-01a000398...@q16g2000prf.googlegroups.com>:
> I've attached the file indirect_io.txt which contains my block device
> driver code that does the IO. I dont know if I am allowed to request
> anyone in here to see if someth
