Re: tgtd segfault

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 03 Aug 2010 17:46:35 +0200
Tomasz Chmielewski <mangoo@xxxxxxxx> wrote:

> On 29.07.2010 04:20, FUJITA Tomonori wrote:
> 
> >> FYI, it works fine since I started it about a week ago. 1.0.6
> >> malfunctioned after 1-2 days.
> > 
> > Thanks, the pthread-per-target changes were reverted, so it should be
> > stable now. tgt had been stable before the changes. Otherwise, vendor
> > guys would hit me hard, I guess. :)
> 
> Looks I'm not so happy with it as well - the version with reversed patch crashed after a week or so:
> 
> Aug  3 06:24:15 megathecus kernel: tgtd[16427]: segfault at 44 ip 0806cbe0 sp 6be26320 error 4 in tgtd[8048000+2b000]
> Aug  3 06:24:15 megathecus tgtd: tgtd logger exits abnormally, pid:16403 
> 
> 
> There isn't anything more in the log though.

That's bad. Seems that disconnections often happens in your
environments so it might be related with it.


> I'll try to run 1.0.5 for some longer now.
> 
> The last version I used before that was 1.0.1, and it was running for months without problems.

Probably, the best choice for you is the version that RHEL5 uses. I
think that it's based on around 1.0.0 including some fixes.

Right now, I have no idea what changes could be bad since 1.0.0.
--
To unsubscribe from this list: send the line "unsubscribe stgt" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux SCSI]     [Linux RAID]     [Linux Clusters]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]

  Powered by Linux