From owner-freebsd-current@freebsd.org Thu Aug 9 14:06:02 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 757C210675EB for ; Thu, 9 Aug 2018 14:06:02 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E1F237432F for ; Thu, 9 Aug 2018 14:06:01 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id w79E5wDl017583; Thu, 9 Aug 2018 07:05:58 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id w79E5v7n017582; Thu, 9 Aug 2018 07:05:57 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201808091405.w79E5v7n017582@pdx.rh.CN85.dnsmgr.net> Subject: Re: ffs_truncate3 panics In-Reply-To: To: Rick Macklem Date: Thu, 9 Aug 2018 07:05:57 -0700 (PDT) CC: Konstantin Belousov , "freebsd-current@FreeBSD.org" , "peter@holm.cc" X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Aug 2018 14:06:02 -0000 > Konstantin Belousov wrote: > [stuff snipped] > >> >Can you print the only buffer on the clean queue when the panic occur ? > >> ffst3 vtyp=1 bodirty=0 boclean=1 > >> buf at 0x428a110 > >> b_flags = 0x20001020, b_xflags=0x2, b_vflags=0x0 > >> b_error = 0, b_bufsize = 4096, b_bcount = 4096, b_resid = 0 > >> b_bufobj = (0xfd8ba94), b_data = 0x5170000, b_blkno = -1, b_lblkno = -1, b_dep = 0 > >> b_kvabase = 0x5170000, b_kvasize = 32768 > >So the buffer was indeed for extended attrs, and never written to the disk. > >I am quite interested what was the inode content prior to the truncation, > >esp. the di_extsize. > Just in case it wasn't clear, this buffer is on the clean list and not the dirty one. > (Does this mean it somehow got onto the "clean list" without being written to disk?) > > >Could you try to formulate a way to reproduce the panic so that Peter > >can recreate it, please ? > I doubt it. It would require him doing a pNFS setup with multiple systems. > (At least that is the only way I reproduce it and I sometimes go a week of testing > before I see them.) > It would be great to have more testers for the pNFS server stuff, but I doubt it > would fit into Peter's setup? It should be possible to design a set of VM's using bhyve, xen or ones favorite hypervisor/virtulization platform to do "more" pNFS testing. If you could provide a rought machine set needed to have a functional test bed, and what should be done to "test" for problems I think it should be possible to get you some addition testers. Thanks, > I can add printf()s anywhere you suggest, but I'm not sure how you would catch > this case sooner? (For example, I could print out di_extsize at the beginning of > ffs_truncate(), if that would help?) > > rick > [more stuff snipped] -- Rod Grimes rgrimes@freebsd.org