From: Dave Chinner <david@fromorbit.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Ryan Lindsay <rlindsay@unimelb.edu.au>,
"xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: Any better way to interact with xfs?
Date: Fri, 29 Jul 2016 12:25:52 +1000 [thread overview]
Message-ID: <20160729022552.GA16044@dastard> (raw)
In-Reply-To: <CAOQ4uxiOavjc+wrRQHW8U16EDocNRRGnM24a7d6dhO8tzV0a1w@mail.gmail.com>
On Thu, Jul 28, 2016 at 09:48:07AM +0300, Amir Goldstein wrote:
> Hi Ryan,
>
> You could use the XFS_IOC_FSINUMBERS/XFS_IOC_FSBULKSTAT API to iterate
> over all inodes in the fs.
That's a read-only API - you can't use it to change the inodes
on disk.
> not having to readdir and recourse the directory tree should safe you
> some time (much less i/o).
> Also, the interface can be used to make your conversion work parallel
> by working on different inode ranges.
It cannot be used to make coherent, atomic changes to the inode
state.
> You can use xfsdump/xfsrestore code as reference.
xfsdump uses bulkstat scan and read inodes, not change anything on
disk.
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-07-29 2:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-28 3:30 Any better way to interact with xfs? Ryan Lindsay
2016-07-28 3:48 ` Eric Sandeen
2016-07-28 6:48 ` Amir Goldstein
2016-07-29 2:25 ` Dave Chinner [this message]
2016-07-30 14:26 ` Amir Goldstein
2016-07-31 0:34 ` Dave Chinner
2016-07-31 6:12 ` Amir Goldstein
2016-07-31 23:08 ` Dave Chinner
2016-07-29 2:33 ` Dave Chinner
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=20160729022552.GA16044@dastard \
--to=david@fromorbit.com \
--cc=amir73il@gmail.com \
--cc=rlindsay@unimelb.edu.au \
--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