Re: [Iscsitarget-devel] Iet drives server to kernel panic or read only LUNs

[Kumar S. <sha...@te...>]

Hi Ross,

> Post a copy of the kernel panic message and let's take a look at it.
I never enabled kernel logging on that server hence no logs with me for 
now, I am just enabling it right now and as soon as I get any kernel 
panic I will post you the logs.

Thanks
Shantanu

On 09/16/2013 07:02 PM, Ross S. W. Walker wrote:
> On Sep 16, 2013, at 9:28 AM, "Kumar Shantanu" <sha...@te...> wrote:
>
>> Thanks Ross for such a quick reply,
>>
>> I will verify my hardwares to make sure everything is fine with it.
>>
>> On a different note, we have faced a kernel panic on a different server as well where we are using hardware raid and ietd. May be I am missing something in iet configuration ?
>> My configuration is as below.
>>
>> ******************
>> Target iqn.2013-07.myserver.myvolume:dbserver
>>         HeaderDigest None
>>         DataDigest None
>>         MaxConnections 4
>>         InitialR2T Yes
>>         ImmediateData Yes #Changed this to get performance
>>         MaxRecvDataSegmentLength 131072
>>         MaxXmitDataSegmentLength 131072
>>         MaxBurstLength 262144
>>         FirstBurstLength 262144
>>         DefaultTime2Wait 2
>>         DefaultTime2Retain 20
>>         MaxOutstandingR2T 8
>>         DataPDUInOrder Yes
>>         DataSequenceInOrder Yes
>>         ErrorRecoveryLevel 0
>>         Lun 0 Path=/dev/tbl001/dbserver,Type=blockio,ScsiSN=2013TbL-0XYz-d2a,ScsiId=2013TbL-0XYz-d2a,IOMode=wb
>> *********************
> Post a copy of the kernel panic message and let's take a look at it.
>
> -Ross
>
> ______________________________________________________________________
> 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.
>