From: Dave Chinner <david@fromorbit.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: xfs@oss.sgi.com
Subject: Re: development APIs for used/free blocks information
Date: Wed, 27 Apr 2016 09:09:25 +1000 [thread overview]
Message-ID: <20160426230925.GH26977@dastard> (raw)
In-Reply-To: <571FF0F6.2030202@sandeen.net>
On Tue, Apr 26, 2016 at 05:51:34PM -0500, Eric Sandeen wrote:
>
>
> On 4/26/16 5:21 PM, Dave Chinner wrote:
> > On Tue, Apr 26, 2016 at 08:51:10PM +0000, Benjamin Wirth wrote:
> >> Hello,
> >>
> >> I was looking for development APIs for XFS. The contents of
> >> xfsprogs-devel seem to only contain a few IOCTL commands, mostly
> >> file/inode based operations.
> >>
> >> I need to query free/used blocks of an entire XFS filesystem and
> >> was hoping to find some user-space APIs for this.
> >
> > $ man 2 statvfs
>
> I was assuming that he was interested in the actual used/free block
> locations, not just the total count. But maybe I was wrong!
Maybe I'm wrong, but asking for free/used blocks is ambiguous to say
the least. If he wants free/used blocks, then we just need to
forward port this kernel branch:
https://git.kernel.org/cgit/linux/kernel/git/dgc/linux-xfs.git/log/?h=fiemapfs
And this xfsprogs branch:
https://git.kernel.org/cgit/fs/xfs/xfsprogs-dev.git/log/?h=spaceman
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2016-04-26 23:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 20:51 development APIs for used/free blocks information Benjamin Wirth
2016-04-26 21:33 ` Eric Sandeen
2016-04-26 22:21 ` Dave Chinner
2016-04-26 22:51 ` Eric Sandeen
2016-04-26 23:09 ` Dave Chinner [this message]
2016-04-27 12:54 ` Benjamin Wirth
2016-04-27 23:41 ` Dave Chinner
2016-06-16 19:57 ` Benjamin Wirth
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=20160426230925.GH26977@dastard \
--to=david@fromorbit.com \
--cc=sandeen@sandeen.net \
--cc=xfs@oss.sgi.com \
/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