Date: Tue, 3 Oct 2017 00:06:25 +0300 From: Andriy Gapon <avg@FreeBSD.org> To: Ben RUBSON <ben.rubson@gmail.com>, Freebsd fs <freebsd-fs@FreeBSD.org> Subject: Re: ZFS stalled after some mirror disks were lost Message-ID: <84f5608e-d312-437c-3c6b-d8e5847de8bc@FreeBSD.org> In-Reply-To: <9ff8ef2c-b445-dad3-d726-b84793c173ee@FreeBSD.org> References: <4A0E9EB8-57EA-4E76-9D7E-3E344B2037D2@gmail.com> <71d4416a-3454-df36-adae-34c0b70cd84e@multiplay.co.uk> <8A189756-028A-465E-9962-D0181FAEBB79@gmail.com> <5d3e1f0d-c618-afa4-7e52-819c9edf30c9@FreeBSD.org> <48D23270-1811-4E09-8AF2-5C0FEC2F9176@gmail.com> <9ff8ef2c-b445-dad3-d726-b84793c173ee@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 02/10/2017 23:55, Andriy Gapon wrote: > Maybe that caused a domino effect in ZFS code. I see a lot of threads waiting > either for spa_namespace_lock or a spa config lock (a highly specialized ZFS > lock). But it is hard to untangle their inter-dependencies. Forgot to add. It would be nice to determine an owner of spa_namespace_lock. If you have debug symbols then it can be easily done in kgdb on the live system: (kgdb) p spa_namespace_lock -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?84f5608e-d312-437c-3c6b-d8e5847de8bc>