From: Benjamin Wirth <Benjamin.Wirth@winmagic.com>
To: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: development APIs for used/free blocks information
Date: Tue, 26 Apr 2016 20:51:10 +0000 [thread overview]
Message-ID: <97A4F433DEE099488FE21C1718A641D2139E86F5@wmsexchsvr01.winmagic.local> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 874 bytes --]
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.
Regards,
Benjamin Wirth | Senior Software Developer
WinMagic Inc.
5600A Cancross Court
Mississauga, ON | L5R 3E9 | Canada
[-- Attachment #1.2: Type: text/html, Size: 3649 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2016-04-26 20:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 20:51 Benjamin Wirth [this message]
2016-04-26 21:33 ` development APIs for used/free blocks information Eric Sandeen
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=97A4F433DEE099488FE21C1718A641D2139E86F5@wmsexchsvr01.winmagic.local \
--to=benjamin.wirth@winmagic.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.