| To: | Amir Goldstein <amir73il@xxxxxxxxx> |
|---|---|
| Subject: | Re: Any better way to interact with xfs? |
| From: | Dave Chinner <david@xxxxxxxxxxxxx> |
| Date: | Fri, 29 Jul 2016 12:25:52 +1000 |
| Cc: | Ryan Lindsay <rlindsay@xxxxxxxxxxxxxx>, "xfs@xxxxxxxxxxx" <xfs@xxxxxxxxxxx> |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <CAOQ4uxiOavjc+wrRQHW8U16EDocNRRGnM24a7d6dhO8tzV0a1w@xxxxxxxxxxxxxx> |
| References: | <SYXPR01MB044863A851C967C37649BE3FF8000@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <CAOQ4uxiOavjc+wrRQHW8U16EDocNRRGnM24a7d6dhO8tzV0a1w@xxxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
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@xxxxxxxxxxxxx |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Subtle races between DAX mmap fault and write path, Dave Chinner |
|---|---|
| Next by Date: | Re: Any better way to interact with xfs?, Dave Chinner |
| Previous by Thread: | Re: Any better way to interact with xfs?, Amir Goldstein |
| Next by Thread: | Re: Any better way to interact with xfs?, Amir Goldstein |
| Indexes: | [Date] [Thread] [Top] [All Lists] |