From: Chris Mason <chris.mason@oracle.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 16:33:07 -0400 [thread overview]
Message-ID: <1216413187.6932.73.camel@think.oraclecorp.com> (raw)
In-Reply-To: <3da3b5b40807181028p42e1a15di938dc62cccbc766c@mail.gmail.com>
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
prev parent reply other threads:[~2008-07-18 20:33 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
2008-07-18 20:33 ` Chris Mason [this message]
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=1216413187.6932.73.camel@think.oraclecorp.com \
--to=chris.mason@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox