From: Jason L Tibbitts III <tibbs@math.uh.edu>
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
Date: Wed, 28 Aug 2019 13:29:00 -0500 [thread overview]
Message-ID: <ufay2zduosz.fsf@epithumia.math.uh.edu> (raw)
In-Reply-To: <20190828174609.GB29148@fieldses.org> (J. Bruce Fields's message of "Wed, 28 Aug 2019 13:46:09 -0400")
>>>>> "BF" == J Bruce Fields <bfields@fieldses.org> 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<
next prev parent reply other threads:[~2019-08-28 18:29 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-13 15:08 Regression in 5.1.20: Reading long directory fails Jason L Tibbitts III
2019-08-13 17:00 ` Jason L Tibbitts III
2019-08-22 19:39 ` Jason L Tibbitts III
2019-08-28 17:46 ` J. Bruce Fields
2019-08-28 18:29 ` Jason L Tibbitts III [this message]
2019-08-28 18:33 ` J. Bruce Fields
2019-09-03 15:49 ` Jason L Tibbitts III
2019-09-03 18:02 ` Wolfgang Walter
2019-09-03 19:06 ` Jason L Tibbitts III
2019-09-03 19:08 ` Chuck Lever
2019-09-03 21:37 ` Wolfgang Walter
2019-09-04 1:50 ` Jason L Tibbitts III
2019-09-06 14:48 ` J. Bruce Fields
2019-09-06 20:47 ` Jason L Tibbitts III
2019-09-06 20:50 ` Chuck Lever
2019-09-08 11:39 ` Benjamin Coddington
2019-09-08 15:19 ` Trond Myklebust
2019-09-08 15:48 ` Chuck Lever
2019-09-08 16:47 ` Trond Myklebust
2019-09-08 16:51 ` Chuck Lever
2019-09-11 16:25 ` Benjamin Coddington
2019-09-11 16:39 ` Chuck Lever
2019-09-11 17:26 ` Benjamin Coddington
2019-09-11 17:27 ` Benjamin Coddington
2019-09-11 17:29 ` Chuck Lever
2019-09-11 17:40 ` Benjamin Coddington
2019-09-11 17:43 ` Chuck Lever
2019-09-11 17:59 ` Benjamin Coddington
2019-09-11 17:50 ` Benjamin Coddington
2019-09-11 17:54 ` Chuck Lever
2019-09-12 12:29 ` Benjamin Coddington
2019-09-12 12:53 ` Trond Myklebust
2019-09-12 13:08 ` Benjamin Coddington
2019-09-12 13:13 ` J. Bruce Fields
2019-09-12 13:25 ` Trond Myklebust
2019-09-12 13:35 ` Benjamin Coddington
2019-09-12 13:14 ` Trond Myklebust
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ufay2zduosz.fsf@epithumia.math.uh.edu \
--to=tibbs@math.uh.edu \
--cc=bfields@fieldses.org \
--cc=km@cm4all.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).