From: C Anthony Risinger <anthony@extof.me>
To: linux-btrfs@vger.kernel.org
Subject: list subvolumes with new btrfs command
Date: Sun, 25 Apr 2010 13:27:43 -0500 [thread overview]
Message-ID: <g2kbe6460751004251127tbdf980b6q867cf1b98fc562dc@mail.gmail.com> (raw)
hello,
i maintain an unofficial initrd hook in Arch Linux that allows BTRFS
to be used as the root device. i am trying to update the hook to use
the more extensive "btrfs" command, adding support for users to change
their default subvolume from within the initrd (i'm creating a sort of
rollback feature, in conjunction with automatic snapshotting via the
package manager), and adding support for hot spares (via a second
BTRFS pool in which devices are "stolen" to repair the primary array).
anyways, i'm having trouble getting a listing of subvolumes:
$ btrfs subvolume list /
ERROR: can't perform the search
the machine has a BTRFS root. i have also tried creating a snapshot
and pointing the command at that, but i get the same results. am i
using the command wrong? relevant code is from btrfs-list.c:
ret = ioctl(fd, BTRFS_IOC_TREE_SEARCH, &args);
if (ret < 0) {
fprintf(stderr, "ERROR: can't perform the search\n");
return 0;
}
kernel:
$ uname -r
2.6.33-ARCH
is there a new CONFIG_* kernel parameter that needs to be set since
2.6.32? everything seems to be in order and working fine... any help
appreciated.
thanks,
C Anthony
next reply other threads:[~2010-04-25 18:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-25 18:27 C Anthony Risinger [this message]
2010-04-26 2:09 ` list subvolumes with new btrfs command sniper
2010-04-26 2:47 ` C Anthony Risinger
2010-04-26 3:22 ` sniper
2010-04-26 17:23 ` C Anthony Risinger
2010-04-26 17:58 ` Hubert Kario
2010-04-26 19:10 ` C Anthony Risinger
2010-04-26 20:51 ` C Anthony Risinger
2010-04-26 22:14 ` C Anthony Risinger
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=g2kbe6460751004251127tbdf980b6q867cf1b98fc562dc@mail.gmail.com \
--to=anthony@extof.me \
--cc=linux-btrfs@vger.kernel.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).