Date: Mon, 18 Nov 2019 05:33:15 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 242047] ctld zvol hangups Message-ID: <bug-242047-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D242047 Bug ID: 242047 Summary: ctld zvol hangups Product: Base System Version: 12.1-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Many People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: pprocacci@gmail.com I believe I'm having similar issues to the following two bug reports but am= not 100% sure: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229958 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D226499 I'm therefore creating a new bug report detailing the problems I have happening. I've created a 1TB ZVOL and have giving it to ctld for iSCSI attachment elsewhere. When the host that is copying large amount of data to this ZVOL fires up ov= er iSCSI, the iSCSI disk hangs and eventually disappears. Furthermore, while this is happening, some processes (not all) on the host itself hang entirely. zpool related commands hang, attempts to restart ctld hang, a forceful kill of ctld does nothing. I'm really not sure what information to provide other than my zfs configuration: ------------------------------- zpool status -v pool: tank state: ONLINE scan: none requested config: NAME STATE READ WRITE CKSUM tank ONLINE 0 0 0 raidz2-0 ONLINE 0 0 0 ada0 ONLINE 0 0 0 ada1 ONLINE 0 0 0 ada2 ONLINE 0 0 0 ada3 ONLINE 0 0 0 errors: No known data errors pool: zroot state: ONLINE scan: none requested config: NAME STATE READ WRITE CKSUM zroot ONLINE 0 0 0 nvd0p2 ONLINE 0 0 0 errors: No known data errors ------------------------------- Other than the above, the only thing I can think to provide are system spec= s: CPU: 29.7% user, 0.2% nice, 2.5% system, 0.1% interrupt, 67.4% idle Mem: 737M Active, 3927M Inact, 13M Laundry, 55G Wired, 2334M Free ARC: 46G Total, 21G MFU, 21G MRU, 2295M Anon, 204M Header, 1635M Other 40G Compressed, 41G Uncompressed, 1.02:1 Ratio .. and perhaps OS version: # uname -a FreeBSD nas.myhome 12.1-RELEASE-p1 FreeBSD 12.1-RELEASE-p1 GENERIC amd64 If there's a way I can debug this problem while it's occuring, I'd like to = know so I can pass it along, but it appears in the other two bug reports I've listed, the problem area is around ZVOL/locking. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-242047-227>