Date: Sat, 10 Aug 2019 18:11:00 +0200 From: hw <hw@adminart.net> To: Korolev Sergey <serejk@febras.net> Cc: freebsd-questions@freebsd.org, Graham Perrin <grahamperrin@gmail.com> Subject: Re: kill -9 does nothing Message-ID: <87zhkh80h7.fsf@toy.adminart.net> In-Reply-To: <05B96F5A-2141-460E-B9F1-7BC4A7854B4A@febras.net> (Korolev Sergey's message of "Sat, 10 Aug 2019 08:53:11 %2B1000") References: <20190808180557.abbdd74fcdb74806aed1fd98@gc-24.de> <b234b18f-4720-6278-89eb-962190a5567a@gmail.com> <87o90yxy99.fsf@toy.adminart.net> <05B96F5A-2141-460E-B9F1-7BC4A7854B4A@febras.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Korolev Sergey <serejk@febras.net> writes: > 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 remember). The main point is that the process hangs in iowait > state, which it never will exit from. The only solution is hard > reboot. The reason of that is rather more complicated, than just "NFS > is bad", or "Apache is bad". First I would need to establish whether it actually was a deadlock or desirable behaviour which is to ensure that data doesn't get lost. It could also have been an incompatibility between different implementations, or even versions, of NFS. > This is an Open Source, and you could always help with a patch, > extensive debug info to clarify the bug, etc, so any help will be > appreciated. I know how that goes: My help is so appreciated that reported bugs are either being ignored or met with a refusal to fix them, and provided patches that do fix the bug are also being ignored. Same goes for feature requests. Help is _not_ appreciated, that much is obvious.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?87zhkh80h7.fsf>