I'm running tgtd under CentOS 6.0 and am getting somewhat frequent
(one a week or so) core dumps where the tgtd process will still be up,
however all clients are disconnected and can not reconnect until the
tgtd process is stopped with a "kill -9" ("service tgtd force-restart"
never returns). This is a fairly lightly used server -- it is only
sharing 4 targets. The server has 8G of RAM, and is booted off a
compact-flash disk with the main data disks being a large RAID-6 array
formatted to XFS. The shared targets are sparse image files.
>From my /var/log/message during the crash, I see:
Nov 3 05:01:59 san2 abrt[19227]: saved core dump of pid 6236
(/usr/sbin/tgtd) to /var/spool/abrt/ccpp-
1320310886-6236.new/coredump (649863168 bytes)
On an ongoing basis, I see things like:
Nov 2 04:32:53 san2 tgtd: abort_cmd(984) found 10000015 e
Nov 2 04:32:53 san2 tgtd: abort_cmd(984) found 1000006e e
Nov 2 04:33:02 san2 tgtd: abort_task_set(1008) found 6 0
Nov 2 04:52:40 san2 tgtd: conn_close(100) connection closed, 0xb71308 2
Nov 2 04:52:40 san2 tgtd: conn_close(106) sesson 0xb4ad80 1
Nov 2 04:52:40 san2 tgtd: conn_close(129) Forcing release of tx task
0xadcad0 0 0
Are there any known stability problems with CentOS 6? (I have another
NAS running tgtd on Centos 5.6 that is 100% stable). Should I abandon
the yum supplied version and download and re-compile the latest from
source?
Any advice would be helpful. I have the dump files available if
anything can be gleamed from them
Thanks
--
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
