Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Goffredo Baroncelli <kreijack@inwind.it>
To: Chris Murphy <lists@colorremedies.com>,
	Hugo Mills <hugo@carfax.org.uk>,
	Imran Geriskovan <imran.geriskovan@gmail.com>,
	Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: BTRFS: could not find root 8
Date: Sun, 29 Nov 2015 15:07:43 +0100	[thread overview]
Message-ID: <565B06AF.9020806@inwind.it> (raw)
In-Reply-To: <CAJCQCtQgjbR77eei2-srOofBLpWp-avj_2OMCRa_4Ffby8eL5g@mail.gmail.com>

On 2015-11-27 23:51, Chris Murphy wrote:
> 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

Looking at the systemd source, it seems that it could enable quota when playing with the "machine":


See src/shared/machine-pool.c:

int setup_machine_directory(uint64_t size, sd_bus_error *error) {
        _cleanup_release_lock_file_ LockFile lock_file = LOCK_FILE_INIT;
        struct loop_info64 info = {
                .lo_flags = LO_FLAGS_AUTOCLEAR,
[...]
        r = check_btrfs();
        if (r < 0)
                return sd_bus_error_set_errnof(error, r, "Failed to determine whether /var/lib/machines is located on btrfs: %m");
        if (r > 0) {
                (void) btrfs_subvol_make_label("/var/lib/machines");

                r = btrfs_quota_enable("/var/lib/machines", true);
[...]

But I was unable to understand if:
- enabling quota is a "per filesystem" attribute or per "subvolume attribute"
- when systemd invokes setup_machine_directory()

Does someone have more information ?

BR


-- 
gpg @keyserver.linux.it: Goffredo Baroncelli <kreijackATinwind.it>
Key fingerprint BBF5 1610 0B64 DAC6 5F7D  17B2 0EDA 9B37 8B82 E0B5

  parent reply	other threads:[~2015-11-29 14:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-27 20:33 BTRFS: could not find root 8 Imran Geriskovan
2015-11-27 20:43 ` Hugo Mills
2015-11-27 22:51   ` Chris Murphy
2015-11-28  7:33     ` Duncan
2015-11-28  9:40     ` Imran Geriskovan
2015-11-28 18:24       ` Chris Murphy
2015-11-28 19:26       ` Chris Murphy
2015-11-28 21:09         ` Imran Geriskovan
2015-11-29 14:07     ` Goffredo Baroncelli [this message]
2015-11-30  2:16       ` Qu Wenruo
  -- strict thread matches above, loose matches on Subject: below --
2015-12-24  9:04 Swâmi Petaramesh
2015-12-24 10:29 ` Hugo Mills
2015-12-24 11:00   ` Swâmi Petaramesh

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=565B06AF.9020806@inwind.it \
    --to=kreijack@inwind.it \
    --cc=hugo@carfax.org.uk \
    --cc=imran.geriskovan@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@colorremedies.com \
    /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