Date: Fri, 29 Nov 2019 16:24:09 +0700 From: Eugene Grosbein <eugen@grosbein.net> To: Konstantin Belousov <kostikbel@gmail.com>, Willem Jan Withagen <wjw@digiware.nl> Cc: FreeBSD Hackers <freebsd-hackers@freebsd.org>, Alexander Motin <mav@FreeBSD.org>, Andriy Gapon <avg@freebsd.org> Subject: Re: Process in T state does not want to die..... Message-ID: <a2daa66f-b073-8c20-3668-aceec25b4ba9@grosbein.net> In-Reply-To: <20191128214633.GV10580@kib.kiev.ua> References: <966f830c-bf09-3683-90da-e70aa343cc16@digiware.nl> <3c57e51d-fa36-39a3-9691-49698e8d2124@grosbein.net> <91490c30-45e9-3c38-c55b-12534fd09e28@digiware.nl> <20191128115122.GN10580@kib.kiev.ua> <296874db-40f0-c7c9-a573-410e4c86049a@digiware.nl> <20191128195013.GU10580@kib.kiev.ua> <1ae7ad65-902c-8e5f-bcf1-1e98448c64bb@digiware.nl> <20191128214633.GV10580@kib.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
29.11.2019 4:46, Konstantin Belousov write: >> sys_extattr_set_fd+0xee amd64_syscall+0x364 fast_syscall_common+0x101 > This is an example of the cause for your problem. I observe this problem too, but my use case is different. I have several bhyve instances running Windows guests over ZVOLs over SSD-only RAIDZ1 pool. "zfs destroy" for snapshots with large "used" numbers takes long time (several minutes) due to slow TRIM. Sometimes this makes virtual guest unresponsible and attempt to restart the bhyve instance may bring it to Exiting (E) state for several minutes and it finishes successfully after that. But sometimes bhyve process hangs in T state indefinitely. This is 11.3-STABLE/amd64 r354667. Should I try your patch too?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a2daa66f-b073-8c20-3668-aceec25b4ba9>