Date: Sat, 10 Aug 2019 08:53:11 +1000 From: Korolev Sergey <serejk@febras.net> To: hw <hw@adminart.net> Cc: Graham Perrin <grahamperrin@gmail.com>, freebsd-questions@freebsd.org Subject: Re: kill -9 does nothing Message-ID: <05B96F5A-2141-460E-B9F1-7BC4A7854B4A@febras.net> In-Reply-To: <87o90yxy99.fsf@toy.adminart.net> References: <20190808180557.abbdd74fcdb74806aed1fd98@gc-24.de> <b234b18f-4720-6278-89eb-962190a5567a@gmail.com> <87o90yxy99.fsf@toy.adminart.net>
next in thread | previous in thread | raw e-mail | index | archive | help
I don't think this is an NFS problem. I had got the same problem with Apache= + ZFS combination (but it was an old FreeBSD version like 7-8, I don't reme= mber). The main point is that the process hangs in iowait state, which it ne= ver will exit from. The only solution is hard reboot. The reason of that is r= ather more complicated, than just "NFS is bad", or "Apache is bad". This is a= n Open Source, and you could always help with a patch, extensive debug info t= o clarify the bug, etc, so any help will be appreciated. > On 9 Aug 2019, at 23:29, hw <hw@adminart.net> wrote: >=20 > Graham Perrin <grahamperrin@gmail.com> writes: >=20 >>> On 08/08/2019 17:05, hw wrote: >>> =85 Firefox has a tendency to become unresponsive. =85 >> Which version of the OS? >=20 > 12 release >=20 > It turned out that Firefox was stuck in some kind of NFS deadlock. I > even had to destroy the VM because it won't shutdown anymore. NFS is > bad with FreeBSD. > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.or= g"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?05B96F5A-2141-460E-B9F1-7BC4A7854B4A>