From mboxrd@z Thu Jan 1 00:00:00 1970 From: Linda Knippers Subject: Re: btrfsctl -A not returning useful information Date: Fri, 18 Jul 2008 15:10:15 -0400 Message-ID: <4880EA97.4070101@hp.com> References: <3da3b5b40807181028p42e1a15di938dc62cccbc766c@mail.gmail.com> <4880D7D6.8040006@hp.com> <3da3b5b40807181125x4a544ca1u159aa631c675401c@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Cc: linux-btrfs@vger.kernel.org To: Ahmed Kamal Return-path: In-Reply-To: <3da3b5b40807181125x4a544ca1u159aa631c675401c@mail.gmail.com> List-ID: 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 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 >>