From: Dave Olson <olson@cumulusnetworks.com>
To: linux-btrfs@vger.kernel.org
Subject: Problem with btrfs fs in 4.1.25 - getting EBUSY on file create - kernel.org bug 173001
Date: Tue, 27 Sep 2016 14:17:29 -0700 [thread overview]
Message-ID: <20160927211729.GC1601@cumulusnetworks.com> (raw)
The full details are in
https://bugzilla.kernel.org/show_bug.cgi?id=173001
Basicly, logrotate has rotated a file to a new name, tries to open a new
file with the original name, and gets EBUSY. The file is not created.
Later on the file can be created with no problems.
I've turned on most of the BTRFS config options, and there are no BTRFS
messages related to the failure.
The file is on the root filesystem.
Dave Olson
olson@cumulusnetworks.com
next reply other threads:[~2016-09-27 21:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-27 21:17 Dave Olson [this message]
2016-10-04 6:39 ` Problem with btrfs fs in 4.1.25 (also 4.8.0) - getting EBUSY on file create - kernel.org bug 173001 Dave Olson
2016-10-06 16:44 ` Problem with btrfs_create() getting EBUSY; cause is stale highest_objectid at mount " Dave Olson
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=20160927211729.GC1601@cumulusnetworks.com \
--to=olson@cumulusnetworks.com \
--cc=linux-btrfs@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).