linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* btrfs fi df returns nothing
@ 2011-03-09 11:20 Brian J. Murrell
  2011-03-09 11:47 ` Hubert Kario
  2011-03-09 11:47 ` Hugo Mills
  0 siblings, 2 replies; 6+ messages in thread
From: Brian J. Murrell @ 2011-03-09 11:20 UTC (permalink / raw)
  To: linux-btrfs

[-- 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 --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2011-03-13  7:24 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-03-09 11:20 btrfs fi df returns nothing Brian J. Murrell
2011-03-09 11:47 ` 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

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).