linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: linux-btrfs@vger.kernel.org
Subject: btrfs fi df returns nothing
Date: Wed, 09 Mar 2011 06:20:28 -0500	[thread overview]
Message-ID: <il7npu$5lh$1@dough.gmane.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1000 bytes --]

I am using btrfs on Ubuntu's LTS kernel (2.6.32-22-generic) and have
updated the btrfs-tools to 0.19+20101101-1~lucid1.  I have also built
the latest from
git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-progs-unstable.git.

The problem is that I don't get anything from btrfs fi df $mountpoint.
i.e., for the btrfs filesystem mounted at /mnt/btrfs-test/

# ./btrfs fi df /mnt/btrfs-test/
#

See, no output.  Is my kernel module too old for that feature?  Maybe it is:

stat64("/mnt/btrfs-test/", {st_mode=S_IFDIR|0755, st_size=72, ...}) = 0
open("/mnt/btrfs-test/",
O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY|O_CLOEXEC) = 3
fcntl64(3, F_GETFD)                     = 0x1 (flags FD_CLOEXEC)
ioctl(3, 0xc0109414, 0x999c320)         = -1 ENOTTY (Inappropriate ioctl
for device)
exit_group(-1)                          = ?

If my kernel module is too old, anyone know of a successful backport of
a newer btrfs for Ubuntu Lucid?  In a PPA or otherwise?

Cheers,
b.



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

             reply	other threads:[~2011-03-09 11:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-09 11:20 Brian J. Murrell [this message]
2011-03-09 11:47 ` btrfs fi df returns nothing Hubert Kario
2011-03-09 11:47 ` Hugo Mills
2011-03-09 12:20   ` Brian J. Murrell
2011-03-09 12:22     ` Hugo Mills
2011-03-13  7:24   ` Chris Samuel

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='il7npu$5lh$1@dough.gmane.org' \
    --to=brian@interlinx.bc.ca \
    --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;
as well as URLs for NNTP newsgroup(s).