Package: tgt-glusterfs
Version: 1:1.0.69-1
Severity: grave
Tags: upstream
Justification: renders package unusable
Dear Maintainer,
with a relatively simple setup:
local glusterfs, with a replica 2 volume, I tried to use tgtd with glfs. My tgt
config was like so:
<target iqn.2018-07.de.xxxxxx:stor-b-0>
vendor_id xxxxxx
bs-type glfs
bsopts "logfile=/var/log/bs-glfs.log;loglevel=3"
write-cache off
initiator-address 10.10.8.0/24
backing-store "[email protected]:/iSCSI_VOL1.img"
backing-store "[email protected]:/iSCSI_VOL2.img"
controller_tid=10
</target>
...
/var/log/daemon.log gives me this endlessly
Jul 30 20:28:55 storage-b-02 tgtd[30479]: tgtd: abort_task_set(1349) found 38ec 0
Jul 30 20:28:55 storage-b-02 tgtd[30479]: tgtd: abort_cmd(1325) found 38ec 6
Jul 30 20:29:05 storage-b-02 tgtd[30479]: tgtd: abort_task_set(1349) found 38ec 0
Jul 30 20:29:05 storage-b-02 tgtd[30479]: tgtd: abort_cmd(1325) found 38ec 6
/var/log/messages contains this
Jul 30 20:34:17 storage-b-02 kernel: [436035.821673] tgtd[31394]: segfault at
220 ip 00007f6944b24dcb sp 00007fffdf64f800 error 4 in
libgfapi.so.0.0.0[7f6944b1d000+25000]
Jul 30 20:37:39 storage-b-02 kernel: [436237.496969] tgtd[31627]: segfault at
220 ip 00007f370a520dcb sp 00007ffd3c51e5c0 error 4 in
libgfapi.so.0.0.0[7f370a519000+25000]
I don't know, if it's related to the Volume-Files being 10T big, but it
shouldn't, I think.
Thanks.
-- System Information:
Debian Release: 9.5
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-7-amd64 (SMP w/12 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages tgt-glusterfs depends on:
ii glusterfs-common 3.8.8-1
ii libc6 2.24-11+deb9u3
ii tgt 1:1.0.69-1
tgt-glusterfs recommends no packages.
tgt-glusterfs suggests no packages.
-- no debconf information
