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=-0.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS 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 88A24C3A5A1 for ; Wed, 28 Aug 2019 18:29:05 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 5D4C522DA7 for ; Wed, 28 Aug 2019 18:29:05 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726592AbfH1S3F (ORCPT ); Wed, 28 Aug 2019 14:29:05 -0400 Received: from mx1.math.uh.edu ([129.7.128.32]:53356 "EHLO mx1.math.uh.edu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726591AbfH1S3E (ORCPT ); Wed, 28 Aug 2019 14:29:04 -0400 Received: from epithumia.math.uh.edu ([129.7.128.2]) by mx1.math.uh.edu with esmtp (Exim 4.92) (envelope-from ) id 1i32gm-0002ay-RH; Wed, 28 Aug 2019 13:29:03 -0500 Received: by epithumia.math.uh.edu (Postfix, from userid 7225) id BF4D6801554; Wed, 28 Aug 2019 13:29:00 -0500 (CDT) From: Jason L Tibbitts III To: bfields@fieldses.org (J. Bruce Fields) 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 References: <20190828174609.GB29148@fieldses.org> Date: Wed, 28 Aug 2019 13:29:00 -0500 In-Reply-To: <20190828174609.GB29148@fieldses.org> (J. Bruce Fields's message of "Wed, 28 Aug 2019 13:46:09 -0400") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Sender: linux-nfs-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-nfs@vger.kernel.org >>>>> "BF" == J Bruce Fields writes: BF> Looks like that's db531db951f950b8 upstream. (Do you know if it's BF> reproduceable upstream as well?) Yes, it's reproducible up in the 5.3.0 RCs as well. However, while trying to do some further bisecting I ran into an odd problem. Now kernels which were previously working (i.e. 5.1.19 and older) are returning errors, but at a different file count. This only gives me more questions. And so, just to be absolutely sure that there isn't some weird server issue involved, I'm going to try to schedule a reboot of the relevant server. BF> Maybe it depends on having names of the right length to place some BF> bit of xdr on a boundary. I wonder if it'd be possible to reproduce BF> just by varying the name lengths randomly till you hit it. I know I can't reproduce with loads of short names, and with relatively long names as well (using sha256sum as filename generator). BF> No clever debugging ideas off the top of my head, I'm afraid. I BF> might start by patching the kernel or doing some tracing to figure BF> out exactly where that EIO is being generated? 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: 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. _ J<