From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 205833] New: fsfreeze blocks close(fd) on xfs sometimes
Date: Wed, 11 Dec 2019 14:03:52 +0000 [thread overview]
Message-ID: <bug-205833-201763@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=205833
Bug ID: 205833
Summary: fsfreeze blocks close(fd) on xfs sometimes
Product: File System
Version: 2.5
Kernel Version: 4.15.0-55-generic #60-Ubuntu
Hardware: Intel
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: XFS
Assignee: filesystem_xfs@kernel-bugs.kernel.org
Reporter: kernel.org@estada.ch
Regression: No
Dear all
I noticed the bug while setting up a backup with fsfreeze and restic.
How I reproduce it:
1. Write multiple MB to a file (eg. 100MB) while after one or two MB freeze
the filesystem from the sidecar pod
2. From the sidecar pod, issue multiple `strace tail /generated/data/0.txt`
3. After a couple of tries strace shows that the `read(...)` works but
`close(...)` hangs
4. From now on all `read(...)` operations are blocked until the freeze is
lifted
System: Ubuntu 18.04.3 LTS
CPU: Intel(R) Xeon(R) CPU X5650 @ 2.67GHz
Storage: /dev/mapper/mpathXX on /var/lib/kubelet/plugins/hpe.com/... type xfs
(rw,noatime,attr2,inode64,noquota)
I used this tool to generate the file. The number of concurrent files does not
appear to matter that much. I was able to trigger the bug, tested with 2, 4 and
32 parallel files:
https://gitlab.com/dns2utf8/multi_file_writer
Cheers,
Stefan
PS: I opened a bug at the tool vendor too:
https://github.com/vmware-tanzu/velero/issues/2113
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2019-12-11 14:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 14:03 bugzilla-daemon [this message]
2019-12-12 18:01 ` [Bug 205833] New: fsfreeze blocks close(fd) on xfs sometimes Brian Foster
2019-12-12 18:01 ` [Bug 205833] " bugzilla-daemon
2019-12-17 9:34 ` bugzilla-daemon
2019-12-17 12:03 ` Brian Foster
2019-12-17 12:03 ` bugzilla-daemon
2022-09-05 14:29 ` bugzilla-daemon
2023-10-09 15:37 ` 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-205833-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.