Dave Olson <ol...@cumulusnetworks.com> wrote: > Dave Olson <ol...@cumulusnetworks.com> wrote: > > > 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.
The cause is that the highest_objectid field in the btrfs_root structure is set incorrectly (an old stale value) at filesystem mount in some cases. See the writeup in the bug for more details. I'm guessing that some of the journal information is not flushed to disk after btrfs_create(), even when the filesystem is mounted with flushoncommit, so if a powercycle is done within a few seconds of the file being created, there is a good chance that this problem will occur on a subsequent reboot. btrfs check (up through 4.7.3) does not seem to detect this stale condition. Dave Olson ol...@cumulusnetworks.com -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
