From: Linda Knippers <linda.knippers@hp.com>
To: Ahmed Kamal <email.ahmedkamal@googlemail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfsctl -A not returning useful information
Date: Fri, 18 Jul 2008 15:10:15 -0400 [thread overview]
Message-ID: <4880EA97.4070101@hp.com> (raw)
In-Reply-To: <3da3b5b40807181125x4a544ca1u159aa631c675401c@mail.gmail.com>
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
>>
next prev parent reply other threads:[~2008-07-18 19:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2008-07-18 20:33 ` Chris Mason
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=4880EA97.4070101@hp.com \
--to=linda.knippers@hp.com \
--cc=email.ahmedkamal@googlemail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.