From owner-freebsd-stable@FreeBSD.ORG Wed Feb 13 23:16:31 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 7230D719; Wed, 13 Feb 2013 23:16:31 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) by mx1.freebsd.org (Postfix) with ESMTP id 01311702; Wed, 13 Feb 2013 23:16:30 +0000 (UTC) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.14.6/8.14.6) with ESMTP id r1DNGJBE073050; Thu, 14 Feb 2013 01:16:19 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.7.4 kib.kiev.ua r1DNGJBE073050 Received: (from kostik@localhost) by tom.home (8.14.6/8.14.6/Submit) id r1DNGHEl073049; Thu, 14 Feb 2013 01:16:17 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 14 Feb 2013 01:16:17 +0200 From: Konstantin Belousov To: Rick Macklem Subject: Re: 9-STABLE -> NFS -> NetAPP: Message-ID: <20130213231617.GZ2522@kib.kiev.ua> References: <20130213203042.GW2522@kib.kiev.ua> <431606432.2998831.1360795813954.JavaMail.root@erie.cs.uoguelph.ca> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="tQONwxv1SlzjgsUV" Content-Disposition: inline In-Reply-To: <431606432.2998831.1360795813954.JavaMail.root@erie.cs.uoguelph.ca> User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on tom.home Cc: Marc Fournier , freebsd-stable@freebsd.org, John Baldwin X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 13 Feb 2013 23:16:31 -0000 --tQONwxv1SlzjgsUV Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Feb 13, 2013 at 05:50:13PM -0500, Rick Macklem wrote: > I got it resent from him. I've attached it to this post, just in case you > are interested in taking a look at it. I do not see the voffset wchains surprising. All of them seems to occur in the multithreading process. The usual reason for the voffset blocking is the use of the same file (as in struct file *) to perform operations =66rom several threads in parallel. One thread locked the file offset by using read() or write(), and sleeping waiting for the vnode locked. All other threads performing read or write on the same file, e.g. by using the same file descriptor, are locked on the file offset before even trying to lock the vnode. What I see interesting in the output you mailed, is the pid 93636. Note that several its threads are in the 'T' state. It means stopped, while other threads obviously do file i/o due to vofflock state. I wonder if some stopped thread owns nfs vnode lock. It could be some omission in the handling of PBDRY/TDF_BDRY, or other bug. It is absolutely impossible to say anything definitive without proper diagnostic. At least the procstat -kk is needed. --tQONwxv1SlzjgsUV Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQIcBAEBAgAGBQJRHB7BAAoJEJDCuSvBvK1BWYQP/0ghBV9Ab0FpZB2v6k1cZ0WW JLsgFcdkn/YpPkiLDhifDDmCA3S1YX/AnlvIHEA61LgHtIvF8yMhkBpk8Ph0gYhF UAyCe3UlZTOtSMF/ZXp3IBvNvGrTyAN90qxYwZDMGB9NbmucTCMOeWgiE18VrLwa kbsHkvyVcbOTIj/ucR/nZg5Tnlp9pr9Dt1h7fEHXS2SdNnMTKwROTk9RoQA2Z7Zt XQoxF+aLHKHD8d3itzSTAZ53zSplo5mwnGuucKB9A8AjZph32j3AtbCPcfVYE/Kj ZGkbSAqlkCkCLa3+21um19cJWENPz8537z60P9YnyVi6HQroSfjTDUFoWOoVeq95 ZAD8dnlRNDdDV9bhHGvInPuwEjWWnavCy1tyfl8q3YsJyZnVLQM5cCA0/VbSgthI Q9dGgNjSxmnJRVRtFlkun7Tg+3RijXptyCGdtxvnMtP/FVoyBsrDffOohdnhDhZT n23sN9EVRm+jW48koSsZYtqaR0Ek7iEMUqLgX77bHDefKhCYWMl2ydYA1cd5F54L krLepKqV5w2Dxo+csyRWzveLTkzUpPhXl2pR7QeL3T4DDD5yfvkADOrWbjVvsVpl 3etTJ3ZlAfPX+AQEay7+NOEc9XJA/Ra8IKI98s47MdktgKWX5km65bpP8JIDjDCq bzdt3DqK3J/yHmeP7Xy1 =DIyu -----END PGP SIGNATURE----- --tQONwxv1SlzjgsUV--