From: Dave Chinner <david@fromorbit.com>
To: Benjamin Wirth <Benjamin.Wirth@winmagic.com>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: development APIs for used/free blocks information
Date: Thu, 28 Apr 2016 09:41:08 +1000 [thread overview]
Message-ID: <20160427234108.GK26977@dastard> (raw)
In-Reply-To: <97A4F433DEE099488FE21C1718A641D2139E972E@wmsexchsvr01.winmagic.local>
On Wed, Apr 27, 2016 at 12:54:24PM +0000, Benjamin Wirth wrote:
> Hello Dave,
>
> Thanks for your response.
>
> And I apologize, reading back my email I wasn't clear about what I
> was looking for.
>
> I want to be able to query which blocks are free or used, not just
> the counts. In EXT I was able to use ext2fs_test_block_bitmap()
> for that. XFS has a BTree with the free extents ordered by block
> number which I was hoping to be able to access from user-space,
> but couldn't find any APIs for it (or the headers containing the
> structure definitions) in the xfsprogs-devel package. Am I trying
> to do something impossible here?
There are prototypes that need a bit of polishing to complete:
http://oss.sgi.com/archives/xfs/2016-04/msg00633.html
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-27 23:41 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
2016-04-27 12:54 ` Benjamin Wirth
2016-04-27 23:41 ` Dave Chinner [this message]
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=20160427234108.GK26977@dastard \
--to=david@fromorbit.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox