On Fri, Nov 27, 2015 at 1:43 PM, Hugo Mills <h...@carfax.org.uk> wrote: > On Fri, Nov 27, 2015 at 10:33:29PM +0200, Imran Geriskovan wrote: >> After upgrading from systemd227 to 228 >> these messages began to show up during boot: >> >> [ 24.652118] BTRFS: could not find root 8 >> [ 24.664742] BTRFS: could not find root 8 >> >> Are they important? > > That's the quota tree. I don't know exactly what's happening, but > possibly systemd is now enabling qgroups for its own purposes, and > what you're seeing is simply the qgroups being enabled for the first > time?
I'm seeing a feature in systemd 228, "systemd-tmpfiles learned two new line types “q” and “Q” that operate like “v”, but also set up a basic btrfs quota hierarchy when used on a btrfs file system with quota enabled." https://lukevizzicks.co.uk/systemd-228-system-and-service-manager-released/ But from github I'm not finding any indication that systemd enables quota. This issue suggests that quota disabled is tolerated. https://github.com/systemd/systemd/issues/1809 Questions: a. Quotas seem to be sufficiently in-flux, and with two (?) deprecated methods, and one new implementation that I don't think it's OK for anything to enable it by default. Are there different opinions on this? b. For the OP, is it possible quotas was ever enabled on this file system? c. How can we determine if quotas are enabled on Btrfs? I don't see a command within btrfs-quota to determine quota status. -- 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
