[Stgt-devel] disk kicked out of RAID -> tgtd segmentation fault
Tue Jul 1 01:34:00 CEST 2008
I've also noticed there is only one tgtd process when running it in
Running in the foreground has been the only way I've been successful
in collecting core files in the past.
I still do not (read: never actually spent time looking) understand
the why/what differences is between foreground and why there is two
processes while in background.
I would have to assume that there is some sort of race condition or
handshake issue between the two processes within your test senerio.
Sorry I can't be of much help.
On Mon, Jun 30, 2008 at 7:00 PM, Tomasz Chmielewski <mangoo at wpkg.org> wrote:
> Mark Harvey schrieb:
>> My 2c worth.
>> Try running the tgtd in 'foreground' mode (after setting "ulimit -c
>> You will then get a core file which should be a little easier to work
>> with (vs gdb on a running tgtd instance).
> It doesn't crash when started in the foreground mode.
> Also, when started in the foreground mode, we only have one tgtd
> process, so perhaps this somehow makes the issue harder or impossible to
> Tomasz Chmielewski
> Stgt-devel mailing list
> Stgt-devel at lists.berlios.de
More information about the stgt