From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 202077] New: xfs transaction overruns on 4.14.67
Date: Wed, 26 Dec 2018 17:19:12 +0000 [thread overview]
Message-ID: <bug-202077-201763@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=202077
Bug ID: 202077
Summary: xfs transaction overruns on 4.14.67
Product: File System
Version: 2.5
Kernel Version: 4.14.67
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: XFS
Assignee: filesystem_xfs@kernel-bugs.kernel.org
Reporter: thomas.walker@twosigma.com
Regression: No
Created attachment 280149
--> https://bugzilla.kernel.org/attachment.cgi?id=280149&action=edit
xfs transaction overrun #1
We've encountered two recent examples of xfs transaction overruns on production
systems running 4.14.67 kernels. Both systems in this case are running docker
with dozens of overlay mounts, using this xfs fs as both upper and lower. In
both cases the filesystem was able to successfully recover when the filesystem
was unmounted and remounted again.
It looks like there has been a good bit of work in 4.16+ addressing similar
issues but none of it has made it back into the 4.14 LTS. Any chance that any
of the attached debug output points to anything specific that might be a
candidate for backport?
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2018-12-26 17:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-26 17:19 bugzilla-daemon [this message]
2018-12-26 17:19 ` [Bug 202077] xfs transaction overruns on 4.14.67 bugzilla-daemon
2019-01-01 22:30 ` [Bug 202077] New: " Dave Chinner
2019-01-01 22:30 ` [Bug 202077] xfs transaction log reservation " bugzilla-daemon
2019-01-02 16:54 ` bugzilla-daemon
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=bug-202077-201763@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-xfs@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).