From: Rutger Helling <rhelling@mykolab.com>
To: 29674@debbugs.gnu.org
Subject: bug#29674: Ceph creates Btrfs subvolumes on Btrfs during tests.
Date: Wed, 27 Dec 2017 23:50:39 +0100 [thread overview]
Message-ID: <20171227235039.4c0006fa@mykolab.com> (raw)
In-Reply-To: <87bmj3its4.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 794 bytes --]
This bug has been open for quite a while now.
If there are no objections in the next few days, I'd like to disable the
tests entirely for now with a FIXME on finding and disabling only the
offending tests.
On Tue, 12 Dec 2017 21:19:07 +0100
ludo@gnu.org (Ludovic Courtès) wrote:
> Tobias Geerinckx-Rice <me@tobias.gr> skribis:
>
> > Ludovic Courtès wrote on 12/12/17 at 17:03:
> >> So does guix-daemon systematically leave /tmp/guix-build-ceph*
> >> behind it?
> >
> > Almost certainly. I can confirm several hundred previously unknown
> > subvolumes filling up my btrfs substitute server. Time to clean
> > up.
>
> Ouch. I find this Btrfs behavior highly questionable.
>
> Let’s make sure our packages don’t leak Btrfs subvolumes then!
>
> Ludo’.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2017-12-27 22:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 10:28 bug#29674: Ceph creates Btrfs subvolumes on Btrfs during tests Rutger Helling
2017-12-12 12:52 ` Ludovic Courtès
2017-12-12 13:10 ` Rutger Helling
2017-12-12 13:23 ` Rutger Helling
2017-12-12 16:03 ` Ludovic Courtès
2017-12-12 16:13 ` Tobias Geerinckx-Rice
2017-12-12 20:19 ` Ludovic Courtès
2017-12-13 8:44 ` Rutger Helling
2017-12-27 22:50 ` Rutger Helling [this message]
2017-12-27 23:07 ` Leo Famulari
2017-12-27 23:16 ` Tobias Geerinckx-Rice
2017-12-28 4:30 ` Tobias Geerinckx-Rice
2017-12-28 7:31 ` Rutger Helling
2018-01-08 14:29 ` Ludovic Courtès
2018-01-08 15:38 ` Rutger Helling
2017-12-28 0:04 ` Marius Bakke
2017-12-12 15:58 ` Marius Bakke
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171227235039.4c0006fa@mykolab.com \
--to=rhelling@mykolab.com \
--cc=29674@debbugs.gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).