linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: C Anthony Risinger <anthony@extof.me>
To: linux-btrfs@vger.kernel.org
Subject: Re: list subvolumes with new btrfs command
Date: Sun, 25 Apr 2010 21:47:31 -0500	[thread overview]
Message-ID: <z2tbe6460751004251947ve533479ax174cc4f8bff50c01@mail.gmail.com> (raw)
In-Reply-To: <q2j9bd6b5361004251909j8dcf6ccbzd978d627e137fadb@mail.gmail.com>

> need super root? in my ubuntu10.04 with latest btrfs-progs:
>
> $ ./btrfs subvolume list /media/sda3-100g/
> ERROR: can't perform the search
> $ sudo ./btrfs subvolume list /media/sda3-100g/
> ID 258 top level 5 path misc/snap/snap-4-26

ah sorry, i forgot to mention that it doesn't work as super user
either, same result:

$ sudo btrfs subvolume list /
ERROR: can't perform the search

the btrfs-progs in ubuntu is probably slightly behind git HEAD (what
i'm using in Arch package), maybe it broke recently, i might try to
bisect and see it i can pinpoint to problem commit.  i am also using
kernel 2.6.33 (ubuntu is .32 i think) that's why i thought maybe there
was an issue there; it seems like the ioctl() call is failing no
matter what in my case.

other details i can think of:
1) filesystem was created by a 2.6.31 kernel

i will use loopback + BTRFS to test what is happening here and report
back; maybe i can't scan / ...?  thanks for the response, any other
input is very much appreciated.

thanks,
C Anthony

  reply	other threads:[~2010-04-26  2:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-25 18:27 list subvolumes with new btrfs command C Anthony Risinger
2010-04-26  2:09 ` sniper
2010-04-26  2:47   ` C Anthony Risinger [this message]
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=z2tbe6460751004251947ve533479ax174cc4f8bff50c01@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).