From owner-freebsd-stable@freebsd.org Wed Oct 4 12:03:15 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DF62DE3801F for ; Wed, 4 Oct 2017 12:03:15 +0000 (UTC) (envelope-from estartu@ze.tum.de) Received: from mail.ze.tum.de (mail.ze.tum.de [IPv6:2001:4ca0:2e03::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.ze.tum.de", Issuer "Zertifizierungsstelle der TUM" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8118F8457F for ; Wed, 4 Oct 2017 12:03:14 +0000 (UTC) (envelope-from estartu@ze.tum.de) Received: from etustar.ze.tum.de (etustar.ze.tum.de [129.187.39.200]) by mail.ze.tum.de (8.15.2/8.15.2) with ESMTPS id v94C3ATZ066791 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Wed, 4 Oct 2017 14:03:10 +0200 (CEST) (envelope-from estartu@ze.tum.de) From: Gerhard Schmidt Subject: nvd0 lockup while compiling ports To: freebsd-stable@freebsd.org Organization: =?UTF-8?Q?Technische_Universit=c3=a4t_M=c3=bcnchen_-_WWW_und_O?= =?UTF-8?Q?nline_Services?= Message-ID: <8d1471c9-7341-8892-88f7-a539fc77c45e@ze.tum.de> Date: Wed, 4 Oct 2017 14:03:10 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: de-DE Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Oct 2017 12:03:16 -0000 Hi, I've got a new Workstation last week with the Main HD as M2 Card. FreeBSD recognizes the card as nvd0 nvd0: NVMe namespace nvd0: 488386MB (1000215216 512 byte sectors) When compiling some ports (in this example VirtualBox-ose) I experiencing lockups on the Harddisk when many files are deleted. here is the entries gstat reports dT: 1.064s w: 1.000s L(q) ops/s r/s kBps ms/r w/s kBps ms/w %busy Name 25281 769 0 0 0.0 0 0 0.0 100.0| nvd0 25279 769 0 0 0.0 0 0 0.0 100.0| nvd0p4 25279 769 0 0 0.0 0 0 0.0 100.0| ufs/USR here the right part of gstat -d -o dT: 1.003s w: 1.000s d/s kBps ms/d o/s ms/o %busy Name 770 24641 31965 0 0.0 100.1| nvd0 770 24641 31965 0 0.0 100.1| nvd0p4 770 24641 31965 0 0.0 100.1| ufs/USR the numbers under L(q) go up to about 160000 and as long as theses operations are not finisched, no outer file operation is possible on this filesystem. The number of ops/s and d/s is constant aproximatly 770. Is there a way to speed up delete operations or limit the queue length? Regards Estartu