* btrfsctl -A not returning useful information
@ 2008-07-18 17:28 Ahmed Kamal
2008-07-18 17:50 ` Linda Knippers
2008-07-18 20:33 ` Chris Mason
0 siblings, 2 replies; 5+ messages in thread
From: Ahmed Kamal @ 2008-07-18 17:28 UTC (permalink / raw)
To: linux-btrfs
[root@btrfs progs-unstable]# btrfsctl -A /dev/sdb
ioctl returns 0
[root@btrfs progs-unstable]# btrfsctl -A /dev/sdc
ioctl returns 0
/dev/sdb has a btrfs, while /dev/sdc is blank. What's that output
supposed to mean ? Is it a bug ?
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: btrfsctl -A not returning useful information
2008-07-18 17:28 btrfsctl -A not returning useful information Ahmed Kamal
@ 2008-07-18 17:50 ` Linda Knippers
2008-07-18 18:25 ` Ahmed Kamal
2008-07-18 20:33 ` Chris Mason
1 sibling, 1 reply; 5+ messages in thread
From: Linda Knippers @ 2008-07-18 17:50 UTC (permalink / raw)
To: Ahmed Kamal; +Cc: linux-btrfs
Ahmed Kamal wrote:
> [root@btrfs progs-unstable]# btrfsctl -A /dev/sdb
> ioctl returns 0
> [root@btrfs progs-unstable]# btrfsctl -A /dev/sdc
> ioctl returns 0
>
>
> /dev/sdb has a btrfs, while /dev/sdc is blank. What's that output
> supposed to mean ? Is it a bug ?
I think not so much of a bug as not completely implemented.
If you look in /var/log/messages or where every your kernel
messages go, you'll see information about the file system on
the device. At least that's how it worked for me.
-- ljk
> --
> 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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: btrfsctl -A not returning useful information
2008-07-18 17:50 ` Linda Knippers
@ 2008-07-18 18:25 ` Ahmed Kamal
2008-07-18 19:10 ` Linda Knippers
0 siblings, 1 reply; 5+ messages in thread
From: Ahmed Kamal @ 2008-07-18 18:25 UTC (permalink / raw)
To: Linda Knippers; +Cc: linux-btrfs
Thanks Linda, I located the kernel message. Is it normal such issues
are not tracked in the project's bugzilla:
http://oss.oracle.com/bugzilla/buglist.cgi?product=Btrfs
which only contains 5 bugs ?!
On Fri, Jul 18, 2008 at 8:50 PM, Linda Knippers <linda.knippers@hp.com> wrote:
> Ahmed Kamal wrote:
>>
>> [root@btrfs progs-unstable]# btrfsctl -A /dev/sdb
>> ioctl returns 0
>> [root@btrfs progs-unstable]# btrfsctl -A /dev/sdc
>> ioctl returns 0
>>
>>
>> /dev/sdb has a btrfs, while /dev/sdc is blank. What's that output
>> supposed to mean ? Is it a bug ?
>
> I think not so much of a bug as not completely implemented.
> If you look in /var/log/messages or where every your kernel
> messages go, you'll see information about the file system on
> the device. At least that's how it worked for me.
>
> -- ljk
>>
>> --
>> 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
>
>
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: btrfsctl -A not returning useful information
2008-07-18 18:25 ` Ahmed Kamal
@ 2008-07-18 19:10 ` Linda Knippers
0 siblings, 0 replies; 5+ messages in thread
From: Linda Knippers @ 2008-07-18 19:10 UTC (permalink / raw)
To: Ahmed Kamal; +Cc: linux-btrfs
Ahmed Kamal wrote:
> Thanks Linda, I located the kernel message. Is it normal such issues
> are not tracked in the project's bugzilla:
> http://oss.oracle.com/bugzilla/buglist.cgi?product=Btrfs
> which only contains 5 bugs ?!
I suppose it depends on whether its a bug with something that's
supposed to work or whether its a feature that's not quite
implemented yet. I think in this case, btrfsctl is providing
some basic capabilities to assist development and testing and
is quite likely to evolve, so to me this wasn't a bugzilla item.
Chris might have different advice though.
-- ljk
>
> On Fri, Jul 18, 2008 at 8:50 PM, Linda Knippers <linda.knippers@hp.com> wrote:
>> Ahmed Kamal wrote:
>>> [root@btrfs progs-unstable]# btrfsctl -A /dev/sdb
>>> ioctl returns 0
>>> [root@btrfs progs-unstable]# btrfsctl -A /dev/sdc
>>> ioctl returns 0
>>>
>>>
>>> /dev/sdb has a btrfs, while /dev/sdc is blank. What's that output
>>> supposed to mean ? Is it a bug ?
>> I think not so much of a bug as not completely implemented.
>> If you look in /var/log/messages or where every your kernel
>> messages go, you'll see information about the file system on
>> the device. At least that's how it worked for me.
>>
>> -- ljk
>>> --
>>> 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
>>
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: btrfsctl -A not returning useful information
2008-07-18 17:28 btrfsctl -A not returning useful information Ahmed Kamal
2008-07-18 17:50 ` Linda Knippers
@ 2008-07-18 20:33 ` Chris Mason
1 sibling, 0 replies; 5+ messages in thread
From: Chris Mason @ 2008-07-18 20:33 UTC (permalink / raw)
To: Ahmed Kamal; +Cc: linux-btrfs
On Fri, 2008-07-18 at 20:28 +0300, Ahmed Kamal wrote:
> [root@btrfs progs-unstable]# btrfsctl -A /dev/sdb
> ioctl returns 0
> [root@btrfs progs-unstable]# btrfsctl -A /dev/sdc
> ioctl returns 0
>
>
> /dev/sdb has a btrfs, while /dev/sdc is blank. What's that output
> supposed to mean ? Is it a bug ?
It isn't an error to scan a partition that doesn't have btrfs on it.
btrfsctl -A is just a single shot scan of a single device. It is meant
for use by programs like udev to scan storage.
It think what you want is btrfs-show.
-chris
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2008-07-18 20:33 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-07-18 17:28 btrfsctl -A not returning useful information Ahmed Kamal
2008-07-18 17:50 ` Linda Knippers
2008-07-18 18:25 ` Ahmed Kamal
2008-07-18 19:10 ` Linda Knippers
2008-07-18 20:33 ` Chris Mason
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox