OK I just did a 2nd boot - all the same everything as the previous dmesg.log (patch kernel snapshot). Identical. But not identical results: timing wise the problem happens much sooner, at 14s the fs goes read only instead of 30+ seconds. And I also get this line:
[ 14.039931] systemd-journald[488]: Failed to set ACL on /var/log/journal/864b0a611b104692b266377c7d4c7a39/user-1000.journal, ignoring: Operation not permitted entire dmesg for this boot: https://drive.google.com/open?id=0B_2Asp8DGjJ9LTRzZjA2SThtbkE Did it fail to set the ACL because the file system is readonly? Or was trying to set the ACL what triggers the problem - then it goes readonly and then we see the the complaint that the ACL failed to be set? There's close proximity timing wise to the first Btrfs error messages, with the most recent patch, and systemd audit messages. Systemd-journald is switching from /run to /var, flushing the journal to disk within about 2 seconds of the first Btrfs error. And systemd does chattr +C on its logs by default now (and I think it's not user changeable behavior so I can't test if it's related). Chris Murphy -- 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
