From: Eric Sandeen <sandeen@sandeen.net>
To: xfs@oss.sgi.com
Subject: Re: development APIs for used/free blocks information
Date: Tue, 26 Apr 2016 16:33:37 -0500 [thread overview]
Message-ID: <571FDEB1.90701@sandeen.net> (raw)
In-Reply-To: <97A4F433DEE099488FE21C1718A641D2139E86F5@wmsexchsvr01.winmagic.local>
On 4/26/16 3:51 PM, 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. I have done the same
> task for EXT filesystem which seemed fairly easy as it provided
> simple open/query/close APIs. I know that XFS is a bit different as
> it manages free extents in two B+ trees per AG, but is this free/used
> block/extent information externalized somehow for developers to use?
> Am I not looking in the right place or these functionalities are
> simply not provided to application developers?
>
> Any help/pointers would be greatly appreciated.
It's not exported for application developers, no; it's not
generally something applications need, AFAIK.
You could look at how the freesp_f function works in xfs_db, I suppose.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2016-04-26 21:33 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 [this message]
2016-04-26 22:21 ` Dave Chinner
2016-04-26 22:51 ` Eric Sandeen
2016-04-26 23:09 ` Dave Chinner
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=571FDEB1.90701@sandeen.net \
--to=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