From: markmcb <markmcb@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] LXC/LXD on btrfs is broken for 6.2 kernel. Upstream lxd 5.11 fixes.
Date: Mon, 13 Mar 2023 21:54:43 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42748@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1219 bytes --]
New issue by markmcb on void-packages repository
https://github.com/void-linux/void-packages/issues/42748
Description:
### Is this a new report?
Yes
### System Info
Void 6.2.2_1 x86_64 GenuineIntel uptodate rFFFF
### Package(s) Affected
lxd-5.9_2
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
https://github.com/lxc/lxd/pull/11333
### Expected behaviour
lxc launch images:archlinux testcreate-arch
... this should create a new Arch Linux container. (OS is irrelevant.)
### Actual behaviour
lxc launch images:archlinux testcreate-arch
Creating testcreate-arch
Error: Failed instance creation: Failed creating instance from image: Failed to run: btrfs qgroup create
0/1868 /var/lib/lxd/storage-pools/default/images/c49a37117b5443dad3226d43b224dae38ff9ccb1694c753d66f377
8e34ff8ec6: exit status 1 (ERROR: unable to create quota group: File exists)
### Steps to reproduce
1. Install lxd/lxc on a few months old Void
2. Update to 6.2 kernel (with btrfs-progs changes)
3. Try to create a new container
next reply other threads:[~2023-03-13 20:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 20:54 markmcb [this message]
2023-03-13 20:55 ` classabbyamp
2023-03-20 4:49 ` markmcb
2023-03-20 16:00 ` CameronNemo
2024-06-14 6:31 ` [ISSUE] [CLOSED] " classabbyamp
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42748@inbox.vuxu.org \
--to=markmcb@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).