BTRFS error message (supposedly harmless)

Hi there, since the last TW update I’m seeing the following on dmesg:

    6.081804] audit: type=1130 audit(1454869878.607:108): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-sysctl comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
    6.082218] BTRFS error (device sdb2): could not find root 8
    6.082229] BTRFS error (device sdb2): could not find root 8
    6.082388] BTRFS error (device sdb2): could not find root 8
    6.082398] BTRFS error (device sdb2): could not find root 8

The error seems to be harmless since my btrfs partition works fine.

I goggled a little bit about the issue but I couldn’t find anything. Should I be worried about this?

Here is the full dmesg log:
http://paste.opensuse.org/82065526

I’m having this exactly same problem:

19.157635] audit_printk_skb: 330 callbacks suppressed
19.157636] audit: type=1130 audit(1454889578.419:114): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=‘unit=systemd-journal-flush comm=“systemd” exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success’
19.225748] BTRFS error (device sda9): could not find root 8
19.226323] BTRFS error (device sda9): could not find root 8
19.226894] BTRFS error (device sda9): could not find root 8
19.227411] BTRFS error (device sda9): could not find root 8
19.247778] BTRFS error (device sda9): could not find root 8
19.248336] BTRFS error (device sda9): could not find root 8
19.248964] BTRFS error (device sda9): could not find root 8
19.249422] BTRFS error (device sda9): could not find root 8
19.249860] BTRFS error (device sda9): could not find root 8
19.250251] BTRFS error (device sda9): could not find root 8

Should I be worried?

I found this bug here but it is marked fixed. Maybe it is a regression:

https://bugzilla.suse.com/show_bug.cgi?id=959764

It is probably related to systemd update which seems to trigger btrfs quota: http://www.spinics.net/lists/linux-btrfs/msg49603.html

I found this bug here but it is marked fixed. Maybe it is a regression:

959764 – systemd 228 failed switch to tty1

This bug is unrelated to these messages (even though reporter quoted them). It makes sense to open new bug report about them. Even if they are harmless, any excessive error logging is bad because it hides real problems.