From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.2 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 8D654C3A5A6 for ; Wed, 28 Aug 2019 18:33:56 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 6E3EE208C2 for ; Wed, 28 Aug 2019 18:33:56 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726909AbfH1Sdz (ORCPT ); Wed, 28 Aug 2019 14:33:55 -0400 Received: from fieldses.org ([173.255.197.46]:49384 "EHLO fieldses.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726586AbfH1Sdz (ORCPT ); Wed, 28 Aug 2019 14:33:55 -0400 Received: by fieldses.org (Postfix, from userid 2815) id AD7341CB4; Wed, 28 Aug 2019 14:33:54 -0400 (EDT) Date: Wed, 28 Aug 2019 14:33:54 -0400 From: "J. Bruce Fields" To: Jason L Tibbitts III Cc: linux-nfs@vger.kernel.org, km@cm4all.com, linux-kernel@vger.kernel.org Subject: Re: Regression in 5.1.20: Reading long directory fails Message-ID: <20190828183354.GD29148@fieldses.org> References: <20190828174609.GB29148@fieldses.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Aug 28, 2019 at 01:29:00PM -0500, Jason L Tibbitts III wrote: > If I had any idea how to do that, I happily would. I'm certainly > willing to learn. At least I can run strace to see where ls bombs: Somewhat of a caveman, I might start at the code for getdents, sprinkle printk's around until I get down to the relevant code in the NFS layer.... There's probably a better way to do it with tracing. > getdents64(5, 0x7fc13afaf040, 262144) = -1 EIO (Input/output error) > > bcodding on IRC mentioned that is a rather large count. Does make me > wonder if the server is weirding out and sending the client bogus data. > Certainly a server reboot, or maybe even just unmounting and remounting > the filesystem or copying the data to another filesystem would tell me > that. In any case, as soon as I am able to mess with that server, I'll > know more. Might also be worth capturing the network traffic and checking whether wireshark thinks the server replies are valid xdr. --b.