From: C Anthony Risinger <anthony@extof.me>
To: Hubert Kario <hka@qbs.com.pl>
Cc: sniper <s3c24xx@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: list subvolumes with new btrfs command
Date: Mon, 26 Apr 2010 14:10:04 -0500 [thread overview]
Message-ID: <r2sbe6460751004261210m1c098d37ia4c424059a4e1c34@mail.gmail.com> (raw)
In-Reply-To: <201004261958.56440.hka@qbs.com.pl>
On Mon, Apr 26, 2010 at 12:58 PM, Hubert Kario <hka@qbs.com.pl> wrote:
> On Monday 26 April 2010 19:23:21 C Anthony Risinger wrote:
>> > I am using ubuntu-10.04-rc with kernel compiled from the almost
>> > lastest source , the btrfs-progs is latest too.
>> >
>> > You can modify line
>> >
>> > =A0fprintf(stderr, "ERROR: can't perform the search\n");
>> > to
>> > =A0fprintf(stderr, "ERROR: can't perform the search: %s\n",
>> > strerror(errno));
>> >
>> > to see what happened on earth.
>>
>> nice:
>>
>> $ sudo btrfs subvolume list /
>> ERROR: can't perform the search: Inappropriate ioctl for device
>>
>> i'm not really familiar with C, or anything this low level, does thi=
s
>> help you diagnose my problem?
>
> Have you tried to run it on the device with the btrfs, not the mount =
point?
>
> It looks like the ioctl was made too restrictive about its arguments.
ah yes i missed mentioning that to, tried that:
$ sudo btrfs sub list /dev/sda2
ERROR: '/dev/sda2' is not a subvolume
no dice :(
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-04-26 19:10 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
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 [this message]
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=r2sbe6460751004261210m1c098d37ia4c424059a4e1c34@mail.gmail.com \
--to=anthony@extof.me \
--cc=hka@qbs.com.pl \
--cc=linux-btrfs@vger.kernel.org \
--cc=s3c24xx@gmail.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;
as well as URLs for NNTP newsgroup(s).